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 articleAn IT support firm sells engineers' time to client offices. Helpdesk shifts, site visits and on-call cover must be filled every day, and the engineer in front of the client is how the firm is judged.

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 requirementsAn IT support firm looks after the computers, networks, printers and software of other businesses, usually under an annual support contract. The team has helpdesk staff who take calls and tickets, field engineers who visit offices, and a few engineers placed full time at a client site. A contract promises response times, so someone must be available on every working day, and often at night or on weekends. Engineers move between customers, carry their own tools and are trained on a mix of brands. Certifications matter for some contracts and for pay. The firm earns when engineers are busy and clients are satisfied. 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.
Leave, sickness and urgent client calls reshuffle the day, and the coordinator solves it by phone with no fixed rule.
An engineer placed at a client office is far from colleagues, taught little and reviewed by someone who never visits.
The same few engineers pick up night calls because they live close or never refuse, and they tire first.
The firm pays for an exam, the engineer leaves for a better offer and both sides feel cheated.
Travel, night and site allowances are claimed from memory and disputed when they differ from what the engineer expected.
The client likes one person and asks that they never be moved, which makes cover hard and the engineer hard to promote.
With no step between engineer and service manager, ambitious people leave for roles with a clearer path.
Start with the topics that matter most here: HR Operations and Governance; Learning and Development; Compensation, Payroll and Benefits. Then work through the rest. Each topic is written for information technology and software, not in general.
An HR function that runs the same way every month.
Training planned from need rather than from the calendar.
Salary structure, payroll inputs and a month that closes on time.
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.
Named backups for the roles that cannot be vacant.
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.
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.
The pieces a IT support firms business puts in place, in an order that makes each easier. Open any card for the detail.
Shifts, weekly offs, cover for leave and a fair on-call rota published two weeks ahead.
What this coversHideShifts, weekly offs, cover for leave and a fair on-call rota published two weeks ahead. See the shift and leave process.
A named lead who visits, a monthly call with peers and a training slot, so site staff stay part of the firm.
What this coversHideA named lead who visits, a monthly call with peers and a training slot, so site staff stay part of the firm.
Everyone fit for night work takes a turn, with rest after a late call and a rate that is known in advance.
What this coversHideEveryone fit for night work takes a turn, with rest after a late call and a rate that is known in advance.
What the firm pays for, what the engineer commits to and what happens on leaving, written once.
What this coversHideWhat the firm pays for, what the engineer commits to and what happens on leaving, written once. The learning and development process helps plan this.
Travel, night, site and standby payments with when each applies, so claims are checked against a rule.
What this coversHideTravel, night, site and standby payments with when each applies, so claims are checked against a rule.
Steps from junior to senior to service lead, with a technical path as well as a managing one.
What this coversHideSteps from junior to senior to service lead, with a technical path as well as a managing one.
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 roster, on-call turn and leave system that stops daily scrambling.
A certification plan with clear commitments for engineers and the firm.
Allowances and skill pay set out in one clear table for helpdesk, field and resident roles.
A hiring route for engineers who can work alone at a client site and talk to non-technical users.
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
Every growing company reaches a point where the founder approving everything stops being speed and starts being the bottleneck. Twelve signs it has happened, and what to fix first.
9 min readRead article
Plastics training dies when it waits for a free Saturday. Tie it to mould changes, purges and cold starts, use one-point lessons and a visible skill ladder, and protect it in peak months.
7 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 articleMore on the GullyHR blog.
Publish a rota two weeks ahead, give rest after a late call, rotate through everyone fit for it and state the payment beforehand. Fairness matters as much as the rate. Allow swaps through the lead.
Some firms do, but bonds can sour relations and can be hard to enforce. Ask a qualified professional about the form. Many firms prefer a shared-cost arrangement with a clear stay period and a fair repayment rule.
Give them a named lead, a monthly call with peers, a training slot and a visit from the office. Treat them as part of the firm, not as clients' staff, and review their work against clear goals.
Hands-on fault finding, clear explanation to a non-technical user, punctuality habits and honesty about what they do not know. A short practical task and a role-play call tell more than a certificate.
Explain the cover and quality reasons in the contract talk, introduce a second engineer early and give the favourite engineer credit and a step up. Dependence on one person is a risk for the client too.
We would look at how your roster is built each morning, who carries the night calls and what happened to engineers whose certifications you paid for. A published roster and on-call rule with an allowance table 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.