The behavioral round is where technical seniors get filtered out for sounding like juniors. The questions are soft (“tell me about a conflict”) but the signal is hard: do you think in trade-offs, own outcomes, and communicate like someone others can follow? This post climbs from “what I did” to “the judgment I’d apply again”.
Mindset: junior describes tasks completed; senior explains the decision made under uncertainty, the alternative rejected, and what they’d do differently with the same information.
Junior — foundations
Q1. “Tell me about yourself.” How do you answer without rambling? A 90-second arc: who you are as an engineer (stack + what you care about), one concrete thing you’ve shipped recently, and why this role fits. No life story, no “I was born in…”. Senior signal: you frame yourself around problems you like solving, not technologies you’ve touched.
Q2. “What’s your biggest weakness?” — how do you answer it honestly? Pick a real, non-fatal one and show the system you built to compensate. “I used to underestimate migration risk; now I always prototype the risky path first.” Avoid fake weaknesses (“I work too hard”) — interviewers hear that immediately. Honesty plus a mitigation reads as self-aware, which is the senior trait.
Q3. “Where do you see yourself in 5 years?” Answer around growth in scope and judgment, not a title wish-list. “I want to be the person a team trusts with its riskiest architectural calls, and to have mentored a couple of engineers into that range.” It shows you’re thinking about leverage, not just promotion.
Q4. “Why do you want this job?” Tie it to something specific: the problem domain, the scale, the team’s way of working. “Your payments scale is exactly the distributed-systems problem I want to go deeper on.” Generic “great company” answers signal you didn’t research — and research is a senior baseline.
Q5. “Describe a bug you fixed.” Use a real one with a clear arc: symptom → how you reproduced it → root cause → fix → what you changed so it can’t recur. Junior answers stop at “I fixed it.” Senior answers end at “and here’s the guard I added” (test, alert, invariant).
Q6. “What do you do when you’re stuck?” Show a repeatable method, not panic: reproduce minimally, isolate (bisect/remove variables), read the actual error and source, then ask a specific question rather than a vague “it doesn’t work”. Senior signal: you unblock yourself with process before escalating.
Mid — tradeoffs & pitfalls
Q1. “Tell me about a disagreement with a colleague.” What are they really testing? Not the conflict — your collaboration texture: did you listen, argue from evidence, and reach a decision you committed to? The trap is either “I was right and they were wrong” (arrogant) or “we just agreed” (no spine). Good answer: state your position with data, acknowledge their valid point, and describe the resolution and what you’d do the same/differently.
Q2. “Describe a project that failed.” How do you frame it? Own the outcome without romanticizing. “We shipped X, it missed adoption, here’s the signal we ignored (we never validated the user need before building).” The senior move is to show you extracted a principle (“now I spike the riskiest assumption first”) — failure as a cheap tuition you actually learned from, not a story you’re embarrassed by.
Q3. “How do you prioritize when everything is urgent?” Show a framework, not a frantic list: impact × user count × reversibility. “A production data-corruption bug beats a cosmetic UI ticket; a reversible config change beats an irreversible data delete.” Then communicate the trade to stakeholders so the priority is shared, not secret. Senior = explicit, communicated prioritization.
Q4. “Tell me about a time you mentored someone.” Concrete, not “I helped the junior.” Describe the person’s starting point, the specific thing you taught (a debugging method, a design pattern), and the measurable outcome (they shipped a feature solo, or started reviewing PRs). Mentoring is a core senior axis — show you grew someone’s capability, not just did their work.
Q5. “How do you handle a vague or changing requirement?” Senior answer: you make the ambiguity explicit and pick a slice you can ship, then learn. “I’d write down the two interpretations, choose the cheaper-to-reverse one, ship a thin version, and get real feedback fast.” Juniors either freeze waiting for perfect specs or build the whole thing on a guess. Speed of learning beats completeness of guess.
Q6. “What’s a technical decision you regret?” Pick one with a real lesson and show the thinking that’s now different. “I over-engineered a config system for flexibility we never used — now I default to the simplest thing that works and add seams only when a real requirement appears.” The regret proves you’ve calibrated your instincts, which is exactly what senior means.
Senior — design & defense
Q1. “You’re the senior — the team wants to ship a risky feature Friday. What do you do?” “I’d separate ‘risky’ into ‘reversible’ vs ‘irreversible’. If it’s reversible (behind a flag, easy rollback), ship it and watch the metrics — Friday is fine with a flag. If it’s irreversible (data migration, billing change), I’d push to Monday and a lower-traffic window, with a rollback plan written before we start. I’d frame the call around blast radius and recovery time, not the calendar. The senior job is to make the risk explicit and the recovery ready — not to be the person who says no, or yes, on vibes.”
Q2. “Tell me about a time you made a call with incomplete information.” Walk a real one: what you knew, what you didn’t, the options, and the bet you made — plus how you de-risked it (small rollout, monitoring, a kill switch). The point is not that you were right, but that you had a process for uncertainty: decide under a time box, make it reversible, and instrument it so reality corrects you fast. That’s the difference between a senior and a gambler.
Q3. “How do you raise the level of engineers around you?” Beyond one-on-one mentoring: I’d point to concrete mechanisms — PR review that teaches (asks the question, doesn’t just fix), a written design doc culture, and post-incident reviews that blame the system not the person. A senior’s force-multiplier is the team’s habits. I’d give an example where a review comment changed how someone approached a whole class of problem.
Q4. “Describe a production incident you led the response to.” Structure: detection (how we knew), containment (what we did in the first 10 minutes — often: stop the bleed, rollback, shed load), root cause, and the durable fix + the guard added (alert, test, runbook). Senior signal: you stayed calm, communicated status to stakeholders, and turned the incident into a permanent improvement. The story proves ownership under pressure.
Q5. “How do you decide between two reasonable technical approaches?” “I write the trade-off table: the two options, their failure modes, their cost at 10x, and what we’d lose by picking each. Then I pick the one that’s cheaper to reverse and instrument it. If both are reasonable and reversible, the choice matters less than committing and learning. I make the reasoning visible so the team can override me with new info — a decision no one understands is a debt.”
Q6. “What does ‘senior’ mean to you, in one sentence?” “Senior means I’m trusted to make the call under uncertainty, own the outcome good or bad, and make the people around me better at making theirs.” Then back it with one 30-second story. That sentence — judgment + ownership + leverage — is the whole behavioral interview in a nutshell, and most candidates never say it.
Self-check
- Junior: I can give a tight intro, answer weakness/honestly-with-mitigation, tell a bug story with root cause + guard, and show a process for getting unstuck.
- Mid: I can frame disagreement with evidence, own a failure as tuition, prioritize by impact×reversibility, and show real mentoring and handling of vague requirements.
- Senior: I can decide ship-vs-hold by blast radius/recovery, show a process for decisions under uncertainty, raise team level via mechanisms, lead an incident response, and define senior as judgment + ownership + leverage.