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 early consumer startup grows faster than its structure. Roles blur, hiring is rushed, and the founder still makes most people calls from memory while customers and investors both press.

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 platform, app or direct-to-consumer startup sells through its own website, app or marketplace to customers, often funded by investors who expect fast growth. Teams are small and mixed: engineers, designers, growth and performance marketers, operations and customer support, with a founder at the centre. Hiring happens in bursts after each funding round, and many first hires join for equity and learning more than pay. Roles are fluid, titles are loose, and pay for the same work may differ. Warehouse, delivery and customer-support staff may sit outside the core team and work shifts. A product launch or sale day can strain everybody. The founder's habits become the company's habits. See 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 platform, app and D2C 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.
After a funding round, people are hired quickly on a handshake, with unclear role scope and pay.
Two people doing the same job earn different amounts and hold different titles, and the gap becomes known.
A candidate hears a share offer in a call, and later nobody remembers the number or the terms.
People come to the founder for every leave, raise and complaint, and decisions depend on mood and memory.
Sale days, launch deadlines and growth targets keep people working late for weeks.
Warehouse and support staff work shifts under different rules and feel apart from the app team.
Employees who joined for equity and see no clear value in it, or lack growth, move to the next startup.
Offers, probation outcomes and changes in role sit in chat threads, and a dispute has nothing to rest on.
Start with the topics that matter most here: Recruitment and Talent Acquisition; Compensation, Payroll and Benefits; Organisation Design. Then work through the rest. Each topic is written for information technology and software, not in general.
Requisition to joining, the same way every time.
Salary structure, payroll inputs and a month that closes on time.
Structure, reporting lines and who is allowed to decide what.
How many people, in which roles, by when — and what they will cost.
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.
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.
An HR function that runs the same way every month.
The pieces a platform, app and D2C startups business puts in place, in an order that makes each easier. Open any card for the detail.
What each role does and a simple band for pay, applied to new hires.
What each role does and a simple band for pay, applied to new hires. The compensation benchmarking work can help.
A standard offer letter with pay, role, probation and any equity point noted for review.
A standard offer letter with pay, role, probation and any equity point noted for review. The HR documentation process helps.
A short screen, a task and a decision by two people.
A short screen, a task and a decision by two people. See the recruitment process.
One short policy on leave, sale-day work and time back.
One short policy on leave, sale-day work and time back. The HR policy packages include a starting set.
Same recognition, communication and an escalation route as the app team.
Same recognition, communication and an escalation route as the app team. See employee engagement.
A conversation with every employee on role, growth and workload.
A conversation with every employee on role, growth and workload. The performance management process shapes 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.
Offer letters, role sheets and records that replace chat-thread agreements.
Pay bands that make fast hiring fairer and avoid hidden gaps.
A simple starting set of policies for a growing, fast-moving team.
A light, repeatable hiring process that keeps pace with growth.
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 a D2C founder can test a performance marketing hire on real work, ignore weak signals such as dashboard screenshots, and run a fair process.
7 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 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.
As soon as you have a handful of employees. A simple offer letter, role sheet and leave rule early prevents bigger problems later.
Create a band for each role and level and place new hires within it. Review existing pay once a year.
In a written note with the amount, vesting and conditions, reviewed by a qualified professional before it is shared.
Plan rosters in advance, rotate heavy duty and give time back afterwards. Burnout after sale days is a leading reason for exits.
Give them clear roles, a path up, regular communication and the same recognition as the app team.
We would ask who has a signed offer, how pay was set and what the founder still decides alone. A good first project is a role and pay sheet with offer templates. Scope is written for you to accept or change.
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.