
When I started preparing for frontend interviews, the most frustrating part wasn’t the questions. It was not knowing what the process even looked like. How many rounds? Is it LeetCode? Do they ask CSS? Will there be system design for a frontend role?
After going through a lot of loops myself and talking to hundreds of engineers through FrontendLead, here’s what a typical big tech frontend loop looks like, round by round, and what each one is really testing.

One disclaimer before we start: every company does it a little differently, and formats change. Always ask your recruiter exactly which rounds you’ll have and what each one covers. It’s a completely normal question, and recruiters generally want you to be prepared.
1. The recruiter call
This is a 15-30 minute conversation. It’s not technical, but it matters more than people think.
- They’ll ask about your background, what you’re looking for, and your timeline.
- They might ask about your salary expectations. I’d politely avoid giving a number this early. Something like “I’d like to learn more about the role and level first, and I’m sure we can find something fair” works.
- Ask about the loop. Which rounds, how long, and whether the coding is JavaScript-specific or general algorithms.
- Ask which level they’re considering you for. The level affects the bar in every round after this one.
2. The phone screen
Usually 45-60 minutes with an engineer, in a shared editor. For frontend roles, it’s most often one of these:
- A JavaScript utility: implement
debounce,Promise.all, a deep clone, flatten an array. - A small UI in vanilla JS or React: a counter, tabs, an accordion, a star rating.
- Occasionally a classic data structures question, especially at companies with a shared software engineering loop.
The phone screen is a filter. They want to know whether you can write working JavaScript, communicate while doing it, and handle a follow-up. A clean, working, well-explained solution is usually enough to pass.
3. The onsite (or virtual onsite)
This is the big one: usually 4-6 rounds, often spread over one or two days. Here’s what each round type tests and how I’d prepare for it.
JavaScript coding
This is the round you’ll see the most, so it deserves the most prep time. Expect utility functions and async control flow: debounce and throttle, promise utilities, event emitters, memoization, retries.
What they’re grading: correctness, edge cases, code clarity, and how well you understand closures, this, and the event loop. I broke down the patterns behind the most common ones in the 10 JavaScript coding questions that keep showing up.
UI / app building
My personal favorite. You’ll build something small and real, with React or vanilla JS: an autocomplete, a todo list, a modal, an image carousel, an infinite scrolling feed.
What they’re grading: component structure, state management, handling loading and error states, accessibility, and how you respond when they add a requirement halfway through. A full list of common ones is in the free app design questions guide.
Frontend system design
Usually for mid-level and above. “Design a news feed”, “design an e-commerce product page”, “design a chat app”.
Unlike backend system design, the focus is the client: components, state, data model, API contract, rendering strategy, performance, and accessibility. You don’t need to design database sharding. I walk through my approach in my frontend system design framework.
Behavioral
Most engineers underprepare for this one, and I was guilty of it too. At senior levels especially, the behavioral round can heavily influence your level, not just whether you pass. Prepare 5-6 real stories ahead of time. I explain how in building a behavioral story bank.
Trivia or domain knowledge
Some companies have a dedicated round, others sprinkle these questions into coding rounds: “How does the event loop work?”, “What’s the difference between display: none and visibility: hidden?”, “What causes a React component to re-render?”. The free trivia guide covers the most common ones, and for React specifically I keep 300+ React interview questions with answers.
How much time to spend on each
| Round | How often you’ll see it | Share of prep time |
|---|---|---|
| JavaScript coding | Almost always, often twice | ~35% |
| UI / app build | Very common | ~25% |
| System design | Mid-level and above | ~15-20% |
| Behavioral | Always | ~10-15% |
| Trivia / fundamentals | Often mixed into other rounds | ~10% |
Adjust based on what your recruiter tells you. If your loop has two system design rounds because you’re interviewing for a senior role, shift time accordingly.
4. Debrief, leveling, and the offer
After the onsite, your interviewers write feedback and a hiring committee or manager makes a decision, including your level. Then there may be team matching, where you talk to a few managers to find a team.
Team matching is a two-way conversation. Ask about the codebase, how they ship, what the on-call looks like, and what success looks like in the first six months.
Then comes the offer, and the negotiation. If you can, line up your loops so offers arrive around the same time. I explain how in how to negotiate multiple frontend offers.
Frontend vs general software engineering loops
Some companies interview frontend engineers with a dedicated frontend loop. Others put everyone through the same general loop, with one or two frontend-specific rounds. This is the single most important thing to find out early, because it changes how much algorithm practice you need.
| Loop type | Coding questions look like | Prep implication |
|---|---|---|
| Dedicated frontend | debounce, promises, DOM, UI builds | Focus on JS, React, and UI questions |
| General SWE | Arrays, hash maps, trees, graphs | Add classic algorithm practice |
| Hybrid | Mix of both | Solid algorithm basics plus frontend depth |
If you need to brush up on algorithms, the free data structures and algorithms guide focuses on what actually comes up for frontend candidates. And if you want to see what specific companies ask, check out the company-specific question lists.
And that’s it, folks. Knowing the shape of the loop takes a lot of the anxiety out of it. Once you know what’s coming, you can prepare for each round on purpose instead of studying everything at once.
