A career in QA
How to start in software testing, what juniors need to know, how testers grow, and how to prepare for interviews.
QA is one of the most accessible ways into IT, and it can lead far: test automation, performance and security, QA leadership, product management or development. Here's a practical roadmap based on what we look for when we work with testers.
What a junior tester needs
| Area | Minimum to start |
|---|---|
| Testing theory | Levels, types, test design techniques, bug life cycle — chapters 1–4 of this handbook |
| Documentation | Write clear checklists, test cases and bug reports |
| Web basics | HTTP, status codes, DevTools, how APIs work |
| Tools | A bug tracker, Postman, basic Git |
| SQL | SELECT with WHERE, JOIN, GROUP BY |
| English | Read documentation and write reports |
| Soft skills | Asking good questions, explaining problems calmly, attention to detail |
How to get experience without a job
- Test open-source projects and real websites, and keep a portfolio of well-written bug reports (without publishing security issues)
- Join crowdtesting platforms to work on real products
- Write test documentation for an app you use every day
- Build a small automation project on GitHub: a few UI tests with Playwright and API tests with Postman or pytest
- Practise with our QA interview questions and quiz
Growth paths
| Level | Typical responsibilities |
|---|---|
| Junior | Executes tests, writes bug reports, learns the product and tools |
| Middle | Designs tests independently, owns features, automates, works with APIs and databases |
| Senior | Defines test strategy, mentors, improves processes, assesses risks |
| Lead / Manager | Builds the team, plans quality across projects, reports to stakeholders |
Manual or automation?
Both. Automation engineers need strong testing skills to know what to automate; manual testers who can read code and write simple scripts are far more effective. Learning one programming language — JavaScript/TypeScript, Python or Java — is the single biggest step up for most testers.
Interviews
Expect theory questions, a practical task (test a form, write a bug report, find bugs on a page) and situational questions. Explain your thinking out loud, ask clarifying questions, and prioritise by risk. Honest “I don't know, but here's how I'd find out” is better than a confident wrong answer.


