Why software employees leave and how to understand why
Engineers and product staff leave for reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleAn AI product startup bets on a handful of engineers and researchers who are hard to find and easy to lose. Pay, equity, goals and growth are decided in a hurry, then questioned a year later.

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 AI product startup builds a product whose core is a model, a data pipeline or an agent, sold to businesses or consumers. The team is small. A few machine learning engineers, data engineers, product engineers and a founder or two carry most of the value, and one resignation can stall a release. The direction can change in a quarter when a new model arrives or a customer asks for something else. Offers are made against rival startups and large companies, with equity as the sweetener. Titles, pay and expectations get set one hire at a time and drift apart. The wider IT and software hub covers what all software firms share, and the SaaS and product companies hub places this type among its neighbours.
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.
GullyHR runs talent acquisition for permanent roles in AI product startups. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
Knowledge of training runs, data choices and evaluation sits in two or three heads. If one leaves, the rest cannot explain why the model behaves as it does.
Each hire is negotiated against a rival offer, so two engineers doing similar work can sit on very different pay, and they find out.
A pivot or a new model makes last quarter's targets pointless, yet people are still judged against them.
Founders say a grant in a call, and the paperwork and records follow late, which breeds doubt about what was agreed.
One side values papers and experiments, the other shipping dates, and appraisals favour whoever is louder.
Fresh graduates join, get little guidance and either learn fast alone or quietly burn out.
Senior and lead labels are handed out to hold a hire, then become hard to defend when the company grows.
Start with the topics that matter most here: Compensation, Payroll and Benefits; Performance 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.
Goals, reviews and ratings that hold up in a conversation.
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.
Training planned from need rather than from the calendar.
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.
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 AI product startups business puts in place, in an order that makes each easier. Open any card for the detail.
Machine learning, data, product engineering and applied roles each get a pay range and a clear step up.
Machine learning, data, product engineering and applied roles each get a pay range and a clear step up. See pay benchmarks.
One sheet per person showing what was offered, when, and the paper that backs it, held by someone besides the founder.
One sheet per person showing what was offered, when, and the paper that backs it, held by someone besides the founder.
Short goals reviewed monthly, with a simple way to retire one that a pivot has made pointless.
Short goals reviewed monthly, with a simple way to retire one that a pivot has made pointless. The performance process can carry this.
A short note per project on data, evaluation and open risks, so a leaver does not take the story with them.
A short note per project on data, evaluation and open risks, so a leaver does not take the story with them.
A buddy, a first project of the right size and a check at two weeks and six weeks.
A buddy, a first project of the right size and a check at two weeks and six weeks. The onboarding process sets it out.
A one-page ladder describing scope at each level, used for promotions and hiring alike.
A one-page ladder describing scope at each level, used for promotions and hiring alike.
Before changing anything, find out what is true today. Work through the checks using a recent operating period. The time needed depends on the records you hold; note missing evidence and use the findings to choose a priority.
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 hiring route for scarce engineers, with a practical task and an honest account of the company's direction.
Bands for machine learning, data and product roles set against what comparable teams pay.
Short goals and reviews that cope with a pivot instead of punishing it.
A look at who is likely to leave, why, and what a counter-offer would really cost.
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 reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
Simple variable pay structures for product and engineering teams: four options, why individual metrics backfire, a build plan and a one page outline to adapt.
6 min readRead article
A practical design for an IT services appraisal cycle: when to run it, how to rate fairly across projects, and how to explain hikes so they hold.
7 min readRead article
What really keeps mobile app and web developers in a small firm: stay conversations, growth paths, fair release rules and a risk sheet an owner can use this month.
6 min readRead articleMore on the GullyHR blog.
Be clear about the problem, the ownership and the learning on offer, and set pay inside a sensible band. Use a practical task over a puzzle quiz. Strong people choose scope over a small salary gap.
No. Bands should follow the role and level, not the person's negotiating skill. Machine learning, data and product engineers can sit in different ranges, with the same logic for stepping up inside each.
Use quarterly goals with a monthly check, and agree up front that a pivot can retire a goal without a penalty. Judge people on what they did with the information they had.
Note who was offered what, when, and under what conditions, and keep the signed paper beside it. Ask a qualified professional about the form. The aim is that nobody argues later about what was said.
Give them shared goals tied to a customer result, review them in the same meeting and recognise both papers and shipped work in appraisals. Shared outcomes cool most turf quarrels.
We would ask which two people you cannot afford to lose, list pay and titles side by side and check how equity promises are recorded. A role ladder with pay bands is a natural first job, with scope written down for your approval.
All 6 business types in SaaS & product companies · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.