Citi Frontend Engineer Interview Preparation

A placeholder disappears as the user types and is not a dependable substitute for a programmatically associated label. Give each control a persistent label and connect instructions and validation messages to it. Test the form with keyboard input, zoom and a screen reader, not only by looking at the desktop layout.

Check your understanding: Submit an invalid field and verify that its name and error can both be found.

Common trap: Judging accessibility from visual appearance alone.

Concept reference: W3C WAI: labeling form controls

Find the first element whose dimensions exceed the viewport. Inspect fixed widths, intrinsic image sizing, long strings and minimum sizes in flex or grid children. Fix the responsible constraint instead of hiding the entire overflow, which can make content or focus indicators inaccessible.

Check your understanding: Test long content at a narrow width and at increased text zoom.

Common trap: Using overflow:hidden on the whole page as the fix.

Concept reference: MDN: the CSS cascade

Cover the user journey: selecting an item, entering details, receiving validation, retrying a failure and seeing a confirmed outcome. Prefer resilient role and label locators. Keep unrelated third-party behavior controlled in tests and retain a smaller integration check for the actual boundary.

Check your understanding: Verify keyboard completion and failure recovery, not a pixel-perfect snapshot alone.

Common trap: A suite that passes while the primary action cannot be used.

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 simplicity, correctness, maintainability and scale, explicitly mitigate the risk of the same job is processed twice and produces conflicting side effects, and confirm system stability using lease-expiry tests, idempotency records and a restart recovery drill.

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 concurrency test and an audit trail demonstrating conflict handling.

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 project example, measured result and repeatable verification step.

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 semantic validation results, quarantine records and a replay verification.

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 before-and-after latency profile plus an explicit rollback threshold.

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