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 technical support centre fixes problems with devices, software and networks for another firm's customers. Agents need product skill as well as patience, and the best ones are quickly wanted by the client, by rivals and by the IT industry.

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 technical support centre takes calls, chats and tickets from customers who cannot get a laptop, router, app or service to work. Work is tiered: first-line agents follow troubleshooting steps, second-line engineers handle harder faults, and a few specialists take the rest. Queues run at night and on weekends for clients in other time zones. Skill is built slowly, and a trained agent is easily lured away to a larger firm or an in-house IT team. Leaders look to HR for hiring people who can learn technical content, a ladder that rewards skill and a way to keep product knowledge up to date. See also HR for IT and software and HR for BPO, KPO and contact centres.
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.
Support is told about the product on the day tickets begin, and agents guess in front of customers.
Those who master the basics and see no ladder leave for a firm that will give them a title and a pay step.
When two L2 engineers go on leave the same week, tickets queue and L1 agents have no one to ask.
Seniors prefer days, so night shift handles hard faults with junior staff and escalations pile up by morning.
Clients ask for a vendor certificate, and agents study at home with no time at work.
Agents who close fast reopen later, while agents who solve properly look slow on the scorecard.
Larger firms and the client's own IT team take trained engineers, often after the centre has paid for their course.
Start with the topics that matter most here: Career and Succession Management; Learning and Development; Organisation Design. 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.
Training planned from need rather than from the calendar.
Structure, reporting lines and who is allowed to decide what.
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.
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 technical support centres business puts in place, in an order that makes each easier. Open any card for the detail.
For each product or release, a briefing and short assessment before tickets begin.
What this coversHideFor each product or release, a briefing and short assessment before tickets begin. The learning and development process plans it.
What an agent must show to move up, how often openings are reviewed and what pay changes.
What this coversHideWhat an agent must show to move up, how often openings are reviewed and what pay changes. The competency and talent management work builds the framework.
A named owner, a review cycle and a habit of adding a note after each hard ticket.
What this coversHideA named owner, a review cycle and a habit of adding a note after each hard ticket.
At least one L2 engineer or a rotating on-call lead, with extra allowance and a rest rule.
What this coversHideAt least one L2 engineer or a rotating on-call lead, with extra allowance and a rest rule.
A scheduled hour each week during work for agents on a certification path, with a clear understanding on cost and service afterwards.
What this coversHideA scheduled hour each week during work for agents on a certification path, with a clear understanding on cost and service afterwards.
Add repeat contact or reopen rates to the scorecard, so that quality is visible beside speed.
What this coversHideAdd repeat contact or reopen rates to the scorecard, so that quality is visible beside speed.
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 skills framework from L1 to specialist, so promotions rest on what people can do.
A product training calendar and certification plan matched to the queues.
Night and weekend rosters that carry a senior on every shift and share the load fairly.
Eye strain, long sitting and night work looked at as part of the working week.
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
Plastics training dies when it waits for a free Saturday. Tie it to mould changes, purges and cold starts, use one-point lessons and a visible skill ladder, and protect it in peak months.
7 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead articleMore on the GullyHR blog.
Most have two or three: first-line, second-line and specialist. Set the number by the kind of faults you handle, and define what each level does alone so that agents see the way up.
Give a visible path to specialist or lead, pay that follows skill, interesting work and time to learn. People leave stagnant roles more often than low-paying ones.
Where hard faults arrive at night, yes. Rotate the role, pay a fair allowance and give the senior a rest rule, so the burden is shared and the queue is safe.
Brief the team before release with a short course, test their understanding on sample tickets and keep a named expert on call for the first weeks.
Yes. Calm speech, clear explanation and empathy matter as much as the fix. Blend short sessions into product training rather than running them as an add-on.
We would ask for your current L1 and L2 role descriptions, the list of agents ready to move up and your night escalation counts. A written ladder with signed-off skills for each level is a natural first job, and scope goes into writing for your sign-off.
All 6 business types in BPO, KPO & contact centres · 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.