Chapter 20 — Interviewing: Preparation and Not Self-Sabotaging

🆘 WHAT TO DO RIGHT NOW

If your interview is in an hour: research the company for fifteen minutes (what they sell, who their customers are, one recent piece of news), prepare your 90-second "tell me about yourself," write down three questions to ask them, and re-read the job posting. That's 80% of the value of preparation.

If they asked for your salary expectations and you have to answer today: do not give a number first if you can avoid it. Say: "I'd like to learn more about the role's scope first. What range has the team budgeted?" In many states it is illegal for them to ask your salary history. See "The Salary Question."

If it's a video interview and something breaks: have the interviewer's phone number ready in advance. Technical problems are normal and handling them calmly is itself a good signal.

If you don't have interview clothes, a way to get there, childcare, or a private room to take the call: all four are solvable, none of them are a character flaw, and the fixes are specific. Skip to "When you can't afford the right option."

If you have an interview and you're panicking: that's normal, it happens to everyone, and it doesn't predict how you'll do. Skip to "Nerves."

What an interview actually is

Interviews feel like an exam. They aren't.

An interviewer is trying to answer three questions:

1. Can you do the job? Skills and experience.
2. Will you do the job? Motivation, reliability, and whether you actually want this job.
3. Can we stand working with you? Fit with the team, communication, whether you're pleasant to be around at 6 p.m. on a hard day.

Most candidates over-prepare for the first and neglect the other two. The third one decides more hires than people admit — when two candidates are similarly qualified, the one who was easier to talk to gets the offer.

The other reframe worth holding: an interview is a mutual evaluation. You are also deciding whether to spend forty hours a week here. Candidates who genuinely hold that frame interview better, because desperation reads and confidence reads, and both are contagious.

The shape of the process

Nobody explains this part, so the first time through you have no idea how many rounds there are, who these people are, or how long it's supposed to take.

  APPLY ► RECRUITER SCREEN ► HIRING MANAGER ► TEAM / PANEL ► FINAL ► OFFER
            15-30 min          45-60 min       2-5 hours    30-60 min
            phone              phone or video  on-site or   often
                                               video block  skipped

Each round is screening for something different, which is why the same answer can land in one and flop in the next.

• The recruiter is checking that you're real, available, authorized to work, and affordable. They are usually not evaluating your craft. Be warm, be brief, be clear about logistics.
• The hiring manager is asking "can this person do the work, and do I want them in my meetings." This is the interview that matters most. It is also usually the person who decides.
• The team or panel is checking that you know what you claim to know and that they can stand you. Peers are often more skeptical than the manager, because they'll be the ones covering for you.
• The final round is frequently a sanity check plus a sales pitch. If someone senior starts selling you on the company, that's a good sign about where you stand.

The recruiter is not your enemy and not your advocate. Their job is to fill the role at or under the budgeted number. But they will tell you an enormous amount if you ask, because it makes their job easier. Ask this in the first two minutes of the first call:

"Before we get into my background — could you walk me through what the rest of the process looks like? How many conversations, who I'd be meeting, and roughly what the timeline is?"

That single question gets you the number of rounds, the names to research, and frequently the salary range without you having to bring it up.

How long it takes: two to eight weeks from first conversation to offer is normal. Government and large institutions routinely take three to six months. Small companies can do it in a week. Silence in the middle usually means something internal — a budget review, a hiring manager on vacation, a competing candidate — and almost never means they're deciding whether you're good enough.

Not every job works this way. Retail, food service, warehouse, home care, and most hourly work often run a single 20-minute interview, sometimes with an offer on the spot. That's not a lesser process; it's a faster one. Everything in this chapter still applies, just compressed.

And ghosting is common. Companies disappear on candidates constantly — after one round, after five rounds, after a verbal offer. It is a failure of their process, it is rude, and it says nothing about you. Assume no news is no news, keep applying, and don't build a theory out of silence.

Preparation

Research the company (60–90 minutes for one you care about)

The essentials: - What do they actually sell, and to whom? Be able to say it in one sentence. - How do they make money? Surprisingly many candidates can't answer this. - Who are their competitors? How are they different? - Recent news. Funding, product launches, layoffs, acquisitions, leadership changes. Search the company name in the news tab. - The team you'd join. Look up your interviewers on LinkedIn — their background, how long they've been there, what they did before. - Their language. How do they describe themselves? Use those words back.

Where to look: the company website (especially the About and Blog pages), recent press, LinkedIn, Glassdoor reviews (read the pattern, not the extremes — angry reviews and glowing reviews are both self-selected), their earnings call or investor materials if public, and their engineering/design/company blog.

For Glassdoor specifically: look for patterns repeated across many reviews and across time. "Poor work-life balance" appearing in thirty reviews over three years is data. One furious review is not.

Re-read the posting

Go line by line. For each requirement, have a specific example ready. Literally write them down — the posting is the interviewer's checklist too.

Prepare your stories

Most interview questions are answerable from a bank of six to eight stories. Prepare them once and reuse them.

Have a story for each of these: 1. A significant accomplishment you're proud of 2. A time you solved a difficult problem 3. A conflict with a coworker and how you handled it 4. A failure or mistake, and what you learned 5. A time you led something (formally or not) 6. A time you handled competing priorities or a tight deadline 7. A time you had to learn something quickly 8. A time you disagreed with a decision

Write them out. Practice them out loud. Not memorized word for word — that sounds rehearsed and it is — but so you know the shape and don't ramble.

The STAR method

For behavioral questions ("tell me about a time when..."), STAR keeps you from wandering.

  S — SITUATION   Set the scene. Brief. Where, when, what was going on.
  T — TASK        What was your specific responsibility or the problem?
  A — ACTION      What YOU did. Not "we." This is the longest part.
  R — RESULT      What happened. With a number if possible.

Weak answer:

"Yeah, we had a project that was behind schedule and it was pretty stressful but we all pulled together and got it done."

STAR answer:

(S) "Last spring we were three weeks from launching a client portal and QA found that the permissions system let users see other accounts' documents."

(T) "I was the engineer on the auth layer, so fixing it was mine, and the launch date was contractual — we couldn't move it."

(A) "I mapped every permission check in the codebase and found we had three different implementations that had drifted apart. Rather than patch all three, I consolidated them into a single middleware layer and wrote tests for every role combination — about forty cases. I also flagged to our PM on day one that this might slip the date, so nobody found out late, and I proposed cutting a lower-priority feature to buy time."

(R) "We shipped on the original date without the cut feature, actually. Zero permissions bugs reported in the first six months, and the consolidated middleware is what the team still uses. The bigger outcome was that we added a permissions test suite to the CI pipeline, so the class of bug can't recur."

Notice: specific, uses "I" for personal actions, includes what they communicated (not just what they built), and ends with a durable result.

Length: 90 seconds to two minutes. Longer and you lose them; shorter and it doesn't land. Practice out loud with a timer — everyone thinks they're briefer than they are.

