Interview prompt
Problem context
A privacy request must remove a user from primary stores, caches, search, analytics, model features, logs, and backups. Today each team owns scripts, retries are unsafe, and restoring an old backup can resurrect deleted data. Design end-to-end deletion and evidence.
Skills being evaluated
privacy architecturedata lineageworkflow correctnessretention policy
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