Company guides
🟦 Google — Frontend Interview Guide
Emphasis: Web fundamentals, accessibility, performance, and raw DOM/JS — often framework-agnostic. Google cares that you understand the platform, not just a library.
Related: Company index · ROADMAP
The loop (typical)
| Round | Focus | Prep section |
|---|---|---|
| Phone screen | JS/DOM coding | 03-javascript |
| Coding 1 | DSA + a DOM/UI twist | 16-machine-coding |
| Coding 2 | Machine coding (vanilla-friendly) | 16-machine-coding |
| Frontend system design | "Design X" | 15-system-design |
| Behavioral / Googleyness | Collaboration | — |
What they emphasize
- Platform fluency — DOM APIs, event delegation, the event loop, browser rendering.
- Accessibility — semantic HTML and keyboard support are frequently scored.
- Performance — Core Web Vitals, minimizing reflows, efficient rendering.
- Clean, framework-agnostic code — be comfortable in vanilla JS, not just React.
Frequently asked (community-sourced)
Machine coding
- Build an Autocomplete → flagship
- Build a Carousel → system design flagship
- Build an accessible Modal / Tabs → 16-machine-coding
- Build Infinite Scroll → flagship
System design
- Design a News Feed → flagship
- Design Google Docs → flagship
- Design an autocomplete/search → flagship
JavaScript / fundamentals
- Event loop, microtasks/macrotasks → 02-browser
- Event delegation,
this, closures → 03-javascript - Debounce/throttle → flagship
Prep plan (2 weeks)
- Lock fundamentals + browser internals.
- Grind JS utilities in vanilla JS.
- Do 3 accessible components with keyboard support.
- 3 mock system designs, focusing on perf + a11y trade-offs.
🟢 Green flags · 🔴 Red flags
🟢 Do: clarify requirements before coding · reason about the platform (DOM, event loop) · make it keyboard-accessible · name performance trade-offs · write clean framework-agnostic code. 🔴 Avoid: reaching for a framework when vanilla is enough · skipping accessibility · ignoring edge cases (empty/error/loading) · over-engineering a simple ask.
📝 Sample interviewer prompts
- "Implement an accessible autocomplete without a library."
- "How would you make this component fully keyboard-navigable?"
- "Walk me through what happens from typing a URL to first paint."
Interviewed at Google? Add the questions you got (role + year) via a PR.