The skeleton, with proportions

The most common failure isn't a bad story. It's a story where the setup eats ninety seconds and the part where you actually did something gets ten.

╔══════════════════════════════════════════════════════════════════════════════╗
║  STAR ANSWER SKELETON                    total: 90 seconds to two minutes    ║
╠══════════════════════════════════════════════════════════════════════════════╣
║                                                                              ║
║  S — SITUATION      ~15 sec   ████                                      ①    ║
║      "Last spring, at [where I worked], [what was going wrong]."             ║
║      Where, when, and just enough context. No cast of characters.            ║
║                                                                              ║
║  T — TASK           ~15 sec   ████                                      ②    ║
║      "My job was [X]. The part that made it hard was [Y]."                   ║
║      YOUR piece of it, plus the constraint. Not the team's mission.          ║
║                                                                              ║
║  A — ACTION         ~60 sec   ████████████████                          ③    ║
║      "So I [did this]. Then [this]. I also told [someone] that [X]."         ║
║      "I," not "we." Three to five concrete moves, in order.                  ║
║                                                                              ║
║  R — RESULT         ~20 sec   █████                                     ④    ║
║      "[What happened, with a number]. And afterward, [what stuck]."          ║
║      The outcome, then the durable change. Most answers stop too early.      ║
║                                                                              ║
║  ──────────────────────────────────────────────────────────────────────      ║
║  THE TAKEAWAY LINE                                                      ⑤    ║
║  If they remember one sentence from this, which sentence is it?              ║
╚══════════════════════════════════════════════════════════════════════════════╝

① Situation — cut it shorter than feels comfortable. The interviewer does not need the org chart. Two sentences of context is almost always enough. If you find yourself explaining who Dave is, you've gone too far.

② Task — this is where you claim the problem. The sentence that matters is the constraint: the deadline that couldn't move, the two people who called out, the budget that was already spent. Difficulty is what makes the story worth telling.

③ Action — "I," not "we." This is the single most common fix. People raised to be team players narrate everything in the plural, and the interviewer genuinely cannot tell what you personally did. Use "we" for context and "I" for every action you took. And include what you said to people, not just what you built or moved — communication under pressure is usually the thing being tested.

④ Result — two parts, and people forget the second. First what happened, ideally with a number, even a rough one ("about ninety minutes a night," "roughly a third fewer callbacks"). Then what stuck: the process that changed, the checklist that's still taped to the door, the thing that can't go wrong the same way again. That second half is what separates a person who fixed a problem from a person who improved a system.

⑤ The takeaway line. Before you tell a story, decide the one sentence you want them to repeat about you in the debrief. Then make sure you actually say it out loud.

Three worked answers

Every interview guide illustrates STAR with a software project or a marketing campaign. Most people's best stories aren't from an office, and interviewers know good judgment when they hear it regardless of the setting.

Question: "Tell me about a time you disagreed with how something was being done."

(S) "I stocked overnight at a grocery store for about two years. The truck hit the dock at 11 p.m. and we had until 6 a.m. to get it all on shelves. We were finishing around 7:30 most nights, which meant customers were shopping around pallets and the morning crew started their day behind."

(T) "I wasn't a supervisor — I was one of five stockers. But I was the one who kept getting stuck with the last two aisles, so I had a clear view of where the time was going."

(A) "For two weeks I wrote down when each of us started an aisle and when we finished, just on the back of the pull sheet. It showed we were losing about forty-five minutes a night breaking down the entire pallet in the back before anybody touched a shelf. I took that to my night lead with the numbers rather than as a complaint, and suggested we run one pallet at a time straight to the aisle. He was skeptical, because it wasn't how he'd been trained, so I asked if we could try it on two aisles for one week and compare. We did. Then I wrote the new sequence on an index card and taped it inside the stockroom door so new people didn't have to be told."

(R) "We started finishing between 5:30 and 6:00 instead of 7:30 — about ninety labor hours a month across the crew. My lead brought it to the store manager and two other stores in the district picked it up. The part I'm proudest of is that it outlasted me. The index card was still on that door when I stopped in a year after I left."

That answer contains initiative, measurement, influencing someone with more authority than you, a low-risk pilot instead of an argument, and a durable result. It happened at 3 a.m. in a grocery store. The setting is not the point.

Question: "Tell me about a mistake you made."

(S) "I was a home health aide for three years, mostly with older clients living alone. One of mine was a man in his eighties with early dementia and eleven prescriptions on different schedules."

(T) "Filling his weekly pill organizer and checking it every visit was my responsibility."

(A) "One Tuesday I put his evening blood pressure medication into the morning slots. His daughter caught it that night. Nothing happened to him — but I had a choice about what to do next. I called my supervisor that evening rather than waiting until morning, and I reported it as an incident even though there was no harm and honestly nobody would have known. Then I changed my own process: I started filling organizers at the beginning of a visit instead of at the end when I was tired, and I photographed the finished tray and texted it to the family, so there were two sets of eyes on it."

(R) "My supervisor put the photo step into the onboarding for new aides on our team. I didn't make another medication error in the two years after. What I actually took from it wasn't 'be more careful,' because that isn't a system — it was that I'd been doing the highest-risk task at the lowest-attention part of my day, and that's a design problem, not a character problem."

Question: "Tell me about a time you handled competing priorities."

(S) "I served at a diner that did about two hundred covers on a Sunday morning with four servers."

(T) "One Sunday two people called out and I had my six tables plus half of another section."

(A) "The first thing I did was stop trying to do everything at the same speed. I walked the whole section once and told every table the truth — that we were two down, that drinks would be about three minutes, that food would be slower than usual — and asked whether anyone was on a clock. Two tables were, so I fired their tickets first. Then I batched everything: all drinks in one trip, all checks in one pass. I also asked the kitchen to call tickets by table number instead of by dish so I wasn't guessing whose plate was up."

(R) "We didn't comp a single meal and my tips came in about level with a normal Sunday. The lasting change was that the manager started announcing short-staffed shifts at pre-shift instead of letting us find out one table at a time."

If your experience isn't from a job

Interviewers are trying to see judgment, not a job title. Stories from outside paid employment count, and you should use them without apology or preamble.

Legitimate sources of stories: a group project where someone stopped contributing; running a club, a team, or a church program; caring for a sick or elderly family member, which is genuinely operations work under pressure; military service; moderating a Discord server or a fan community; a side hustle, a resale business, a repair thing you did for cash; translating for your parents at appointments; managing a household on a fixed amount of money; volunteering; teaching yourself something and shipping it.

Do not open with a disclaimer. Not "this isn't really work experience, but..." — just tell the story. "When I was coordinating my grandmother's care, there were four different specialists and none of them talked to each other, so I..." is a completely normal answer to a question about handling complexity.

The questions you will be asked

"Tell me about yourself"

The most common opener and the most commonly fumbled. They are not asking for your life story. They're asking: why are you sitting here?

