Your goal: turn "sync these two systems" into a design you could build: a clear outcome, a
model, a matching rule, a source of truth per field, a safe update path and checks.
How this works (about 30 minutes)
- Ryan runs the round and plays the customer. He holds a fact sheet about the systems and the data,
made up for the exercise. Ask what you need; he won't volunteer.
- A shared notepad is there if you want to sketch the model. Ask Ryan to open it, and tell him when
you've written something.
- Lots of follow-ups, one curveball, then a shorter question.
- No hints and no scores during the call. Your report comes after.
What scores well
- Clarify who uses the result and what goes wrong today before you design
- A canonical model, a matching rule with a fallback, and a stated rule for a wrong match
- A source of truth per field, not one winner for the whole record
- Re-runs that are safe: incremental sync, idempotent writes, a backfill plan
- Data checks and a human review path; what you tell the customer when the data is worse
Tips
- Take FDE Coach · Data Integration first.
- Say the outcome and the consumers before you draw a single table.