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 cloud service company designs, moves and runs customers' workloads on large public clouds. Its engineers hold exams that the market values highly, so pay, projects and growth decide who stays.

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 cloud service company helps businesses move to, build on and run their systems on the large public clouds. Work comes as migration projects, build projects and ongoing managed operations. The team holds architects, cloud and DevOps engineers, security specialists, data engineers and project managers, many with provider certifications that rivals want. A project may need ten engineers for four months and none after, while operations need a steady core. Engineers see their market value grow with every exam and every tool, and offers arrive often. The firm must decide how to staff projects, pay for scarce skills and grow the next generation of lead architects. See the IT and software hub and the hub for infrastructure and managed services.
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.
Every new exam raises market value, and the company often pays for the exam that leads to the exit.
A large migration needs a full team at once, then people are idle or moved to work they do not like.
Hiring against rival offers creates gaps between old and new staff, and the old staff hear about it.
A few senior people review every design, so projects wait and the architects never get time to teach.
New services appear every month, and engineers study at night with no recognised time or plan.
A solution is sold that the delivery team has not built before, and the strain falls on the engineers.
Project engineers get the new work and the praise, while the people who keep systems running see little recognition.
Start with the topics that matter most here: Compensation, Payroll and Benefits; Career and Succession Management; Retention and Attrition Management. Then work through the rest. Each topic is written for information technology and software, not in general.
Salary structure, payroll inputs and a month that closes on time.
Named backups for the roles that cannot be vacant.
Who leaves, when, why — and which of them mattered.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
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.
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.
Induction, records, incident reporting and follow-through.
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 cloud service companies business puts in place, in an order that makes each easier. Open any card for the detail.
Ranges for cloud, DevOps, security and data roles, with a stated step for certified skills.
What this coversHideRanges for cloud, DevOps, security and data roles, with a stated step for certified skills. See pay benchmarks.
Decide how idle time between projects is used for training, internal tools or pre-sales support, and how it is credited.
What this coversHideDecide how idle time between projects is used for training, internal tools or pre-sales support, and how it is credited.
Name future architects, give them design tasks under a senior and write when each could take a review role.
What this coversHideName future architects, give them design tasks under a senior and write when each could take a review role. The succession planning work helps.
A fixed number of hours each month, linked to the certifications and services the company needs.
What this coversHideA fixed number of hours each month, linked to the certifications and services the company needs.
A short check by an engineering lead before a new solution is promised, with a record of the concerns raised.
What this coversHideA short check by an engineering lead before a new solution is promised, with a record of the concerns raised.
A structured induction on tooling, accounts, security practice and the firm's way of working.
What this coversHideA structured induction on tooling, accounts, security practice and the firm's way of working. The onboarding process can carry it.
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.
Bands for cloud, DevOps, security and data roles with a clear step for verified skills.
A named pipeline for lead architects and engagement managers before one leaves.
A first month that gets new engineers productive on client accounts safely.
Training for technical leads who move from building to managing teams and projects.
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
How to design incentives for operators, setters and inspectors in fastener, gear, spring and valve units so that accepted lots, not piece counts, earn the bonus.
7 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
How to spot an unmanageable workload before it becomes an exit or an error, what to look at, how to talk about it and what to change, without guessing.
5 min readRead articleMore on the GullyHR blog.
A step in pay or a one-time recognition can work, but tie it to use at work. A bonus for every exam rewards collecting rather than delivery. Review the list of valued certifications yearly.
Plan the project team early, borrow from operations by agreement, add trained contractors only where skills are missing and keep a small core. Be open with engineers about when peaks and quiet periods occur.
Share review duties with a second architect, write design standards and let strong senior engineers approve routine designs. Give architects time for teaching, and measure them partly on how many others they grow.
Give them clear career steps, a share in project reviews, recognition for uptime and the chance to rotate into projects. A visible ladder and pay that reflects skill signal that operations matter.
Tools and accounts, security rules, one supervised task, shadowing a project and a review at thirty days. Pair with a buddy. Productive work on real accounts should begin with guardrails, not on day one without cover.
We would list engineers with pay and certifications side by side, ask who could replace your lead architect and look at how projects are staffed. A pay band with a bench policy 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.