Software quality is a career, not a stepping stone. People build long careers testing games, banking systems, medical devices, cars, websites, and now AI systems. This final step of the "Start here" level in our software testing learning path describes the main roles and how people get started.
If you have worked through the earlier steps, from What Is Software Testing? to How to Report a Bug, you have already practiced the core of the first role below.
The main roles
Titles vary between companies, but most quality work falls into a few roles. Many people move between them over a career.
Software tester or test analyst. Designs and runs tests, often by hand, explores the software looking for problems, and writes bug reports. Test analysts specialize in understanding the business: what the software is supposed to do for its users, and how it could let them down. Strong writing and attention to detail matter more here than programming.
Test automation engineer. Writes code that tests other code, so that thousands of checks can run automatically every time the software changes. This role combines testing judgment with real programming skill. Some companies call it SDET (software development engineer in test). Our QA Library includes a real automation test engineer job description if you want to see what employers ask for.
Specialist tester. Some testers go deep on one kind of quality: performance (does it stay fast with many users?), security (can someone break in or steal data?), accessibility (can people with disabilities use it?), or AI evaluation (does an AI system answer accurately, safely, and consistently?). Each is a field in its own right.
Quality engineer. Works inside a development team, helping developers build quality in from the start: reviewing designs, setting up automated checks in the build pipeline, and measuring where defects come from.
Test manager or test lead. Plans testing for a whole project or organization, estimates the effort, builds and coaches the team, and tells leadership how ready the software is to release. See our test manager job description for the full scope.
Skills worth building now
You do not need all of these to start. Each one opens more doors.
- Curiosity and skepticism. The habit of asking "what if?" and "how do we know?" is the heart of testing.
- Clear writing. Bug reports, test cases, and status reports are all writing. Practice saying exactly what happened in as few words as possible.
- A programming language. Python and JavaScript are common choices for test automation and are friendly for beginners.
- How the web works. What happens when you load a page: browsers, servers, requests, and responses. Browser developer tools are free and worth exploring.
- Basic databases. Enough SQL to look up a record and check that the software saved what it claims it saved.
- Version control. Git is how teams share code, including test code.
A first credential: ISTQB Foundation
The ISTQB Certified Tester Foundation Level (CTFL) is one of the most widely recognized entry-level testing certifications. It covers the vocabulary and core techniques the profession shares, including several ideas from this learning path: the principles of testing, test design techniques such as equivalence partitioning and boundary value analysis, and defect management. In the United States, ISTQB exams are administered by ASTQB.
There is no formal prerequisite for Foundation, which makes it a practical goal for students and career changers. After Foundation, testers can specialize through the Advanced and Specialist levels. Our guide to the ISTQB Advanced Level path maps those options.
Rex Black Inc. is an ASTQB-accredited training provider and teaches ISTQB courses for teams and individuals. You can read about them on our training page, but you do not need a course to learn the material. The official syllabi are free to download from ISTQB.
Practical first steps
- Test things you already use. Pick an app, write test cases, and write bug reports for anything you find. Keep them. They become examples of your work.
- Learn to automate one test. Choose one test you wrote and try to automate it with a free browser automation tool in Python or JavaScript.
- Read the Foundation syllabus. Even before any exam, it gives you the shared vocabulary that interviewers listen for.
- Contribute to open source. Many open-source projects welcome well-written bug reports and test contributions. It is real experience, done in public.
- Keep going on this path. The next level, Foundations, moves from single tests to how professional teams decide what to test and how much.
Where to go next
You have finished the "Start here" level. The Foundations level of this path uses our professional library, written for working testers, so it will feel more demanding. Take it one piece at a time, and use the glossary whenever a term is unfamiliar.