Behavioral vs Technical: the prep strategy for each

If you spend the week before a behavioral interview doing LeetCode, you will probably tank the behavioral. If you spend it writing STAR stories, you'll probably also tank the behavioral — just for different reasons.

They're testing different things. Not just different content — different skills, different failure modes, and preparation that actually transfers looks completely different for each.

What technical interviews are actually testing

The obvious answer is "whether you can code." That's partly true but it misses most of the picture.

Technical interviews are primarily testing pattern recognition and communication. Can you look at a new problem and identify which category it belongs to? Do you recognize that you've seen something structurally similar before? Can you explain your thinking in a way that makes sense to someone else who's watching you think?

The candidate who's worked through 300 problems has an advantage not because they've memorized 300 solutions, but because they've developed pattern intuition. When they see a problem involving intervals, something clicks. When constraints suggest O(n log n), they know what kind of solution to look for.

What behavioral interviews are actually testing

Not your stories. Your judgment.

Behavioral interviews use your past as a proxy for how you'll behave in the future. "Tell me about a time you disagreed with a coworker" isn't about whether you've had a disagreement. It's about whether you handle disagreement productively, whether you stayed professional, whether you can reflect on a situation honestly and say what you'd do differently.

The interviewer is trying to figure out: is this person who they say they are? Will they actually behave the way they're describing?

This is why vague answers are so damaging. "I worked with a difficult teammate once and we eventually figured it out" tells the interviewer nothing. They can't evaluate your judgment if you don't give them specifics to evaluate.

STAR done wrong sounds worse than not using STAR

STAR — Situation, Task, Action, Result — is a useful scaffold. It's also been cargo-culted into something almost painful to sit through.

Good behavioral answers are specific. They name real constraints — the actual deadline, why it was tight, what was at stake. They describe real decisions with real tradeoffs, the specific thing you said to that coworker, the thing that almost went wrong. They show what you actually did, not what a reasonable person in your situation would have done.

The "R" in STAR gets skipped the most. "We shipped on time" is not a result. What did the project actually accomplish? What did you learn? What would you do differently? That's where the judgment shows.

The prep strategies are completely different

For technical: Practice by doing. Solve problems out loud. Track which categories you miss, not which specific problems. When you get something wrong, understand why the correct approach works before you move on. The goal is pattern fluency, not problem coverage.

For behavioral: Write out your stories in advance — not as bullet points, as actual narratives. Then practice saying them without reading them until they sound natural rather than scripted. Know four or five stories deeply, not twenty shallowly. Interviewers ask follow-up questions, and if you only know the surface of your story, you'll run out of answer fast.

One more thing: use different stories for different questions. Candidates who answer "tell me about a challenge," "tell me about a failure," and "tell me about a conflict" all with the same project are obvious. It also makes it look like that's the only interesting thing you've ever done.

The real mistake

Most people treat interview prep as a single undifferentiated task. They have a job interview coming up, so they "prepare." What they actually do is whatever feels most comfortable — usually some mix of reading solutions and writing bullet points — and call it preparation.

The candidates who do well tend to be the ones who think about what specifically they're being tested on, what specific skill is actually being evaluated, and what kind of practice develops that skill. It sounds obvious. Barely anyone does it.