React Developer OOPS Concepts Interview Guide

Choose composition when the relationship is about using a capability rather than being substitutable for the base type. Delegate behind a small interface and keep invariants local. Inheritance can be appropriate, but test that derived behavior honors the expectations of callers using the base abstraction.

Check your understanding: Replace the implementation behind an interface and run the same contract tests.

Common trap: Using inheritance only to avoid copying a few lines.

Concept reference: Dev.java: language, collections and JVM learning paths

Not necessarily. Encapsulation protects meaningful invariants and exposes valid operations, rather than merely making fields private. Model state transitions so callers cannot construct invalid combinations, and keep representation details from leaking through mutable references.

Check your understanding: Attempt an invalid transition through the public API.

Common trap: Equating private fields with a complete domain model.

Concept reference: Dev.java: language, collections and JVM learning paths

Look for implementers that must provide meaningless operations or callers that depend on methods they never use. Split responsibilities around real usage while avoiding one interface per line of code. Test consumers against alternate implementations to expose hidden assumptions.

Check your understanding: Implement a second legitimate provider without no-op methods.

Common trap: Designing an interface from one implementation’s internals.

Concept reference: Dev.java: language, collections and JVM learning paths

If filtering depends only on current items and the search term, calculate it during rendering. A second state variable and an Effect introduce a render with stale data and another update. Measure expensive filtering before adding memoization. Keep Effects for synchronization with external systems, with cleanup for subscriptions.

Check your understanding: Change the search term and data independently; verify there is no stale intermediate list.

Common trap: Treating useEffect as the default place for every calculation.

Concept reference: React: when an Effect is unnecessary

Choose one owner at their nearest shared boundary and pass the value and change handlers down. Keep transient UI state local where possible. For remote persistence, distinguish the editable draft from the last saved version so a late response cannot overwrite new typing.

Check your understanding: Edit from both components and simulate an out-of-order save response.

Common trap: Duplicating an editable value in several components without a reconciliation rule.

Concept reference: React: when an Effect is unnecessary

Exercise the form through its labels and submit control. Simulate a failed request, assert that the draft and accessible error remain, then retry and verify the success state. Separate server validation from client hints and test repeated clicks rather than checking component internals.

Check your understanding: Run the same scenario using keyboard navigation and a delayed response.

Common trap: Only asserting that a mock function was called.

Concept reference: Playwright: reliable browser tests

First, identify technical constraints and define measurable service objectives. Next, trace state, rendering and network work from user action to painted result. Contrast architectural trade-offs across reuse, clarity, extensibility and accidental complexity, explicitly mitigate the risk of a retry loop multiplies work during an outage, and confirm system stability using load-test results, retry counts and a measured cost estimate.

Common trap: Reaching for a specific library or framework before defining constraints, failure envelopes, and automated verification criteria.

Prioritise the failure mode exhibiting the highest user blast radius and lowest observability. Formulate an explicit containment boundary, implement idempotent retries with jitter, and establish an automated rollback threshold. Verify resilience through a trace, a minimal reproduction and a regression test.

Common trap: Relying on passive monitoring dashboards without defining explicit error-budget alerts, rollback triggers, and verified recovery procedures.

Structure the response using Context-Decision-Tradeoff-Result: articulate the business and technical constraints, compare viable alternatives, explain the implementation (trace state, rendering and network work from user action to painted result), and document the accepted trade-off. Provide concrete proof: a focused unit test, dependency boundary and refactoring comparison.

Common trap: Speaking only in high-level abstractions or team accomplishments without detailing your direct implementation decisions, trade-offs, and measured results.

Formulate a falsifiable hypothesis from observable telemetry before altering configurations. Then inspect the interaction trace, render causes, network waterfall and accessibility tree. Isolate the defect to the smallest reproducible boundary, validate root cause with evidence, and confirm full resolution using a before-and-after latency profile plus an explicit rollback threshold.

Common trap: Applying speculative fixes or restarting services blindly without establishing an observable signal connected to a falsifiable hypothesis.

Produce a performance profile and keyboard-accessible regression test. Document baseline assumptions, technical mechanism (trace state, rendering and network work from user action to painted result), rejected alternatives, bounded failure envelopes, and deterministic pass criteria. Supply reproducible verification via a concurrency test and an audit trail demonstrating conflict handling.

Common trap: Presenting architecture diagrams or slides lacking automated unit/integration tests, observable metrics, or automated rollback configurations.