Yelp Software Engineer interview typically runs 4 rounds: HR screening, coding, behavioral, and system design/panel. It usually takes a few weeks and is a structured, full-day loop with multiple interviews packed together.
$113K
Avg. Base Comp
$275K
Avg. Total Comp
4-6
Typical Rounds
3-6 weeks
Process Length
We’ve seen Yelp lean toward candidates who can turn familiar algorithms into something that feels product-aware. Multiple candidates described the coding as LeetCode-medium in spirit, but with Yelp-specific framing: seating restaurant groups, ranking lists, finding similar places, or working with n-gram-style text logic. That pattern matters because the bar is not about clever tricks; it’s about whether you can stay clean and structured when the prompt gets a little messy. The questions in the shared pool reinforce that theme too — anagrams, target indices, flattening arrays, LRU cache, reservoir sampling, and string manipulation all point to breadth with a practical edge.
A recurring theme across experiences is that Yelp seems to care just as much about judgment and communication as raw problem-solving. Candidates repeatedly mentioned conversational behavioral prompts around disagreement, escalation, and digging into past projects, which suggests they’re listening for how you collaborate when there isn’t a perfect answer. We also noticed that system design tends to be grounded in real user data and product behavior, like exporting everything a user has shared or handling location-based matching at scale. The non-obvious make-or-break here is pacing: several candidates described a dense, exhausting loop, so the people who did best were the ones who could keep their reasoning crisp even after multiple back-to-back conversations. In other words, Yelp rewards candidates who can connect technical choices to user experience without losing clarity.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Yelp process.
The process was longer and more structured than I expected, and it ended up feeling like a full-day interview loop. It started with a 30-minute HR screening, then moved into a 1-hour live coding round that felt around LeetCode medium difficulty. The coding questions I saw were pretty practical: one was about sorting and ranking a list and array, and another had an n-gram flavor, so it was less about obscure tricks and more about writing something clean under time pressure. There was also a short cultural interview, about 15 minutes, where they asked how I’d handle it if I couldn’t reach an agreement with a colleague and needed to escalate. That part was very conversational and focused on judgment and communication.
The later stages were the most intense. I had a panel-style session that combined system design, two coding challenges, and a cultural discussion, and at one point there were four interviews packed into one day with only a short break. That made the whole thing feel pretty exhausting, even though everyone I spoke with at Yelp was kind and easy to talk to. The hiring manager chat came very late in the process and was informal, almost like a final check-in just before the decision. In the end I didn’t get an offer, but the process was clear and well organized. My main takeaway is to be ready for a long loop that mixes live coding with behavioral questions, and to practice medium-level coding problems that involve arrays, ranking, and n-gram style logic.
Prep tip from this candidate
Be ready for a long, structured loop that mixes live coding with system design and behavioral questions. I’d specifically practice array ranking/sorting problems and n-gram style coding, plus a concise answer for how you’d escalate a disagreement with a colleague.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Yelp
Determine whether there exists a permutation of an input string that is a palindrome.
| Question | |
|---|---|
| The Brackets Problem | |
| Flatten N-Dimensional Array to 1D Array | |
| Groups of Anagrams | |
| Sort Strings | |
| Reservoir Sampling Stream | |
| Valid Anagram | |
| Target Indices | |
| Common Prefix | |
| Yelp-like System | |
| String Palindromes | |
| Evaluate News | |
| LRU Cache 1 | |
| Sum Numbers As Strings | |
| Length Of Longest Palindrome | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Weighted Keys | |
| Raining in Seattle | |
| Delivery Estimate Model | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Employee Salaries | |
| Random SQL Sample | |
| Closest SAT Scores |
Synthesized from candidate reports. Individual experiences may vary.
The process may begin with an online coding assessment. Candidates described it as relatively easy and manageable for someone with solid preparation, serving as an initial screen before live interviews.
A recruiter or HR call follows to discuss your background, the role, and general fit. In some cases this stage also covers high-level team information and basic logistics.
Candidates then have a behavioral conversation with a team member focused on past projects, challenges, and fit. Interviewers may dig into how you handled difficult situations and how you communicate with others.
This round is a live coding interview with LeetCode-medium style problems. Questions were practical and Yelp-flavored, including array sorting/ranking, n-gram logic, seating/waitlist decisions, and similar-place matching.
The final onsite-style loop is virtual and panel-based, with four interviews packed into one day. It typically includes system design, two additional coding rounds, and a behavioral or cultural discussion, with questions framed around Yelp-specific product scenarios.
A hiring manager chat appears late in the process and feels more like a final check-in than a deep interview. It is informal and used to confirm fit before a decision is made.