Home › Blog › Yelp Coding Interview Questions: Coding, Search and Local Data

Yelp Coding Interview Questions: Coding, Search and Local Data

Yelp, based in San Francisco, connects people with local businesses through reviews, search, advertising and tools such as Request a Quote for home services. It closed its New York, Chicago and Washington, D.C.

Yelp, based in San Francisco, connects people with local businesses through reviews, search, advertising and tools such as Request a Quote for home services. It closed its New York, Chicago and Washington, D.C. offices in 2022 and describes itself as remote-first, and candidates commonly report a HackerRank test, a live screen and a virtual onsite of about four rounds. This page covers what Yelp builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.

What Yelp builds and who it hires

Yelp's engineers build business search and ranking, reviews and photos, the automated recommendation software that decides which reviews are shown, advertising and Yelp for Business tools, and the iOS and Android apps. The site began as a large Python web application called yelp-main, and Yelp's engineering blog describes years of breaking it into services that run on PaaSTA, Yelp's own platform on Kubernetes. In 2021 Yelp introduced Nrtsearch, an open-source search engine built on Lucene, and a 2025 post said it had moved more than 90 percent of its Elasticsearch traffic to it.

What the process tends to look like

StageWhat happensHow to prepare
Online assessment (reported)A HackerRank test as an early step; reports range from one short problem to two or three over about 90 minutesTimed problems with edge cases checked
Recruiter or hiring-manager callBackground, interest in Yelp and logistics; some describe a behavioral conversation with an engineerA short answer on why local businesses interest you
Technical screenAbout 45 to 60 minutes with an engineer: live coding, sometimes alongside a walkthrough of a résumé projectExplain trade-offs as you code
Virtual onsiteUsually about four rounds: two coding, one system design, and a behavioral or project deep dive, plus the hiring managerOne location-based design and a project you can dissect

Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.

Local search, reviews and Python services

Location-aware search. Finding a business near the user means filtering by distance, category and opening hours before ranking. Know geohashes and quadtrees, how to page through results, and why a cached result for one neighborhood may be wrong a few blocks away. Our system design walkthroughs for marketplaces, maps and payments include a proximity example, and our Elasticsearch interview questions cover the Lucene ideas behind Nrtsearch.

Ranking and trust. Ranking blends relevance, distance and quality signals, and Yelp's recommendation software decides which reviews appear. Be ready to discuss which signals might flag a suspicious review and how you would measure a ranking change without being unfair to businesses.

Python at scale. Most product code is Python, and Yelp's talks describe service APIs specified with Swagger. Know Python's data structures and their costs, generators, profiling slow code and drawing service boundaries with clear API contracts. Our Python interview questions are a good refresher.

Product-aware answers. Interviewers commonly ask how a technical choice affects consumers and business owners. Tie each trade-off to an outcome, such as search latency on a phone or an owner seeing a stale rating after a new review.

Representative problem types

These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.

  1. Merge overlapping time intervals, such as opening hours or reservations.
  2. Rank the top K businesses or keywords by frequency or score with a heap.
  3. Find businesses within a radius of a point and sort them by distance.
  4. Design type-ahead search for business names and categories.
  5. Design a near-me proximity service.
  6. Keep an average rating up to date as reviews arrive and are removed.
  7. Easy and medium problems on hash maps, recursion and sorting.

What interviewers score

The behavioral side

Technical rounds decide most outcomes, but every Yelp loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:

Structures and sample answers for the common questions are in our software engineer behavioral answers guide.

A three-week prep plan

  1. Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
  2. Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
  3. Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.

For practice lists, use LeetCode company-tagged questions and the NeetCode 150 roadmap; for design rounds, read system design building blocks; and compare the practical style of Stripe.

Where CoPilot Interview fits

Most of a Yelp loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

What programming language should I use in a Yelp interview?

Python is Yelp's main back-end language and a common choice in its interviews, though HackerRank and live rounds usually allow other mainstream languages. Search-infrastructure roles work in Java, since Nrtsearch is built on Lucene, and mobile roles use the platform languages.

Does Yelp send an online assessment?

Many candidates report a HackerRank test as an early step, from a single short problem to a longer set of two or three, and some say failing unseen test cases ended their process. Not every pipeline includes one, so ask your recruiter.

Is Yelp fully remote?

Yelp closed several US offices in 2022 and describes itself as remote-first, hiring across the US and in countries including Canada, the UK and Germany. Interviews are virtual, and each posting says where the role can be based.

How should I prepare for Yelp coding questions?

Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Yelp's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.

Can I use AI tools in a Yelp interview?

Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.

Practice this interview before the real one

The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.

Start a mock interview