QA / Test Automation
Break things before users do.
QA automation engineers build test frameworks that catch bugs before release.
What the work looks like
Writing automated tests, designing test plans, reporting bugs, improving release quality.
Key skills
- Testing fundamentals
- Programming (Java/Python/JS)
- Automation frameworks
- API testing
- CI integration
Common tools
SeleniumPlaywrightPostmanJUnit/PyTestJenkins
Pros
- Accessible entry into tech
- Can transition to SDET/dev
- Valued in large companies
Cons
- Sometimes seen as less prestigious
- Repetitive manual testing in some roles
- Release-time pressure
A 12-month starter roadmap
Months 1–3
- • Testing concepts
- • One language
- • Git
- • Manual test cases
Months 4–6
- • Selenium/Playwright
- • API testing
- • Test frameworks
- • Automate a real site
Months 7–12
- • CI/CD integration
- • Performance testing
- • SDET skills
- • ISTQB (optional)
Reality check
Students like: Finding the bug everyone missed.
Students dislike: Being blamed when bugs slip through.
Hardest part: Writing tests that aren't flaky.
Common myth: Modern QA is engineering, not just clicking.