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 travel technology startup builds booking and itinerary software while handling a human problem: travellers in trouble at odd hours. HR must balance engineers, supplier teams and round-the-clock support through seasonal peaks.

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 traveltech startup builds an app or platform for booking flights, hotels, holidays or itineraries. A small product and engineering team writes the software and connects it to airlines, hotels and payment partners. Alongside, a support desk answers travellers who have missed a flight, lost a booking or been refused at a hotel, often at night. Supplier managers negotiate rates and chase refunds. Sales or partnerships staff sign agents and corporates. Demand follows seasons, holidays and sudden disruption, so workload swings from quiet to frantic in a day. Money is limited, titles are loose and a handful of people hold all the knowledge of how the integrations work. 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 TravelTech 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 holiday weekend or a strike doubles bookings and queries, and the engineers who built it are also the ones fixing it.
Travellers call when a flight is cancelled at 2 a.m., and the desk is covered by whoever is awake.
Only one engineer understands the airline or hotel connection, and a resignation puts bookings at risk.
Support says the app is broken, engineering says the query was wrong, and the traveller waits.
Refund chasing is a quiet job that no one owns, and customers write angry reviews while the money is stuck.
Early hires got equity talk and informal raises, and newer people compare notes and find gaps.
Partnerships staff sign agents on features that are still on the roadmap, and support absorbs the anger.
Offer letters, leave records and notice terms are made up case by case until a dispute exposes them.
Start with the topics that matter most here: HR Strategy and Workforce Planning; Retention and Attrition Management; Organisation Design. Then work through the rest. Each topic is written for information technology and software, not in general.
How many people, in which roles, by when — and what they will cost.
Who leaves, when, why — and which of them mattered.
Structure, reporting lines and who is allowed to decide what.
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.
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 TravelTech startups business puts in place, in an order that makes each easier. Open any card for the detail.
Mark expected peaks, freeze risky releases before them, and plan cover for engineering and support.
Mark expected peaks, freeze risky releases before them, and plan cover for engineering and support. See attendance, shift and leave.
Fixed shifts, a rest rule after a late night, an on-call engineer and a clear escalation path.
Fixed shifts, a rest rule after a late night, an on-call engineer and a clear escalation path. Pay for night duty follows your payroll provider.
A runbook, a second engineer and a named owner for every supplier connection.
A runbook, a second engineer and a named owner for every supplier connection. See learning and development.
Plain titles, expected scope and a pay range per level, so offers are consistent.
Plain titles, expected scope and a pay range per level, so offers are consistent. See compensation benchmarking.
One person, a tracker and a weekly review of stuck cases with supplier managers.
One person, a tracker and a weekly review of stuck cases with supplier managers. See performance management.
Offer letters, role descriptions, notice terms and a leave record for every person.
Offer letters, role descriptions, notice terms and a leave record for every person. See HR documentation.
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.
Peak calendar, night rota and rest rules for a team that cannot go quiet.
Runbooks and second owners so no integration depends on one engineer.
Role levels and pay ranges that make offers consistent as the team grows.
Offer letters, role descriptions and records ready before the next hiring wave.
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 decide which digital marketing work to hire for, which to buy from an agency, and which to split, with a worksheet and a five step plan.
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 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.
Set fixed shifts, a rest rule after late nights, an on-call engineer and an escalation path. Keep a small bench for peaks.
Write a runbook for each connection, name a second owner, and let that person fix a real issue under supervision.
Plan the calendar early, freeze risky releases, arrange temporary cover and give time off after the peak.
Write down what was promised and confirm the terms with a qualified professional. Do not leave informal assurances undocumented.
Agree one ticket form, a joint review of repeated issues each week and a shared measure such as time to resolve.
We would meet a founder, the support lead and the engineering lead and look at the peak calendar, the night rota and the list of people who hold integrations. A fitting first task is a role-and-level chart with a support rota. Scope and fees are put in writing after we talk.
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.