Questions candidates have reported from Meta, Google, Uber, Atlassian, and Airbnb frontend interviews, grouped by round, with sources. Practice the coding ones with real tests, build a reported UI question, and map each system design question to a deep dive.
Before memorizing questions, know which rounds you'll face. The Front End Interview Handbook, written by ex-FAANG engineers, groups frontend interviews into five formats:
throttle, an event emitter) or a polyfill.What candidates report about specific companies (loops change often; treat this as a guide, not a guarantee):
| Company | Reported loop | Source |
|---|---|---|
| Meta | Phone screen, then onsite: 2 coding, 1 behavioral, 1 system design; more design rounds at higher levels | Handbook: Meta |
| 2 data-structures-and-algorithms rounds, 1 frontend/UI, 1 system design, 1 behavioral ("Googleyness") | Handbook: Google | |
| Atlassian | A timed screen with rapid-fire modern-JavaScript questions plus coding; strong emphasis on vanilla JavaScript and frontend system design | Handbook: Atlassian |
| Amazon | Behavioral questions built on its Leadership Principles, answered in STAR format | Handbook: Amazon |
| Airbnb | JavaScript and algorithms with hashmaps and arrays, a component built for reuse, "write a simple promise" | Glassdoor reviews |
What changes at senior level is less the questions than the bar: interviewers expect you to drive the conversation, name trade-offs unprompted, handle edge cases (race conditions, accessibility, performance) without being asked, and connect decisions to users and teams. Candidates at Atlassian, for example, mention "a lot of cross questioning" about why you chose a data structure.
The next steps work through reported questions round by round.