Compass Software Engineer candidates describe a recruiter screen, LeetCode-style coding, debugging, system design and behavioral rounds. Reports are mixed and mostly end in no offer.
$145K
Avg. Base Comp
$198K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates interviewing for Compass software engineering roles describe a loop that mixes classic algorithms with more practical exercises. Two mention debugging rounds. One described an emailing and address book script with a 2D array for email opt-outs, where only print statements were available. If you are given a script to fix, ask early about tooling and talk through your reasoning.
Coding reports lean on scheduling problems. One candidate was asked for Meeting Rooms II and had to write their own test cases. Another was asked to design a calendar manager class with unit tests. Practice interval questions, and get used to writing tests alongside your solution. One backend candidate also had a take-home CSV task on finding similar fields, so budget time if you receive one.
System design appears in more than one account, including designing a WhatsApp-style messaging app in 45 minutes with diagrams and trade-offs. Behavioral rounds are also prominent. Candidates describe hiring manager conversations that probe past projects, questions tied to company values, and prompts on ambiguity and customer impact. The candidate who received an offer described an AI-assisted round on forms and pattern matching, so ask your recruiter what to expect.
Experiences vary widely, and most reports here ended without an offer. Candidates also cite slow or sparse recruiter communication, so follow up politely and keep your preparation broad.
Synthesized from 10 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 Compass process.
I went through most of Compass's loop for the Software Engineer role and didn't receive an offer at the end. Even so, the process was fairly straightforward and the people I met were friendly. It started with a phone screen where the recruiter asked about my salary expectations and how comfortable I was with the tech stack. After that came a LeetCode-style coding round, then another coding round paired with a system design round. The interviewers were warm throughout, which helped the technical rounds feel less intimidating.
The detail that stood out most was the format. No AI assistance was allowed at any point, so this was a traditional live coding setup where you have to reason through problems out loud and write working code on your own. I'd plan for that explicitly rather than assuming a more relaxed style. The loop also included two behavioral rounds. I didn't get specific feedback on what decided the outcome, so my main takeaway is to stay sharp and consistent across every round, not just the technical ones.
Prep tip from this candidate
Expect a classic live coding format with no AI assistance, so practice solving problems aloud and writing code on your own. Also be ready to discuss your salary expectations and tech stack knowledge in the initial phone screen.
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 Compass
Reconstruct the path of a trip so that the trip tickets are in order.
| Question | |
|---|---|
| Minimum Days for Scheduling All Meetings | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Google Maps Improvement | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Daily Retention Summary | |
| P-value to a Layman | |
| First Touch Attribution | |
| Job Recommendation | |
| Find Bigrams | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call covering background and sometimes experience with cloud, DevOps or Java. One candidate described a 15-minute screen focused on the role. Experiences vary, and one candidate reported a dismissive recruiter and never advanced past this stage.
Candidates report live coding of roughly 45 to 60 minutes. Reported problems include Meeting Rooms II with self-written test cases and a calendar manager class with unit tests. Difficulty may vary by interviewer, so prepare interval problems and testing habits.
Two candidates mention a debugging round. One was handed a buggy emailing and address book script with an opt-out tracking issue and had only print statements available. This round rewards methodical reasoning, clarifying questions and asking about tooling up front.
Some candidates report a design question for a messaging app like WhatsApp, with about 45 minutes to sketch architecture, data flow and trade-offs. Not every account mentions this round, so confirm the loop with your recruiter, but prepare to explain scalability choices clearly.
Candidates report behavioral rounds with the hiring manager and other leaders. Topics include past project ownership, ambiguity, prioritization, customer impact and company values. One in-person account also included business-facing questions about real estate, so have structured stories ready.
