A tester with three years in the company asks for a call. She says she likes the team but cannot see where her work leads. The only promotion she has watched in the QA group went to a developer who moved across. Her manager has no answer, and she has already opened a job portal.
This is common in small software firms. Testing is treated as a stage, not a career. This post sets out a simple path for QA and testing engineers that a head of QA or delivery can write down this month.
Why good testers leave quietly
Testers often see the whole product before anyone else does. They know the weak modules, the late changes and the shortcuts. When they feel stuck, they take that knowledge elsewhere. Pay is rarely the only reason. Three reasons show up again and again in exit conversations.
- No visible next step beyond senior tester, so growth means leaving QA.
- Automation skills are valued in hiring but not rewarded once someone joins.
- Release pressure lands on testing last, with no say in the release decision.
Teams that specialise in testing have the same problem at a larger scale. See how software testing companies structure their delivery and people questions.
Draw two tracks, not one ladder
A single ladder pushes everyone towards managing people. Many testers prefer to go deeper in the craft. Offer two tracks that meet at the same level of pay and respect.
- Craft track: tester, senior tester, test specialist, test architect. Each step adds scope, such as test design, automation frameworks or performance work.
- Lead track: tester, senior tester, test lead, QA manager. Each step adds people, planning and client contact.
Write one short description for each level. A role design and job descriptions exercise helps you keep these descriptions plain and comparable.
Define what changes at each level
Levels fail when they only add years. Describe what the person does differently. A senior tester may own the test plan for a module. A specialist may choose the tools and teach others. Use verbs and outputs, not adjectives.
Level name and track.
Scope: which products or modules the person owns.
Typical work: test design, automation, reviews, client calls.
Decisions they can make alone.
Skills to show before moving up.
Who reviews the case for promotion.
Pay band reference, kept by the founder or HR.Build the path in six steps
- 1
List current roles
Write down every tester, their tasks and the tools they use today. Note who already does automation or client calls.
- 2
Draft the levels
Keep to four or five levels per track. Share the draft with two trusted senior testers and ask what is missing.
- 3
Fix the evidence for each step
For each promotion, name two or three things a manager can see, such as a framework built, a defect pattern analysed or a new joiner coached.
- 4
Hold a review twice a year
Put promotions on a calendar so people know when to expect a decision. Do not wait for a resignation.
- 5
Link pay to levels
Agree with the founder or finance head how each level maps to a pay band. Keep the band sheet private to managers and HR.
- 6
Tell the team
Walk through the cards in a team meeting and invite questions. A path nobody has seen does not retain anyone.
Talk about the path in one to one meetings
A written path only works if managers talk about it. Ask every tester once a quarter where she sees herself in a year. Note the answer in a shared sheet. Then agree one skill to build and one piece of work that would show it. This takes fifteen minutes per person and turns a document into a habit. Be honest about timing. Some people are ready now and the budget is not. Say so, and name when the next review is. Silence is the most common reason a patient person gives up.
Give testers a voice at release time
Many testers feel they carry blame without authority. Give them a clear role in the release call. A tester can state the open risks in writing, and the delivery head decides with those risks in view. This single habit tells testers their judgement counts. It also pairs well with fair rules for late nights. Read about compensation and rules for release night work so that testing does not absorb every late hour.
Reward automation and learning honestly
If automation skill earns a premium in the market, say whether you reward it. Silence breeds resentment. Options include a skill allowance, a faster review for those who build and maintain frameworks, or paid time to study. The right mix is your decision and depends on margins and client contracts.
Look at who is doing the invisible work
In many teams one tester keeps the regression suite alive, another trains new joiners and a third handles the client's awkward questions. None of this appears in a title. List this work by name during the first step. Then decide which level it belongs to. People who see their quiet work counted tend to stay longer.
Hire into the path
Once levels exist, use them in hiring. A scorecard that names the level and the evidence expected keeps offers consistent. The post on a scorecard and skills test for hiring developers shows the method, and the same shape works for testers.
Check the path is working
- Count how many testers moved up in the last year, and how many left.
- Ask in each exit conversation whether the path was clear.
- Review the level cards after every big client change.
- Check that the lead track and craft track are treated as equals in pay talks.
If you want help drafting the cards or reviewing the structure, the employee retention and attrition management page describes how GullyHR works with small teams.
