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 software testing company checks other firms' products for faults before release. Its people work on client schedules, often across time zones, and many fear being seen as a lesser career than development.

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 software testing company takes on manual testing, automation, performance checks and release sign-offs for clients who build products elsewhere. Teams sit on client projects, with test leads, manual testers, automation engineers and a few specialists in security or performance. Release dates drive the rhythm: calm for weeks, then long days and weekend runs. Some clients work in other time zones, so early starts and late calls are normal. Many testers join as freshers, learn on the job and leave for development roles within two or three years. The wider IT and software hub and the software development hub cover what software firms share.
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.
Many testers want to move to development, so the firm trains people who then leave just as they become useful.
Before a client release, test runs stretch into nights and weekends, and then the project goes quiet with little recognition for the push.
Testers join late calls with distant clients and still start early on the next project, and tiredness shows in missed defects.
Careful exploratory testers are paid less than automation engineers, though many catch faults that scripts never would.
New testers need weeks to learn a client product, test tools and defect writing, and this learning is rarely planned.
If testers are judged on numbers of bugs found, they log trivial ones and argue with developers, which harms the client relationship.
A tester may serve two or three clients in a week, and leave, shifts and workload are hard to see from any one lead.
Start with the topics that matter most here: Retention and Attrition Management; Learning and Development; Organisation Design. Then work through the rest. Each topic is written for information technology and software, not in general.
Who leaves, when, why — and which of them mattered.
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.
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 software testing companies business puts in place, in an order that makes each easier. Open any card for the detail.
One track for manual and exploratory depth, one for automation and tooling, each with clear levels and pay.
What this coversHideOne track for manual and exploratory depth, one for automation and tooling, each with clear levels and pay. Role design keeps the titles consistent.
A first-quarter plan covering the test tools, defect writing, client product basics and a review each month.
What this coversHideA first-quarter plan covering the test tools, defect writing, client product basics and a review each month. Learning and development can shape it.
Write who covers late calls, how rest is given the next day and how weekend release runs are planned.
What this coversHideWrite who covers late calls, how rest is given the next day and how weekend release runs are planned. See attendance, shift and leave.
Judge testers on coverage, clarity of reports, defects that escaped to production and how they worked with developers.
What this coversHideJudge testers on coverage, clarity of reports, defects that escaped to production and how they worked with developers.
A short, regular talk about workload, learning and next role, held by the lead, so signs of leaving are seen early.
What this coversHideA short, regular talk about workload, learning and next role, held by the lead, so signs of leaving are seen early.
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 fresher path and skill steps from manual to automation.
Shift cover for client time zones and release peaks.
Early signs of leaving among testers and a plan to answer them.
Clear levels for manual and automation tracks with matching pay.
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 to spot an unmanageable workload before it becomes an exit or an error, what to look at, how to talk about it and what to change, without guessing.
5 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.
Often they see testing as a first step to development, or find pay and growth are slower than in other roles. A visible career path and fair pay for depth change this more than any one-off perk.
There may be a difference in market rates, but depth in exploratory testing is valuable too. Build a ladder where senior manual testers can grow in pay and respect without needing to learn code.
Plan runs early, share the late hours across the team, give time off after the push and do not let the same people cover every release. Tell testers the plan ahead, not on the day.
Name a small rota for late calls, give rest the following morning and keep the rest of the team on normal hours. Rotating fairly matters more than the exact pattern.
Look at report quality, coverage, faults that escaped to production, learning and teamwork. Counting bugs found rewards noise. A conversation with developers and the client adds a useful second view.
First we would ask long-serving testers why they stayed, count exits within three years and read how testers are appraised today. A two-track career ladder with a fresher plan is a natural first job, and scope goes into writing for your sign-off.
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.