Behavioral Interviews cheat sheet

• 90 seconds is about 200 words. The usual error is 60 seconds of background and 15 of action.
• Add a short "because" to your main actions. Cut to the two or three actions that show the signal.

Watch out: The "we" trap: "We decided, we tested, we shipped." Say "I proposed the queue, I wrote the load test", and share credit for the rest.

1. Collect from your resume, old pull requests and last review.
2. Pick six stories, at least two about mistakes or hard moments. Tag the signals each can show.
3. Fill a matrix (stories by signals). Two ready stories per common signal.
4. Say each aloud, cut to 90 seconds, memorise the bullets and the first sentence.

Tip: Expect follow-ups: what did YOU do, why that option, what would you do differently, how do you know it worked.

Present (15 s)

Backend dev, 4 years; I own a notification service. Failures down from 3% to 0.5%.

Past (30 s)

A startup where I did everything, then a team with review and tests.

Future (15 s)

I want reliability work at larger scale; your platform role is that step.

• About 60 seconds, 150 words, one number. Write the future part first.
• Change only the last sentence per company. Mention only highlights you could discuss for five minutes.
• Fresher: projects plus a user count. Career switcher: the old career as a strength, plus proof of work.

Watch out: Do not start in childhood, list technologies, or say "hard worker, team player". The interviewer has your resume.

Product

One true thing you tried or learned

Work

A detail from their blog, talk, code or job post

You

How you fit, or what you want to learn

Tip: Leaving: start with something you learned, give one neutral reason, point to the future, 30 seconds. Layoff or gap: one plain sentence, no blame.

Watch out: No fake weakness ("I care too much"), no villain, no hero story for a problem you caused. Disagree with a manager: bring a fact and a smaller option.

• Level shows in scope: junior finishes tasks, mid owns a feature, senior finds problems and brings others along.
• Without approval: act only on small, reversible things and tell your manager the same day.

Tip: No exact figure? Say "I estimate about 40%". Never invent 37.4%, and never claim impact you did not cause.

• Personal or illegal question: answer the work concern behind it, deflect politely, or decline. Keep notes. Not legal advice.
• Put the awkward fact second, then follow with the future.

Watch out: Never "I'm a perfectionist". Never lie about dates; they can be checked.

Tip: Prepare 8, ask 3 to 5, each tied to something they said. One flag is a question; three is a pattern. Send a short thank-you the same day.

• Know three numbers: walk-away, target, reach. Know your alternative.
• Ask for their range first. Never lie about current pay. Do not accept on the call; ask for details in writing.
• Counter once, in writing, warmly, with specific numbers and one or two reasons.

Watch out: Higher base is not always higher pay. A cliff means no equity before month 12. RSUs are often taxed at vesting. Numbers here are invented.

Stuck: invoice export (ticket 412)
Problem: CSV empty above 500 rows
Tried: query is fine; export ok at 100
Question: should export.ts page?
Meanwhile: moving to ticket 415

1. Late task: tell your manager the moment you know.
2. Say status, reason, new range, options, recommendation.
3. Ask for a decision by a date.

• Monday plan, Friday summary (done, not done, learned). Main point first, one topic per message.
• 1:1 is your meeting: wins, help needed, feedback, growth. Write actions.
• Disagree once with facts and an option, then commit. Move heated chat to a call.

• Score 1 to 4, with evidence, on motivation, proactivity, unstructured work, perseverance, conflict, empathy, growth, communication.
• Bands out of 32: 28+ strong, 24 to 27 good, 20 to 23 borderline. Any 1 is a red alert.

Tip: Answers run 1.5 to 3 minutes. Start with the point, say the result slowly, and pause two seconds before answering.