Key takeaways
- There's no official standard for testing job titles. The same work has different names at different companies, and the same name can mean different work.
- Most titles fall into three kinds of work: testing by hand, analysing requirements and designing tests, and writing code that tests. Leading the testing is a fourth.
- To know what a job really is, read the responsibilities and tools, not the title.
Why there are so many names
Testing grew up differently in every company. Each one named the job after its own structure, so titles multiplied.
Even ISTQB, the main testing certification body, doesn't define job titles. Its Foundation syllabus describes just two roles: a testing role (analysing, designing, implementing and running tests) and a test management role (planning, monitoring and leading the testing). One person can hold both.
Everything else is a company's own label. So treat the descriptions below as what each title usually means, not a rule.
First, why "QA"?
QA stands for quality assurance. Strictly, it means improving the process so that fewer defects get made: better requirements, reviews, standards.
Testing is different. ISTQB calls it a form of quality control: checking the product to find defects.
In practice, most "QA" jobs are mainly testing jobs. The name stuck, and it's fine to use it. Just know the difference when someone asks.
The titles, one by one
Software Tester / Manual QA Tester
This is the classic entry point. You design test cases, run them by hand, explore the product to find problems nobody scripted, and write clear bug reports.
"Manual" describes how the tests are run, not how skilled the work is. Exploratory testing, usability checks and judging whether something "feels wrong" still need a human.
QA Analyst / Test Analyst
The focus is on analysis: reading requirements, spotting gaps and contradictions, defining acceptance criteria and choosing what to test and how.
QA Analysts often know the business domain well, such as banking, insurance or healthcare. They usually test by hand too.
QA Engineer
The broadest title, and the one with the most variation. At one company it's the same as a manual tester. At another it means testing APIs, setting up test data, checking logs and writing some automated tests.
If you see only "QA Engineer", the job ad's details tell you everything.
QA Automation Engineer / Test Automation Engineer / SDET
This role writes code that tests the product: automated UI, API and integration tests, the frameworks that run them, and their place in the CI pipeline.
SDET means Software Development Engineer in Test. Microsoft made the title popular. It usually signals a role close to a developer, with solid programming skills.
QA Lead / Test Lead / Test Manager
This is ISTQB's test management role. These people plan the testing, decide priorities, report on quality to the rest of the business and lead the testers. Usually it comes after a few years in one of the roles above.
Side by side
| Title | Main focus | Writes code? |
|---|---|---|
| Software Tester / Manual QA Tester | Running tests, exploring, reporting bugs | Rarely |
| QA Analyst | Requirements, test design, business rules | Rarely |
| QA Engineer | Varies: often a mix of manual and some automation | Sometimes |
| QA Automation Engineer / SDET | Automated tests, frameworks, CI | Yes, daily |
| QA Lead / Test Manager | Planning, priorities, people | Rarely |
How to read a job ad
The responsibilities and the tools tell you more than the title does.
- Look for the tools. Playwright, Selenium, Cypress, plus Java, Python or TypeScript means automation. Jira, TestRail and test cases mean mostly manual testing.
- Look for the verbs. "Execute", "explore", "report" point to testing by hand. "Analyse requirements", "define acceptance criteria", "work with stakeholders" point to analysis. "Build", "maintain the framework", "integrate into CI" point to automation.
- Check the seniority. "Junior", "Mid" and "Senior" usually matter more for pay and expectations than the title itself.
- Ask in the interview. "What does a typical week look like?" gets you the real answer.
Do
Apply based on what the job involves. A "QA Engineer" ad asking for exploratory testing and bug reports may be exactly the beginner role you want.
Don't
Skip an ad just because of its title, or put five different titles on your CV to match every ad. Describe what you've actually done.
When companies rename the roles
Titles change when companies reorganise. Big tech is a good example.
For years Microsoft had separate developer (SDE) and SDET roles. Teams commonly had about two developers for each SDET.
In mid-2014, Microsoft formally retired the SDET role. The developer title was renamed Software Engineer, and developers became responsible for testing their own code.
The title went away, but the testing work didn't. It moved into everyone's job.
Lesson: a job title describes how a company is organised. The skills underneath, such as designing good tests and automating them, carry over whatever the role is called.
Google took a different path. In 2011 it described three roles on its testing blog: the developer (SWE), the Software Engineer in Test (SET), who builds testing tools and makes code testable, and the Test Engineer (TE), who focuses on users and risk. Similar work, different names again.
Where people usually start
A common path is to start as a manual tester or QA Analyst, then specialise. Some move into automation, some into analysis and domain expertise, some into leading teams.
None of these is "better" than the others. Teams need all of them.
Ready to apply? Where to find your first testing job and writing a QA CV and LinkedIn profile cover the next steps.
Check yourself
A job ad is titled 'QA Engineer'. The responsibilities say: 'Build and maintain our Playwright test suite in TypeScript and run it in CI on every pull request.' What role is it, really?
Show answer
It's an automation role, what other companies would call QA Automation Engineer or SDET. The title is generic, but the tools (Playwright, TypeScript, CI) and the verbs (build, maintain) show you'll be writing test code every day.
