Software Engineer I applicants have rated the interview process at Compass with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 28% positive. To compare, the company-average is 46.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer I roles take an average of 23 days to get hired, when considering 36 user submitted interviews for this role. To compare, the hiring process at Compass overall takes an average of 23 days.
Common stages of the interview process at Compass as a Software Engineer I according to 36 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 24%
Presentation: 15%
Skills test: 9%
Group panel interview: 3%
Other: 3%
Personality test: 3%
IQ intelligence test: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. I interviewed at Compass (New York, NY) in Feb 2019
Interview
Interview consisted 1 phone interview with recruiter, 2 technical phone interview, and onsite 5 hour interview including lunch before offer was presented. Recruiters were overall very transparent and easy to work with. There was also a small chat after offer was signed to then be assigned on a team.
I don't remember much of the first phone interview, but it was pleasant. They will send you their engineering blog and also videos of the product at some point to look at. From there, you can get a better idea of the product and also the engineering culture.
2 phone interviews were over coderpad. Basic algorithms you can find on Hackerrank or Leetcode. I am entering as Front-End engineer so my interviews were all JavaScript based. I say study some basic algorithms, whatever language you picked, and get used to the coderpad. I accidently messed up the time of my interview and they were wonderful with it.
The onsite consisted 4 interviews and 1 hour lunch. I got to see their building and interviewed with 4 engineering managers. They were all great and pleasant to talk to. 2 had some "white boarding" or coding and 2 had some architeture discussion. Culture fit seemed to be more important. I did just okay I felt like on the coding questions but all of the managers seemed layback and transparent with their feed back.
I also had questions of my own since I've heard about the company growingfairly quickly. I wanted to know how they are planning to handle the work culture as they grow and also where they will fit all the new people? I felt they took the questions well and the managers all seemed passionate about their work.
At the end the COO also popped in to say hello to me which was super nice of her!
Overall I had a good experience interviewing with Compass.
Interview questions [1]
Question 1
Explain the architecture of the last project you worked on in detail with the different technologies.
I applied through college or university. I interviewed at Compass (Bellevue, WA)
Interview
Pretty chill. Three rounds of debugging, technical (leetcode), and behavioral, which was more like high-level with AI assistance. The values did not come up very much while going through the interview process.
Interview questions [1]
Question 1
Had us do an AI round about forms and matching things.
Debugging, technical, then behavioral. I had been given two language options for the debugging portion (Java or Python) during the phone interview then when I went to the onsite there seemed to be a miscommunication because the interview said I could use JS since I was applying as a frontend engineer. The debugging was pretty doable, the behavioral was odd but fine.
The interview process felt chaotic and poorly organized. What I was asked in the interview didn’t align with what HR told me to expect, and the interview started late. The lack of alignment between HR and the interviewer made it feel like the company overall may be chaotic. Afterward, HR’s follow-ups were generic and robotic, and the employer also mentioned layoffs, which added to the uncertainty. Overall, it didn’t feel worth the effort.