Yelp frontend interviews use a coding challenge, small React tasks, and practical problems based on real Yelp work. See the process, questions, and prep plan.
This guide is built from 4 Yelp interview reports shared by FrontendLead members between February and September 2024, combined with Yelp’s official careers prep page and posts from the Yelp engineering blog about how it designs and scores interviews. Member data for Yelp is thin, so this guide says clearly what comes from members, what comes from Yelp, and what is our recommendation. Confirm the details of your loop with your recruiter.
The most useful thing to know: Yelp builds its technical questions from problems its teams actually solved, scaled down to interview size. That matches what members saw: small stateful React components, a graph traversal problem, and a web-crawling style task. The exact prompts are in the members-only sections below. Expect practical tasks, not puzzles, and practice explaining trade-offs out loud.
By Shivam Bhalla · Updated
01Yelp frontend interview at a glance
- Process
- Application, coding challenge, recruiter conversation, first-round interview, panel interview, offer
- Coding challenge
- Online and timed; members built small React apps for frontend roles
- First round
- Live technical interview, often with resume and “why Yelp” questions
- Panel
- Problem solving, system design, and two behavioral interview types
- Coding language
- JavaScript with React was accepted in members’ frontend assessments
- Question style
- Scaled-down versions of real problems Yelp teams have solved
- Decision
- Yelp says recruiters generally follow up within one week of your interview
- Work model
- Yelp describes itself as a remote company
02Yelp frontend interview process
Yelp’s official prep page lists the steps below. Member reports add frontend-specific detail to the coding challenge and first round.
- 1
Application
Yelp encourages candidates to learn its products and business model before interviewing, and points to its Investor Relations page as a good overview. You don’t need to be an expert, but general knowledge helps in every round.
- 2
Coding challenge
Online, timedA Yelp engineering blog post says the online challenge is usually the first step and that Yelp runs it on HackerRank, so take a practice test to learn the interface. One member took a frontend challenge twice and passed both times. Both tasks were small React apps focused on state, timers, and event handling. An older intern report described a 15-minute string-processing problem.
- 3
Recruiting partner conversation
A conversation about your background, interest in Yelp, and the role. Use it to confirm whether the role is frontend or full-stack. One member found out late in the process that only full-stack roles were open.
- 4
First-round interview
About 45 minutes in one member’s reportA live technical interview with an engineer. Members saw a graph traversal question with follow-ups on edge cases, and a crawling problem involving async requests. One interviewer opened with why Yelp, what you like most about Yelp, and what you would improve. Yelp’s blog says first interviews typically cover easy to medium problems.
One member in Canada received an invite to the next round within 10 minutes of finishing.
- 5
Panel interview
Several back-to-back interviewsYelp’s blog says the onsite usually moves to medium and hard problems. A separate blog post on structured interviews describes four standardized question types (covered below), so expect a mix of coding, system design, and behavioral interviews. No member has shared a full frontend panel yet; ask your recruiter for the exact rounds.
- 6
Offer
About 1 weekYelp says recruiters generally follow up within one week after your interviews and will keep you updated if it takes longer.
03How Yelp designs and scores interviews
Yelp has written publicly about moving to structured interviews. According to its engineering blog, it standardized questions across roles into four types, built technical questions from real problems teams recently solved, and scored every question against the same dimensions it uses to level engineers internally.
| Interview type | What it covers | How to prepare |
|---|---|---|
| Problem Solving | Coding a practical, scaled-down task | Small UI apps, JavaScript utilities, and graph or string problems |
| System Design | Designing a feature or system end to end | Product-focused frontend design for search, maps, and reviews |
| Playing Well with Others | Collaboration, communication, and conflict | Stories about partner teams, feedback, and disagreements |
| Ownership, Tenacity, and Curiosity | Driving work to completion and learning new areas | Stories where you pushed through obstacles or learned fast |
The scoring dimensions Yelp lists are Technical Skill, Ownership, Business Insight, Continuous Improvement, and Leadership. Business Insight is the one candidates forget. Tie technical decisions to users and local businesses: why a faster search page matters to a diner, or why a review form needs strong validation.
Yelp’s blog also describes three moments to speak up in a coding interview. Restate the problem and ask clarifying questions, because some criteria are deliberately left out. Offer two or three approaches with pros and cons before you code. After coding, walk through each line and test it verbally. It also warns that the first question may not be the only one, so keep a steady pace.
04Coding questions Yelp candidates were asked
Premium
These prompts come from member reports, plus questions FrontendLead members have tagged with Yelp. The reports are from 2024 and earlier, so treat them as examples of the style rather than a list to memorize.
Counter that starts and stops
Frontend, coding challengeGiven an initial value, pressing a button increments the number every second; pressing it again stops counting. The member built it in React. The deep dive below shows a clean version and the bugs interviewers look for.
Practice: Stoppable Repeat Timer and Lap Split Stopwatch.
Color buttons that restyle a box
Frontend, coding challengeGiven an empty div and an array of color hex codes, render one button per color. Clicking a button changes the box’s background to that color. Use the color as the key, give each button an accessible label (a swatch alone isn’t readable by screen readers), and show which color is selected with aria-pressed.
Follow the path to its final endpoint
Frontend, phone interviewGiven a list of start and end points, return the final endpoint reached from an input. Follow-ups added loops and multiple edges from the same point. Use a map from start to end and a visited set to detect cycles; with multiple edges, switch to depth-first search and return every reachable endpoint.
Practice: Linked List Loop Entry for cycle detection.
Find broken links across pages
Intern, first roundGiven a set of web pages, identify links that fail, for example ones that return 404. The member had about 10 minutes, and the interviewer simplified it to extracting every link from a single page. Plan the crawl first: a queue of pages, a visited set, and limited concurrency for the requests.
Practice: Depth-First Site Crawl and Async Map with Limit.
Longest common prefix
Intern, coding challengeFind the longest prefix shared by every string in a list. Compare character by character against the first string and stop at the first mismatch or the end of the shortest string. Handle an empty list.
Debounce and throttle
Tagged by membersFrontendLead members have tagged debounce and throttle questions with Yelp. Both fit Yelp’s product: debounce the search box, throttle scroll and map-move handlers. Know the difference, and implement leading and trailing options.
Practice: Debounce I and Throttle.
05Deep dive: timers in React
Premium
A start and stop counter looks trivial, but it tests whether you understand effects, cleanup, and stale state. These are the bugs that show up most often in timer questions:
- Starting a new interval on every click without clearing the old one, so the count speeds up.
- Calling
setCount(count + 1)inside the interval, which captures a stale value and stops at the initial value plus one. - Not clearing the interval on unmount, which leaks timers.
Drive the interval from a single isRunning flag and let the effect own the timer:
function StoppableCounter({ initialValue = 0 }) {
const [count, setCount] = useState(initialValue);
const [isRunning, setIsRunning] = useState(false);
useEffect(() => {
if (!isRunning) return;
const id = setInterval(() => setCount((value) => value + 1), 1000);
return () => clearInterval(id);
}, [isRunning]);
return (
<div>
<output aria-live="polite">{count}</output>
<button type="button" onClick={() => setIsRunning((running) => !running)}>
{isRunning ? "Stop" : "Start"}
</button>
</div>
);
}
Explain the follow-ups before they’re asked. A functional update avoids stale state. The cleanup function runs both when isRunning turns false and on unmount. If the interviewer wants the count to resume exactly where it paused within the current second, you need to store the remaining time, because setInterval restarts the full second.
06Yelp frontend system design: what to prepare
Premium
Yelp’s structured interviews include a system design type, but no member has shared a Yelp frontend design prompt yet. Yelp asks candidates to learn its products, so the prompts below are our recommendations based on Yelp’s core features. They are not reported questions.
Business search with autocomplete
RecommendedSearch by name, category, or location with suggestions as you type. Cover debounced requests, canceling stale responses, caching recent queries, and keyboard navigation in the suggestion list.
Study: Design Auto Complete Search.
Search results with a synced map
RecommendedA results list next to a map, where moving the map updates results and hovering a result highlights its pin. Cover throttled map-move handlers, marker clustering, URL state for filters, and pagination.
Study: Design Google Maps and Design Airbnb.
Business page with reviews and photos
RecommendedA page with business details, paginated reviews, sorting, and a photo gallery. Cover server rendering for SEO, lazy-loaded images with responsive sizes, and keeping the page fast on mobile.
Study: SSR vs CSR and Image Optimizations Strategies.
Review composer
RecommendedA star rating plus a text review with photo uploads and draft saving. Cover validation, autosave to local storage, upload progress, and accessible rating input.
Practice: Star Rating System.
07Behavioral interview at Yelp
Yelp’s careers page says it values employees who treat others with respect, appreciate different viewpoints, show tenacity in reaching their goals, and bring their authentic selves to work. Its two behavioral interview types map closely to those values.
One member’s interviewer opened with three product questions. Have answers ready:
- Why Yelp?
- What do you like most about Yelp?
- What would you suggest Yelp improve?
For the improvement question, use the app for a week before your interview and pick one concrete, frontend-flavored idea, such as a faster filter flow or a clearer review composer. Explain who it helps and how you would measure it. That shows Business Insight, one of Yelp’s scoring dimensions.
Prepare at least two stories for each behavioral type: two for Playing Well with Others (a disagreement you resolved, feedback you acted on) and two for Ownership, Tenacity, and Curiosity (a project you drove past a blocker, an area you learned quickly). Expect resume deep dives as well; one interviewer asked detailed questions about every project listed.
08How to prepare for the Yelp frontend interview
Yelp’s blog recommends strong computer science fundamentals, regular coding practice from easy to hard, and mock interviews where you explain your thinking out loud. This two-week plan adapts that advice for frontend roles.
| Days | Focus | Practice |
|---|---|---|
| 1 to 2 | Small React apps | Stoppable Repeat Timer, a small state-driven widget, and To-do App |
| 3 to 4 | JavaScript utilities | Debounce I, Throttle, Async Map with Limit |
| 5 to 7 | Graphs and strings | Depth-First Site Crawl, Linked List Loop Entry, and common string problems |
| 8 to 10 | System design | Autocomplete and a search page with a map |
| 11 to 12 | Behavioral and product | Four stories, plus answers to why Yelp and what you would improve |
| 13 to 14 | Mocks | Two timed sessions; restate, offer options, code, then test verbally |
Find more practice in the coding questions and behavioral interview questions, or build a schedule with the study plans.
09Yelp frontend interview FAQ
What are the steps in the Yelp interview process?
Yelp lists six steps: application, coding challenge, recruiting partner conversation, first-round interview, panel interview, and offer. Frontend members described the coding challenge as small React tasks and the first round as a live technical interview.
Does Yelp ask LeetCode questions for frontend roles?
Some. Members saw graph and string problems in phone interviews alongside React tasks. Yelp’s blog says first interviews cover easy to medium problems and onsite interviews medium to hard, so practice both UI and algorithms.
Can I use React in the Yelp coding challenge?
One member completed two frontend coding challenges in React and passed both. Confirm the allowed languages and frameworks with your recruiter before you start.
How long does Yelp take to respond after an interview?
Yelp says recruiters generally follow up within one week. One member received a next-round invite within 10 minutes of finishing a phone interview.
What does Yelp look for in interviews?
Yelp’s engineering blog lists five scoring dimensions: Technical Skill, Ownership, Business Insight, Continuous Improvement, and Leadership. Show how your technical choices help users and local businesses, not just that the code works.
Is Yelp a remote company?
Yelp’s careers page describes it as a remote company with team members in several countries and time zones. Interviews are typically virtual; confirm the format with your recruiter.
