Compass Software Engineer interview typically runs 4 rounds: recruiter screen, technical round, engineering manager, onsite rounds. Timeline is about 2-4 weeks, with multiple interviewers and inconsistent communication.
$129K
Avg. Base Comp
$160K
Avg. Total Comp
4-6
Typical Rounds
3-6 weeks
Process Length
We’ve seen Compass look for engineers who can move comfortably between classic technical depth and the company’s real-estate context. Multiple candidates reported a mix of algorithmic coding, system design, and debugging, but the signal wasn’t just whether they reached the right answer — it was whether they could explain edge cases, reason through messy inputs, and stay grounded when the prompt was under-specified. One candidate specifically noted that a LeetCode-style interval problem became more revealing because they were expected to generate their own test cases, which tells us Compass values careful problem framing as much as implementation speed.
A recurring theme is that Compass wants people who can connect engineering work to the business. Our candidates report questions about core values, past projects, and even sales- or agent-facing scenarios, which is unusual for a software engineering loop but very consistent with a company that sits at the intersection of SaaS and real estate. The strongest responses were the ones that translated technical decisions into product impact or operational tradeoffs, not just architecture jargon. We also noticed that the debugging exercise can be a differentiator: one candidate described fixing a buggy email/address-book workflow with limited tooling, which suggests Compass is watching for practical troubleshooting under constraints.
The non-obvious make-or-break factor here is polish in communication, both during the interview and after it. One candidate had a smooth recruiter experience, while another reported weak follow-through and unclear closure after an initially positive screen. That inconsistency matters because it mirrors the broader pattern: Compass seems to reward candidates who are organized, self-directed, and able to keep momentum even when the process itself is a little uneven.
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 Compass process.
The process started off better than I expected, but it went downhill after that. I had an initial phone screen with the recruiter, and that conversation went well enough that I was told to expect an email with next steps soon. That email never came, and even after I followed up a couple of times, I didn’t get a response. It felt pretty bad from a candidate experience standpoint because there was no clear closure.
Before that, the recruiter did ask the usual intro questions like tell me about yourself, and there were also questions about my experience with cloud, DevOps, and Java. In the technical rounds, the interview was more involved: there were multiple technical rounds, each about an hour long, with multiple interviewers per round. Those covered system design and coding problems, and one of the coding prompts was just to solve a technical problem without much context, which made it harder than it needed to be. I also had an in-person portion where I met with three people from different teams and the head of sales, and that part was more conversational. One question that stood out there was about the most important role of a real estate agent, which felt a bit unexpected for a software engineering interview. Overall, the process felt inconsistent, and the communication after the recruiter screen was the weakest part. I ended up with no offer, so my main takeaway is to be ready for a mix of coding, system design, and some business-facing questions, but don’t expect the process to be especially organized.
Prep tip from this candidate
Be ready for hour-long technical rounds that include both system design and coding, and don’t be surprised if a coding prompt is given with very little context. It also helps to prepare for a business-oriented question about Compass’s real estate side, since that came up in the in-person portion.
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 | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Raining in Seattle | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Google Maps Improvement | |
| Download Facts | |
| Prime to N | |
| Upsell Transactions | |
| P-value to a Layman | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| First Touch Attribution | |
| Find Bigrams | |
| Job Recommendation | |
| Find the Missing Number | |
| Recurring Character |
Synthesized from candidate reports. Individual experiences may vary.
An initial phone screen with the recruiter covers standard intro questions like "tell me about yourself" along with your experience in cloud, DevOps, and Java. In at least one experience, this conversation went well enough that the candidate was told to expect next steps afterward.
Candidates may be asked to complete a take-home project, described as a fairly simple CSV task involving finding similar fields using any technology they want. The assignment can still take real time to complete and appears to be part of the evaluation before final decisions.
There are multiple technical rounds, often with multiple interviewers per round, covering coding, system design, and debugging. Examples included a LeetCode-style interval problem like Meeting Rooms II with custom test cases, a system design discussion, and a debugging exercise involving a buggy emailing/address book workflow.
The onsite portion can include three in-person rounds with engineers and managers from different teams. One round focused on the engineering manager reviewing past work and Compass core values, while another was more conversational and included business-facing questions, such as the role of a real estate agent.
