Zum Inhalt springen

FieldsSoftware DevelopmentQA Engineer

QA Engineer

Design the tests that catch failures before users do.

Career

Structure
8 modules, each ending in a milestone
Proof
Verified against real tasks from module 2
Ends in
A defended capstone and a high-assurance credential

Get early access

The journey

  1. Practised under observation

    1. The verification mindset and quality fundamentalsWhat quality assurance actually is: the mindset, the vocabulary, and the disciplined curiosity that finds what others walk past.Practised under observation
      MilestoneFinds what matters, reports what's real

      A defect report is complete when someone else reproduces it from your steps alone, first time, without asking you anything.

  2. From here, milestones are verified rather than practised.

    Verified against a real task

    1. The system under testYou cannot verify what you cannot dissect, so the web platform is read fluently and a first automation language is taught from zero.Verified against a real task
      MilestoneDissects the system, speaks the language

      You read the page, the traffic and the console rather than guessing, a symptom lands in its own layer, and the fix starts in the right place.

    2. Test design and manual testing as engineeringThe intellectual core: tests designed against risk, coverage claimed honestly, and manual testing executed as engineering rather than clicking.Verified against a real task
      MilestoneDesigned against risk

      Every test case comes from a technique you can name, and what the design leaves untested is stated rather than discovered later.

    3. Automation engineering: the interface seatTest code is production code, built to survive change, with the flakiness war fought at root cause.Verified against a real task
      MilestoneAutomation that survives

      Automation survives the refactor that breaks naive selectors, and a flaky test is taken to its root cause rather than re-run until it passes.

    4. Automation: API, integration and mobile seatsVerification below the pixels, with contracts checked where checking is cheapest and services exercised in combination.Verified against a real task
      MilestoneVerified at the right layer

      The same failure is caught at the cheapest layer that can catch it, contracts are checked where checking is cheap, and a stand-in never hides the thing it was meant to isolate.

    5. Non-functional verification: performance, accessibility and security testingThe truths beyond it works: load read honestly, accessibility verified with real assistive technology, and security probed ethically.Verified against a real task
      MilestoneThe hard truths, measured

      Load results name a bottleneck rather than present a graph, and what an automated audit or an authorised probe misses is found by a person rather than assumed absent.

    6. Quality in the pipeline: CI/CD, monitoring and quality signalsVerification as infrastructure, wired into delivery gates, with results humans actually read and quality watched into production.Verified against a real task
      MilestoneThe gate and the watchtower

      A failing check stops the change rather than a person remembering to look, a quarantined test keeps its ticket and its owner, and the dashboard tells a stranger the product's state in about a minute.

    7. The QA Engineer in the organization: strategy and quality leadershipFrom tester to quality leader, with the release call made on evidence under pressure.Verified against a real task
      MilestoneThe quality leader

      The release call is made on evidence, and no is a sentence you can say to people who do not want to hear it and still be in the room afterwards.

    1. Capstone

      Confidence, manufactured end to end

      A complete quality engineering engagement on a real product, built under observation, from a risk-driven strategy through layered automation and non-functional verification to a release call made on evidence.

      Defence

      You walk an instructor through your own strategy: why this shape for this product rather than a template, what it deliberately does not cover and why that risk is acceptable, where your suites would still miss something, and what would make an organisation stop trusting a green result from you. The credential is not awarded if you cannot account for your own work.

    2. Credential

      High-assurance credential

      Evidence that you can manufacture confidence an organisation will bet a release on. It does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works

Related capability paths

What is not live yet

The desktop app, consent-based observation, scoring, and credentials are in development. Nothing here implies they are live yet.

Get early access