Software Engineer 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 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 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%
Drug test: 1%
IQ intelligence test: 1%
Here are the most commonly searched roles for interview reports -
Had a phone call with the recruiter and then was sent a karat interview to start off with. Didn't do well the first time but karat gives you a chance to interview the second time which I nailed. 2-3 weeks go by and I hear nothing, even when prompting the recruiter with emails. It got up to the point where I had to go on Linkedin and connect with other recruiters to see if they can check up on my candidacy. Finally, I get an email telling me that I wasn't going to advance. My biggest gripe with the whole interview process was that I had to go all this way just to find to find out about the status of my candidacy. Ghosting your candidates never looks good. I never write reviews on here but I felt the need to write a review about this particular experience I've had.
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.