Software Engineering · QA / Test Engineering

QA Engineer

Break it before users do — test cases, bug hunts, and the automation that keeps releases safe.

QA TesterManual QA AnalystJunior QA EngineerSoftware Test EngineerQuality Assurance Analyst
$102,610 median · +15% — counted in the same fast-growing group as software developers
~$55,000–$70,000 to start (manual QA — industry figure, not BLS). U.S. BLS figure for Software Quality Assurance Analysts and Testers (15-1253); a median is the midpoint of everyone employed, so entry pay runs lower — the entry range here is an industry estimate, not BLS. Verify against the live BLS page before deciding.
Is this you? Take the free assessment

What you actually do

You make sure software actually works before it ships. Day to day you write and run test cases, reproduce bugs until you can hand a developer exact steps, do exploratory testing on new features, and re-run regression checks before every release. It's one of the more accessible software rungs: manual QA is self-study viable and doesn't require heavy coding to start. The career, though, grows through automation — Selenium, Playwright, Cypress — and toward SDET, where testing becomes an engineering discipline of its own.

  • •Run the regression checklist against last night's build and log anything that broke
  • •Reproduce a customer-reported bug until you can write exact steps a developer can follow
  • •Exploratory-test a new feature, probing edge cases the requirements never mentioned
  • •Write and update test cases as the sprint's stories change underneath you
  • •Flag a release risk in standup that nobody else has noticed yet

What the work feels like

CommunicationHigh
Technical depthMedium
TroubleshootingHigh
Customer contactLow
On-callLow
Remote-friendlyVery high

This fits you if…

  • ✓You instinctively poke at things to see how they break
  • ✓You like methodical, checklist-driven work with visible results
  • ✓You want a software career without starting from heavy coding

Less ideal if…

  • −You need to build features to feel satisfied — finding flaws in others' work grates on some people
  • −You dislike repetitive, detail-heavy tasks
  • −You'd rather avoid delivering critical feedback, sprint after sprint
The honest downsides: QA is often treated as lower-status than development, and pay lags dev until you automate. Release weeks bring crunch, regression testing is genuinely repetitive, and there's steady pressure to move from manual testing into automation faster than you may feel ready for.

Skills to build

Testing fundamentals (test cases, test plans, coverage) Foundational How to turn 'does it work?' into a repeatable, reviewable process.
Bug reporting & reproduction Foundational Exact steps, expected vs. actual, environment — a great bug report is your calling card.
Exploratory & regression testing Foundational
SQL & API testing basics Working Check the data behind the screen; poke APIs with Postman.
Test automation (Selenium / Playwright / Cypress) Working The skill that moves you from tester to engineer — and raises pay.
CI/CD & version control basics Working
Programming (JavaScript / Python / Java) Emerging The SDET track — building full automation frameworks — runs on real code.
Jira / Azure DevOpsTestRail / ZephyrPostmanPlaywright / CypressSeleniumGitSQLChrome DevTools

Your roadmap

An ordered path from beginner to employable. Certifications are optional checkpoints, not the point — skills and a portfolio are.

  1. 1
    Learn how testing works

    Test-case design, the bug lifecycle, and where QA sits in the software process — free via Test Automation University and Ministry of Testing. Practice on demo apps built to be tested.

  2. 2
    Build a public portfolio

    Write real test plans and bug reports against open-source or practice apps and put them on GitHub. This is your resume — manual QA hiring runs on demonstrated craft, not credentials. Add ISTQB CTFL if listings in your market ask for it.

    Study guide: ISTQB Certified Tester Foundation Level →
  3. 3
    Land manual QA and learn the product

    Get in as a tester, master the domain, and quietly add SQL and API testing (Postman) — the skills that separate you from checklist-only testers.

  4. 4
    Automate

    Pick Playwright or Cypress, learn enough JavaScript or Python to be dangerous, and automate your own team's most repetitive regression checks. Pay and status both move here.

  5. 5
    Grow toward SDET

    Build test frameworks, wire tests into CI/CD, and own quality as an engineering problem — or use the coding base to branch into development outright.

Certifications for this path

A facet of the path, not the path itself — skills and a portfolio come first.

Honest priority check: a public portfolio of real test plans, sharp bug reports, and one small automation project beats any QA cert on a resume. ISTQB CTFL is an optional filter-passer, not a requirement.
ISTQB Certified Tester Foundation Level Optional signal

The one QA credential hiring managers recognize worldwide — lifetime validity, and it formalizes the vocabulary of the craft.

View study guide →

Try it this weekend

Do the actual job for an evening: pick a public website, try to break it methodically, and write up what you find as professional bug reports.

Free 60–90 minutes Just a browser and a text editor — everything stays on your machine, submit nothing, contact no one. You're practicing the write-up, not reporting real bugs.

Related paths

Software Developer →

Automation skills turn QA into SDET and open the dev door.

 IT Project Coordinator →

QA discipline and requirements-thinking transfer directly into coordination and BA work.

Not sure this is the one?

Take the free 10-minute assessment and see your three strongest IT paths.

Take the IT Career Navigator →