Skip to content
Interview rounds

Kafka & events · Production incident

Saved, refreshed, and the old value is back

A user saves a change, refreshes, and sees the old value, because the page reads a model built from events. How do you let users see their own writes?

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

Thursday 14:30 · account-service and the account pageIllustrative scenario, not a real incident

Support: 140 tickets this week saying 'I saved my new address and it changed back'

Users edit their delivery address on the account page. After a save the page reloads the profile. Since Monday, some users see the old address after saving, and many of them save again.

A few orders have gone to an old address, because the user gave up and assumed the change had been lost.

What the dashboards and logs show

Tickets
140 since Monday, nearly all between 12:00 and 14:00
Save requests
all returned 200, no errors
Repeat saves
one user in five saves the same address twice
Deploys
none to the account service or the page this week

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"

It is 12:10 and the tickets are coming in again. 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.