How to Answer "Walk me through a project you led"

Mid-career software engineer

"Headline: I led the migration of our notification platform from a legacy monolith to event-driven services — four engineers, seven months, zero missed notifications, 35% lower infrastructure cost. My exact role: I wrote the design doc, set the strangler-fig rollout plan, and owned the cutover decision. Three pivotal calls: first, I killed a proposed big-bang rewrite in design review — the risk math didn't work. Second, I insisted we build the shadow-traffic validation harness before any production code; it felt slow and caught fourteen edge-case bugs that would have been incidents. Third, when the queue's ordering guarantees broke a billing flow, I paused the migration two weeks to fix the ordering layer rather than work around it. What I'd do differently: I under-communicated with the support team, who got surprised by new error codes. Now I write the support briefing first, not last."

Veteran translating a military project

"The project that translates most directly: I managed the rollout of a new property-accountability system across a 700-person organization — think of it as an ERP migration for $45M of tracked equipment, with an immovable deadline set by an external inspection. My role: I owned the project plan, trained the twenty unit-level administrators, and reported weekly to the colonel — our steering committee. Two decisions I'd defend anywhere: I piloted with the two most resistant units first, because their objections surfaced every real defect while stakes were low; and I refused go-live until a full parallel-run reconciliation matched to the item — one extra cycle that made the final audit anticlimactic. The obstacle nobody planned for: a third of the legacy records were simply wrong, and we rebuilt them by physical count. Outcome: zero deficiencies at inspection. What I'd change: user training started too late — skeptical users need a month, not a week."