Skip to content
Interview rounds

Kafka & events · Production incident

The parcel that went back in transit

Events for one entity are handled out of order by a Kafka consumer. How do you keep each entity's events in order?

BackendSenior14 min
Interview-style scenarioLast reviewed: Checked against official documentation

Monday 09:15 · tracking-pageIllustrative scenario, not a real incident

Support: delivered parcels show as "in transit" on the tracking page

Depot scanners publish a status event for every parcel: collected, in transit, delivered. The tracking service consumes parcel-events and overwrites the parcel's row with the status of each event it reads.

Since the morning peak, some parcels show an earlier status than the one they last had. The events are all in the topic, and none was lost or duplicated.

What the dashboards and logs show

Topic
parcel-events, 3 partitions
Consumer group
3 instances, one partition each
Event payload
parcel id, status, scan time
Consumer lag
near zero outside the peak

Clarify · optional · scored under "Hypothesis before change"

Ask the interviewer

0 of 3 asked

Each question reveals a fact. What you ask before you act is part of your score.

First move · scored under "Mitigate before root cause"

Support is taking calls about parcels that look undelivered. What do you do first?

Your rubric score, the model answer, the follow-up questions and the related lessons appear once you have answered the last step.