AdvancedPrincipalArchitecture Leadership & Decisions65 minutesPro answer

SDV-073

Recover a failing cross-team architecture program after confidence collapses

Reset scope, authority, milestones, and truth when a strategic migration is late, teams optimize locally, and sunk-cost pressure hides missing value.

Change ManagementOrganizational DesignTechnical DebtGovernance

Interview prompt

Problem context

A two-year platform migration spans twelve teams, is nine months late, and has moved only low-risk traffic. The old system still receives features, temporary bridges multiply, and executives receive green status based on tasks completed. Take over the program and recover or stop it.

Skills being evaluated

program recoveryarchitecture strategystakeholder trustportfolio decisions

The full reasoning guide is part of Pro

The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.

Sign in to continue

What the full guide covers

Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize