JPJobPrepfull-stack interview
RoadmapsJS CompilerStar on GitHub
Career Roadmaps · QA Automation

Career roadmap

QA Automation Engineer

Replace manual regression with suites that run in minutes and are trusted enough to block a release.

Time
4-7 months part-time
Entry bar
Manual testing experience or a junior development background.
Stages
5 · 25 topics
0/25 studied0%
All roadmaps

Before you start QA Automation

  • Understanding of how web applications work
  • Willingness to write real code
  • Basic Git

Testing fundamentals

3-5 weeks · 0/5 topics

Automation without testing judgement just produces fast, useless tests.

  1. The vocabulary interviewers use, and the reasoning behind what to test.

    • Test levels: unit, integration, end to end
    • The test pyramid and its critiques
    • Black box, white box and grey box
    • Static versus dynamic testing

  2. Systematic techniques beat 'try things and see', and are directly interviewed.

    • Equivalence partitioning and boundary values
    • Decision tables and state transitions
    • Pairwise and combinatorial testing
    • Risk-based prioritisation

  3. Automation finds regressions; exploration finds the bugs nobody predicted.

    • Charters and time-boxed sessions
    • Heuristics and oracles
    • Note-taking and reproducibility
    • When exploration beats automation

  4. A bug report nobody can reproduce is wasted work, and this is assessed in interviews.

    • Reproduction steps that actually work
    • Severity versus priority
    • Evidence: logs, screenshots, network traces
    • Triage and duplicate handling

  5. Testing at the end is the most expensive place to find anything.

    • Shift-left and early involvement
    • Acceptance criteria and definition of done
    • Agile testing quadrants
    • Release and regression strategy

BuildWrite a full test plan for a real feature, including the cases you decided not to automate.

Programming for automation

5-6 weeks · 0/5 topics

Automation is software development. The code quality bar is the same.

  1. JavaScript/TypeScript, Python or Java. Pick the one your target employers use.

    • Language fundamentals and data structures
    • Async programming and promises
    • Error handling
    • Package management

  2. Unmaintainable suites get deleted. This is the main reason automation projects fail.

    • DRY without over-abstraction
    • Page object and screenplay patterns
    • Configuration and environment handling
    • Code review for tests

  3. Test code lives with product code and follows the same process.

    • Branching and pull requests
    • Reviewing test changes
    • Keeping tests alongside features
    • Handling merge conflicts in suites

  4. Understanding what developers test stops you duplicating it at the UI level.

    • Unit test frameworks and assertions
    • Test doubles: stubs, mocks, fakes
    • Integration test boundaries
    • Coverage and its misuse as a target

  5. Shared mutable test data is the most common cause of flaky suites.

    • Fixtures and factories
    • Isolation between tests
    • Seeding and cleanup strategies
    • Handling production-like data safely

BuildA small utility library with tests, packaged and versioned, before writing any UI automation.

UI and API automation

5-7 weeks · 0/5 topics

Build suites that are fast, stable and worth the maintenance they demand.

  1. Playwright has become the default. Auto-waiting removed most classic flakiness.

    • Locator strategies that survive refactors
    • Auto-waiting and explicit assertions
    • Fixtures, contexts and parallelism
    • Trace viewer for debugging failures

  2. Faster, more stable and more valuable per test than UI automation.

    • REST and GraphQL request testing
    • Schema and contract validation
    • Authentication in test suites
    • Testing error and edge responses

  3. A flaky suite is worse than no suite, and this is the most-asked interview topic.

    • Root causes: timing, state, order dependence
    • Detecting flakes systematically
    • Quarantine policy
    • Deterministic test design

  4. A distinct skill set with its own tooling and device constraints.

    • Appium and platform drivers
    • Device farms and emulators
    • Mobile-specific gestures and waits
    • Cross-platform test reuse

  5. Automated checks for things assertions cannot express.

    • Visual regression testing
    • Baseline management and review
    • Automated accessibility scanning
    • Integrating checks into the suite

BuildAutomate a real application's critical journeys and get the suite under ten minutes with zero flakes.

CI and quality engineering

3-5 weeks · 0/5 topics

A suite that does not run automatically on every change is documentation.

  1. Speed and reliability decide whether teams keep the gate or bypass it.

    • Pipeline stages and test selection
    • Parallelisation and sharding
    • Containerised test environments
    • Feedback time targets

  2. Failures that nobody investigates train the team to ignore red builds.

    • Readable failure reports
    • Artefacts: screenshots, video, traces
    • Trend and flake dashboards
    • Ownership of failures

  3. Environment instability is blamed on tests more often than it deserves.

    • Ephemeral environments per branch
    • Service virtualisation and mocking
    • Managing third-party dependencies
    • Environment parity

  4. Deciding what to automate and at which level is the senior part of the role.

    • Coverage of risk, not lines
    • Cost of maintenance per test
    • Deleting tests deliberately
    • Balancing suite levels

  5. Measuring quality without creating incentives to game the numbers.

    • Escaped defects and severity trends
    • Suite runtime and flake rate
    • Coverage as a signal, not a target
    • Reporting quality to stakeholders

BuildWire the suite into CI with parallelism, reporting and a policy for what blocks a merge.

Interview preparation

2-4 weeks · 0/5 topics

QA interviews mix test design questions with a live automation exercise.

  1. How would you test this. The oldest and most reliable QA question.

    • Designing cases for a described feature
    • Boundary and negative cases
    • Prioritising under time pressure
    • Explaining what you would not test

  2. Write automation live, usually against a public site or API.

    • Automating a flow from scratch
    • Handling waits correctly
    • Structuring for reuse
    • Basic algorithm questions

  3. The suite is flaky and the team stopped trusting it. What do you do.

    • Diagnosing flakiness systematically
    • Rebuilding trust in a suite
    • Arguing for time to fix tests
    • Handling a release with known bugs

  4. Direct questions on the framework the employer uses.

    • Playwright or Selenium specifics
    • Locator strategy trade-offs
    • Parallel execution mechanics
    • Reporting integration

  5. A public framework demonstrates code quality, which is what employers doubt.

    • Public automation repository
    • Documented design decisions
    • CI running on every push
    • A flakiness reduction case study

BuildA public automation framework with a README explaining the design decisions.

QA Automation tools on your CV

  • Playwright
  • TypeScript / Python
  • Postman / REST clients
  • GitHub Actions
  • Appium
  • Allure reporting
  • Docker

What QA Automation employers ask to see

  • A public automation framework with CI running
  • A suite runtime reduction with before/after numbers
  • A flakiness investigation and fix write-up
  • A written test strategy for a real product

Steady demand across product companies, service companies and regulated industries. Manual-only testing roles are shrinking; automation skills are what keeps the career growing.

Content last reviewed 2026-08-31. Guidance only — no institute or paid placement is endorsed anywhere in this book.