Engineering and IT · Job description template

QA Engineer job description template

When a team ships quickly, bugs reach customers unless someone owns quality on purpose. The QA engineer sets the test strategy, builds automated checks and helps developers test their own work. They are accountable for the team knowing, before each release, what has been tested and what risk remains.

First-year outcomes

What should be visibly different a year from now. Results, not tasks.

  • A written test strategy, agreed with the engineering lead, says what is tested by unit, integration, end-to-end and manual tests for each part of the product.
  • The ten most important user journeys have automated regression tests that run on every pull request and finish in under 15 minutes.
  • Bugs found by customers after release fall by at least 40 percent compared with the first quarter, counted in the bug tracker.
  • Every release has a short sign-off note listing what was tested, known issues and any accepted risk.

The work

Recurring work

  • Review new features early and write test cases with the developer before coding ends.
  • Write and maintain automated tests for key journeys.
  • Run exploratory testing on risky changes before release.
  • Triage incoming bug reports, reproduce them and set severity.

Projects

  • Write and roll out the test strategy.
  • Build the automated regression suite and connect it to the build pipeline.
  • Set up reliable test data and test accounts for staging.

Decisions they own

  • The severity of a bug and whether it should block a release.
  • Which journeys are covered by automation and which by manual checks.
  • When a flaky test is removed or quarantined until fixed.

People they work with

  • Developers, to agree what each change needs tested and to pair on tests.
  • The product owner, to understand which journeys matter most to customers.
  • Support staff, to learn which problems customers hit and how to reproduce them.

Requirements

Essential on day one

  • Has planned and run testing for a web or mobile product that real customers used.
  • Can write automated tests in code with a tool such as Playwright, Cypress, Selenium or Appium.
  • Writes clear bug reports with steps, expected and actual results.
  • Understands how to test an API directly, for example with Postman or code.

Helpful, but can be learned

  • Your product domain and business rules.
  • Performance and load testing tools.
  • Your build pipeline and how to run tests in it.

How to assess it

One piece of evidence for each first-year outcome.

OutcomeEvidence to look for
Written, agreed test strategyAsk them to outline a test strategy for a small product you describe. Good answers balance unit, integration and end-to-end tests and explain why.
Automated regression for ten key journeysAsk for a sample of automated tests they wrote, or have them write one for a login page. Good tests are readable, stable and do not rely on fixed waits.
Fewer customer-found bugsAsk about a time they reduced escaped bugs. Good candidates show how they found the gap and what changed in the process.
A sign-off note for every releaseAsk them to write a sign-off note for a release with one known bug. Good notes are short, honest about risk and clear on what was not tested.

Opening for the job ad

You will own how our team tests software and decides a release is ready. In your first year, we should have a clear test strategy, automated checks on our most important journeys and far fewer bugs reaching customers.

Turning this into an ad? See how to write a job ad that gets applicants.

Next: interview for these outcomes

Eight structured questions for this role, each tied to an outcome above.

QA Engineer interview questions

Similar roles

Your next hire, start to finish, in one place.

Free workspace. No card. Full scoring free for 7 days.