Interview prompt
Problem context
Fraud scores and finance reports are computed by separate streaming and batch stacks. They disagree on late events, corrections, and feature logic. Teams manually overwrite online state after nightly jobs, causing unexplained decision changes. Design one contract and safe correction flow.
Skills being evaluated
stream-batch semanticsevent-time reasoningdata contractscorrection strategy
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