Frontend Platform Engineer
Airbnb · Senior
Recommended next: your first attempt
Do the Frontend coding assessment round.
A complete first attempt shows where you stand before any narrow practice starts.
The loop
Pick a round to see what it asks of you and where you stand on it.
Frontend coding assessment
Deliver a coherent frontend feature that remains correct during rapid input and failed requests.
Coding · 60 minSet up this round
Not tried yetNo attempt yet.
What strong sounds like
- Separate input, request, result and selection state with explicit transitions.
- Write complete component logic for the requested interaction.
- Prevent stale responses and explain cleanup or cancellation.
- Manually trace empty input, rapid typing, failure and keyboard selection.
Expect to be pushed on
What happens when the component is removed mid-request?
How is an old selection handled after the query changes?
Shapes of problem you may get
- One asynchronous search component with keyboard and failure states
How to prepare
- 01
Map async states before coding
Write the states for empty input, loading, success, failure, and selection. Define which event changes each state and what must remain true after every transition.
The reported candidate account mentions autocomplete, debouncing, keyboard interaction, and network errors. Treat this as useful evidence, not a confirmed Airbnb question.
Company researchAirbnb frontend candidate: component, performance and collaboration loop
- 02
Rehearse stale-response handling
Choose a cancellation or request-identity strategy. Trace two requests that return out of order. Explain why the older result cannot replace the current result.
The round bar explicitly tests rapid input and failed requests. A race trace exposes gaps that debouncing alone does not solve.
A first attempt takes the full 60 minutes.
What this loop tests
Prepare to implement a frontend feature, reason about browser performance and platform architecture, and explain how your work improves the experience of guests, hosts, and product teams. Airbnb’s values interview deserves the same preparation as coding. Build depth in asynchronous state, accessibility, loading performance, and adoption of shared infrastructure; bring project stories that connect technical choices to user and developer outcomes.
They reward
- Care for guests, hosts and colleagues
- Accessible, predictable interactions
- Performance grounded in measurement
- Platform impact demonstrated through adoption
What to avoid
- Do not treat debouncing as protection against every request race.
- Do not leave keyboard behavior until after the feature is complete.
- Do not use effects to synchronize values that can be derived.
- Do not trade correctness for visual polish.
- Do not prescribe lazy loading for content needed immediately.
How sure we are
Worth redoing if you hear something from the recruiter that contradicts this.
Attempts
Every session saved against this target, newest first. Standings live on the round cards.
Frontend coding assessment, Frontend feature extension, Frontend platform and performance, Project impact and collaboration, and Core values interview have no attempts yet.