Topic 9 — Resumes and applications

Goal: Build a resume and application approach that gets you noticed.

Lesson 9.1 — The one job a resume has

Teodora Vrabie has a problem most career-changers know by heart. Her old teaching resume is two pages, and it opens with a line she's quietly proud of: "Dedicated educator passionate about lifelong learning." She's about to send it to Brightwell, a 40-person edtech startup, for a junior support-and-operations role. Before she does, she shows it to Renske Aldous, Brightwell's in-house recruiter, over a quick video call.

Renske reads the top, then looks up. "Teo, what do you want this piece of paper to do?"

Teo isn't sure how to answer. Tell them about her? Prove she's qualified?

"It has exactly one job," Renske says. "Get you a conversation. That's it."

That reframes everything. A resume is not your autobiography or a complete record of your working life. It's a focused marketing document with a single goal: earn the interview. Every line is either helping a stranger decide to talk to you, or it's taking up space. The "passionate lifelong learner" line isn't doing the job, so it can go.

A resume isn't there to get you hired. It's there to get you the conversation where you can get hired.

Once Teo holds that test in her head — does this line help me earn the interview? — the two-page document starts shedding weight on its own.

Lesson 9.2 — Six seconds and a robot

Here's the part that stings a little. Teo imagined a thoughtful person at Brightwell sitting down with a coffee and reading her resume top to bottom.

That's almost never what happens.

Two realities decide whether her resume survives. Renske walks her through both.

Reality one: it gets scanned, not read. An eye-tracking study by the careers site Ladders clocked recruiters spending an average of about 7 seconds on a resume during the first pass. Renske personally has 15–25 open roles at any moment and can get hundreds of applications for a single one. On that first sweep she isn't reading — she's scanning for a few signals, and if she doesn't see them fast, she moves on. So the most relevant things have to sit at the top, in plain text, easy to catch in one glance.

Reality two: a robot often looks first. Most mid-size and large companies run an ATS — Applicant Tracking System — software that ingests every resume, parses it, and lets recruiters search and rank by keywords. It's nearly universal at the top end: in a 2025 scan, an ATS was detected at 489 of 500 Fortune 500 companies (~98%) — and that's a floor, not a ceiling, since the handful not detected almost certainly run in-house or proprietary systems the scan couldn't see. A large share of applicants get filtered out before any human sees them, often for missing the exact terms the role was searching on.

Teo's reaction is the honest one: so I'm writing for a machine and a seven-second glance? Yes — and the good news is the same moves satisfy both. Front-load the relevant stuff, name things the way the industry names them, and keep the layout clean enough that software can read it.

Lesson 9.3 — Speaking the ATS's language

Bao Trinh, a senior PM at Brightwell who's become Teo's informal mentor, gives her the trick that finally makes the ATS feel beatable. "Put the job posting next to your resume," he says, "and read them like a matching game."

