
I’ll be honest: I almost didn’t prepare for behavioral interviews. I figured I’d just talk about my work. Then in one of my early loops I got “Tell me about a time you disagreed with your manager”, and I rambled for five minutes without really answering the question.
Behavioral rounds can make or break an offer, and at senior levels they often decide your level. The good news is that they’re the easiest round to prepare for, because you already have the material. You just need to organize it.
Here’s the system I used: build a small bank of stories once, then reuse them for almost any question.
Step 1: Collect 6 real stories
Go through the last 2-3 years of your work and write down projects or moments where something interesting happened. Look for:
- A project you’re proud of, with a measurable result.
- A disagreement with a teammate, designer, PM, or manager.
- A mistake or failure, and what you changed afterward.
- A time you led something without being asked.
- A time the requirements were vague and you figured it out.
- A time you helped someone else grow.
Frontend engineers have great material here: performance improvements, design system decisions, accessibility pushes, migrations (class components to hooks, JavaScript to TypeScript), and cross-functional work with design and product.
Step 2: Map stories to themes

Most behavioral questions fall into a small set of themes: conflict, failure, leadership, ambiguity, impact, and growth. A good story usually covers two or three of them.
Make a simple grid like the one above. When you get a question in the interview, you’re not inventing an answer. You’re picking the best-fitting story from your bank. That takes a lot of pressure off.
Step 3: Structure each story with STAR
STAR stands for Situation, Task, Action, Result. It’s a simple way to keep your answer focused.
| Part | What to say | Time |
|---|---|---|
| Situation | Context in one or two sentences | ~15% |
| Task | What you specifically needed to do, and why it was hard | ~10% |
| Action | What you did, step by step, including decisions and trade-offs | ~60% |
| Result | The outcome, ideally with a number, and what you learned | ~15% |
The most common mistake is spending most of the time on the Situation. Interviewers care about your Actions. That’s where they find the signal.
An example answer
Question: “Tell me about a time you disagreed with a teammate.”
“Situation: Our team was building a new checkout flow, and a senior engineer wanted to build our own date picker component to match the design exactly.
Task: I owned the accessibility review, and I was worried a custom date picker would take weeks to make keyboard and screen-reader friendly.
Action: Instead of arguing in the PR, I built a quick prototype using a well-tested accessible library, styled to match the design as closely as possible. I listed the specific gaps compared to the mockup, and estimated the effort for both options. Then I set up a 20-minute call with him and our designer to go through it. The designer was fine with the small visual differences once she saw them side by side.
Result: We went with the library and shipped about two weeks earlier than planned. And because he felt heard, he later asked me to review accessibility on his other projects. What I learned is that a working prototype settles disagreements much faster than a debate.”
Notice what makes it work: it’s specific, it’s about what “I” did, there’s a trade-off, there’s a result, and there’s a lesson. It also doesn’t make the other person the villain.
Important: use your own real stories. Don’t invent or exaggerate details. Good interviewers ask follow-up questions, and made-up details fall apart quickly.
Mistakes I see constantly
- “We” instead of “I”. Team credit is nice, but the interviewer is evaluating you. Say what you did.
- No result. End with an outcome. Numbers help: load time, conversion, bugs, time saved, adoption.
- Blaming others. In conflict stories, show you understood the other person’s point of view.
- Fake failures. “I work too hard” isn’t a failure. Pick a real mistake, own it, and show what you changed.
- Going too long. Aim for about two minutes. Let them ask follow-ups.
Questions to prepare for
- Walk me through your resume / tell me about yourself.
- Tell me about a project you’re most proud of.
- Tell me about a time you disagreed with someone. How did you resolve it?
- Tell me about a time you failed or made a mistake.
- Tell me about a time you received difficult feedback.
- Tell me about a time you had to make a decision without all the information.
- Tell me about a time you influenced a decision without authority.
- Why do you want to work here?
For “Tell me about yourself”, have a 60-90 second version ready: what you do now, one or two highlights relevant to this role, and why you’re interested in this company. Practice it out loud until it sounds natural, not memorized.
Level matters
| Level | What your stories should show |
|---|---|
| Junior / mid | Ownership of your work, learning quickly, working well with others |
| Senior | Leading projects, influencing technical decisions, mentoring |
| Staff+ | Impact across teams, setting direction, handling ambiguity at the org level |
If you’re interviewing for senior and all your stories are about tasks you were assigned, you might get down-leveled even if your coding was strong. Pick stories that show the scope you’re interviewing for.
I wrote a more detailed free behavioral interview guide, and the behavioral questions section has example answers for the most common questions.
And that’s it, folks. Six stories, a simple grid, and STAR. A few evenings of prep here can be worth more than another week of coding questions.