The 90-second structure: Present → Past → Future.

The template, with the blanks marked:

"Right now I'm [role] at [place], where I mostly [the one specific thing you do most]. Before that I was [previous role], which is where I [the skill or habit you picked up]. What I've found is that the part I'm best at — and honestly the part I like — is [the thread that connects them]. That's why this role caught my eye: [the specific connection to their posting]."

Four sentences. Present, past, the thread, the reason you're sitting here.

"I'm currently a data analyst at Kestrel Health, where I spend most of my time on the reporting layer for our clinical operations team — building dashboards that help them see where patients are getting stuck in the referral process. Before that I was in a more generalist analyst role at a smaller consultancy, which is where I learned SQL properly and got comfortable talking directly to non-technical stakeholders. What I've found is that the part I like most is the translation piece — figuring out what someone actually needs to know versus what they asked for. That's why this role caught my attention; it's the same work but on a product where the decisions have more leverage."

The same structure works when your history isn't a straight line, and it works better than apologizing for the line:

"For the last four years I've been an assistant manager at a Sherwin-Williams store — running the schedule for nine people, handling inventory, and doing most of the commercial accounts, which is the part where I'm basically managing relationships with contractors who spend forty thousand dollars a year with us. Before that I was in the Army, motor transport, which is where I got comfortable being responsible for expensive things going wrong at bad times. What I've realized is that the piece I'm actually good at is the account side — knowing what a customer needs before they ask. That's why I applied here; this is that job without the paint."

Do not start with where you were born. Do not recite your résumé chronologically. Do not apologize for anything in the first ninety seconds. Do end at why you're here.

A note on nerves and this question: it's the one people rehearse into stiffness. Know the four beats, not the words. If you find yourself reciting, you'll hear it, and so will they.

"Why do you want to work here?"

They're testing whether you're applying to everything.

Be specific about them. Reference the product, the mission, something they published, their approach. Connect it to something true about you.

Do not say: "It seems like a great opportunity," "I've heard good things," or anything about compensation or benefits.

"Why are you leaving your current job?"

Never disparage a current or former employer. No matter how justified. Interviewers hear it as "this is how they'll talk about us."

Reframe toward what you're moving toward:

"I've learned a lot there and I'm grateful for it, but the team's scope has narrowed and I want to work on [specific thing this role has]."

If you were laid off: say so plainly. It's extremely common and carries no stigma. "My role was eliminated in a restructuring in March — about 15% of the company."

If you were fired: be brief, honest, non-defensive, and forward-looking. "It wasn't the right fit and I own my part in that — I wasn't communicating enough about where I was struggling. What I took from it is that I ask for help much earlier now." Do not over-explain. One or two sentences and move on.

The two-sentence rule

Almost everyone has one thing they're dreading being asked about. A firing. A two-year gap. A career change nobody understands. A conviction. A degree that isn't finished. A stretch where you were too sick to work.

Here is the rule: two sentences, then a question back. Sentence one is the fact. Sentence two is what's true now. Then you hand the conversation back.

The reason is mechanical, not moral. Interviewers take their emotional cue from you. If you deliver a fact in four calm seconds, it registers as a fact. If you spend ninety seconds contextualizing, justifying, and pre-empting objections, the interviewer concludes there must be something worth all that defending — even when there isn't. Length reads as shame, and shame reads as risk.

Worked examples.

Fired:

"I was let go in November — it wasn't the right fit and I own my share of that. I've been much more direct since about flagging problems early instead of trying to fix them quietly. Is that kind of directness something this team wants, or is it more of a heads-down culture?"

A gap:

"I was out of work from March 2024 to early 2025 taking care of my mother after her stroke. She's in a facility now and I've been back to full availability since February. What does the schedule actually look like on this team?"

Another gap, no tidy reason:

"I took about eight months off after that job, partly by choice and partly because the search took longer than I expected. I've kept current with [specific thing] and I'm ready to go now." — You do not owe anyone the private version. "I took some time off" is a complete answer.

Career change:

"I spent six years in restaurants and moved into scheduling and ordering, and that turned out to be the part I was good at. I've done a certificate in supply chain since. The move isn't a whim — it's the direction I was already drifting."

A conviction, where they've asked lawfully:

"I have a felony conviction from 2019 for [offense]. I completed my sentence and I've been working steadily since 2021 — my last supervisor will confirm that. Happy to answer anything else about it." — Many states and cities have "ban the box" laws that delay when this can be asked at all, and some prohibit blanket disqualification. This varies enormously by state and by industry. Chapter 19 covers the Federal Bonding Program and the Work Opportunity Tax Credit, both of which are worth mentioning to a hesitant employer, and Chapter 28 covers your rights more broadly.

What breaks the rule: volunteering it before you're asked, blaming a named person, crying about it, saying "honestly" three times, or explaining the same thing twice in one interview. If they follow up, answer the follow-up. If they don't, it's over — let it be over.

"What's your greatest weakness?"

The most-hated question, and the answer is simpler than people think.

Do not give a fake weakness ("I'm a perfectionist," "I care too much"). Interviewers have heard it thousands of times and it reads as evasive.

Do give a real one that isn't disqualifying, and show what you're doing about it.

"I've historically been bad at delegating — I'd take on too much because it felt faster than explaining. It caught up with me when I was leading a three-person project and became the bottleneck for all of it. Since then I've made myself hand off at least one thing per sprint that I'd normally keep, and I write a short handoff doc instead of a verbal explanation. It's still not instinctive, but it's much better than it was."

Do not name a weakness that is the core of the job. Don't say "I'm not detail-oriented" in an accounting interview.

"Where do you see yourself in five years?"

They want to know: will you stay, and are you ambitious in a way that fits.

Answer in terms of skills and scope, not titles, unless a specific ladder is clearly relevant.

"I want to be deep enough in this domain that I'm the person people come to with the hard problems, and I'd like to be mentoring more junior people. Whether that's a formal management track or a senior IC role, I don't know yet — I'd want to see which one fits."

"Tell me about a conflict with a coworker"

The trap is that people either claim they've never had one (nobody believes this) or relitigate the whole thing and reveal that they're still angry.

What's actually being tested: whether you can describe someone you disagreed with in a way that shows you understood their position.

"A designer and I disagreed hard about whether to ship a feature without an accessibility review. I thought we had to hold it; she thought the review would take three weeks we didn't have and that we could patch after. I asked her to walk me through the timeline she was working against, and the real constraint turned out to be a conference demo, not the launch. So I proposed we ship it behind a flag for the demo and do the review before general release. We both got the thing we actually needed. What I'd do differently is ask about her constraint first instead of arguing the principle for twenty minutes."

The moves that make it work: state the other person's reasoning fairly, describe what you did to understand it, land on a resolution, and name one thing you'd do differently. Never end with "and it turned out I was right."

"Tell me about a time you failed"

