Getting Hired: Portfolio, Resume, and the Honest Market

You now know more testing theory than many working testers. The market doesn't hire theory — it hires evidence. And here's the news that makes QA unusually kind to newcomers: unlike most tech roles, testing lets a beginner manufacture evidence — real bug reports on real products, visible test design, a portfolio that does the interview's heavy lifting before you say a word. This is the chapter you bought the book for; this page turns eleven chapters of skill into hirable proof.

The chef's audition is the frame. Culinary school on the resume opens the door; the tasting plate gets the job. QA is rare in tech because you can cook the tasting plate at home, tonight, using any restaurant's ingredients — any public product is your kitchen.

The Junior QA Market, Honestly

No sugar. Entry-level QA is competitive — many applicants, and "junior" postings that list senior wish-lists. It's also real: once you're in, the field has steady demand and clear growth (Chapter 9 mapped the paths). Two honest decodings. First, postings are wish-lists, not requirements — "automation experience preferred" on a junior role usually means "willing to learn," and the evidence-bearing candidate beats the checkbox-matcher who applied to nothing they didn't fully match. Second, junior roles hide in specific places: support-to-QA transitions (companies promote support staff who show testing instinct), and domain-heavy industries (finance, healthcare, logistics) that will train testers who know the domain. Apply wider than your comfort, and apply as the candidate with a tasting plate.

The Portfolio That Works

Four artifacts, each mapped to a skill it proves — and every one of them is something you built at Fernway, now reproduced on a real public product:

A public bug report — the FW-312 anatomy on a real open-source or public product (bug bounty platforms are one venue, with Chapter 10's disclosure etiquette). A test-design document — partitions, boundaries, and a decision table for any real app's feature: literally the SUMMER15 workup applied to, say, a food-delivery app's promo code. An exploratory session — a charter and its notes (Chapter 7). And a one-page release report — covered, found, risks, on a product you spent an evening testing. Four artifacts, each proving a distinct competence, none requiring a job to produce.

The Resume Without Experience

The trick is translation: convert course competence into honest, demonstrable claims. "Designed test cases using equivalence partitioning and boundary value analysis" — true, and you can prove it on the spot. "Wrote structured bug reports with reproduction steps and evidence" — true, portfolio attached. What dies in one interview question: padding you can't back up ("expert in Selenium" when you've read about it). The honest version is stronger anyway, because every claim survives the follow-up. And certification — ISTQB Foundation, evaluated honestly, exactly as promised at the book's start: it's a real signal in Europe and at testing agencies, a shrug in much of US product hiring, and never a substitute for the portfolio. Worth it if employers in your market and region ask for it — check actual postings before spending the money and time. It's a door-opener in some doorways and invisible in others; the tasting plate opens all of them.

Where to Apply the Craft First

A concrete two-week plan to build the kit from zero. Days 1–3: pick a public product you use (a to-do app, a small open-source tool) and run a test-design doc on one feature — partitions, boundaries, a decision table. Days 4–7: test it for real, file two or three genuine bug reports (to the project's tracker if open-source, with the FW-312 anatomy). Days 8–10: run a 90-minute exploratory charter, keep the notes. Days 11–14: write the one-page release report tying it together, and translate all of it into resume bullets. Two weeks, four portfolio pieces, zero permission needed — because the market's one law is simple: evidence beats claims, and one great public bug report outweighs a paragraph of self-description every time.

Fernway, Turned Inside Out

Here's the book's quiet device, finally revealed. Everything you "built" at Fernway is the portfolio template. FW-312's bug report — that's the bug-report artifact. The SUMMER15 decision table — the test-design doc. The 90-minute modification charter that found FW-372 — the session notes. The Friday one-pager — the release report. The fiction was a rehearsal; the assignment is to run it once more on a real product, and the fiction becomes your resume. You didn't just read about a QA engineer's first year — you assembled, page by page, the exact evidence that gets a QA engineer hired. Now go produce it in the real world, where the tracker is real and the byline is yours.