Reported Yelp Software Engineer interviews include an HR screen, live coding, a cultural discussion, and a later panel that mixes coding, system design, and communication.
$177K
Avg. Base Comp
$275K
Avg. Total Comp
Not reported
Typical Rounds
3-6 weeks
Process Length
Reported Yelp Software Engineer interviews begin with an HR screening before moving into live coding. One candidate described a one-hour coding round at roughly medium difficulty, including sorting and ranking a list or array and an n-gram-style problem. Another report described coding questions framed around Yelp-like scenarios, including restaurant seating logic and similarity matching among places. Practice explaining your approach as you code, including the trade-offs behind a clean, workable solution.
Communication is part of the technical assessment as well as the behavioral portion. A reported cultural conversation asked how the candidate would respond when they could not resolve a disagreement with a colleague and needed to escalate. Prepare a concise example that shows how you listened, attempted to resolve the issue directly, and escalated constructively when appropriate.
Later stages can be demanding. Candidates reported a virtual onsite or panel that combined coding, system design, and behavioral discussion; one report described four interviews packed into one day with a short break. System-design preparation should emphasize stating assumptions, organizing the design, and discussing scale and trade-offs. A hiring-manager conversation was reported late in the process, so keep your project examples and questions about the team ready through the final stages.
Synthesized from 3 candidate 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.
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 | |
| N-gram Dictionary | |
| Groups of Anagrams | |
| Sort Strings | |
| Reservoir Sampling Stream | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Target Indices | |
| Common Prefix | |
| Yelp-like System | |
| Slow SQL Query | |
| A Simpler KNN From Scratch | |
| String Palindromes | |
| Find Mismatched Words | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| Evaluate News | |
| LRU Cache 1 | |
| Sum Numbers As Strings | |
| Length Of Longest Palindrome | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap |
Synthesized from candidate reports. Individual experiences may vary.
A Software Engineer candidate reported that the process started with a 30-minute HR screening before the technical stages. Detailed questions were not reported. Use this conversation to give a focused overview of your background, relevant projects, and interest in the role, while making sure your experience is easy for the recruiter to place against the opening.
One candidate described a one-hour live coding interview at roughly medium difficulty, with sorting and ranking of a list or array and n-gram-style logic. The same report included a short cultural interview about handling an unresolved disagreement with a colleague and escalating it. Another candidate reported Yelp-themed coding prompts. Narrate your solution clearly and prepare a specific collaboration example.
Candidates reported a later virtual onsite or panel combining system design, coding, and behavioral discussion. One Software Engineer report described two coding challenges, system design, and a cultural discussion, with four interviews scheduled in one day and only a short break. A hiring-manager conversation was reported late in the process and felt informal, so stay prepared to discuss both technical work and team fit.
