
Two Hopper analyst candidates describe a recruiter screen, a loosely defined analysis exercise or live SQL test, and open-ended business-case follow-ups. Both were rejected. This guide covers what to prepare.
$90K
Avg. Base Comp
$105K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe Hopper's analyst interviews, and both emphasize open-ended business problems over clean, scripted analytics questions. One candidate says the recruiter screen was high level, then a roughly three-hour, two-part exercise on two datasets was announced. That candidate was asked how Hopper could improve its healthy margins, and the recruiter said they wanted ideas rather than metrics, even though the email framing mentioned metrics.
A second candidate describes a different path. A standard live SQL assessment included a window function where a syntax slip prompted an extra take-home. That take-home was not SQL. It was a write-up or presentation, and the follow-up call became a live business case on the same dataset, including how to calculate the optimal number of active listings for a city. This candidate was also told a partner-team call and a co-founder meeting would follow.
The practical takeaway is to prepare for ambiguity. Refresh window functions so you can write them cleanly, be ready to rerun numbers live on data you have already analyzed, and have a structured way to brainstorm margin or marketplace-supply ideas. Both candidates received no offer, so treat this as two reports rather than a settled pattern.
Synthesized from 2 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 Hopper 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 Hopper
The task is to implement a shortest path algorithm (like Dijkstra's or Bellman-Ford) to find the shortest path from a start node to an end node in a given graph. The graph is represented as a 2D array where each cell represents a node and the value in the cell represents the cost to traverse to that node.
| Question | |
|---|---|
| Improve Search Results | |
| Parking Application System Design | |
| Why Do You Want to Work With Us | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Button AB Test | |
| 2nd Highest Salary | |
| Experiment Validity | |
| Top Three Salaries | |
| Last Transaction | |
| First to Six | |
| Raining in Seattle | |
| Fair Coin | |
| User Experience Percentage | |
| Employee Salaries (ETL Error) | |
| Ad Comments | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Revenue Retention | |
| Impression Reach | |
| Uniform Car Maker | |
| Top 3 Users | |
| P-value to a Layman | |
| Download Facts | |
| Third Purchase | |
| Google Maps Improvement | |
| k-Means from Scratch | |
| Decreasing Comments | |
| Find the Missing Number |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a recruiter screen that stayed high level, covering basic data analysis questions and some industry discussion. Expect to explain your analytics background and how you approach data problems. Details beyond this are not reported, so treat the rest as typical rather than certain.
Candidates report different technical stages. One was told to expect a two-part, roughly three-hour exercise summarizing two datasets. Another took a live SQL assessment with fairly standard questions, where a window function syntax slip drew extra scrutiny. Prepare for either format and confirm the expectations with your recruiter.
One candidate reports being asked how Hopper could improve its margins and was told the interviewer wanted ideas rather than metrics, despite the earlier email wording. Be ready to structure a broad business brainstorm, and ask early what kind of answer is expected. This is one candidate's account.
After the SQL slip, one candidate was asked to complete a non-SQL take-home, either a write-up or a presentation. The review call then became a new live business case on the same dataset, with on-the-spot calculations such as the optimal number of active listings for a city. Practice recomputing figures live.
The SQL-assessment candidate was told a call with a partner team and a meeting with a co-founder would follow, though they did not reach those stages. Applicants may encounter further conversations beyond the technical rounds, but this is based on what one candidate was told rather than what they experienced.