The Behavioral Interview

The four components

• Situation — set the scene. Brief: one or two sentences. What project, team, or context are we in? Don't over-explain. Get to the tension.
• Task — your specific responsibility. What were you asked to do or what did you take ownership of? "The team needed to..." is not the same as "My responsibility was to..."
• Action — this is the heart of the answer. What did YOU do? Be specific. Use first person. Describe your reasoning, your approach, the hard decision you made — not what the team did.
• Result — what happened? Quantify where possible. Be honest about partial successes. A story where everything went perfectly is less credible and less interesting than one where it was hard.

Common STAR mistakes

• Spending 80% of the answer on Situation and Task, then rushing through Action and Result — the two parts interviewers actually care about
• Saying "we" throughout the Action. The interviewer wants to understand your contribution, not your team's.
• Choosing a story with no real tension or challenge. "I did a thing and it went well" is forgettable.
• Not having a result. "The project was ongoing when I left" is weak. Find something concrete: adoption rate, team feedback, a process improvement.
• Giving the same polished story to every question instead of actually matching it to the prompt.

Stories to have ready

• Biggest technical challenge — a hard problem, the path you took, what you learned. This covers "tell me about a technical challenge" and "describe a complex project."
• A disagreement with a colleague or manager — how you handled the conflict, what you did to resolve it, what the outcome was. This covers collaboration, communication, and dealing with conflict.
• A failure or mistake — what went wrong, what you owned, what you changed. The most revealing story. Interviewers remember candidates who can be honest about failure.
• Learning something new under pressure — when you had to pick up an unfamiliar technology, domain, or skill quickly. Covers growth mindset questions.
• Influencing without authority — a time you changed a decision or direction without being in charge. Covers leadership, influence, and initiative.
• Delivering under constraints — tight deadline, reduced scope, under-resourced team. Covers prioritisation, pragmatism, and delivery focus.
• Mentoring or helping someone grow — applies to senior roles. Covers leadership, communication, and investment in others.

Preparing each story

Don't memorise a script. Instead, know three things for each story:

• The opening — one clear sentence that sets the context and signals what kind of story it is
• The core tension — the specific hard thing, the decision, the conflict, the constraint
• The outcome — what happened, what you'd do differently, what you learned

From those three anchors, you can tell the story naturally and adapt the emphasis to what the question is actually asking.

"Tell me about yourself"

A 2-minute career narrative. Not your CV read aloud. The structure:

• Where you started and what you built in the early years (brief)
• The progression that led to where you are now (the thread)
• Why this role / company specifically (the landing)

Rehearse this until it feels natural. You'll use a version of it in every interview.

"Why do you want to leave your current role?"

Be honest, but be forward-looking. The answer should point toward what you want — not away from what you dislike.

• What you want to do more of, not what you're tired of
• Never speak negatively about your current employer — it raises trust concerns
• "I've learned a lot here. I'm looking for more X, and this role seems like the right next step" is always a defensible answer

"What's your biggest weakness?"

The trap: giving a non-weakness ("I work too hard"). The other trap: giving a genuine red-flag weakness with no reflection.

• Give a real weakness — something that has actually caused friction or a missed opportunity
• Show that you're aware of it and have a specific strategy for managing it
• Show evidence of growth — what's changed
• Keep it relevant: a weakness in an area that doesn't affect the role you're interviewing for is less powerful than one that does, handled maturely

"Where do you see yourself in 3 years?"

Show direction, not a specific destination. Interviewers want to know you're ambitious but also realistic about where this role fits in your trajectory.

• Reference a direction (deeper technical expertise, moving toward architecture, leading a team) that connects naturally to this role
• Avoid: "I want to be a CTO" unless it's genuinely credible in context
• The honest answer often wins: "I want to be significantly more capable in X. I see this role as the environment where that growth happens."

Finding the numbers in your stories

• Did it affect time? (reduced X by Y hours/weeks, released Z weeks earlier)
• Did it affect money? (saved X in infrastructure cost, increased conversion by Y%)
• Did it affect users? (improved load time for N million users, reduced error rate from X% to Y%)
• Did it affect the team? (reduced onboarding from 4 weeks to 2, eliminated 3 hours of manual testing per sprint)
• Did it reduce risk? (prevented a class of security vulnerabilities, made the system recoverable from failure in minutes instead of hours)

When you can't quantify

Not every impact is measurable. When you can't use a number, use a qualitative statement that's still specific:

• "It changed how the team thought about deployment — we went from fearing releases to deploying twice a day."
• "The client explicitly mentioned it in the post-project review as the reason they extended the contract."
• "It became the template that two other teams adopted for their own services."

Questions that reveal what you actually care about

• "What does success look like in this role at 6 months? At 12?"
• "What's the biggest challenge the team is facing right now?"
• "How are technical decisions made — is it top-down or does the team have real influence?"
• "What's the on-call situation like for this team, and how is incident response handled?"
• "Can you tell me about someone who's grown quickly in this team? What did they do differently?"
• "What would make you regret hiring the wrong person for this role?"
• "What's the biggest thing the team has changed its mind about in the last year?"

What to avoid

• "What does your company do?" — do your research
• "How much paid time off do I get?" — save compensation questions for the recruiter
• Asking about something clearly covered on the company's website or in the job description — it signals you didn't prepare

The basics

• Know your number before the conversation — "What are your salary expectations?" should never catch you off guard. Research the market, know your target range.
• Avoid anchoring first if you can — "I'm flexible and more interested in the full opportunity" buys you time to hear their range first. But have a number ready if they push.
• Give a range, not a point — "I'm looking for €X–Y, depending on the full package." The lower end should be the minimum you'd accept.
• Everything is negotiable — even when they say it isn't. Signing bonus, remote days, equity, start date, professional development budget — all levers.
• Silence is not awkward — after an offer is made, it's expected. Take 24–48 hours to consider. It shows you're treating the decision seriously.
• Never negotiate against yourself — if they make an offer, don't immediately say "I was hoping for more." Counter with a specific number and a brief justification.