Interview Formats by Company

Each major tech company has a distinct frontend interview process. Knowing the format in advance lets you prepare strategically instead of generically.

Read the tables below as a dated snapshot, not as a contract. Round names, counts, and ordering change without announcement, they differ between orgs inside the same company, and every published guide — this one included — is describing what was true when it was written. The person who knows your actual loop is your recruiter, and they will send it to you in writing if you ask. Do that as soon as a phone screen is scheduled. Use these tables to know what to expect and what questions to ask; use the recruiter's reply as the source of record.

Meta (Frontend Engineer)

Meta has a dedicated Frontend Engineer interview loop, separate from their general SWE track:

Round	Duration	Focus
Recruiter Screen	30 min	Behavioral, role fit
Technical Phone Screen	45 min	JavaScript coding, DOM manipulation
Onsite Round 1: Coding	45 min	Vanilla JS problem — no frameworks allowed
Onsite Round 2: Coding	45 min	Algorithmic or UI implementation from scratch
Onsite Round 3: Frontend System Design	45 min	Design a news feed, autocomplete, or spreadsheet
Onsite Round 4: Behavioral	45 min	Collaboration, conflict resolution, project impact

Key Meta notes:

• The coding rounds test vanilla JavaScript, not React or any framework
• The system design round is frontend-specific — component architecture, state management, data flow, rendering performance
• Meta uses a hiring committee model — interviewers submit independent feedback and a separate committee makes the hire/no-hire decision

Google (Frontend / SWE)

Google's frontend process is less differentiated from general SWE than Meta's:

Round	Duration	Focus
Recruiter Screen	30 min	Background, role expectations
Phone/Video Technical Screen	45 min	Coding on shared editor (algorithms or frontend-specific)
Onsite Coding x 2-3	45 min each	Mix of algorithms/DSA and frontend-specific (DOM, CSS, JS)
Onsite Frontend System Design	45 min	Frontend architecture with scalability considerations
Onsite Behavioral	45 min	"Googleyness & Leadership" assessment

Key Google notes:

• Google historically weights algorithms more heavily than Meta for frontend roles
• The hiring committee is separate from the interviewers — they review written feedback and decide
• Candidates can be "pooled" — approved by committee but waiting for a team match
• Some Google teams still run a generic SWE loop even for frontend candidates

Amazon (Frontend / SDE)

Amazon's process is unique because Leadership Principles (LPs) are evaluated in every single round:

Round	Duration	Focus
Recruiter Screen	30 min	Background, LP alignment
Online Assessment	60-90 min	Coding problems on HackerRank or Amazon's platform
Onsite Coding x 2	60 min each	Algorithmic + frontend-specific (15-20 min LP per round)
Onsite System Design	60 min	Frontend or full-stack depending on team
Onsite Behavioral/LP	60 min	Deep LP assessment (often a "Bar Raiser" round)

Key Amazon notes:

• Every round starts with 15-20 minutes of behavioral/LP questions — this is not optional
• The 16 Leadership Principles (Customer Obsession, Ownership, Bias for Action, etc.) are the backbone of Amazon's hiring
• LP performance can override technical performance — a strong technical showing with weak LP signals can result in rejection
• Prepare 2-3 STAR stories per Leadership Principle — this is not an exaggeration
• The "Bar Raiser" is a specially trained interviewer from another team whose job is to maintain hiring standards

Apple

Apple is the most opaque of the major tech companies about their process:

Round	Duration	Focus
Recruiter Screen	30 min	Background
Technical Phone Screen	45-60 min	Team-specific coding
Onsite Coding x 2-3	45-60 min each	Practical, applied problems related to the team's product
Onsite System Design	45-60 min	Frontend or full-stack
Onsite Behavioral x 1-2	45 min	Culture fit, attention to detail, craft
Manager Interview	30-45 min	Hiring manager and sometimes skip-level

Key Apple notes:

• The process is team-specific — the hiring manager has significant influence
• Apple values craft, attention to detail, and passion for user experience
• They ask about accessibility, performance optimization, and cross-browser compatibility more than other companies
• Questions may involve real-world scenarios relevant to the team's product (Safari, Maps, Music, etc.)

Startups

Startup interview processes are more varied but typically shorter:

Format	Description	Time
Take-Home Assignment	Build a small React app or implement a feature	2-8 hrs
Pair Programming	Build something collaboratively with an interviewer	60-90 min
Portfolio Review	Deep-dive discussion of past projects and decisions	45-60 min
System Design Lite	Informal whiteboard architecture discussion	30-45 min
Paid Trial Day	Work on real codebase issues for 1-2 days	1-2 days

Key startup notes:

• Total process is typically 2-3 rounds (vs. FAANG's 5-6)
• Many startups are moving away from long take-homes toward shorter, timed exercises (2-4 hours max)
• Pair programming is increasingly popular — it tests collaboration and communication alongside coding
• Culture fit often matters more than algorithmic ability

Quick Comparison

Company	Coding Emphasis	System Design	Behavioral	Total Rounds
Meta	Vanilla JS	Frontend-specific	Standard	6
Google	Algorithms heavy	Frontend + scale	Googleyness	6-7
Amazon	Mixed	Team-dependent	LP in every round	5-6
Apple	Applied/practical	Team-specific	Craft & detail	5-7
Startups	Practical/pair	Informal	Culture fit	2-3

Reading Your Own Loop

Company names go stale; loop archetypes do not. When your recruiter sends the round list, match it to one of these four shapes and your preparation follows from the shape, not from whose logo is on the offer letter.

Next, we'll build your personalized 8-week study plan based on your target companies. :::