anjela. Start 1/11

00 Start

A recruiter gives your resume 6 seconds. AI will give it as long as you need

Let it look with the same eyes — and say out loud what a recruiter usually only thinks.

I've hired performance marketers by the hundreds — 500+ people, easily. And here's what that taught me: candidates get rejected less often because they lack experience, and more often because that experience is written in words that say nothing — "responsible," "team player," "good communicator." A resume like that gets closed halfway through the first paragraph.

Next up: 6 prompts. Together they cover the whole distance from "resume gets zero replies" to "answering tricky questions with confidence" — first a brutally honest read of your current resume, then rebuilding it around numbers, then checking it against a real posting and building three summary versions, then prepping for specific questions, then a hard mock interview with the same interviewer persona.

What you'll walk away with

How this page worksOne screen, one action. Your answers are saved in your browser and drop themselves into the prompts. Map (☰) up top, arrows ← → flip through steps.

00 Start

A "good resume" and a resume that actually gets a call are different texts

The difference isn't formatting. It's whether the text answers the one question a recruiter is actually asking.

Resume-as-descriptionResume-as-evidence
"Responsible for company social media"
"Grew reach from 4K to 60K in 5 months, running the account solo"
The recruiter has to guess whether that's good or not
The recruiter sees the scale instantly, no guessing needed
Reads like a job description
Reads like a result they could get too

A recruiter doesn't really read a resume — they scan it for proof that you've already produced this result before. Prompt one shows you exactly where that proof is missing. Prompt two writes it in.

01 Resume

What role are we aiming at?

Write it the way the job posting words it — we'll reuse those exact words in the prompts.

Your context · building
Role: [ROLE]. Industry: [INDUSTRY].

01 Resume

Prompt 1 — resume audit through a recruiter's eyes

Open your resume in another tab and copy the full text — you'll need it now.

Prompt · audit
Here's my resume: [paste resume text].

Act as an HR recruiter in the [INDUSTRY] field who screens 200 resumes a day for a "[ROLE]" role. Look at mine and answer:
— What catches your eye in the first 6 seconds?
— What raises doubt?
— Which phrases sound empty ("responsible," "team player," "good communicator")?

Score the resume out of 10 and explain each point.

Brace yourself: this is usually more honest than feedback from an actual recruiter friend — AI isn't worried about hurting your feelings. If it goes easy on you, say so directly: "don't hold back, score it like you've got 300 resumes in the queue and I'm not your friend."

Why 6 seconds specificallyThat's not a figure of speech — it's the average first-look time recruiters actually spend. In that window they read the top third of the page. If there's not a single number or concrete result there, they don't read any further.

01 Resume

Prompt 2 — rewrite bullets into results

Every duty turns into evidence through the same formula.

WHAT YOU DID "handled marketing" RESULT "launched 3 campaigns" IN NUMBERS 1,200 leads, $80k budget Every bullet goes through all three stages — not just the headline
The formula for turning a duty into evidence: the recruiter sees scale, not a job description.
Prompt · rewrite
Take every bullet in my experience and rewrite it using the formula: [what I did] → [what result] → [in numbers].

Example: not "handled marketing," but "launched 3 ad campaigns that generated 1,200 leads on an $80k budget."

If there are no numbers, suggest which metrics I could add and help me phrase them.

That last line matters most. Most people don't have exact figures on hand, and that's fine — AI will point to where those numbers could plausibly live ("how many people were on the team," "how much faster did the process get," "how many clients did you serve per month") — and you'll recall the rough order of magnitude yourself.

Outcome of this step

A resume where every bullet is evidence of a result, not a description of a role. Same experience, different framing.

01 Resume

Prompt 3 — ATS match against a real posting

One resume, many postings — checking the match for each one is cheaper than rewriting the whole resume from scratch.

Most large companies run resumes through an ATS (Applicant Tracking System) — software that scans the text for a match against the posting — before a human ever sees it. A resume can be beautifully rewritten around results and still fail that filter if it's missing the right words.

Prompt · ATS match
Here's the job posting I'm applying to: [paste posting text].

Here's my resume, already rewritten around results: [paste the resume from the previous step].

Act as an ATS (Applicant Tracking System) that scans resumes before a human sees them. Compare my resume to the posting and show:
— a keyword/skills match percentage,
— specific words from the posting missing from my resume — worth adding verbatim if they're actually true for me,
— which requirements in the posting my resume doesn't cover at all.

Don't rewrite the resume for me — just show the gaps, I'll fill in the wording myself.

