Interview prompt
Problem context
A legacy application and a new service both need customer records. Hundreds of jobs and reports read shared tables directly, and writing through only the new API is not immediately possible. Design a strangler that does not end with permanent dual ownership.
Skills being evaluated
strangler migrationdata ownershiplegacy integrationexit planning
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 continueWhat 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