Compass coding interviews are generally considered medium to hard, similar to Amazon's standard bar. The questions are less about obscure algorithms and more about clean, scalable implementation and communicating your thought process. Expect a strong emphasis on edge cases and test cases, and be prepared for follow-up questions that test your ability to iterate on a solution.

Master arrays, strings, hash maps/dictionaries, and two-pointer techniques. Over 70% of initial screening questions for SDE-1 come from these fundamental areas. Focus on writing bug-free, modular code with clear variable names, as clean code is a key evaluation metric at Compass, more so than a single optimal solution.

The biggest mistake is giving vague answers not structured with the STAR method (Situation, Task, Action, Result). Candidates also fail to explicitly name and connect their story to the specific Compass LP (e.g., 'Customer Obsession' or 'Learn and Be Curious'). Prepare 8-10 detailed stories that can be flexibly mapped to multiple LPs, and always end with a quantifiable result.

Proactively discuss trade-offs between different approaches (time/space complexity) and ask clarifying questions about constraints. After solving, suggest test cases, including edge cases. Most importantly, link your solution back to a real-world scenario, like how it might apply to search in Compass's real estate platform or processing listing data.

The internal review and calibrations, often involving the 'Bar Raiser' (a senior leader from another team), can take 2-4 weeks after your final round. You may hear back from the recruiter first with a verbal update, followed by the formal offer letter. It's acceptable to send a polite follow-up email to your recruiter after 3 weeks if you haven't heard anything.

For SDE-2, the coding problems will often involve more complex system design integration, and you'll be expected to lead the technical discussion significantly. The behavioral round will probe deeper on mentorship, project leadership, and scaling past just your own tasks. System design fundamentals become critical for SDE-2 and above.

Study Compass's 16 Leadership Principles on their careers page and find specific examples of how engineers apply them. Practice explaining your code as you write it, simulating a pair-programming environment. Use platforms like Pramp for mock interviews focused on communication. Search on Glassdoor for very recent ('last 6 months') Compass interview questions to gauge current trends.

The Bar Raiser is an Amazon-hired external interviewer who ensures Compass's hiring bar matches Amazon's leadership principles. It is a deeply behavioral round focused on past experiences that demonstrate Compass's LPs. It's not about hypotheticals. You must tell compelling, specific stories with metrics that show you operate at a senior level of ownership and impact, even if you're interviewing for a junior role.