If the percentage is low, don't panic yet. Often it's not the experience, it's the words: the posting asks for "project management," the resume says "task coordination" — same thing to a human, not to an ATS.

Why run this per postingThe same experience sounds different in the language of different postings. The check takes 30 seconds of copy-paste — cheaper than applying and never finding out why you got no reply.

01 Resume

Prompt 4 — three versions of the same resume

The same resume shouldn't sound identical to a filter, a human, and a startup.

An ATS looks for keywords. A live recruiter looks for a story that's easy to retell. A small-company founder looks for someone who can cover three roles at once, not one narrow one. Three audiences read the same text with three different questions in mind — the summary at the top is worth adapting for each.

Prompt · three summaries
Build three summary versions (2-3 sentences at the top of the resume) based on my rewritten experience: [paste resume].

1) For the ATS filter — as many exact keywords from the "[ROLE]" posting in [INDUSTRY] as possible, formal tone, no metaphors.

2) For a human reading the resume — natural, human, leading with the result that's clear without extra context.

3) For a startup — foreground that I can cover several roles at once and own outcomes, not just tasks.

Each version — no more than 3 sentences.
Which one goes whereThe ATS version for job-board application forms. The human version for a direct message to a hiring manager or a referral. The startup version for small teams and early-stage companies where one person covers several areas.

02 Interview

Prompt 5 — 15 questions worth prepping for

The goal isn't memorizing answers — it's understanding what each question is actually testing.

Prompt · prep
I'm interviewing for a [ROLE] role at a company in the [INDUSTRY] field.

Write 15 questions I'll likely be asked — from standard to tricky. For each one, write:
— what the interviewer actually wants to hear,
— the ideal answer structure,
— a sample answer based on my resume [paste the rewritten resume from the previous step].

Separately, list 5 questions I should ask myself to come across as a strong candidate.

The valuable part here isn't the question list itself (you can find that anywhere) — it's the "what the interviewer actually wants to hear" column. "Tell me about a conflict with a coworker" rarely tests the conflict itself; it usually tests whether you can talk about yourself without self-blame or shifting responsibility.

How to use these 15Don't memorize the answers word for word — it comes across as rehearsed in a real interview. Run through each answer's structure out loud once or twice in your own words. Your brain will assemble the exact phrasing on the spot.

02 Interview

Prompt 6 — mock interview

Not a list anymore — a live conversation, with AI acting like a real, exacting interviewer.

Prompt · mock interview
Play a strict interviewer for a [ROLE] role.

Ask questions one at a time, wait for my answer, then evaluate: what was strong, what was weak, how to rephrase it. If my answer is vague, push back like a real HR would: "can you be more specific?", "any numbers on that?"

After 10 questions, give an overall verdict and 3 key pieces of advice.

Answer by voice or text — but treat it exactly like a real interview: full sentences, no "so, uh, basically what happened was." It's tempting to cut corners and answer in bullet points — don't. That's where the actual training happens.

If it starts feeling awkward and you want to stopThat's a normal reaction to the first round of hard feedback. That discomfort now is saving you discomfort in the real interview. Push through at least 10 questions — the verdict is worth it.

03 Level up

Your resume and answers are ready. Don't fumble the first minute

Same experience, same prep — but if the first 60 seconds of the conversation are muddled, all that work starts in a hole.

There's a separate method for introducing yourself in one minute and actually being memorable — it works both in the interview itself ("tell me about yourself") and at the networking event afterward. Same formula as the resume: not "who I am," but "what's in it for you" — just spoken out loud this time instead of read off a screen.

Where to go next

Browse the guides hub for the self-introduction method that finishes what this interview started, using the same evidence-first logic.

03 Final

Done. Same experience — a completely different pitch

What you did

Ran your resume through an honest audit, rewrote your experience into numbers-backed evidence, checked the ATS match and built three summary versions, prepped for 15 likely questions, and rehearsed a live interview under pressure.

6
prompts from resume to offer
15
questions broken down in advance
10
rounds of live rehearsal

Where to go next

I show tricks like this in the channel first

Get the next ones before anyone else

Breakdowns of real problems from my focus groups — from careers to business — show up first in my WhatsApp channel.

Subscribe on WhatsApp →

And don't dodge the hard feedback from AI — better it tells you the uncomfortable truth now than a recruiter quietly closing the tab later.

Guide map

Completed steps are checked. You can return to any completed step — the road ahead opens as you go.

Your progress lives in this browser

Nothing is sent anywhere and no account is needed. Leaving for a while or switching devices — grab the bookmark link.

← All guides