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 machine learning company builds models and systems that learn from data. Here is how to manage data scientists, ML engineers and annotators where research is uncertain, compute is costly and good people are very scarce.

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 machine learning company builds models that predict, classify, recommend or generate. Teams include data scientists who experiment, ML engineers who put models into production, data engineers, annotators who label data, product managers and researchers. Progress is uncertain. An experiment may take weeks and fail, which is hard to explain to clients and investors. Compute is costly, so teams fight for it. Good data scientists are few and often have strong opinions about method. Annotators do repetitive work, and their quality decides the model, yet they are often paid and treated as the lowest tier. Ethical questions about data, bias and use arise, and staff want to be heard. See also HR for IT and software.
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 machine learning companies. 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.
Teams hide negative results to avoid blame, which wastes time and hides what was learned.
Researchers want to explore, engineers want to ship, and ownership of the model blurs.
Labelling is repetitive, pay is low, and quality problems are blamed on them rather than the instructions.
Teams compete for training time, and ranking by seniority breeds resentment.
Strong data scientists are approached weekly, and counter-offers are expensive.
Staff worry about bias or misuse of data, and have no clear place to say so.
Business buyers expect fixed results from work that is statistical, and the team absorbs the gap.
Deployed models drift, and someone must watch them, but that duty is rarely planned.
Start with the topics that matter most here: Performance Management; Retention and Attrition Management; Organisation Design. Then work through the rest. Each topic is written for information technology and software, not in general.
Goals, reviews and ratings that hold up in a conversation.
Who leaves, when, why — and which of them mattered.
Structure, reporting lines and who is allowed to decide what.
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.
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 machine learning companies business puts in place, in an order that makes each easier. Open any card for the detail.
Clear lines for who owns experimentation and who owns production, with a hand-off.
Clear lines for who owns experimentation and who owns production, with a hand-off. Compensation benchmarking helps place pay for scarce skills.
Review experiments openly, record what was learned and treat a clear failure as useful.
Review experiments openly, record what was learned and treat a clear failure as useful. Use the performance management process.
Training, quality feedback and a route to reviewer or data operations roles, with decent pay and working hours.
Training, quality feedback and a route to reviewer or data operations roles, with decent pay and working hours.
A simple booking and priority system agreed by leaders, so access is not decided by rank.
A simple booking and priority system agreed by leaders, so access is not decided by rank.
A named person or group to receive concerns about bias or data use, with a way to record outcomes.
A named person or group to receive concerns about bias or data use, with a way to record outcomes. Confirm legal duties with a qualified professional.
A rota or owner for monitoring deployed models, with time set aside in plans.
A rota or owner for monitoring deployed models, with time set aside in plans.
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.
Evidence on what scarce ML skills earn, so offers and counter-offers are measured.
Goals suited to uncertain work, rewarding learning and sound method as well as results.
A trusted route for concerns, including ethical ones, raised by staff.
Time for papers, courses and tools, with growth paths for annotators and engineers.
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 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 article
A founder's guide to building job grades, titles and billing levels for a growing IT services firm, with a step-by-step method and a grade description outline.
6 min readRead articleMore on the GullyHR blog.
Look at method quality, learning from experiments, collaboration and impact, not just model scores. Uncertain work needs goals that allow for honest failure.
Define who owns each stage, pair them on projects and set shared goals around a model that works in production. Include both in planning.
As skilled contributors whose quality decides the model. Offer training, feedback, fair pay and a way to move up. Review the instructions they follow before blaming their output.
Use a visible booking system with priority rules tied to project goals. Leaders should review it often so it does not drift into favouritism.
Name a person or small panel, tell everyone about it and keep records of what was done. Protect the person who raises a concern from retaliation.
We would ask about experiment reviews, annotator careers, compute fairness and ethics routes. A sensible first project is a role split between research and engineering with an annotator ladder. Scope goes into writing before you decide.
All 61 business types in information technology and software · 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.