Pick a real failure with real stakes. A fake one ("I once underestimated a timeline by a day") reads as evasive, same as the fake weakness.

The structure: what happened, what you did about it at the time, what changed permanently. Own it in the first sentence and don't hedge with "the situation was set up to fail." The home health aide answer above is the model.

What not to use: anything where the failure was someone else's, anything involving a protected characteristic, anything so recent and so raw that you can't discuss it evenly, and anything that would be disqualifying for this specific job. Failing to catch a math error is a bad story for an accounting interview.

"How do you handle stress or pressure?"

They are not asking whether you feel stress. Everyone does. They're asking what you do when the volume goes up.

Answer with mechanics, not temperament. "I stay calm" is not an answer. "I triage out loud" is.

"When it gets loud I get more explicit, not less. I write down the three things that actually have to happen, I tell whoever's affected which of them is going to be late, and I stop trying to do everything at the same quality level. The thing I've learned to do faster is the telling-people part — the work being late is usually survivable, and being surprised by it isn't."

"Tell me about a time you got hard feedback"

Underrated question, and a good answer moves you up a lot, because most people describe feedback they secretly disagreed with.

"My manager told me in a review that I was hard to interrupt in meetings — that people had stopped bringing up half-formed ideas around me. My first reaction was that I was just being thorough. I sat with it and asked two people on my team directly, and they both confirmed it, more gently than she had. So I started asking one question before offering an opinion, and in meetings I run I ask for objections before I say what I think. It's still the thing I have to consciously do."

"Why should we hire you?"

An oddly aggressive-sounding question that is really just an invitation. Take it.

Three sentences: the two or three things the role most needs, why you're specifically credible at them, and one honest line about wanting it. Don't list every strength you have. Match the posting.

"What are you looking for in your next role?"

Answer honestly and specifically, because a mismatch here is genuinely bad for you too. If you want to stop being on-call, say you want a role without an on-call rotation. If you want to stop managing, say so. You are allowed to want things.

"Is there anything that would prevent you from starting?" / "Any concerns about the role?"

Usually a logistics question. Answer the logistics: notice period, a planned surgery, a trip you already paid for, a schedule constraint. Say the trip now, not after you accept. Nearly every employer will accommodate a pre-booked commitment disclosed before the offer, and almost none enjoy learning about it in week one.

If you have a genuine reservation about the role, this is your opening to raise it: "The one thing I want to understand better is how much of this job is the reporting versus the analysis — the posting reads about half and half, but I've heard two different versions today." That's not a red flag to them. It's a candidate doing due diligence.

"Do you have any questions for us?"

Always yes. "No, you covered everything" reads as disinterest, every time.

Have five prepared — some will get answered during the conversation.

Good questions: - What does success look like in this role in the first six months? - What's the biggest challenge the person in this role will face? - How is the team structured, and who would I work with most closely? - What do you like about working here? (The pause before the answer is informative.) - How would you describe the management style on this team? - Why is this position open? (Growth, or did someone leave, and why?) - How does the team handle disagreement? - What's changed most about the team in the last year? - How is performance evaluated? - What are the next steps in the process?

Questions that reveal culture: - What happens when a project goes wrong here? - When was the last time someone on this team pushed back on a decision, and what happened? - How often does the team work past normal hours, honestly?

Don't ask about salary and benefits in a first interview (unless they raise it), vacation policy, or anything answered on the homepage.

What each question actually gets you

Questions aren't only for looking engaged. Sorted by what they surface:

Watch the pause, not just the words. A hiring manager who needs four seconds to think of something they like about working there has told you something. So has one who answers "why is this open" with a fluent, obviously prepared non-answer.

The salary question

This will come up, often early, often in a screening call.

Salary history bans: many states and cities prohibit employers from asking what you currently earn. If asked in a jurisdiction where it's banned, you can simply decline. Even where it's legal, you're not obligated to answer.

Pay transparency laws in a growing number of states require employers to post ranges. Check whether the posting includes one before you answer anything.

The script

If asked for your expectations:

"I'd like to understand the scope better before naming a number. Can you tell me the range you've budgeted for this role?"

Most of the time they'll tell you. If they push back:

"Based on my research for this role, in this market, at this level, I'd expect something in the range of $X to $Y — but I'm flexible depending on the full package and the scope. What's the range on your end?"

Give a range where your target is at the bottom. If you want $85,000, say "$85,000 to $95,000." Employers hear the bottom of your range as your number.

If asked for your current salary in a place where it's legal:

"I'd rather focus on the value of this role — I'm targeting $X based on the market for this position."

Research your number first: levels.fyi (tech), Glassdoor, Payscale, Salary.com, the BLS Occupational Employment Statistics (bls.gov/oes, searchable by occupation and metro area), professional association surveys, and — most valuably — asking people in your field.

If they won't move on and you have to say a number

Sometimes the recruiter has a field in a form and cannot advance you without filling it. Fine. Say a number — just say it deliberately.

"If you need a number for the system, put down $78,000 as a starting point, with the understanding that I'd want to revisit it once I understand the scope and the rest of the package."

That framing does two things: it gives them what they need, and it explicitly reserves your right to negotiate later, which is the thing people accidentally sign away. A number given in a first screen is an anchor, not a contract, and you are allowed to say later: "Based on what I've learned about the scope since we spoke, I'm now looking at $X."

Do not lie about your current salary. Declining to answer is completely safe. Inflating a number is the rare interview mistake that can be discovered and can cost you an offer after it's made.

Chapter 22 is the whole negotiation — how to counter, what else is negotiable besides base pay, and the sequence that gets you more without risking the offer. The only job of this chapter is to get you to the offer stage without having capped yourself.

Formats

Phone screen (15–30 min)

Usually a recruiter confirming basics: are you real, do you meet the requirements, what are your expectations, are you authorized to work, what's your timeline.

Have your résumé in front of you. Be somewhere quiet with signal. Smile — it's audible.

Video interview

Test everything the day before: camera, mic, the specific platform, your link.

Setup: - Light in front of you, not behind. A window or a lamp facing you. Backlighting turns you into a silhouette. - Camera at eye level. Stack books under a laptop. Looking down at a camera is unflattering and reads as disengaged. - Neutral background, or a tidy real one. Virtual backgrounds glitch. - Look at the camera, not the screen, when you're speaking. It's the only way to make eye contact, and it feels unnatural until you practice it. - Headphones prevent echo. - Close everything else. Notifications, other apps, anything that might make noise. - Have the interviewer's phone number in case the connection fails. - Notes are fine — just don't obviously read from them. Sticky notes near the camera work well.

When the connection dies — and it will, eventually — do not spend two minutes typing "can you hear me?" into a chat. Have a plan and execute it:

1. Turn your camera off first. Video is the bandwidth hog; audio usually survives when video won't.
2. If audio goes too, call the number you saved and say: "Hi, it's Dana — my connection dropped. Happy to keep going by phone, or I can rejoin in two minutes, whichever's easier for you."
3. If you have a phone with data, know in advance how to turn on its hotspot. Practice it once when you're not panicking.

