Debugging scenarioMedium~10 min

Interview question

Two parts of a UI unexpectedly change the same object. How would you explain and fix the shared-reference mutation?

Diagnoses aliasing and shallow-copy mistakes, then restores explicit state ownership and immutable update boundaries.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Objects are values with identity, and variables can refer to the same object. If two UI states share that reference, a mutation through either path is visible through both. I would confirm the shared identity, find where the reference was reused, and replace the mutation with an update that creates the changed object and every changed container along its path.

Full answer below

Practice focus

Practical reasoning about object identity, nested references, state ownership, and evidence-led debugging.

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.
Overview
The bug is usually not that JavaScript copied an object incorrectly. It is that two paths still reach the same mutable object.
Objects are values with identity, and variables can refer to the same object. If two UI states share that reference, a mutation through either path is visible through both. I would confirm the shared identity, find where the reference was reused, and replace the mutation with an update that creates the changed object and every changed container along its path.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A shallow spread only copies one level. { ...order } still shares order.customer unless that nested object is also replaced. I would reproduce the smallest failing action, compare identities with strict equality, and inspect the write point rather than the later render where the symptom appears. Then I would establish one owner and pass snapshots or explicit update operations to consumers.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I would also check whether a cache, selector, reducer, or optimistic update relies on reference equality. In-place mutation can make one consumer rerender unexpectedly while another misses the change because its top-level reference stayed stable. Development-time freezing or immutable-state checks can expose writes, but the durable fix is clear ownership and tested update semantics, especially around rollback and concurrent optimistic changes. I add a regression test that proves the previous snapshot remains unchanged and that a failed optimistic operation restores the intended state.

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

Assuming a spread or Object.assign performs a deep copy.
Cloning the entire application state to hide unclear ownership.
Debugging only the component that displayed the changed value.
Using JSON serialization as a general cloning strategy.

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

Details

The proposed fix preserves shared nested references.
Object identity is not considered during diagnosis.
The answer recommends deep cloning on every update without measuring cost or semantics.

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.

Why can a shallow copy still share nested data?
How would mutation affect memoization?
When is mutation acceptable?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

2 linked

Next in path

Move forward in the planned practice sequence.

Lost this bindingContinue from object identity to method invocation context.

Prerequisite

Review this first if the current drill feels shaky.

var, let, and constSeparate reassignment of a binding from mutation of its object.

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?