Process · Team Building
Hire deliberately. Grow people continuously.One hire at a time, then everyone, every cycle.
The test team is the product. This process structures hiring as a reversible, repeatable loop and pairs it with an always-on skills and career-path program.
- Sub-steps
- 9
- Hiring cycles
- Repeat as needed
- Career reviews
- Continuous
You cannot out-tool a thin team. The hiring process and the skills program compound over time; neglect either and the whole test program decays.
Key takeaways
Four things to remember.
01
Start every hire with explicit permission
Written approval to fill a role prevents downstream political reversals when the best candidate shows up.
02
Advertise the job you actually need
A vague posting attracts vague candidates. Write the role description from the skills gap you have measured, not the headcount budget you were handed.
03
Never stop screening
Resume review, phone screen, in-person interview. Each stage eliminates a distinct failure mode. Collapse the stages and the failures arrive later, as bad hires.
04
Career paths are a retention tool
Revisit them with each team member regularly. The test career lattice is wider than "QA analyst to senior QA analyst", design paths that keep people growing.
Why this exists
The problem this process fixes.
Most test team problems we are asked to diagnose are really hiring problems, skills problems, or career problems in disguise. The system looks fine from the outside: roles are filled, headcount is reported, budget is met. Inside, the team is drifting.
This process treats hiring and growth as a single, always-on activity. Step 1 is a discrete hiring loop you run for each open role. Step 2 is a continuous program you run for everyone. Step 3 is the reminder that both run forever.
The checklist
12 steps, in order.
- Phase 1
Hire appropriate test team members.
- 1.A
Get permission to hire.
- 1.B
Define and advertise the position.
- 1.C
Gather and screen candidates, based on their resumes and phone interviews, eliminating unqualified or undesirable candidates.
- 1.D
Interview qualified, desirable candidates in person.
- 1.E
If appropriate, extend an offer to the most-successful candidate, often via an offer letter.
- 1.F
If the most-successful candidate accepts, orient the new hire. If not, repeat steps 1.E and 1.F for the second-most-successful candidate, either until a successful candidate accepts or the process must restart at step 1.A. Notify rejected candidates that they should pursue other opportunities.
- Phase 2
Foster team skills and career growth.
- 2.A
Work with new hires to develop career paths.
- 2.B
Regularly revisit the career paths for all employee's and each employee's progress on their path.
- 2.C
Actively manage the employee's skills growth necessary to reach employee and team goals.
- 3
Iterate step 1 as needed to add new people. Iterate step 2 continuously.
One more thing
Step 3 is the whole point. Hiring is event-driven; skills growth and career management are steady-state. The best test organizations we have seen treat the second as non-optional, even when the first is on pause.
Take it with you
Download the piece you just read.
The library is free. Tell us who you are so we can send you updated versions. One form; this browser remembers you after that.
In the library
Pair this with.
Process · The Master Framework
Four phases, applied in order, every project.
The top-level testing process used on every engagement. Four phases contain twelve sub-processes, each of which is documented in its own checklist in this library.
Read →Process · Test Estimation
Estimate testing the way projects actually work.
Test estimates fail either because they skip the work breakdown or because they skip stakeholder buy-in. This process does both, in sequence, so the resulting schedule and budget survive contact with management.
Read →Process · Test Execution
Run the tests, capture the data, adjust daily.
Test execution is where the risk register becomes results. These eight steps cover selection, assignment, the per-test inner loop, blocking-issue resolution, and the daily replanning that keeps a cycle on the rails.
Read →
Keep reading
Related reading
- Primer
Careers in Software Quality: Roles, Skills, and First Steps
What testers, test automation engineers, quality engineers, and test managers actually do, the skills each role uses, and practical first steps for students and career changers, including the ISTQB Foundation certification.
Read → - Primer
Errors, Defects, and Failures: What a Bug Really Is
Everyone says 'bug', but testers use three precise words: error, defect, and failure. Learn the difference, why it matters, and how severity and priority decide which problems get fixed first.
Read → - Primer
How Software Gets Attacked: Common Vulnerabilities in Plain English
The most common ways attackers break into software, explained without jargon: trusting input, broken access control, weak sign-in, misconfiguration, and outdated components. Each one comes with the defense that stops it.
Read → - Primer
How to Report a Bug So It Actually Gets Fixed
Finding a bug is half the job. Learn how to write a bug report a developer can act on: a clear summary, exact steps to reproduce, expected versus actual results, and the habits professional testers use to make every report count.
Read → - Primer
Security Testing Basics: Finding Weaknesses Before Attackers Do
An introduction to security testing for new testers and developers: thinking in threats, designing abuse cases, testing access control, the role of automated scanners and penetration tests, and the rules that keep security testing legal and ethical.
Read → - Primer
Staying Safe Online: Passwords, Sign-In, Phishing, and Updates
The everyday security habits that stop most attacks: strong unique passwords, multi-factor sign-in, spotting phishing, keeping devices updated, and sharing carefully. Written for students, families, and anyone starting out.
Read →
Practices
Where this leads
- QA & testingSoftware testing
Software quality consulting since 1994: we test the releases that matter, coach your team on the method, and measure how its testing matures.
Book a call →