The move is mirroring keywords: use the exact skills and terms from the posting (and from your target role's normal vocabulary), in the words they use. If the listing says "customer support" and "Zendesk," don't write "client assistance" and "helpdesk software" — write customer support and Zendesk. The ATS is matching strings, not reading for vibes.

One keyword matters more than the rest: the target job title, near the top of the page. Title is one of the first things a recruiter searches by. Teo's last title was "Geography Teacher," which no one at Brightwell is searching for. So under her name she adds a clear line naming the role she's aiming at — "Customer Support / Operations — Career Changer (ex-Educator)" — so both Renske's search and the ATS find her.

This is also why one generic resume sprayed everywhere quietly fails: it's tailored to no one, so it mirrors no posting well. Tailoring measurably lifts your results.

Two layout rules keep the parser happy:

• Standard headings — Experience, Skills, Education. The ATS knows these words; it may choke on "My Journey."
• No text trapped in images, text boxes, or fancy tables. A pretty two-column template can look great to you and arrive as scrambled gibberish to the software. A simple, single-column layout parses cleanly.

Tailor for the human in seven seconds and for the robot that never blinks. The same clean, keyword-honest resume serves both.

Lesson 9.4 — Achievements, not duties

Teo's first draft of her experience section reads like her old job description: "Responsible for lesson planning." "Responsible for parent communication." "Responsible for grading."

Renske circles all three. "These tell me what you were assigned. Show me what you changed."

That's the difference between a duty and an achievement. A duty is the task. An achievement is the result, ideally with a number on it. Compare:

• Responsible for reports → Reduced weekly reporting time by 40% by building a shared tracking spreadsheet

The second one proves impact, and a number is the single easiest thing to catch in a seven-second scan. So Teo rewrites. "Responsible for parent communication" becomes "Managed weekly communication with 120+ families, resolving concerns and keeping satisfaction high across the year." Same true facts — now it reads like results.

A simple shape helps every bullet: strong verb + what you did + the outcome (with a number where you honestly have one). Built, led, cut, grew, launched, resolved — not responsible for, not helped with. And not every line needs a perfect statistic; "120+ families" and "across two grade levels" are real, honest numbers that still land. Invented metrics, on the other hand, fall apart the moment someone asks about them in the interview.

Lesson 9.5 — Reframing a whole career

Teo's deepest fear: my experience is in a different world entirely. Why would an edtech startup care that I taught geography?

Davor Halász, a friend one step ahead of her — an ex-accountant now working as a junior data analyst — pushes back hard. "I thought the exact same thing about spreadsheets and audits. The work transferred. I just had to translate it."

That translation is reframing transferable experience: describing what you actually did in the language of the target role. A teacher doesn't write "taught geography." A teacher writes:

• Explained complex concepts clearly to non-expert audiences (every lesson, every day)
• Managed stakeholders — students, parents, and administrators with competing needs
• Used data to track progress and adjust based on what the numbers showed
• Ran a "room" of 30 daily — comfortable owning outcomes under pressure

None of that is invented. It's Teo's real teaching career, said in words Brightwell recognizes. For a career-changer, demonstrable skill usually outweighs your past title — so she pairs the reframe with proof: the role's coursework she's finished, plus a small portfolio project (a mock support-ticket triage she wrote up) that shows the skill rather than just claiming it.

She also runs the whole thing through one last filter, and it's not optional. One page. No typos. For a lot of tech roles the resume is a work sample — a live demonstration of how she communicates and how carefully she checks her own output. A single sloppy typo can read as "doesn't proofread," and that's enough to get cut. Marisol Ferreira, Brightwell's founder and herself an ex-teacher, puts it bluntly to her team: the resume is the first thing they'll ever ship me. So Teo reads hers out loud, backwards, and has Davor check it too.

Lesson 9.6 — Applying like it's a process

Resume sharp, Teo's instinct is to fire it at every open tech job she can find. Davor talks her down.

"I sent 200 generic applications and got nothing," he tells her. "Then I sent 15 tailored ones and got four replies. Quality, not spray."

This is quality over quantity. A small number of tailored, thoughtful applications beats a generic resume blasted at hundreds of postings. And the single strongest combination is the one from Topic 8: a referral plus a tailored resume. A warm introduction from someone inside often skips the ATS pile entirely and lands you in front of a human — which is exactly why Teo built relationships before she needed them.

A few habits make each application count:

• Add a short, genuine cover note when it fits. Two or three honest sentences: why this role, and what you uniquely bring. Specific, not a generic template. ("I'm an ex-teacher moving into support, and Brightwell building for schools is exactly the bridge I want" beats "I am a hardworking team player.")
• Don't over-filter yourself out. Postings are wish-lists, not checklists. If you meet the core must-haves and you're excited about the role, apply — let them decide. Plenty of great hires didn't tick every box. (Davor's analyst posting "required" a tool he'd never opened. He learned it in a weekend after they made the offer.)
• Track everything. A simple spreadsheet — role, date, whether you had a referral, the outcome — turns the search from a fog into a diagnosable process.

That tracker is what lets you fix the right thing, which is the next lesson's whole point.

Worked example — Teo's two weeks, in the tracker

Brightwell posts a "Customer Support & Operations Associate" role. Watch Teo run the full play.

She reads the posting beside her resume and mirrors its language: customer support, Zendesk, cross-functional, onboarding. Under her name she puts the target title, Customer Support & Operations, so Renske's search and the ATS both find her. Her experience section now leads with achievements — "Managed weekly communication with 120+ families", "Cut grading turnaround by building a shared tracker" — every geography duty reframed into support-and-ops language. One page, single column, standard headings. She reads it backwards for typos.

Because of Topic 8, she has a real connection: Bao agrees the role fits and refers her internally. She attaches a three-sentence note on why Brightwell specifically. Then she logs it in her tracker: Brightwell — Support Assoc — referral: yes — applied Jun 3.

Two weeks later her tracker tells a story. Of 12 tailored applications, she's had 3 recruiter screens — including Renske's. That ratio means her resume and targeting are working; if it had been 0 of 12, the fix would be the resume, not her interviewing. The diagnosis lives in the data, which is the entire reason she tracked it.

Renske, on her side, pulls Teo's resume out of the Brightwell ATS in about seven seconds flat. The target title is right there. The keywords match. The numbers jump out. The referral flag is on. She books the screen.