QA Engineer
You break software on purpose so customers don't find the bugs first. Part of the job is manual testing, but increasingly it's writing automated tests in code.
What Tuesday looks like
You start at 9am reviewing the test results that ran overnight. Six tests failed — four are real bugs, two are flaky tests that fail randomly and everyone ignores. You file the four bugs in Jira with reproduction steps, screenshots, and logs. A developer pings you to argue that one of your bugs isn't actually a bug; you spend 20 minutes proving it is. After standup, you write automated tests for a new checkout feature being released Friday. The feature keeps changing, so your tests keep breaking, and you rewrite them twice. Lunch is quick. In the afternoon you do exploratory testing on a mobile build — tapping buttons in weird orders, trying to crash it. You find one good bug and feel briefly useful. End of day you update the test plan spreadsheet nobody else reads. Pace is steady, rarely dramatic, occasionally tedious.
Career profile
Career shape
Tap or hover each point to explore a dimension
In the landscape
Tap or hover any dot to identify a career
Salary range
$62K
Entry
$82K
Median
$108K
Senior
$48K floor
$140K ceiling
10-yr growth
+8%
8/10 exposure
Reward profile
3 quick questions to see how this career fits the way you work.
What school costs — and when it pays off
Bachelor's degree · Four years at a public university. Costs here use the cheaper in-state rate.
The chart shows your annual salary over time alongside the annual loan repayment. The shaded band at the bottom is what goes to the loan each year — when it disappears, your full salary is yours.
Takes about 12 working years to earn back the school investment — but you do come out ahead.
Entry-level salary
$62K
25th percentile — what most people start at
Experienced salary
$108K
75th percentile — after ~10 years in the field
School & training cost
$80K
+ $29K interest over 10 yrs
Loan paid off
Year 14
$910/mo for 10 years
First year of work
After loan's paid (yr 14)
Salary range reflects 25th–75th percentile nationally, growing from entry-level to experienced over 10 working years. School costs are national averages — yours will vary. Loan assumes you borrow the full amount at 6.54% interest, repaid over 10 years. Monthly figures are pre-tax.
The first years
Year 1: Junior QA / Manual Tester
You're mostly doing manual testing — clicking through the same checkout flow for the tenth time this week, following test scripts someone else wrote. You learn Jira, how to write a bug report developers won't immediately close as 'works on my machine,' and how to take useful screenshots. Pay is around $55–65K and you'll sometimes wonder if you're actually an engineer or just a professional clicker. The wins are small: catching a bug before release feels good, even if nobody notices.
Year 2–3: QA Engineer (Learning to Code)
You realize manual-only QA is a dead end — automation is where the job is going, and AI tools are eating the repetitive testing work. You start learning Selenium, Cypress, or Playwright, usually on your own time, and write your first real automated tests. They're ugly and flaky but they run. Salary climbs to $70–85K. The grind is real: you're testing during the day and learning to code at night, and your tests break every time a developer changes a button.
Year 4: The Fork
You're solid at automation now and people trust your bug reports. But you can see the field splitting: pure QA roles are shrinking, and you have to pick a lane. Option A: go deeper into test automation and become an SDET (Software Development Engineer in Test) — basically a developer who writes testing infrastructure, pays $100–130K. Option B: move into a developer role entirely, which means more coding work but better long-term prospects. Option C: pivot to specialized areas like security testing or performance engineering. Staying as a generalist manual QA is increasingly risky given how much of that work AI can now do.
Decision point
Specialize into SDET/automation, transition to full software development, or pivot to a niche like security or performance testing. Staying in pure manual QA is the path most likely to get squeezed by AI and offshoring.
Year 5–7: Senior QA / SDET
If you went the SDET route, you're now building the testing frameworks other QAs use, reviewing pull requests, and sitting closer to the dev team than the QA team. You're paid like a mid-level developer ($110–140K) and spend more time writing code than testing manually. The work is more interesting but the pressure is higher — when the test suite breaks, releases stop and everyone looks at you. Some weeks feel like real engineering; other weeks you're still arguing with a developer about whether a bug is a bug.
The path in
Computer Science · Software Engineering · Information Technology · Computer Information Systems
Most QA Engineer job postings list a bachelor's in CS or a related field as a requirement, though hiring managers often waive it if you can demonstrate real testing skills. The degree matters less than being able to write code (Python, Java, or JavaScript) and understand test frameworks like Selenium, Playwright, or Cypress.
Computer Science · Software Development · Information Technology
A 2-year CS or IT degree from a community college can get you into manual QA or junior tester roles, especially if you build a portfolio of automated test projects on GitHub. Many people use this as a cheaper stepping stone, then transfer to a 4-year program or skip it if they land a job.
QA Automation · Software Testing · Full-Stack Development
QA-focused bootcamps teach Selenium, API testing, and CI/CD pipelines fast, and some have decent job placement. The catch: AI tools are automating a lot of basic test writing, so bootcamp grads need to learn coding deeply — not just click-and-record testing — to stay employable.
ISTQB Certification · Self-study in Python/Java + Selenium
Some QA engineers break in by self-studying, earning an ISTQB Foundation certificate, and building automated test projects on GitHub. It's harder to get past resume screens without a degree, but freelance testing work and small startups are realistic entry points.
Known for this field
Top-ranked CS program in the country with strong software engineering and testing research. Graduates land at every major tech company.
Excellent CS program with a software engineering thread that covers testing, verification, and quality. Affordable for Georgia residents and well-respected nationally.
Affordable public university right in Silicon Valley — top feeder school for Bay Area tech companies including QA roles at Google, Apple, and Adobe.
Free courses on Selenium, Playwright, Cypress, and API testing taught by working QA engineers. Industry-recognized and a standard self-study resource.
Strong CS program in a major tech hub. In-state tuition is reasonable and Austin's tech scene hires heavily for QA and SDET roles.
One of the few schools offering a dedicated Software Engineering bachelor's (not just CS), with online options. Coursework explicitly covers testing and QA.
Strong CC in Silicon Valley with a transfer pipeline to UC schools. Cheap way to start a CS degree and pick up real coding skills.
One of the better-known QA-specific bootcamps with job placement support. Focuses on practical skills employers actually ask for, including SQL and API testing.
Related paths
Software Developer
QA engineers who write automated tests often pick up enough coding to move into full developer roles. It's a common bridge into software engineering.
Product Manager
QA engineers know the product deeply and talk with users about bugs, which can make product management a natural pivot.
Cybersecurity Analyst
Both careers involve finding weaknesses in software before they cause problems. QA looks for bugs; cybersecurity looks for security flaws.
DevOps Engineer
QA engineers who automate tests often move into DevOps because the tooling and mindset are similar. Both focus on reliable, repeatable software delivery.