Decision Making
decision-making
Behavioral Interviews
Making Hard Decisions Under Uncertainty
Hard-decision questions are the judgement probe at staff and above. They test whether you can act when the information is incomplete, the choice is irreversible, the timeline is short, the answer is unpopular, or all four at once. This lesson defines what makes a decision genuinely hard, walks through a four-step decision framework (frame, generate options, weigh, decide) you can lean on under interview pressure, contrasts calibrated confidence with overconfidence, and provides fully worked model STAR answers for the seven prompts you are most likely to hear including the rare and high-signal 'tell me about a decision you got wrong'. After this lesson you will be able to take any consequential decision in your career and shape it into an answer that scores on judgement, ownership, and self-awareness simultaneously.
Building Consensus & Alignment
Consensus-building questions are the senior-staff alignment probe. They test whether you can move a group of stakeholders to a shared decision when reasonable people disagree, without steamrolling, watering down, or faking the alignment. This lesson disentangles consensus from unanimity, draws the line between when consensus is the right goal and when 'disagree and commit' is, walks through the four moves mature engineers use (shared problem framing, shared evaluation criteria, surfacing hidden objections, iterating the proposal), and provides fully worked model STAR answers for the seven prompts you will hear most. After this lesson you will be able to take any contentious technical or organisational decision from your career and tell the story so the rubric reads judgement, communication, and trust simultaneously.
Navigating Technical Trade-offs
Trade-off questions are the senior-engineering judgement probe. They test whether you can weigh competing technical priorities, articulate the criteria that drove your choice, own the path you took including its costs, and distinguish real trade-offs from false choices that better engineering would dissolve. This lesson defines trade-off literacy across the canonical axes (consistency vs availability, build vs buy, simplicity vs flexibility, speed vs safety, cost vs latency), walks through the explicit-criteria framework strong candidates use to make trade-offs visible, covers the technical-debt framing that scores best in interviews, and provides fully worked model STAR answers for the prompts you will hear most. After this lesson you will be able to take any consequential technical choice from your career and tell the story so the rubric reads judgement, calibration, and ownership simultaneously.
System Design Decision Stories
System design decision questions are the staff-and-above architecture probe. They test whether you can shape a design that compounds correctly over years, demonstrate second-order thinking about how decisions interact, balance forward-looking design with iterative delivery, and tell a story that operates at the right altitude for staff scale. This lesson defines what counts as a scale-shaping decision (architectural choices whose costs and benefits compound), walks through how to present design decisions in narrative form rather than whiteboard form, covers the second-order-thinking moves that distinguish staff stories from senior stories, addresses when to over-engineer versus when to ship-and-iterate, and provides fully worked model STAR answers for the prompts you will hear most. After this lesson you will be able to take any consequential architectural decision from your career and tell the story so the rubric reads design judgement, second-order thinking, and operating at staff altitude.
Working Under Pressure & Tight Deadlines
Pressure questions probe whether your judgement holds when stakes are high and time is short. The interviewer is grading a specific set of moves: calm decomposition under stress, deliberate scope cuts, parallel-track thinking, and clear communication upward. They are not grading whether you worked weekends. This lesson distinguishes pressure (real time-bound stakes) from rush (artificial urgency or poor planning), names the four behaviour signals graders look for, and walks through worked answers for the prompts you will hear most. After this lesson you will be able to take a high-pressure story from your career and tell it so the rubric reads judgement under stress, deliberate trade-offs, and proactive escalation, without crossing into hero framing or learned-helplessness about workload.
Dealing with Ambiguity
Ambiguity is the senior and staff judgement signal. Interviewers ask 'tell me about a time you operated with significant ambiguity' to probe whether you can act decisively when requirements are unclear, when there is no precedent, when ownership is undefined, or when success criteria are vague. The trap is the false-clarity reflex: the candidate retroactively pretends they had clear direction the whole time. The strong move is to show judgement under uncertainty without falsely claiming clarity. This lesson covers the four kinds of ambiguity, the four-step ambiguity workflow (frame, hypothesise, validate cheaply, expand), the difference between escalating for direction and moving forward with cheap probes, and what staff-scale ambiguity stories look like in practice. After this lesson you will be able to take a real ambiguity story from your career and tell it so the rubric reads judgement, calibrated confidence, and the courage to commit to a direction without complete information.
Persuading & Negotiating
Persuasion and negotiation questions probe whether the candidate can move a decision in a direction they think is right without burning the relationship that makes future decisions possible. Interviewers ask 'tell me about convincing your manager' or 'walk me through pushing back with data on a senior leader' to evaluate whether persuasion was framed in the listener's interest, whether the candidate surfaced the listener's criteria before proposing, and whether the candidate held the line between persuasion and manipulation. The trap is the win-the-argument reflex: the candidate retells the case they made for their own position. The strong move is persuasion-as-service: framing from the listener's perspective, surfacing their criteria, proposing with their criteria, and pre-empting their objections. After this lesson you will be able to take a persuasion or negotiation situation and tell it so the rubric reads listener-first influence, not advocacy.
Managing Stakeholders & Expectations
Stakeholder management questions probe whether the candidate can hold consistency, trust, and forward motion across a network of people whose interests do not all align. Interviewers ask 'tell me about managing competing stakeholder needs' or 'walk me through saying no to a stakeholder request' to evaluate whether the candidate maps stakeholders deliberately, manages expectations proactively rather than reactively, communicates on the right cadence for each kind of message, and says no with options rather than with friction. The trap is the keep-everyone-happy reflex, which produces over-commitment and surprises that erode trust. The strong move is calibrated stakeholder discipline: a deliberate map, proactive expectation-setting before surprises, three communication cadences (incident / proactive / scheduled), no-with-options rather than no-with-friction, and the upward-management discipline of giving senior stakeholders the information they need to back you. After this lesson you will be able to take a multi-stakeholder situation and tell it so the rubric reads calibrated coordination, not heroics.
Community
Technical Debt: When It's Debt vs When It's Just Old
Most code labeled technical debt is not debt at all. Here is the test I use to tell debt from age, and the rule I follow when paying it down.
Writing RFCs and Design Docs That People Actually Read
Most design docs are unreadable not because they are too short, but because they answer the wrong question. Here is the structure I now use.
Disagree and Commit Without Sounding Spineless
Disagree-and-commit is the most misused phrase in modern engineering culture. Done well it is a senior move; done badly it sounds like you fold under any pushback. Here is the line.
Engineering Manager vs IC Track: How I Chose
I tried both. Here is the actual day-to-day of each, the trade I did not see coming, and the question that decided it for me.
