I had a decent story ready but I spent too long on the 'what changed and why' part and ran out of steam before getting to the stakeholder re-alignment piece, which is clearly what they cared about most.
Choose a project where a mid-course change had real stakes, and narrate it as a structured story: the original plan, the change and its driver, your impact assessment, the re-prioritization and stakeholder alignment process, and the measurable outcome. Emphasize how you turned ambiguity into a clear, communicated plan while protecting team morale and technical quality.
Pro tip: Show that you distinguished between what was truly fixed (e.g., launch date, core user need) and what was negotiable (e.g., feature set, architecture), then explicitly traded scope for time rather than silently absorbing the change. Quantify the outcome and name the trade-off you made, because Google interviewers value engineers who make deliberate, data-informed decisions under ambiguity.
Briefly describe the project, your role, the original scope, timeline, and team structure so the interviewer understands what 'normal' looked like before the change.
State exactly what changed, who drove it (e.g., product, leadership, customer, market shift), and why it mattered, showing you understood the business or user rationale behind it.
Explain how you evaluated the impact on timeline, design, and team capacity, then how you re-prioritized work—what you cut, deferred, or re-sequenced—and the criteria you used.
Describe the communication plan: who you informed, how you framed the trade-offs, how you got buy-in, and how you kept the team motivated and focused.
Report the concrete result (e.g., shipped on time with reduced scope, improved metrics, stakeholder satisfaction) and what you would do differently or now apply to future changes.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.