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 HRTech startup builds software for the people function, so its own HR is watched by every customer. Here is how to run engineers, product staff, customer success and sales teams while practising what you sell.

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 HRTech startup builds products for recruitment, payroll, attendance, performance, engagement or learning, sold to companies and used by their HR teams and employees. Its staff include engineers, product managers, designers, data analysts, implementation consultants, customer success managers, support agents and sales staff who speak to HR heads and founders. Because the buyer is an HR professional, the startup's own people practices are noticed: how it hires, how it treats staff and whether its own team uses the product. Product teams work in short cycles, implementation teams meet clients' messy data, and customer success handles demands from many different employers. Funding rounds change hiring plans quickly, and fast growth often leaves roles unclear. Domain knowledge of HR is rare among engineers and sales staff. 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 HRTech 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.
Features are built without an understanding of how real HR teams work, and rework follows each customer complaint.
Executives promise features in meetings with HR heads, and engineering learns of them after the deal is signed.
They clean data, adjust workflows and handle demands from several clients at once, with long hours and no clear scope.
Each client wants something different, and the team has no rule on what to refuse or send to product.
Its attendance, leave and review processes are on spreadsheets, and customers who ask for a demo of the company's own HR are disappointed.
A round leads to many offers within weeks, onboarding is thin and role clarity is lost.
Staff handle payroll and personal details of customers' employees, but access rules and conduct expectations are informal.
Engineers and support teams carry release pressure and escalations, with weekend work becoming routine.
Start with the topics that matter most here: Onboarding and Probation; HR Technology and Automation; Learning and Development. Then work through the rest. Each topic is written for information technology and software, not in general.
A first day that is the same for the fifth joiner as the first.
Records that survive people, and approvals that do not queue.
Training planned from need rather than from the calendar.
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.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
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.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a HRTech startups business puts in place, in an order that makes each easier. Open any card for the detail.
Regular sessions with practising HR professionals, customer visits for engineers and a glossary of HR terms, using the learning and development process.
Regular sessions with practising HR professionals, customer visits for engineers and a glossary of HR terms, using the learning and development process.
A simple form where sales confirms any feature promise with product before including it in a proposal.
A simple form where sales confirms any feature promise with product before including it in a proposal.
A standard statement of what implementation includes, how extra requests are handled and who approves them.
A standard statement of what implementation includes, how extra requests are handled and who approves them.
Run your attendance, leave, performance and onboarding on your own system, and let staff give feedback.
Run your attendance, leave, performance and onboarding on your own system, and let staff give feedback. See the employee onboarding process for the structure.
A hiring plan tied to funding with role definitions and a standard first-month plan for every joiner.
A hiring plan tied to funding with role definitions and a standard first-month plan for every joiner.
Who may see customers' employee data, why and how it is logged.
Who may see customers' employee data, why and how it is logged. Confirm with a qualified professional the data protection duties that apply to you. HR documentation helps put it in writing.
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 first-month plan so rapid hiring does not leave new joiners lost.
Building HR domain knowledge inside product and engineering teams.
Policies on data access, conduct and leave that you can show to customers.
A review process that also tests your own product's fit.
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 first-week plan for bringing in an outside specialist: what access to give, how to protect client data, and the confidentiality steps to settle on day one.
7 min readRead article
A simple timesheet routine for IT services teams: a short form, daily entry, light approval and a month-end lock that finance can bill from.
6 min readRead article
A founder's guide to hiring freshers and running a first-year programme: campus or open drives, a screening round, a training plan by quarter, mentors and checkpoints.
6 min readRead articleMore on the GullyHR blog.
Arrange customer visits, sessions with practising HR professionals and a shared glossary. Seeing real users changes how features are built.
Use a short product check before any proposal contains a feature promise. It saves rework and relationships.
Write a standard scope, record extras and approve them. Without it, the team absorbs everything.
Yes, where it fits. It improves the product and gives customers a credible reference.
Hire in waves, define each role and give every joiner a standard first month. Fast hiring needs a repeatable start.
We would look at how your own HR runs, how promises reach product and how new joiners start. A sensible first piece of work is an onboarding plan and a data access policy. Scope follows in writing, so you can accept or trim it.
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.