QA Engineer

You break software on purpose so users never see it break by accident. QA is one of tech's classic entry doors — and it split into two very different jobs: clicking scripts, and engineering test systems. Know which one you're walking into.

Median pay (US)

~$90k / yr (automation)

Typical range

$55k–$130k+

Degree required?

No — proof of rigor wins

What the job actually is

QA engineers protect quality: designing test plans, hunting edge cases, filing bugs developers can actually reproduce, and — in the automation flavor — writing code that tests code (Playwright, Cypress, Selenium; API and load testing). Manual QA explores and verifies by hand; automation QA (often titled SDET) builds the safety nets that run on every deploy. The mindset is the constant: professional pessimism, applied kindly.

Is it actually you?

You'll probably love it if

You notice what's off — the misaligned button, the weird edge case
Breaking things methodically sounds fun, not tedious
You write clearly; a good bug report is half the job
You like being the user's last line of defense
You want a tech door that doesn't demand a CS degree

Maybe not, if

Repetitive verification would numb you (manual QA has lots)
You hate being the bearer of bad news right before a deadline
You'd rather build the feature than test it
Status as "not a real engineer" (wrong, but common) would eat at you

The real day-to-day (no hype)

Manual and automation are diverging fast. Manual-only QA is shrinking and pays modestly; automation QA is solid engineering work at engineering pay. If you enter manual, start learning to code immediately.
AI changed the leverage. AI generates test cases and even test code now — which makes one good QA engineer cover far more ground, and makes pure-manual clicking the exposed end of the field.
You'll deliver unwelcome news. Finding the release-blocking bug on Friday makes you briefly unpopular. Good teams thank you; know how to read whether you're on one.
It's a genuine on-ramp. QA → developer, QA → DevOps, QA lead → engineering manager are all well-worn paths. You learn the whole system's weak points — valuable everywhere.

How people break in — or switch in

Manual QA remains one of tech's lowest gates: strong attention to detail, clear writing, and domain knowledge can land it without a degree. Stand out by doing the job before you have it — pick a real app, write a small professional test plan, file two thoughtful bug reports on an open-source project. For automation roles, one public repo of Playwright/Cypress tests against a demo app is the portfolio.

Detail-heavy pasts — bookkeeping, compliance, pharmacy, editing — are QA superpowers wearing other names. Frame your history as years of professional error-catching.

Your application, already half-written

Here's a question every QA Engineer application asks, answered the way pirch would — in a real voice, grounded in real experience:

“Tell us about the best bug you ever found.”

Testing a checkout flow, everything passed — until I tried it the way my mom would: typed the coupon code with a trailing space from autocorrect. Discount silently failed, no error, full price charged. It had survived because every tester typed codes cleanly. I filed it with the exact reproduction, the affected revenue estimate from support tickets mentioning "coupon didn't work," and a one-line fix suggestion (trim input). That's my whole philosophy: test like real humans behave, not like the spec assumes they do.

pirch's co-pilot writes answers like this for your background and the exact job — try it free →

pirch finds the QA roles that are actually you

Tell pirch who you are — your eye for detail, your test work, the field you came from — and it hunts down real, still-open QA jobs that fit the whole you, with a tailored cover letter already written.

start your free hunt

first hunt free · we never auto-apply · you stay in control

Common questions

Is QA a good way into tech without a degree?

Yes — it's one of the classic doors. Manual QA hires on rigor and communication; from there, learning automation moves you onto the engineering pay scale.

How much do QA engineers make?

Manual QA runs roughly $55k–$75k; automation engineers (SDET) run $85k–$130k+, with a US median around $90k for the field overall. The coding line is the pay line.

Will AI replace QA testers?

It's replacing rote test execution and generating test code. What it can't replace: judgment about what matters, empathy for how real users misuse things, and accountability for release quality. Automation-skilled QA engineers who direct AI are getting more valuable, not less.

QA engineer vs developer — can I switch later?

Yes, it's a well-worn path. QA teaches the codebase's weak points and the discipline of edge-case thinking; many developers and DevOps engineers started in QA.