L5+ Behavioral: Policy vs Efficiency Trade-offs & Leadership

L6 behavioral conducted by a senior Director. Discussion-style — interviewer probes past leadership stories (tree-level and forest-level) and weaves in policy-vs-efficiency dilemmas that feel like trolley-problem variants. No standard 'tell me about a time' prompts; expect to defend judgments live. Requirements 60-minute discussion-style behavioral, not a checklist of standard prompts. Cover past projects at two levels: project-detail ('the tree') and strategic / cross-team ('the forest'). Be ready for policy-vs-efficiency dilemmas presented as hypotheticals — e.g. 'a new safety policy slows down the simulator pipeline; how do you weigh it against shipping velocity?' The interviewer is typically a senior D / VP-level engineer; expect direct push-back and follow-up on every claim. Notes Structure stories with cause → choice → outcome → reflection. Senior interviewers credit the reflection layer specifically — what would you do differently, what did the experience change in your decision framework. Tree vs forest. Have two of each kind of story prepared: Tree-level: concrete engineering decision, with numbers, that you owned end-to-end. Forest-level: cross-team or organizational decision where you influenced direction without holding the authority. Policy-vs-efficiency dilemmas. Frame the response around explicit trade-off axes (safety, velocity, cost, fairness, downstream maintenance). Pick a stance and defend it; refusing to commit is a documented red flag at the L6 bar. Influence without authority. Be ready to describe a specific time you changed another team's roadmap. The interviewer will ask 'what would have happened if you hadn't pushed' — have a credible counterfactual. Pushback handling. When the interviewer challenges a choice, restate the trade-off in their language before defending. This signals you can update on new information rather than reciting a memorized story. Don't oversell. Senior interviewers notice puffed-up impact claims; quantify outcomes conservatively and acknowledge collaborators by name. Specific Waymo themes that have surfaced: decisions weighing rider safety against fleet utilization; ML model promotion gates; managing cross-team review for safety-critical changes; deprecating a beloved feature for compliance reasons. Preparation Build a story matrix: 6 projects × 4 themes (technical depth, leadership, conflict, ambiguity). Refresh against the most recent 18 months. Practice a 90-second elevator pitch for each of the top 6 projects — interviewers often interrupt 30 seconds in and you must land cleanly. Rehearse two policy-vs-efficiency dilemmas aloud with a peer, taking opposite sides each time. The goal is fluency in trade-off vocabulary, not a 'correct' answer. Prepare three thoughtful questions for the interviewer that signal you've thought about Waymo's tech and culture — bonus credit for asking about leveling and feedback culture at L5/L6.