QA Engineer Bootcamp — Program
QA Engineer Bootcamp — Program
A paced, ~9-week program that turns the QA path from a self-serve course into a bootcamp: it sequences the lessons (Topics 1–10), the capstone deliverables (real QA artifacts, AI-reviewed against rubrics), the interview drills, and career services into one journey with weekly milestones.
It's self-paced — the weeks are a recommended rhythm (roughly 5–8 focused hours each), not hard deadlines. Your capstone is fixed: across the whole program you own QA for one feature area — the checkout-and-promo-code flow of ShopSphere (see capstone/capstone.md) — and every deliverable builds on the same feature, so the work forms one coherent, portfolio-ready story.
Core program (Weeks 1–9)
| Week | Learn (topics) | Capstone deliverable | Interview practice | ~Hours |
|---|---|---|---|---|
| 1 | Topic 1 (What is QA?), Topic 2 (QA roles and terms) — (+ general Core Tech Baseline alongside) | — | QA Fundamentals (D1–D3) | 5 |
| 2 | Topic 3 (The software development and testing lifecycle), Topic 4 (Types of testing) | (read the capstone brief; review the spec & raise risks — "shift left") | QA Fundamentals (D4–D6) + Behavioral & Collaboration (D1–D2) | 6 |
| 3 | Topic 5 (Writing test cases and test plans) | D1 — Risk-based test plan for the checkout release | Test-This-Scenario (D1–D2) | 7 |
| 4 | (Topic 5 applied — deepen test-case craft) | D2 — Test-case suite for the promo-code & checkout flow | Test-This-Scenario (D3–D4) | 8 |
| 5 | Topic 6 (Finding and reporting bugs), Topic 7 (Test design techniques) | D3 — Test-design coverage matrix (equivalence & boundary) | Bug Reporting & Quality (D1–D3) | 7 |
| 6 | Topic 8 (Bug tracking and test management tools) | D4 — Professional bug report pack | Bug Reporting & Quality (D4–D6) + Mock-interview checkpoint #1 (QA fundamentals + test-this-scenario) | 7 |
| 7 | (Topic 8 applied — execution & reporting in TestRail/Jira) | D5 — Test execution & release sign-off report | Behavioral & Collaboration (D3–D5) | 6 |
| 8 | Topic 9 (An introduction to automation and APIs) | D6 — API smoke-check notes for the promo endpoint | Automation & API Awareness (D1–D4) | 7 |
| 9 | Topic 10 (Landing the QA job) + general Employability & Job Hunting | Assemble the portfolio (all 6 deliverables) | Mock-interview checkpoint #2 (full mock across all five banks) + career services (below) | 8 |
By the end of Week 9 you have: the full curriculum learned, a 6-artifact QA portfolio for one feature (test plan → test cases → coverage matrix → bug pack → sign-off report → API checks), repeated interview practice across all five drill banks, and your resume/LinkedIn ready.
Career services (lite)
Delivered mainly in Week 9, drawing on the general Employability & Job Hunting track (content/general, Topics 6–10). These are self/AI-reviewed against rubrics (no human mentor required).
Resume review rubric
Model "Excellent (3)" resume bullets (built from the ShopSphere capstone — aim for this, don't copy it verbatim). A "Projects" or "QA Experience" entry titled ShopSphere — Checkout & Promo-Code QA (capstone) with bullets like:
- Owned QA end-to-end for the checkout-and-promo-code release: authored a risk-based test plan and a 42-case test suite covering equivalence classes and boundary values across cart, promo, and payment.
- Caught 9 defects pre-release, 2 Critical money-path — including a promo code that stacked on an already-discounted total (revenue leak); filed reproducible reports with severity/priority and made the go/no-go call to hold the build until both were fixed.
- Ran a smoke check on the promo API endpoint (status codes, schema, invalid/expired-code paths) and a release sign-off report, cutting regression re-test time ~30% by prioritizing high-risk paths first.
- Tools: Jira, TestRail, Postman; STLC, bug life cycle, regression, exploratory & boundary testing.
Why this is a 3: every bullet leads with an outcome and a number, uses real QA vocabulary, and points to a named, linkable artifact instead of describing duties.
- Outcome-focused bullets — 1: duties only · 2: some results · 3: quantified outcomes ("caught X critical defects pre-release", "cut regression time by Y%").
- QA vocabulary & relevance — 1: generic · 2: some QA terms · 3: clearly reframed for QA (test plans, test cases, bug life cycle, severity/priority, regression, STLC).
- Portfolio linked — 1: none · 2: mentioned · 3: linked and tailored — the ShopSphere artifacts (test plan, bug reports, sign-off) shown and tied to the role.
- Clarity & format — 1: cluttered/typos · 2: clean · 3: crisp, one page, scannable in seconds. (See general Topic 9 — Resumes and applications.)
LinkedIn review rubric
Model "Excellent (3)" LinkedIn headline + About (built from the ShopSphere capstone — adapt it, don't paste it).
Headline:
Aspiring QA Engineer | manual & API testing | ShopSphere checkout portfolio | ex-[your field]
About:
I'm transitioning into QA, where my [retail / support / ops] background — spotting the edge case everyone else misses and caring about the customer's actual experience — is an asset on day one.
In my capstone I owned quality for ShopSphere's checkout-and-promo-code release end-to-end: a risk-based test plan, a 42-case suite, and bug reports written so a developer can reproduce them in one read. During execution I caught a Critical money-path defect — a promo code stacking on an already-discounted total — and made the go/no-go call to hold the release until it was fixed.
I work in Jira, TestRail, and Postman, and I think in test design, severity/priority, and the bug life cycle. Portfolio (test plan → test cases → coverage matrix → bug pack → sign-off → API checks): [link]. Open to junior QA Engineer / QA Analyst roles — let's connect.
Why this is a 3: the headline names the target role plus a concrete portfolio hook; the About tells the pivot story (where heading, what you bring, proof) and lands on the same named artifact, Critical defect, and go/no-go call as the resume — one coherent story.
- Headline signals target role — 1: old title only · 2: mentions QA · 3: clear target + value ("Aspiring QA Engineer | ex-[field] | manual & API testing").
- About tells the pivot story — 1: empty/generic · 2: present · 3: confident pivot story (where heading, what you bring, why, proof).
- Skills & proof — 1: none · 2: some · 3: QA skills listed (test design, bug reporting, Jira/TestRail, API basics) + portfolio/projects shown.
- Activity — 1: inactive · 2: occasional · 3: connecting/engaging with the QA community. (See general Topic 7 — A standout LinkedIn profile, and Topic 8 — Networking in tech.)
Mock-interview checkpoints
Use the AI mock interview (interview/mock-interview.md): Checkpoint #1 (Week 6) — QA fundamentals + test-this-scenario; Checkpoint #2 (Week 9) — a full mock spanning all five banks (qa-fundamentals, test-this-scenario, bug-reporting-and-quality, behavioral-and-collaboration, automation-and-api-awareness). Track which rubric criteria you repeatedly miss and focus there. (See general Topic 10 — Interviewing and landing the offer.)
Salary-negotiation practice
A short, hands-on drill built on a concrete offer so you negotiate like a QA Engineer, not from a generic script. The AI role-plays the recruiter and gives feedback against the rubric below.
The sample offer (work with this one):
Junior QA Engineer, mid-size US SaaS company (~200 people, hybrid). $62,000 base, 0.02% equity, standard benefits. Verbal offer on the phone; recruiter asks "does that work for you?"
Step 1 — Buy time (don't accept on the call). Say: "Thank you, I'm excited about the team. Can you send the details in writing? I'd like to review the full package and get back to you by [Thursday]." Never negotiate a number you heard 30 seconds ago.
Step 2 — Anchor on a real market range, not a feeling. Pull an actual range before you counter:
- Levels.fyi → search "QA Engineer" / "Quality Assurance", filter to entry / L3 / Junior and your metro (e.g., Austin, Remote-US). Note total comp and base.
- Glassdoor (or LinkedIn Salary / Built In) → "QA Engineer" salaries, filter by region + 0–2 yrs experience, and read the base-pay distribution, not just the headline average.
- Triangulate across both, then write down a defensible band — e.g., for a US junior QA role you might land on $64k–$72k base. Use your own current numbers; the band below is illustrative.
- Sanity-check against the offer: $62k sitting below the bottom of your band is your strongest, most factual lever.
Step 3 — Counter with a value-anchored script that cites your ShopSphere capstone. Tie the ask to a specific artifact and decision you actually produced, then to the market band:
"I'm really keen to join. In my capstone I owned QA for ShopSphere's checkout-and-promo-code release end-to-end — I built the risk-based test plan and test-case suite, and during execution I caught a Critical money-path defect (a promo code stacking on top of an already-discounted total) before release and made the go/no-go call to hold the build until it was fixed. Based on that hands-on experience and a market range of $64k–$72k for junior QA in this region, I'd like to discuss a base of $68k. Is there room to move there?"
Swap in your real defect and your real range. The pattern is fixed: proof (named artifact + severity + the call you made) → market band → specific number → open question.
Step 4 — Evaluate the whole offer, not just base. If base won't move, negotiate the levers that often can: sign-on bonus, an earlier (3- or 6-month) salary review, learning budget (a TestRail/ISTQB or automation course), title (QA Engineer vs. QA Analyst), or remote/hybrid days. Then weigh growth: is there a path to mid-level QA / SDET, mentorship, and ownership of a real test suite? A slightly lower base with a clear ramp can beat a higher one with none.
(Topic 10 + general Topic 10.)
Salary-negotiation rubric
- Anchored on a real range — 1: a vibe or a number with no source · 2: one source, no level/region filter · 3: a defensible band from ≥2 sources (Levels.fyi + Glassdoor/LinkedIn) filtered to junior QA + your region, with the offer compared against it.
- Value tied to QA artifacts — 1: generic "I work hard" · 2: mentions QA in the abstract · 3: cites a named ShopSphere artifact and outcome (Critical money-path defect caught pre-release, the go/no-go call) as the reason for the number.
- Counter is specific and collaborative — 1: no counter or "give me more" · 2: a number but no framing · 3: proof → band → one concrete number → open question, delivered politely with a path to yes.
- Whole-offer evaluation — 1: base only · 2: notices benefits exist · 3: trades across base / sign-on / review timing / learning budget / title / remote and weighs growth and fit.
How it fits together
Lessons teach the concept → the matching capstone deliverable makes you do it on the ShopSphere checkout (and the AI reviews it against the rubric) → interview drills rehearse explaining it out loud → career services package it for the job hunt. That loop — learn, do, get feedback, present — is what makes this a bootcamp rather than a reading list.