Most interview advice boils down to a list: here are 20 questions, here are sample answers, good luck. I've sat on the other side of the table for enough of these to tell you why that approach fails. It's not that people don't prepare. It's that they prepare for the wrong unit. They memorize answers to specific questions, and the second the conversation drifts even slightly off-script, the polish disappears and you're watching someone reconstruct a sentence in real time.
The fix isn't a longer list of questions. It's a smaller number of well-built stories, a structure that keeps you from rambling, and a plan for the follow-up questions that actually trip people up.
Build stories, not answers
There are maybe six or seven distinct things an interviewer is trying to figure out about you: can you solve problems, do you work well with others, do you handle conflict without falling apart, can you lead when it's needed, do you learn from mistakes, can you manage ambiguity. Every behavioral question is really just a different door into one of those themes.
So instead of prepping answer-per-question, go through your last three to five years of work and pull out four to six real situations that were genuinely hard, messy, or high-stakes. A project that almost fell apart. A disagreement with a coworker that you had to navigate. A time you were handed something with no clear instructions. A mistake you made and caught. If you can only think of easy, tidy examples, dig further back — the good stories are usually the ones you'd rather not bring up.
Each of those four to six stories should be flexible enough to answer several different questions depending on which part you emphasize. The same project-rescue story can answer "tell me about a time you solved a difficult problem," "describe a conflict with a teammate," and "tell me about a time you had to influence someone without authority" — you just pull a different thread out of the same fabric. That's the actual skill: not memorizing 20 answers, but knowing your 5 stories cold enough to reshape them on demand.
A structure that isn't just "STAR"
You've heard of STAR — Situation, Task, Action, Result. Naming the acronym isn't the useful part; almost everyone already knows it exists, and knowing it exists is not why people still ramble. The reason STAR answers go sideways is that people spend 80% of their airtime on the Situation and Task — scene-setting, org-chart context, backstory nobody asked for — and then rush the Action, which is the only part that's actually about them.
Use this weighting instead: 20% context, 60% what you specifically did, 20% result and what you'd change. That middle section needs to be about your decisions, not your team's. Interviewers are listening for "I" statements that show actual judgment, not "we" statements that describe a group outcome you were adjacent to.
Here's the difference in practice. Weak version, buried in "we":
"So our team was dealing with a client who was unhappy with the timeline, and we had a lot of back and forth, and eventually we figured out a way to restructure the deliverables, and the client ended up happy and we kept the account."
You learn almost nothing about the candidate from that. Now the same situation, restructured around what one person actually did:
"A client was six weeks from a launch date and told our account lead they were pulling the contract over slipped deadlines. I asked to sit in on the next call, and instead of defending the timeline, I asked the client which three deliverables actually mattered for their launch versus which were nice-to-haves we'd bundled in. Turned out only two of the eight items were blocking their launch. I split the contract into a two-item rush delivery and a slower phase two, got sign-off from my director same day, and we hit the rush deadline with four days to spare. The client stayed, and we changed our default proposal template to separate launch-critical items from phase-two work on every deal after that."
Notice the second version has a number, a specific decision, and a lasting change that came out of it. That last sentence — what changed afterward — is the "what you'd do differently" beat, folded in naturally instead of tacked on as an afterthought.
The follow-up is where rehearsed answers fall apart
Here's the part almost nobody prepares for, and it's the part that actually separates candidates. A good interviewer doesn't just take your STAR answer and move to the next question. They poke at it: "What would you have done if the client said no to splitting the contract?" "How did your director react before you had the client's sign-off?" "Was there anyone on your team who disagreed with that approach?"
If your story is real, these are easy — you were there, you remember the texture of it. If your story is polished-but-thin, or lightly exaggerated, this is exactly where it collapses, because you haven't thought past the version you rehearsed. So for each of your core stories, spend a few minutes anticipating the two or three most obvious follow-ups and actually think through honest answers, including ones where the honest answer is "I got lucky" or "I'd handle that differently now." Interviewers trust a slightly imperfect real answer far more than a suspiciously clean one.
"What's your greatest weakness" and salary questions, without the dodge
Two questions produce more transparently fake answers than anything else in an interview, and both are worth actually preparing for instead of deflecting.
On weaknesses: skip "I work too hard" and skip full self-flagellation too. The useful format is a real limitation plus the concrete thing you're doing about it. For example: "I default to solving problems myself before looping in the team, which works fine solo but slows things down on group projects. I've started setting a rule for myself — if something will take me more than a day, I post it in the team channel before I start, not after." That's specific, it's believable, and it shows you actually noticed the pattern and did something with it rather than just naming a flaw and moving on.
On salary, the non-answer everyone gives — "I'm flexible, what's your range?" — is fine as an opening move, but if pushed, have an actual number ready, anchored to research, not a guess: "Based on similar roles at companies this size in this market, I'm targeting $X to $Y, and I'm open to discussing the full package." Vague deflection reads as unprepared, not as savvy negotiation.
What to actually do before the interview
Write out your four to six stories in a few bullet points each — situation in one line, your specific actions in three or four lines, result and change in one line. Read them the day before, not the morning of. Think through two follow-up questions per story. Have a real weakness and a real salary number ready. That's the whole plan. It's less flashy than a 20-question crib sheet, and it's the reason some candidates sound sharp under pressure and others sound like they're reading off a card that got taken away.