Concept questionMedium~7 minMutations & Workflows / 1 of 6

Interview question

When would you use optimistic UI, and when would you wait for the server before updating the screen?

Choose optimistic UI or server-confirmed updates

Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would use optimistic UI for low-risk, easily reversible actions such as toggling a favorite, marking read, or changing a local preference. The UI updates immediately, sends the mutation, and rolls back or reconciles if the server rejects it. I would wait for server confirmation for payments, permissions, destructive actions, limited inventory, or anything where showing success before confirmation can mislead the user.

Full answer below

Practice focus

Optimistic updates, server authority, rollback, latency perception, conflict handling, and user trust.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Optimistic UI is not just a frontend trick. It changes how users perceive authority, errors, and conflicts, so the API and UI need to agree on recovery.
I would use optimistic UI for low-risk, easily reversible actions such as toggling a favorite, marking read, or changing a local preference. The UI updates immediately, sends the mutation, and rolls back or reconciles if the server rejects it. I would wait for server confirmation for payments, permissions, destructive actions, limited inventory, or anything where showing success before confirmation can mislead the user.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would design optimistic updates around stable client-side intent. The mutation needs an idempotency key or a predictable operation so retries do not create duplicates. The UI should show pending state when the action is not fully confirmed, and it should reconcile with the server response because server rules may adjust the final result. If conflicts are likely, I would use explicit conflict UI rather than silently overwriting.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would keep optimistic behavior consistent across tabs, refreshes, and reconnects. Offline queues or retry queues need durable client intent and clear limits. I would monitor rollback rate, mutation latency, duplicate attempts, and user retries after failures. If a feature has compliance, money, access, or audit implications, I would bias toward server-confirmed state and make latency acceptable through better loading design rather than false certainty. I would test rejection and retry paths directly, because optimistic UI usually fails in the uncomfortable edge cases rather than the happy path.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using optimistic success for irreversible or high-risk actions.
No rollback behavior after rejection.
Creating duplicate records when a retry happens.
Not reconciling with the server response.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot name cases where optimistic UI is unsafe.
No idempotency or retry plan.
The UI shows confirmed success before the server accepts the action.
Conflict handling is only last-write-wins by accident.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Which actions are safe to update optimistically?
How would you show pending versus confirmed state?
How would retries avoid duplicate writes?

Continue the section

Next in Mutations & Workflows: Double Submit Prevention

Step 2 of 6

Prevent double submits and duplicate mutations

Opening drill

Concept questionMedium~7 minMutations & Workflows / 1 of 6

Interview question

When would you use optimistic UI, and when would you wait for the server before updating the screen?

Choose optimistic UI or server-confirmed updates

Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Optimistic updates, server authority, rollback, latency perception, conflict handling, and user trust.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Optimistic UI is not just a frontend trick. It changes how users perceive authority, errors, and conflicts, so the API and UI need to agree on recovery.
I would use optimistic UI for low-risk, easily reversible actions such as toggling a favorite, marking read, or changing a local preference. The UI updates immediately, sends the mutation, and rolls back or reconciles if the server rejects it. I would wait for server confirmation for payments, permissions, destructive actions, limited inventory, or anything where showing success before confirmation can mislead the user.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would design optimistic updates around stable client-side intent. The mutation needs an idempotency key or a predictable operation so retries do not create duplicates. The UI should show pending state when the action is not fully confirmed, and it should reconcile with the server response because server rules may adjust the final result. If conflicts are likely, I would use explicit conflict UI rather than silently overwriting.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would keep optimistic behavior consistent across tabs, refreshes, and reconnects. Offline queues or retry queues need durable client intent and clear limits. I would monitor rollback rate, mutation latency, duplicate attempts, and user retries after failures. If a feature has compliance, money, access, or audit implications, I would bias toward server-confirmed state and make latency acceptable through better loading design rather than false certainty. I would test rejection and retry paths directly, because optimistic UI usually fails in the uncomfortable edge cases rather than the happy path.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using optimistic success for irreversible or high-risk actions.
No rollback behavior after rejection.
Creating duplicate records when a retry happens.
Not reconciling with the server response.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot name cases where optimistic UI is unsafe.
No idempotency or retry plan.
The UI shows confirmed success before the server accepts the action.
Conflict handling is only last-write-wins by accident.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Which actions are safe to update optimistically?
How would you show pending versus confirmed state?
How would retries avoid duplicate writes?

Continue the section

Next in Mutations & Workflows: Double Submit Prevention

Step 2 of 6

Prevent double submits and duplicate mutations

When would you use optimistic UI, and when would you wait for the server before updating the screen?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

When would you use optimistic UI, and when would you wait for the server before updating the screen?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section