The Non-Technical Half of the Interview: Behavioral Questions, the STAR Method, and What Recruiters Are Actually Scoring

Part 5 of 10 · ~2 min

Why the Action Section Is the One That Actually Gets Scored

Go back to both stories above and count sentences per STAR section. In both, Action is the longest part by a wide margin, and that's not an accident of how they happened to come out — it should be true of almost every well-built answer, because Action is the only section that's actually about you. Situation is about the company and the project. Task is one sentence of scope-setting. Result is largely about outcomes that weren't entirely under your control either — a customer's reaction, a finance analyst's catch, the market. Action is the one place in the whole structure where an interviewer gets direct evidence of how you think and what you actually did, which is the entire reason the question got asked in the first place.

Most candidates compress it out of instinct, the same way Ananya's first attempt did — "we had this invoicing feature that took longer than we thought" skips straight from problem to outcome and leaves out every decision in between, which is exactly the part an interviewer can't infer and has no way to score. The fix is a habit, not a formula: for any story going into a story bank, ask what the two or three real decision points were, and for each one, name what the options actually were and which one got picked and why. "I raised it with my manager and we decided to slip the date" compresses an entire trade-off analysis into a passive "we decided" — the stronger version from the invoicing story names the two actual options on the table and states, specifically, which one the candidate personally recommended and the reasoning behind it. That's the difference between describing an outcome and describing a decision, and a decision is the only one of the two that says anything about how you'd handle the next one.

It's also worth being precise about the pronouns doing work here. "We decided to slip the date" is honest when a decision genuinely was made jointly — most real decisions on a team are — but it still has to be paired with what you specifically contributed to getting there: the option you raised, the trade-off you flagged, the data you brought to the conversation. An interviewer isn't looking for a candidate who claims sole credit for a team outcome. They're looking for evidence of your actual contribution inside a real, collaborative decision, which is a different and more believable thing than either "I alone fixed everything" or "we, collectively, somehow arrived at a good outcome with no visible individual reasoning behind it."