I froze last time. Do I memorize a speech?

Memorize the first sentence of each story and the result number. The middle can be conversational. A fully memorized 4-minute monologue is how people sound like a podcast when the interviewer asks a follow-up.

I don't have 'leadership' stories.

Ops coordinator work is full of them if you stop looking for 'I managed a team of 12'. A cycle count, a vendor save, a backlog, a fight over a process — those are the stories. Scale is optional. A number is not.

They asked for salary in the recruiter screen.

Give a range you researched, then ask what they have budgeted. 'I'm targeting $56–62k for this ops coordinator seat, depending on benefits and shift. What range is approved for the role?' Do not volunteer $49k because that is what you make now.

Video vs panel vs one hiring manager?

Same scripts. On video, tape a sticky note under the camera: 90s / STAR / stop. In a panel, look at the person who asked, then include the rest on the last sentence. Do not perform a different personality for each face.

Career Skills

Interview Answers That Land

Six STAR stories, timed answers, a salary line, and a 24-hour follow-up — not a TED talk

1h 35m16 photographed stepsBeginner

You will build a one-page story bank from ops coordinator work, write STAR answers for tell-me-about-yourself, weakness, conflict, failure, why us, and salary, then practice out loud with a timer. Finish with a follow-up email you can send within 24 hours. Specific, timed, and slightly dry — not a speech about being passionate.

What you'll learn

How to pick 6 stories and map each to a question type
STAR on paper so you stop rambling at 3 minutes
A 90-second tell-me-about-yourself and a salary line that is a number, not a shrug
A 24-hour follow-up that names one thing from the room

Inside this course

Six stories, not a memoirIf you walk in with 'my whole career', you will talk for six minutes and still miss the question. You want six labeled cards.
The questions they will actually askTell-me-about-yourself, weakness, conflict. Write them. Then cut them until they fit a timer.
Failure, why us, and the moneyThese are the ones people either ramble through or try to dodge. You will do neither.
Out loud, with a clockReading the doc is not practice. Standing up and hearing your own filler words is practice.
The 24-hour follow-upIf you wait until you 'feel ready' to write it, you will write nothing. Draft it the same afternoon.

Full step-by-step lessons with photos unlock with a subscription.

Free preview

First steps from Six stories, not a memoir

See how every step looks — photo, checklist, and pro tips included.

Raw list first. Pretty sentences later. If it is not on this page, you will invent it under pressure.

01Write 10 messy bullets from the actual job

Set a 12-minute timer. Title the doc Ops coordinator — raw. Write what you actually did: cycle counts, receiving, vendor emails, ticket queues, shift handoff, the spreadsheet nobody opened. No adjectives. Example bullets that count: found $12,400 of stock sitting in bay C12 labeled empty; got 200 units of packing tape in 36 hours after the freight failed; closed a 40-ticket backlog in 3 weeks; argued with a warehouse lead who wanted to skip the scan; rolled a shared sheet that three people ignored; trained two temps on the receiving checklist in one afternoon.

If a bullet has no number, add scale in brackets: [team of 6], [~80 orders/day], [vendor lead time 5 days]. You are not writing the interview yet. You are making sure the raw material exists. Ten bullets. Ugly is fine.

02Keep 6, label the question each one covers

Circle six. Kill the rest for this interview — they can live in a parking lot doc. Map them so you are not telling the vendor story four times: (1) inventory miss → problem-solving, (2) 36-hour vendor save → under pressure, (3) 40-ticket backlog → ownership, (4) warehouse lead vs scan step → conflict, (5) spreadsheet nobody used → failure, (6) why this posting → same-day vendor SLA language in the job ad matches story 2.

Write one line under each: Question this answers. If two stories answer the same question, drop the weaker number. You need coverage, not six versions of 'I work hard'. Put the six in a table. That table is the whole course until the scripts exist.

Full library access