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 enterprise software company sells large systems to big customers and then lives with them for years. Implementation, support and account people carry the relationship, and long sales and rollout cycles shape every hiring and review decision.

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 enterprise software company sells systems for finance, supply, people or operations to large customers, then configures, rolls out and supports them over years. Sales cycles are long and a single contract may need a team for a year. The company employs product developers, implementation consultants who sit at customer sites, support engineers who answer tickets across time zones, trainers and customer success managers. Customers judge the company by how a go-live week goes and how fast a fault is fixed. The wider IT and software page covers what the sector shares.
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.
Weeks away from home during a rollout wear people down, and the best consultants are in constant demand.
Support, consultants and developers work long days together, and the strain shows up as resignations afterwards.
Tickets arrive through the day and night, and the team handling them is often the least recognised in the company.
A few senior people understand the oldest parts, and the company is exposed if one of them leaves.
A strong consultant becomes a programme manager overnight, with no help to manage people or customer politics.
Relationships sit with a manager who may move on, and the customer feels the change.
A new consultant needs months to learn the product and the customers' processes, and the early period is often left unstructured.
Start with the topics that matter most here: Career and Succession Management; Onboarding and Probation; Policies, Compliance and Governance. Then work through the rest. Each topic is written for information technology and software, not in general.
Named backups for the roles that cannot be vacant.
A first day that is the same for the fifth joiner as the first.
Policies a manager can apply, and obligations with owners and dates.
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.
Training planned from need rather than from the calendar.
Communication, recognition and the conditions people actually work in.
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 enterprise software companies business puts in place, in an order that makes each easier. Open any card for the detail.
A simple policy on time at sites, travel days and home weeks, applied the same way across programmes.
What this coversHideA simple policy on time at sites, travel days and home weeks, applied the same way across programmes. The attendance and leave process can include it.
A plan with product learning, shadowing at a customer and checks with a mentor.
What this coversHideA plan with product learning, shadowing at a customer and checks with a mentor. Onboarding sets the shape.
Identify the senior people whose knowledge is rare and prepare others, with a documented plan.
What this coversHideIdentify the senior people whose knowledge is rare and prepare others, with a documented plan. See succession planning.
A short programme for people moving to programme or team lead roles, built from real situations.
What this coversHideA short programme for people moving to programme or team lead roles, built from real situations. The manager development programme covers this.
Pair each key account with a second contact so relationships survive a move.
What this coversHidePair each key account with a second contact so relationships survive a move.
Include support engineers in reviews, rotations to project work and visible credit for fixes.
What this coversHideInclude support engineers in reviews, rotations to project work and visible credit for fixes.
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 plan for key product and customer knowledge held by a few people.
A first-quarter route for consultants and support engineers.
Written rules for travel, site work, shifts and conduct at customer premises.
Reviews that recognise delivery, support quality and customer trust.
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 two-hour exercise that names the roles you could not fill quickly, who could cover them, and what readiness would actually require.
7 min readRead article
Hour by hour, then week by week, for a recruit's first month at a module, inverter, pack or junction box line: safety and handling first, a practice bench, a buddy, a sign-off and a day-30 review.
7 min readRead article
A practical contents list for an employee handbook in a growing Indian business: what to cover, what to leave to policies, and how to keep it usable and current.
5 min readRead articleMore on the GullyHR blog.
Set travel and rest rules, plan rollouts to spread time at sites and recognise the strain in pay and grade. Give a route to roles that need less travel.
Identify rare knowledge, name a second person, pair them on real work and record the results. Review twice a year because teams and products change.
Start with a short programme, give a mentor, let them lead a small stream and check progress. Do not assume technical strength brings people skills.
As a core team. Include them in reviews, offer rotation to project work and share customer praise. A desk that feels ignored is a desk that leaves.
Plan for a quarter at least, with learning, shadowing and small tasks, then review. Product knowledge builds slowly, so give time and structure.
First we would list people whose departure would stall a rollout, count travel weeks for consultants and read how the last promotion to manager was handled. A succession plan and a first-quarter onboarding route are a natural first job, with scope agreed in writing.
All 6 business types in software development companies · 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.