# Interview Formats at Top Tech Companies: What to Expect at Google, Meta, and Airbnb > Discover interview formats at Google Meta and Airbnb. Learn about recruiter screens technical phone interviews and on-site assessments to prepare for your tech interviews. - Repository: [Yangshun Tay/tech-interview-handbook](https://github.com/yangshun/tech-interview-handbook) - Tags: overview - Published: 2026-02-25 --- **Top technology companies use a consistent three-stage hiring pipeline—recruiter screen, technical phone interviews, and multi-round on-site assessments—though the specific focus, tools, and constraints vary significantly between firms like Google, Meta, and Airbnb.** Leading software companies structure their evaluation processes to test algorithmic proficiency, system design capabilities, and cultural alignment. According to the [yangshun/tech-interview-handbook](https://github.com/yangshun/tech-interview-handbook) repository, documented in [`apps/website/contents/interview-formats-top-companies.md`](https://github.com/yangshun/tech-interview-handbook/blob/main/apps/website/contents/interview-formats-top-companies.md), candidates encounter distinct interview formats that differ in coding environments (whiteboard versus laptop), round composition, and domain emphasis. Mastering these **interview formats at top tech companies** requires understanding both the universal recruitment flow and firm-specific quirks. ## Common Three-Stage Interview Structure Despite company-specific variations, most top tech firms follow a recognizable pattern: 1. **Recruiter Screen** – A brief conversation to gauge fit, review resume details, and align on salary expectations. 2. **Technical Phone/Video Interview** – One or two rounds focusing on algorithms, often conducted on collaborative editors like **CoderPad**, **Google Docs**, or **CodePen**. Some companies include front-end implementation tasks at this stage. 3. **On-Site (or Virtual On-Site) Loop** – A full-day assessment comprising four to six sessions covering algorithm coding, system design, behavioral evaluation, and domain-specific implementation. The specific constraints and tools allowed during these stages vary significantly by company and role type. ## Company-Specific Interview Formats ### Google Google's process emphasizes whiteboard-based evaluation and cultural assessment. As documented in [`apps/website/contents/interview-formats-top-companies.md`](https://github.com/yangshun/tech-interview-handbook/blob/main/apps/website/contents/interview-formats-top-companies.md), the pipeline includes: - **Recruiter phone screen** - **Technical phone interview**: One to two algorithm problems using **Google Docs** - **On-site rounds**: - Front-end whiteboard (Vanilla JS/jQuery) - Two to four algorithm whiteboard sessions - One **General Cognitive/Leadership/"Googleyness"** assessment - Team-matching conversations In rare cases, candidates bypass the phone screen entirely and proceed directly to on-site interviews. ### Meta (Facebook) Meta enforces strict whiteboard-only policies during on-site evaluations. The process includes: - **Recruiter phone screen** - **Technical phone interviews**: One to two rounds covering algorithm or front-end problems via **Skype/CoderPad** - **On-site loop**: - Two whiteboard coding rounds (**no laptops allowed**) - One behavioral interview - One design/architecture session University graduate candidates follow a similar round structure with adjusted difficulty. ### Airbnb Airbnb allows candidates to use personal laptops for all coding rounds, requiring a prepared development environment. The format includes: - **Recruiter phone screen** - **Technical phone interview**: One to two rounds testing algorithm or front-end skills on **CoderPad/CodePen** - **On-site General track**: Two algorithms, one system design, one past-experience discussion, and two cross-functional sessions - **On-site Front-End track**: Two front-end tasks on **CodePen**, one general coding session on laptop, one past-experience, and two cross-functional rounds ### Dropbox Dropbox focuses heavily on front-end implementation skills, including pixel-perfect page recreation. The structure comprises: - **Recruiter phone screen** - **Technical phone interviews**: Two rounds (algorithm/front-end) on **CoderPad/CodePen** - **On-site Front-End track**: Two front-end tasks on **CodePen** using vanilla JS/jQuery, one general coding round on **CoderPad**, and one manager-style experience discussion Candidates may look up APIs and reference code on their laptops during these sessions. ### Lyft Lyft's process is front-end intensive, offering flexibility in coding environments: - **Recruiter phone screen** - **Technical phone interview**: Algorithm or front-end problems on **JSFiddle** - **On-site Front-End**: Four front-end tasks on **CoderPad** or personal laptop, plus one behavioral round Candidates may choose between whiteboard or laptop for coding, and may use any framework (React examples are common). ### Palantir Palantir incorporates extended laptop-based sessions for front-end candidates: - **Recruiter phone screen** - **Technical phone interview**: Algorithm problems via **HackerRank CodePair** or **Skype** - **On-site General**: Two algorithm whiteboard rounds and one system-design decomposition session - **On-site Front-End**: One 1.5-hour front-end task on laptop and one system-design round React is frequently used for front-end evaluations. ### Asana Asana emphasizes system design across multiple rounds: - **Recruiter phone screen** - **Technical phone interview** - **On-site Product Engineer**: Three algorithm plus system-design whiteboard rounds, plus a laptop-based algorithm and system-design session No front-end questions are reported for engineering roles. ### Indeed Indeed uses level-specific tracks with platform-based assessments: - **Recruiter phone screen** - **Optional technical phone interview** - **On-site assessment**: - **HackerRank** online assessment (L0-L2 levels) - Resume discussion - One to two algorithm rounds on **HackerRank** - Code review on **GitHub** - One to two system-design rounds (L3+) - Technical presentation (L4+) Hiring decisions and leveling occur through separate processes. ### WhatsApp WhatsApp maintains a pure algorithm focus with no front-end components: - **Recruiter phone screen** - **Technical phone interview**: Two algorithm problems on **CoderPad** - **On-site Web Client Developer**: Four algorithm whiteboard rounds One interviewer will always be an Engineering Manager. ## Programming Environments and Constraints The choice between **whiteboard coding** and **laptop development** significantly impacts preparation strategy: - **Whiteboard-only firms**: Google, Meta, and Palantir require candidates to write code without execution or IDE support. Practice writing syntactically correct code without autocomplete or compiler feedback. - **Laptop-friendly firms**: Airbnb, Dropbox, and Lyft allow personal laptops. Prepare a clean development environment with your preferred IDE, and be ready to look up documentation during the interview. - **Hybrid approaches**: Some companies permit either whiteboard or laptop (Lyft), or use specific platforms like **CodePen** for front-end tasks (Airbnb, Dropbox). ## JSON Data Structure for Interview Planning The following JSON representation from the source documentation captures the interview stages for programmatic access or study planning: ```json { "Airbnb": { "stages": [ "Recruiter phone screen", "Technical phone interview (Algorithm / Front‑end on CoderPad/CodePen)", "On‑site General (2 Algorithms, 1 System Design, 1 Past Experience, 2 Cross‑functional)", "On‑site Front‑End (2 Front‑End, 1 General coding, 1 Past Experience, 2 Cross‑functional)" ] }, "Google": { "stages": [ "Recruiter phone screen", "Technical phone interview (Algorithm on Google Docs)", "On‑site Front‑End (Whiteboard, Vanilla JS)", "On‑site Algorithms (2‑4 Whiteboard)", "On‑site General Cognitive / Leadership / Googleyness", "Team matching conversations" ] }, "Meta": { "stages": [ "Recruiter phone screen", "Technical phone interviews (Algorithm / Front‑end on Skype/CoderPad)", "On‑site Coding (2 Whiteboard)", "On‑site Behavioral", "On‑site Design / Architecture" ] } } ``` ## Summary - **Interview formats at top tech companies** follow a three-stage pattern: recruiter screen, technical phone interview, and on-site loop. - **Google** and **Meta** enforce whiteboard-only coding with strict "no laptop" policies during on-site rounds. - **Airbnb**, **Dropbox**, and **Lyft** allow personal laptops and permit looking up APIs during coding sessions. - **System design** rounds appear at senior levels (L3+) in most companies, while **front-end** specialized tracks exist at Airbnb, Dropbox, Lyft, and Palantir. - **WhatsApp** focuses exclusively on algorithms with four whiteboard coding rounds and no system design or front-end questions. - Source documentation resides in [`apps/website/contents/interview-formats-top-companies.md`](https://github.com/yangshun/tech-interview-handbook/blob/main/apps/website/contents/interview-formats-top-companies.md) within the yangshun/tech-interview-handbook repository. ## Frequently Asked Questions ### How many rounds are typical in top tech company interviews? Most companies conduct three distinct phases: an initial recruiter screen (30 minutes), one or two technical phone interviews (45-60 minutes each), and an on-site loop comprising four to six sessions. The on-site typically includes two to four algorithm rounds, one system design discussion, and one behavioral interview, though specific counts vary by company and level. ### Can I use my own laptop during coding interviews? It depends on the company. **Meta (Facebook)** and **Google** enforce whiteboard-only policies with no laptops permitted during on-site coding rounds. Conversely, **Airbnb**, **Dropbox**, and **Lyft** explicitly allow candidates to code on their personal laptops using their preferred development environment. Always confirm the environment with your recruiter beforehand. ### What is the difference between General and Front-End interview tracks at companies like Airbnb? General tracks focus on algorithmic problem-solving and system design across multiple domains, while Front-End tracks substitute general coding rounds with implementation tasks using **CodePen** or similar tools. For example, Airbnb's Front-End track features two front-end tasks on CodePen using vanilla JS/jQuery, whereas the General track emphasizes algorithms and cross-functional collaboration. ### Which companies use HackerRank or CoderPad for technical screens? **Indeed** utilizes **HackerRank** for online assessments and live coding rounds, while **Palantir** uses **HackerRank CodePair** for phone screens. **Airbnb**, **Dropbox**, **Lyft**, and **WhatsApp** frequently use **CoderPad** for collaborative coding. **Google** uniquely uses **Google Docs** for phone screen algorithms, requiring candidates to write code without syntax highlighting or execution.