Collaboration & Conflict

Tests whether criticism of your code lands as criticism of you. Answer with one blunt comment, what you did to understand it before replying, the change you made, and the working relationship afterwards.

Tests whether bad news travels fast and arrives with a plan. Answer with the moment you knew, how quickly you said it, what you offered alongside the slip, and the revised date you then held.

Probes conflict resolution and self-awareness. Describe one person in observable behaviours, the charitable read you tested, the direct conversation you had, what you changed yourself, and a work outcome with the relationship still standing.

Tests whether you can be wrong without defending it. Name a real call you got wrong, how you found out, what you said and to whom, and the guardrail that came out of it.

Tests backbone without ego. Pick one disagreement that genuinely mattered, show you raised it privately with evidence rather than opinion, and land on the decision, the outcome, and a working relationship that survived.

Tests whether you separate the idea from the person. Answer with one concrete disagreement, evidence you went and got instead of opinions you asserted, a decision that actually got made, and a relationship still intact.

Tests whether you hold a line on risk without making it a contest. Answer with one change you refused to approve, the concrete harm you named, the alternative you offered, and where the code and the relationship both ended up.

Tests whether you can disagree with the business without stonewalling it. Name the commitment, show the evidence it would not hold, and leave the stakeholder choosing between real options rather than facing a wall.

Tests whether you can be direct and kind at once. Answer with one specific behavior and its measurable impact, feedback delivered privately and promptly to the person themselves, and a follow-up that shows the relationship survived.

Tests whether you can lose an argument and still implement the decision fully. Name the convention, the case you made once with evidence, and how you complied visibly while leaving a route to revisit it.

Tests whether you own the effect of your writing rather than defending your intent. Answer with one message that landed badly, the repair you initiated fast, and the habit you changed afterwards.

Tests whether you can defend your contribution without starting a feud. Answer with one concrete instance, facts checked before motive assumed, a private correction first, and a working relationship that survived it.

Probes adaptability rather than conflict. Name a concrete style difference in behaviour terms, say what you adapted, what you asked for in return, and give one piece of evidence that the working rhythm actually improved.

Probes judgment about when not to block. Answer with the reservation you put in writing, why the risk was acceptable that day, what made the change reversible, and how you made sure the follow-up actually happened.

Probes whether you can hold a technical position without making it a contest. Answer with one comment you genuinely disagreed with, the reviewer's concern stated fairly, the evidence you brought, and the decision that landed.

Tests whether you can end an unproductive review loop instead of waiting it out. Answer with how long it stalled, how you separated real disagreements from preferences, the move that broke the loop, and what the delay cost.

Tests whether you fix systems or win arguments. Name the debate that kept resurfacing, show you moved it out of code review into a formatter, a lint rule or a written decision, and give the cost that removed.

Tests whether you move a dependency instead of waiting on it. Answer with the deliverable that was blocked, what you learned about their priorities, the trade or patch that got it moving, and a shipped result.

Tests whether you can clear a blocker by doing the work yourself without trampling another team's ownership. Answer with the ask you made before writing anything, the patch built to their standards, and who maintains it now.

Probes whether you design around a time-zone gap instead of complaining about it. Answer with one concrete round-trip that cost days, the written handoff or decision rule you introduced, and what it saved.

Checks whether you have deliberate written habits or just hope your work speaks for itself. Answer with two or three specific practices, one moment they paid off, and how you avoid performative noise.

Tests composure and ownership when the account of events is wrong about you. Own your genuine share first, correct the timeline with evidence rather than counter-accusation, and finish on the fix that removed the ambiguity.

Probes judgement about when direct handling stops working. Show the attempts you made first, the threshold that made escalation necessary, that you told the person before your manager, and what the escalation actually bought the work.

Probes sunk-cost resistance and whether your ego is attached to your own code. Name the work, the signal that killed it, the cost you stated out loud, and what shipped in its place.

Tests persuadability: whether evidence moves you rather than seniority or volume, and whether you concede where the original argument happened. Show the challenge, what specifically changed your mind, and the credit you gave.

Tests whether you can commit to a decision you argued against without sulking or sandbagging. Answer with your position stated once, the moment you got behind the call publicly, and evidence you delivered it well.

Probes judgment about decision velocity: whether you can tell consensus-seeking from stalling. Answer with a debate you timeboxed, escalated to a named decision owner with the options costed, then executed without sulking.

Tests disagree-and-commit. Show that you argued once, substantively, and then executed wholeheartedly — visible commitment to your team, no quiet slow-walking, and a data trigger rather than resentment as the way back to the question.

Tests whether you can win a disagreement without damaging the person. Answer with their position stated fairly, the interest underneath it that you actually found, the evidence that spoke in their terms, and a relationship that got easier afterwards.