Handling a technical failure calmly is a genuinely good signal and interviewers know their own tools break too. Handling it by disappearing is not.

One-way / recorded video interviews

Increasingly common and genuinely unpleasant — you record answers to prompts with no human present.

Treat it like a live interview: dress the same, set up the same, and take the practice question seriously. You usually get limited retakes; check before you start. Speak to the camera as if it's a person, and accept that it will feel strange.

Panel interview

Multiple interviewers at once.

Address the person who asked, then make eye contact with the others as you answer. Get everyone's name at the start (write them down) and use them. Ask each person about their role.

Draw the seating chart in your notebook as they introduce themselves. Nobody minds, and it saves you from "and to your point earlier, um, sorry —".

Group interviews (several candidates at once)

Common in retail, hospitality, call centers, and some seasonal hiring. Several applicants in a room, sometimes doing exercises together.

What's being watched: whether you can be pleasant to people you're competing with. Talking over other candidates loses more of these than being quiet does. Contribute early so you're not invisible, credit someone else's idea out loud at least once, and be the person who asks the quiet applicant what they think.

Working interviews and shift trials

You come in and actually do the job for a few hours — common in restaurants, salons, trades, veterinary clinics, and some clinical roles.

If you are doing productive work under their direction, you are generally owed wages for that time. Federal and state wage law treats a genuine unpaid "audition" narrowly, and the details vary by state. Ask before you go: "Is the trial shift paid, and at what rate?" A place that's cagey about paying you for four hours of covered shifts is showing you exactly how payroll will go later. If it happened and you weren't paid, your state labor department takes wage complaints, and so does the federal Wage and Hour Division (dol.gov/agencies/whd).

The multi-round gauntlet

Some processes run five, six, seven rounds across two months. Sometimes that's a serious role. Often it's an organization that can't decide.

You are allowed to ask about the end. "Just so I can plan — is this the last conversation, or are there more rounds after this one?" And if a fifth round appears out of nowhere: "I'm happy to do it. Can you tell me what this round is meant to answer that the previous four didn't?" That's a reasonable question asked reasonably, and the answer tells you whether anyone is actually driving.

Costs are not symmetric. Each round costs them an hour and costs you a day of PTO you may not have. It is fine to say that out loud: "I've used most of my flexibility on the earlier rounds — could we do this one at 8 a.m. or after 5?"

On-site / final round

Often four to six back-to-back interviews plus a meal.

Bring: copies of your résumé, a notebook, your questions, water.

During a meal: you're still being evaluated. Order something manageable, mirror what they order in price, don't drink alcohol even if offered (or at most one, if everyone else does), and be conspicuously kind to the service staff. How candidates treat waitstaff is something a lot of interviewers watch for deliberately.

Be pleasant to everyone — the receptionist, the person in the elevator. Their opinion is sometimes solicited, and it should count anyway.

Technical interviews and assessments

Coding interviews: think out loud, ask clarifying questions before writing, start with a working brute-force solution before optimizing, and test your own code. Being stuck is normal; how you handle being stuck is what's being assessed.

Case interviews (consulting): structure first, state your assumptions, do arithmetic out loud, and check in with the interviewer.

Take-home assignments: clarify the expected time investment before starting. If a take-home would take more than four to six hours, it's reasonable to ask whether it can be scoped down — and a company that expects twenty unpaid hours is telling you something about how it values your time.

⚠️ THE TRAP: The "test project" that is actually free labor

There is a real difference between an exercise and an unpaid job, and it isn't subtle once you know where to look.

A legitimate exercise uses fake or public data, is scoped to a few hours, is given to every candidate at the same stage, and produces something the company has no use for. Debugging a toy codebase. Writing a sample memo about a made-up client. A design critique of a hypothetical screen.

Free labor looks like: "here's our actual backlog," "write three posts for our real blog," "audit our live account and tell us what you'd fix," "build the onboarding flow we're currently missing," "design a logo concept for our upcoming launch." The tell is that they could ship it. If the deliverable has commercial value to them tomorrow morning, they are not testing you, they are getting the work done.

Who profits: companies that have discovered they can get twenty or thirty candidates to produce real deliverables for free, and keep the good ones. This is most common in marketing, design, content, and social media roles, and it is common enough in those fields that it is worth expecting.

What to say, without torching the process:

"Happy to do an exercise. This one looks like it's on your live account, so I'd want to either work from a sample instead, or discuss a rate for it — I keep a firm line between exercises and client work. Either is fine with me."

A serious employer will say "oh, use whatever sample you like." Some will offer to pay, which is increasingly normal and a genuinely good sign. The ones who get offended have told you the answer.

Also protect the work itself. Don't hand over anything you'd mind seeing used. Watermark deliverables, submit as PDF rather than an editable file where that makes sense, and don't include your novel idea in a free sample. And if you find your unpaid submission published, that's potentially copyright infringement in the US — you own what you create unless you signed it away. Read anything they ask you to sign before an exercise.

What to wear

The rule: one level above the company's daily dress.

• Corporate/finance/law → suit
• Business casual office → blazer with slacks or a dress; a button-down and slacks
• Startup/tech → clean, well-fitting, no logos. A sweater or button-down. Jeans are often fine.
• Creative → clean and put-together with room for personality
• Trades/manufacturing → clean work-appropriate clothing; boots if you're going on a floor
• Retail/service → business casual

If you genuinely don't know, ask the recruiter. "What's the dress code for the interview?" This is a completely normal question and asking it signals nothing bad.

Universally: clean, ironed, fits properly, comfortable, nothing you'll fidget with. Fit matters more than price — a $40 blazer that fits beats a $400 one that doesn't.

And if you can't afford any of this, that is an extremely common situation with specific, unglamorous, actually-working solutions. They're below.

💸 WHEN YOU CAN'T AFFORD THE RIGHT OPTION

Interviewing costs money — clothes, transit, gas, parking, childcare, and unpaid hours you gave up to be there. Nobody puts that in the guides, and it is the reason a lot of people quietly stop showing up. Here is the actual version.

Clothes. A clean, plain, dark pair of pants and a clean, plain shirt in a solid color is genuinely fine for the overwhelming majority of jobs. Not "acceptable" — fine. Interviewers notice clean, ironed, and fitting; almost nobody can price your shirt. Skip the blazer before you wear a bad one.

Free professional clothing, in rough order of ease: Dress for Success (dressforsuccess.org, women and gender-diverse clients, many affiliates require a referral, which your caseworker, shelter, or workforce center can write); Career Gear (careergear.org, men, referral-based); your local American Job Center, findable at careeronestop.org or by calling 1-877-872-5627 — many run clothing closets or issue thrift vouchers; 211 (dial 2-1-1) for local clothing programs; church clothing pantries, which usually don't ask questions; and Buy Nothing groups on Facebook, where "I have an interview Thursday and I'm a men's medium" gets answered within hours more often than you'd expect.

