Why software employees leave and how to understand why
Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleA managed service provider runs a customer's IT for a monthly fee, so service levels, not hours, are what it sells. Tiered engineers, night desks and account teams must stay steady for the contract to pay.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsA managed service provider takes over a customer's infrastructure, monitoring and support for a monthly fee set against service levels. The work is organised in tiers: level one engineers take alerts and tickets, level two fix deeper faults, level three and architects handle design and hard problems. A network operations desk often runs through the night, and client teams are assigned to accounts for months or years. Margin depends on how many customers a small team can serve well. Engineers learn client environments the hard way, so when one leaves, the knowledge goes too. See the IT and software hub and the infrastructure and managed services hub.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
Alerts and tickets are repetitive, the route to level two is vague and the best juniors leave within eighteen months.
Rotating night shifts tire engineers, and the cover rule depends on who volunteers.
Only one person knows a customer's odd setup, and the account suffers when they are off or gone.
A contract is signed, the start date is fixed and the delivery team is told afterwards.
Missed response times are blamed on the engineer, even when the roster was one person short.
Senior people who should design are on calls, and the junior ones see no one to learn from.
Promises made at renewal do not match what the team can deliver.
Start with the topics that matter most here: Organisation Design; Career and Succession Management; Health, Safety and Wellbeing. Then work through the rest. Each topic is written for information technology and software, not in general.
Structure, reporting lines and who is allowed to decide what.
Named backups for the roles that cannot be vacant.
Induction, records, incident reporting and follow-through.
How many people, in which roles, by when — and what they will cost.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Policies a manager can apply, and obligations with owners and dates.
Who leaves, when, why — and which of them mattered.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a managed service providers business puts in place, in an order that makes each easier. Open any card for the detail.
Describe what a level one, two and three engineer can do alone, and what shows readiness to step up.
What this coversHideDescribe what a level one, two and three engineer can do alone, and what shows readiness to step up. See role design.
Maximum consecutive nights, rest between rotations, a swap method and a known allowance, written once.
What this coversHideMaximum consecutive nights, rest between rotations, a swap method and a known allowance, written once.
A short note on each environment, owned by two engineers, so one absence does not stop the account.
What this coversHideA short note on each environment, owned by two engineers, so one absence does not stop the account.
Ask delivery and HR to check headcount and skills before a new contract's start date is agreed.
What this coversHideAsk delivery and HR to check headcount and skills before a new contract's start date is agreed.
A competency check for each tier using live scenarios, linked to the next step.
What this coversHideA competency check for each tier using live scenarios, linked to the next step. The competency work describes it.
Keep a fixed share of architects' week free from tickets, written in their goals.
What this coversHideKeep a fixed share of architects' week free from tickets, written in their goals.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
A written ladder for service desk, tiered engineers and architects with clear handovers.
Skill checks for each tier, linked to the next role and to pay.
Rest rules and wellbeing practice for people who run night desks and on-call duty.
Goals and incentives tied to service levels without punishing the desk for roster gaps.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.

Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead article
A two-hour exercise that names the roles you could not fill quickly, who could cover them, and what readiness would actually require.
7 min readRead article
A shift, weekly and monthly safety routine for rubber plants that names who checks platen guards, mill trip bars, autoclave doors, burst-test cages and slings, and who acts on near misses.
7 min readRead articleMore on the GullyHR blog.
Show a real path to level two, with defined skills and a date for assessment. Rotate them across customers and tasks so the work is not just alerts. Many leave because they cannot see what comes next.
Use a fixed rotation with a cap on consecutive nights, enough rest between rotations and a known allowance. Keep volunteers from becoming the permanent night staff. Check the legal rules with a qualified professional.
Name a primary and backup engineer for each account, keep a written note of the environment and schedule short handover sessions. Reward engineers who document and teach, not just those who fix.
Rarely. Keep their time for design and the hardest problems, with a small on-call slot if needed. If they are always firefighting, juniors lose their teacher and the company loses its design capacity.
Include a delivery manager in renewal talks, share what the team can promise and review each customer together monthly. Disagreement is reduced when both sides see the same service data.
We would count how many level one engineers moved up, list how many people know each customer and ask night-desk staff about consecutive nights. A tier ladder with competency checks is a natural first job, with scope written for your approval.
All 5 business types in IT infrastructure & managed services · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.