Real, anonymous reports from people who interviewed for Software Engineer at CarGurus, newest first and distilled into what to expect across the loop.
I was initially reached out to by a sourcer on LinkedIn, which led to a recruiter call that went well. Not long after, I had a phone screen with an engineer and cleared it because the questions felt very easy. After that, I was asked about my availability for onsite.
My process started with a recruiter screen, then I moved into live coding on CodePen where I worked through a front-end style share-and-solve session. After that, I had an onsite that broke into multiple one-on-one interviews: I remember two rounds with software engineers that mixed behavioral questions with system design themes, and a separate hiring-manager round that was behavioral-only. The onsite didn’t end with just the in-person part for me—I had additional remote interviews the next day, including more behavioral questions and another live coding challenge on CodePen.
The interview process typically starts with a recruiter call that is described as organized and respectful, often followed by a technical phone screen. Candidates appreciate prompt communication and clarity from the recruiter throughout the process.
Candidates experience a technical coding interview that often includes live coding sessions, primarily focusing on SQL queries, algorithm problems, and web-related tasks. The difficulty varies, but many find the questions manageable and relevant to the role.
The onsite interview typically consists of multiple rounds, including technical interviews, behavioral assessments, and sometimes system design discussions. The format is often collaborative, with interviewers focusing on problem-solving approaches rather than just correct answers.
Candidates generally report receiving timely feedback after interviews, which is appreciated, although some have experienced gaps in communication or lack of follow-through after technical rounds. Clear communication is a recurring theme in positive experiences.
The overall difficulty of the interviews is often described as average, with some candidates finding certain areas, like system design, more challenging. The tone of the interviews is usually friendly, but some candidates have faced abrupt or unprofessional interactions.
Candidates often reflect on their experiences, noting areas they wish they had prepared differently, such as deeper knowledge in specific technologies or better handling of unexpected interview dynamics. This self-assessment can guide future preparation.