Thrift stores in expensive neighborhoods are where good clothes go to be cheap. Go on the store's discount day. An $8 blazer that fits your shoulders looks better than a $200 one that doesn't, and a tailor charging $15 to shorten sleeves is the highest-return money in this chapter.

Getting there. Ask. "Is there any travel reimbursement for the on-site?" Larger employers often have a policy and simply don't advertise it. If the answer is no and the trip is genuinely unaffordable, say so plainly and offer the alternative: "The commute for an in-person round is a real barrier for me this month. Would a video round work, or could we do it on a day you have other candidates on-site?" This is a normal request. 211 can also connect you to transportation assistance in many areas, and some job centers issue bus passes.

Childcare. You do not have to explain your childcare situation to an employer, and you shouldn't have to solve it alone either. 211 lists drop-in and emergency childcare; state child care resource and referral agencies (search "[your state] child care resource and referral") can find subsidized slots. If you're stuck, ask for a time slot that fits what you already have: "Would 9:30 a.m. work? I have a hard stop at 11:30." Nobody will ask why.

Time off you can't afford to take. If you're hourly and every interview hour is money you don't get, say the availability part without the reason: "I'm available before 9, after 5, or on Saturdays." You are not obligated to disclose that you're currently employed, or where. Many employers will accommodate early and late slots for exactly this reason. Phone screens can often happen on a break.

Nowhere private to take the call. This is more common than the internet admits. Options, roughly best to worst: a public library study room (free, quiet, bookable, and librarians will help you find one — many library systems now specifically reserve rooms for job interviews); an American Job Center, which usually has a computer and a private room for exactly this; a friend's apartment during their work hours; a parked car.

The car works. Park somewhere quiet and legal — a library or church lot, not a busy street. Sit in the driver's seat with the sun in front of you, phone propped against the steering wheel or on the dash so your face is centered and the camera isn't looking up your nose. Engine off, windows up, hazards off. Say nothing about where you are. If they ask, "I'm out of the house for this one" is a complete answer, and honestly half the people interviewing you have taken a call from a car.

And the honest part: none of this is a level playing field, and pretending otherwise is insulting. A candidate with a car, a spare room, and a closet is starting ahead of you. What's true anyway is that interviewers remember the answers, not the shirt, and that the workarounds above are used constantly by people who got the job.

Nerves

Everyone is nervous. Interviewers expect it and account for it. Visible nerves have not cost nearly as many jobs as candidates believe.

What helps:

• Preparation. Most nerves come from uncertainty, and the questions above are 80% predictable.
• Practice out loud. Not in your head — out loud, to a mirror, a friend, or a recording. Your first spoken attempt at a story is always worse than your fifth.
• Arrive early. Fifteen minutes early to the area, five minutes early to the door. Rushing compounds everything.
• Slow down. Nervous people talk fast. Deliberately pause before answering. A three-second pause reads as thoughtful, not slow — and it feels like an eternity to you and like nothing to them.
• Reframe the physical sensation. Anxiety and excitement produce nearly identical physiological states. Telling yourself "I'm excited" rather than "calm down" is better supported by evidence and easier to do.
• Remember it's mutual. You're evaluating them.
• Have water. Drinking is a legitimate way to buy three seconds.

If you blank: "That's a good question — let me think about that for a second." Then think. Silence is fine. Or: "Could you rephrase that?" Both are completely normal.

If you realize you gave a bad answer: you can circle back. "Actually, can I add something to my earlier answer about X?" This reads as self-aware, not scattered.

If your hands shake or your voice goes: put the water down where you can reach it, plant both feet on the floor, and slow your exhale — a longer breath out than in, three times, is the one physiological trick that reliably works and is invisible from across a table. Shaking hands are a caffeine-and-adrenaline problem, not a competence problem. Consider skipping the second coffee.

If you cry: it happens, usually when a question lands somewhere raw. "Sorry — give me a second." Then take it. Do not apologize four times or explain. Most interviewers will move on faster than you will.

You are allowed to ask for accommodations for the interview itself. Under the ADA, and under equivalent law in many other countries, a disability — including anxiety disorders, ADHD, autism, and chronic illness — can entitle you to reasonable adjustments in the hiring process. In practice you can request the questions in advance, extra time on a timed assessment, a written rather than verbal exercise, a quieter room, breaks, or a video interview instead of an on-site. You ask the recruiter, and you do not have to disclose a diagnosis to do it:

"Could you send the interview questions or the general topics in advance? I do my best thinking with a little prep time."

Plenty of employers do this for every candidate now, because it produces better interviews. If they say no to a plainly reasonable request, that's information.

Afterward: you cannot tell how it went. People walk out certain they bombed and get offers, and walk out glowing and get rejected. The replay in your head at 11 p.m. is not evidence, and it's not a review — it's just adrenaline finishing. Write your notes within an hour while they're useful, then close the laptop and go do something with your hands.

After

The thank-you email

Send it within 24 hours. Always. To every interviewer.

It is a small effort with a real effect, and a meaningful share of candidates skip it.

Subject: Thank you — [Role] interview

Hi [Name],

Thank you for taking the time to talk with me today. I especially appreciated hearing about [specific thing they said] — it clarified what the first six months would actually look like.

