Tell Me About a Time You Changed How Engineering Works Across the Whole Organization
Behavioral and LeadershipLeadership and MentorshipAsked atPrincipalUpdated
They're checking whether you can change how a whole engineering organization behaves, and make it last. Strong answers name the practice, the evidence it needed changing, how adoption spread, and proof that it held.
Rubric by Level
Junior
- Adopted a team practice, like code review norms or testing habits, and can say why it matters.
- Suggested a small improvement to how the team works.
- Shows the suggestion was tried.
Mid
- Changed a practice on your team, like how you run retros or write tests.
- Got teammates to try it by showing results.
- Names the measure that improved.
Senior
- Changed a practice for your team and a neighboring one, with evidence it helped.
- Made it easy to adopt with templates or tooling.
- Shows it continued after you stopped reminding people.
Principal
- Changed how the whole engineering organization works, like incident practice, design review, or deploy cadence.
- Changed promotion criteria, onboarding, or tooling so the change could run without you.
- Aligned engineering leadership so managers reinforced it.
- Shows the change held a year later, with a measure.
Red Flags
- Changed culture by writing a memo or giving a talk.
- Relied on a mandate from leadership with no adoption plan.
- Has no measure that shows the change.
Follow-Ups to Expect
- Which group resisted longest, and why?
- What did you change in promotion or hiring to make it stick?
A Story Shape That Holds Up
The Habit
What the org did and what it was costing.
The First Teams
Where you started and what they proved.
The Systems
What you changed so the new way became the default.
A Year Later
The measure that showed the change held.