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 articleThese startups pair engineers with teachers, clinicians or finance people, in fields where mistakes hurt real users. People who build the product, advise on content and serve customers must work together on shared trust.

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 education, health or finance technology startup builds software for learners, patients or money users, and so needs two kinds of people. Engineers, designers and product staff build; domain experts such as teachers, doctors, nurses, accountants or credit analysts shape content, rules and safety. Alongside sit support and operations staff who deal with worried students, patients and account holders. Data is sensitive: marks, health records, bank and identity details. Customers place heavy trust in the product, and one wrong answer or leaked file can end it. Domain experts may be part-time, consultants or advisers, and their pay and status differ from the engineers'. 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 education, health and finance tech 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.
A product rule that makes sense to a doctor or teacher is read differently by an engineer, and defects follow.
A consultant doctor or visiting teacher is available a few hours a week, which slows decisions and leaves gaps.
Health records, student marks and bank details are visible to support and operations staff who need only part of them.
They deal with worried parents, ill patients or people who lost money, and burnout is quick.
Pay, titles and recognition favour the tech side, and the people whose judgement keeps users safe feel unseen.
One careless hire in a trust-heavy role can harm users, yet the pressure to grow fast pushes for speed.
Policies on content, refunds or data shift often, and the support team is the last to hear.
Someone in finance or operations handles HR on the side, and records and promises are inconsistent.
Start with the topics that matter most here: Organisation Design; Policies, Compliance and Governance; Employee Engagement and Experience. 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.
Policies a manager can apply, and obligations with owners and dates.
Communication, recognition and the conditions people actually work in.
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.
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.
Two routes — one for complaints, one for conduct — kept separate.
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 education, health and finance tech startups business puts in place, in an order that makes each easier. Open any card for the detail.
A short sheet on which calls belong to experts, product and engineering, with an escalation route.
A short sheet on which calls belong to experts, product and engineering, with an escalation route. The HR documentation process helps record it.
Clear scope, hours, pay and decision rights for part-time experts, reviewed yearly.
Clear scope, hours, pay and decision rights for part-time experts, reviewed yearly. See compensation benchmarking.
A register of who sees what, reviewed monthly, with removal on exit.
A register of who sees what, reviewed monthly, with removal on exit. See employee information management.
Scripts, escalation, breaks and a regular debrief for support staff who handle distress.
Scripts, escalation, breaks and a regular debrief for support staff who handle distress. The employee engagement process can host it.
Structured interviews, task tests and reference conversations by the hiring manager.
Structured interviews, task tests and reference conversations by the hiring manager. The recruitment process shapes it.
A short note and a named owner for each policy shift, sent to support before customers ask.
A short note and a named owner for each policy shift, sent to support before customers ask.
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.
Access records and exit routines that protect user data.
A careful, structured route for trust-heavy roles and domain experts.
Support for staff who deal with distressed users and recognition for experts.
Decision rights, role notes and expert agreements that avoid friction.
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
How an India head can sort a global parent's HR policies into apply, adapt or replace, write an India addendum with advisers, and keep headquarters on side.
7 min readRead article
Eighty per cent responded, the report was thorough, and six months later trust was lower than before. What went wrong between the survey and the silence.
8 min readRead articleMore on the GullyHR blog.
Define scope and hours, compare with roles in the same field and review yearly. Clear scope avoids both overpaying and under-using them.
Write who decides what, hold a short shared review each sprint and give experts a voice in planning.
Only those who need it for their job, by role, with a register that is reviewed each month and updated on exit.
Give scripts, escalation help, regular breaks and a debrief, and rotate difficult queues.
Yes, within reason. A structured process with a task and a reference conversation costs days and prevents larger problems.
We would ask who owns decisions between experts and engineers, who can see user data and how support is looked after. A good first project is a decision-rights sheet with a data-access register. 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.