Our conversation about [specific topic] reinforced my interest. [One sentence connecting your experience to something they raised, or briefly addressing something you wish you'd said better.]

Please let me know if there's anything else useful from my end. I'm looking forward to hearing about next steps.

Best, [Name]

Personalize each one if there were multiple interviewers — they compare.

This is also your chance to fix something. If you gave a weak answer, one sentence here can repair it: "On your question about handling conflicting deadlines, I gave a fairly general answer — the concrete example I should have used was..."

The short version, if writing it is what's stopping you from sending it:

Hi [Name] — thanks for the time today. The part about [specific thing] was genuinely useful, and it made me more interested, not less. Let me know if anything else would help from my end. — [Your name]

Three sentences beats nothing by an enormous margin, and nothing is what most candidates send. Email, not handwritten — a card arrives after the decision. Get addresses from the calendar invite, the recruiter, or the standard format at that company (firstname.lastname@ is a safe guess); if you can't find one, send it all to the recruiter and ask them to pass it along.

Following up

• If they gave a timeline, wait for it, then follow up once.
• If they didn't, follow up after a week.
• One follow-up after that, a week later.
• Then move on.

Keep applying while you wait. Nothing is real until you have a written offer, and even then things fall through.

Rejection

Ask for feedback. Most companies won't give it (legal caution), but occasionally someone will, and it's valuable.

"Thank you for letting me know. If you're able to share any feedback about where I fell short, I'd genuinely appreciate it — I'm trying to improve."

Stay in touch with people you connected with. Candidates who were the runner-up get called when the next role opens, or when the hire doesn't work out. This happens more often than people realize.

And: rejection is mostly not about you. They had an internal candidate, someone had adjacent experience, the budget changed, the hiring manager had a preference nobody articulated. You will never know, and constructing a story about your deficiencies from no information is a bad use of your energy.

Red flags in the interview

You're evaluating them. Watch for:

• Disorganization — interviewers who haven't read your résumé, rescheduling repeatedly, no clear process
• Evasiveness about why the role is open or about turnover
• Trouble answering "what do you like about working here?"
• "We're like a family" — often precedes boundary problems and unpaid overtime
• Enthusiasm about how hard everyone works, "hustle," or people being here at 9 p.m.
• Vagueness about compensation deep into the process
• Pressure to decide immediately — a good employer gives you days
• Badmouthing the previous person in the role
• Interviewers who seem unhappy or exchange looks
• Wildly different descriptions of the role from different interviewers
• Unpaid work disguised as an assessment — a take-home that is a real deliverable they'd otherwise pay for
• Refusing to put the offer in writing

Trust these signals. Interview processes are the company on its best behavior. If it's bad now, it will not improve.

What the worst ones actually mean

Some of these are worth translating, because they sound mild and aren't.

"The last person? It just wasn't a fit." Delivered vaguely, twice, by different people, this usually means the role is impossible, the manager is difficult, or someone was managed out and nobody wants to say so. Follow up once: "How long were they in the seat?" A number under a year, twice in a row, is your answer.

Resistance to naming a range. In much of the US it is now legally required to disclose one, and everywhere else it's just information they already have. A recruiter who won't say — after you've asked directly, twice — is preserving the option to lowball you, and that same instinct will show up at raise time. It is also, practically, a reason to stop spending your unpaid hours on them.

"We all wear many hats here." Sometimes true and fine at a genuinely small company. Often it means the job has no defined scope and the workload has no ceiling, because there's nobody to say no on your behalf. Test it: "If I'm here six months and doing a great job, what am I spending Tuesday on?" A specific answer is reassuring. A laugh and "honestly, anything" is not.

"We need an answer by tomorrow." Legitimate offers come with days. An exploding deadline is a device to stop you from comparing, negotiating, or thinking. It is also the most common feature of the offers people most regret. See Chapter 22 for how to buy time without losing the offer.

A process that keeps breaking. Interviewers who haven't read your résumé, rounds rescheduled three times, two weeks of silence and then a same-day request. This is the company's recruiting process, which is the part they've resourced and rehearsed. Whatever this is like, your onboarding will be worse.

⚠️ THE TRAP: "We're like a family here"

It's said warmly and it usually is meant warmly, which is what makes it work.

What it functionally means: the boundary between the job and the rest of your life is going to be treated as negotiable. Families don't have overtime, or job descriptions, or exit interviews. You don't send a family member a written complaint about their conduct. You don't leave a family for a better offer without it being a betrayal. Every one of those is a protection you need at work and don't have at home.

Who profits: an employer that gets discretionary effort, unpaid hours, and reduced turnover out of loyalty rather than out of pay. It costs nothing to say and it saves real money.

How to check what's underneath it. Ask, pleasantly: "That's nice to hear — practically, how does the team handle time off and after-hours requests?" Then listen for whether the answer is a policy or a vibe. A good workplace answers with a mechanism. "We have unlimited PTO and the manager takes three weeks so people feel okay taking it" is a mechanism. "Honestly, we just take care of each other" is not.

What healthy looks like instead: clear scope, written expectations, people who go home, and a manager who describes leaving well as a normal thing that happens. The best teams talk like a good team, not like a family.

And a specific version to watch for: "family" language plus a founder who tells origin-story anecdotes about sleeping in the office, plus an inability to name a single person who left on good terms. That combination is not a culture, it's a staffing strategy.

🎓 GOING DEEPER: Legal boundaries on questions

Employers generally may not ask about, or base decisions on: race, color, religion, national origin, sex (including pregnancy, sexual orientation, and gender identity), age (40+), disability, genetic information, or citizenship status beyond work authorization. Many states add marital status, arrest record, and more.

Questions that cross the line: Are you married? Do you have children? Are you planning to? Where are you from originally? What's your religion? How old are you? When did you graduate (as a proxy for age)? Do you have a disability? Have you ever been arrested?

They may ask: Are you legally authorized to work in the US? Will you need sponsorship? Can you perform the essential functions of this job, with or without accommodation? Are you over 18? Have you been convicted of a crime (subject to ban-the-box laws)?

If asked something improper, you have options depending on how much you want the job: - Answer the underlying concern: "If you're asking about my availability, I can work the schedule this role requires." - Redirect gently: "I'm not sure how that relates to the role — can you tell me more about what you're looking for?" - Decline: "I'd prefer to keep the conversation on my qualifications."

And note it. An improper question is itself information about the employer. If you believe you were discriminated against, you can file with the EEOC (eeoc.gov) — generally within 180 days, extended to 300 in states with their own agency.

🌍 OUTSIDE THE US

Norms differ meaningfully.

• Personal questions that are illegal in the US (age, marital status, children) are legal and routine in a number of countries. Know the local convention.
• UK: understatement is cultural, and American-style self-promotion can read as arrogance. Public sector and much of the NHS run structured competency interviews — scored against published criteria, often with the criteria given to you in advance. Prepare a STAR answer for each stated competency, literally in order. References are usually taken after an offer, and offers are commonly "subject to references and DBS check." Notice periods of one to three months are normal, so "when can you start" has a different answer than in the US.
• Canada: very similar to the US in format. Human rights codes are provincial, and the protected grounds are broadly comparable. Employers may ask about work authorization but not citizenship. Bilingual roles in the federal government and in Quebec may include a language assessment.
• Australia and New Zealand: informal in tone, structured underneath. Expect explicit "behavioural" questions and often a required response to selection criteria for government roles. Referees are contacted seriously and early — line up two who will actually pick up the phone. Ask about the award or enterprise agreement covering the role; it sets minimum pay and conditions.
• Germany, Netherlands, Nordics: more formal, more structured, directness valued over enthusiasm; overselling reads badly. German applications may still include a photo and a Lebenslauf with personal details, though this is fading and is optional. Probation periods (Probezeit) of six months are standard and are discussed openly.
• France: the CV and lettre de motivation are both expected, and interviews can be more intellectual and less behavioural — expect to defend your reasoning rather than recite examples.
• Japan: highly formalized, including how you enter the room, how you sit, and how you receive a business card with two hands. New-graduate hiring runs on a synchronized annual cycle that is almost unrecognizable from the outside.
• India: multiple technical rounds are common, and interviewers frequently ask directly about current salary and expected salary — negotiation is usually framed as a percentage hike over your current package. Notice periods of 30 to 90 days are standard and are a real scheduling constraint.
• Gulf states (UAE, Saudi Arabia, Qatar): offers are tied to visa sponsorship, and the package (housing, flights, schooling) matters as much as base salary. Personal questions that would be illegal in the US are routine.
• Salary discussion happens at different stages everywhere; in some countries it's raised openly in the first minute. Confirm the local norm before you apply the US advice about deflecting. Appendix D has more.

Common mistakes

• No specific questions for them at the end.
• Not researching the company.
• Rambling instead of using STAR.
• Speaking badly about a former employer.
• A fake weakness.
• Being unable to explain why this company.
• Naming a salary number first, or naming one too low.
• Not sending a thank-you email.
• Memorizing answers word for word.
• Not practicing out loud.
• Backlighting on video calls.
• Ignoring red flags because you need a job.
• Assuming visible nerves have cost you the role.
• Narrating every accomplishment as "we" so the interviewer can't tell what you did.
• Spending ninety seconds on the situation and ten on the action.
• Over-explaining a firing, a gap, or a record when two sentences would have closed it.
• Apologizing for experience that came from retail, service, caregiving, or the military.
• Doing a twenty-hour "test project" on their live account for free.
• Not asking what the rest of the process looks like, then being surprised by round five.
• Never asking why the position is open.
• Accepting an exploding deadline because you were afraid to ask for two days.

Key numbers

Chapter recap

• They're answering three questions: can you, will you, and can we work with you.
• Prepare six to eight stories and reuse them. Practice out loud.
• STAR keeps behavioral answers tight. Use "I," not "we," for your actions.
• "Tell me about yourself" is Present → Past → Future in 90 seconds.
• Never badmouth a former employer.
• Give a real weakness with a real remedy.
• Always have questions. "No" reads as disinterest.
• Don't name a salary number first; give a range with your target at the bottom.
• Send a thank-you within 24 hours, personalized, and use it to fix a weak answer.
• Ask what the whole process looks like in the first five minutes of the first call.
• Spend your STAR time on the action, and say "I," not "we."
• Your best stories can come from a warehouse, a diner, or caring for a family member. Don't apologize for them.
• Two sentences and a question back, for anything you're dreading being asked.
• An exercise uses fake data. If they could ship it tomorrow, it's work, and you can say so.
• Clean and plain is genuinely fine. Free clothing programs exist and you're allowed to use them.
• You can ask for interview accommodations without disclosing a diagnosis.
• Interview processes are the company at its best. Believe the red flags.

Exercises

Do this right now (30 minutes)

20.1 — Write your 90-second intro. Present → Past → Future, four sentences. Time yourself saying it out loud. Cut until it fits under 95 seconds. Deliverable: a written intro you could say cold, tomorrow, to a stranger.

20.2 — List your eight stories. Just the headlines — the situations, one line each. Force at least two of them to come from outside an office: a job on your feet, a family situation you managed, something you ran for free. You'll flesh them out next.

20.3 — Write five questions to ask an interviewer, tailored to a role you actually want. At least one must be from the turnover column and one from the workload column of the table above.

20.4 — Look up salary data for your target role, level, and city. Use two sources, not one — bls.gov/oes plus one site with self-reported numbers. Deliverable: a written range, the two sources, and today's date, so you know when it goes stale.

This week (4 hours)

20.5 — Write all eight stories in STAR format. Actually write them. Include a number in every Result section, even a rough one, and end each with what stuck afterward.

20.6 — Time one story with a stopwatch and check the proportions. Situation and task together under 30 seconds, action around a minute. Most people discover their setup is twice as long as they thought. Fix that one story, then apply the same cut to the rest.

20.7 — Write your two-sentence answer for the thing you're dreading being asked. Fact, then what's true now, then a question back. Say it out loud six times until it comes out at a normal speed with no extra words attached.

20.8 — Practice out loud. Record yourself answering five questions on your phone. Watch it back. This is uncomfortable and it is the single most effective preparation there is.

20.9 — Fix your video setup. Light in front, camera at eye level, tidy background, headphones. Test on the actual platform, not a different one. Then deliberately break it — turn off your wifi mid-call — and practice the recovery.

20.10 — Do a mock interview. With a friend, a career center, an American Job Center, or in front of a mirror. Ask them to be a bit tough, and specifically to ask you the question from 20.7.

20.11 — Write your weakness answer. A real one, with a real remedy. This is the question people most need to prepare.

This month (varies)

20.12 — Research one company thoroughly. Ninety minutes on a company you actually want: what they sell, how they make money, who competes with them, one recent piece of news, and the LinkedIn history of two people you'd work with. Notice how different you'd sound with that preparation.

20.13 — Draft your thank-you template. Both versions — the full one and the three-sentence one — so you can personalize and send in ten minutes rather than agonizing for two days and sending nothing.

20.14 — Practice the salary deflection out loud until it's smooth, including the version where they won't budge and you have to name a number anyway. This is worth thousands of dollars and takes ten minutes to rehearse. Then read Chapter 22.

20.15 — Get your interview outfit ready. Clean, fitting, hanging up. If you don't have one, get one now, not the night before — thrift store discount day, a Buy Nothing post, or a call to 211 or your American Job Center.

20.16 — Solve the logistics before you need them. Write down, on one page: where you'll take a video call if the house is loud, how you get to an on-site without a car, who covers childcare on two days' notice, and which hours you can interview without losing pay. Every one of these is easier to solve on a Tuesday than the night before.

20.17 — Write your red flag list. What would make you turn down an offer? Decide now, while you're not desperate, and keep it somewhere you'll actually reread it when you are.

20.18 — Start an interview log. One row per interview: company, role, date, who you met, the questions they asked, what you wish you'd said, and the outcome. After six entries you'll be able to see your own pattern — the question that keeps ambushing you, the round where things stall. That pattern is the whole point.

Reflection

20.19 — What's the hardest interview question for you? Why? Write the answer you wish you could give, then edit it into one you can.

20.20 — Have you ever taken a job despite red flags? What happened? What would you notice now?

20.21 — What do you want an interviewer to remember about you an hour after you leave? Does your preparation make that likely?

20.22 — Which of your stories comes from work you've been quietly embarrassed about — a service job, a warehouse, caring for someone? Read it back as if a stranger had told it to you. Would you hire that person?

📋 ADD TO YOUR OPERATING SYSTEM

Add to Section 19: Career:

• Your eight STAR stories, written out — update these as you accumulate new accomplishments
• Your 90-second intro
• Your standard questions for interviewers
• Your salary research: role, level, market, range, sources, date researched
• Your salary deflection script
• Thank-you email template
• Interview log: company, role, date, interviewers, questions asked, how it went, outcome
• Your red flag list
• Your two-sentence answer for the thing you're dreading being asked
• Your interview logistics page: quiet space, transport, childcare, hours you can interview without losing pay
• Any interview accommodations you ask for, and who said yes
• Interview outfit status

Keep the log in the document itself, not in your head. No SSNs, full account numbers, or passwords anywhere in this file.

Next: Chapter 21 — you got it. The first ninety days determine more than most people realize, and there are rules nobody writes down.