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 articleConsumer app startups ship weekly, watch downloads and handle angry reviews. HR work is hiring the first engineers and designers, keeping growth and support teams sane and building habits before the team doubles.

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 B2C app startup builds a product for the general public, such as a food, fitness, learning, finance or social app. The team usually includes mobile and backend engineers, a designer, a product manager, growth and marketing people, community or support staff, and the founders doing a bit of everything. Work follows release cycles, campaign launches and user numbers. Funding rounds change headcount plans, a bad release triggers late nights, and a one-star review wave lands on support. Roles are fuzzy, titles are loose, and early joiners carry much unwritten knowledge. HR problems tend to appear when the team goes from ten to fifty. 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 B2C app 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.
Weekly launches and quick fixes push engineers into late nights, and recovery time is not planned.
A campaign goal that was key in March is dropped in April, leaving marketers unsure what they are measured on.
Support staff read abuse and refund demands all day, with shifts that cover evenings and weekends.
The first engineers know the code and the shortcuts, and their exit leaves new hires lost.
Offers differ person to person, and later joiners discover they earn more than earlier ones.
People are told they will get shares, but the terms and timing are not in writing.
A raise brings fast hiring, a delay brings freezes, and employees feel the whiplash.
Habits like stand-ups and feedback exist only in founders' heads, and new joiners feel adrift.
Start with the topics that matter most here: Organisation Design; Compensation, Payroll and Benefits; Retention and Attrition Management. 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.
Salary structure, payroll inputs and a month that closes on time.
Who leaves, when, why — and which of them mattered.
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.
Goals, reviews and ratings that hold up in a conversation.
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 B2C app startups business puts in place, in an order that makes each easier. Open any card for the detail.
One page per role with what it owns and how it is judged.
One page per role with what it owns and how it is judged. This also feeds the performance management.
A simple band per level so offers are consistent and fair.
A simple band per level so offers are consistent and fair. See compensation benchmarking.
Whatever is promised should be stated clearly in the offer, with vesting and exit terms checked by your lawyer.
Whatever is promised should be stated clearly in the offer, with vesting and exit terms checked by your lawyer.
After a big release or incident, plan a lighter few days, and track who has been on call for how long.
After a big release or incident, plan a lighter few days, and track who has been on call for how long.
Rotation, breaks, escalation help and a debrief after rough days.
Rotation, breaks, escalation help and a debrief after rough days. The workplace health, safety and wellbeing page covers the basics.
Short architecture notes and handover sessions so no single person is a single point of failure.
Short architecture notes and handover sessions so no single person is a single point of failure.
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.
Hiring the first engineers and growth staff with clear scopes.
Pay bands so offers stay consistent as the team grows.
Goals that survive a changed campaign target.
Handovers when an early joiner leaves.
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 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 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
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.
Before the team crosses about twenty or after the first unfair-pay complaint, whichever comes first. A little structure early prevents harder fixes later.
Review goals monthly, write down changes, and judge people on goals that stood for the period they worked on.
Plan recovery after releases, rotate on-call duty and avoid treating every fix as an emergency.
Plainly, in writing, with vesting, cliffs and exit terms reviewed by a lawyer. Avoid verbal promises.
Document key systems, share knowledge across two people and keep a respectful, planned handover process.
We would look at role scopes, offer consistency and who holds unwritten knowledge. A pay band note and a role scope set are a sensible first job. After we talk it through, scope and deliverables are put in writing.
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.