Cambridge Mobile Telematics Software Engineer Interview Questions
& Process

The HR folks were good and kept me in the loop, telling me what to expect and updating me. The process was really organized, starting with the HR call, then some tech tests, talking with the team and manager, and then a final chat with leadership about culture fit. It felt like each step was necessary. Everyone I talked to was nice and seemed genuinely interested. The technical questions were tough but fair, more about solving actual problems than random brain teasers. Scheduling was easy and they gave feedback pretty quickly. It was a good experience overall, made me feel positive about the company. It would've been cool to know more about the role and career path earlier on, though.

So the interview process had five rounds in total. It kicked off with a recruiter phone screen. After that, I went into a technical interview, which included a coding review and a systems design part. Then there were two behavioral interviews. I actually only made it to the technical interview stage, and didn't pass that to move forward. The technical interview itself was 45 minutes long and I had to solve two Leetcode medium problems.

The interview process spanned about a month. It began with a recruiter screener, followed by a live coding assessment. After passing that, I expected one or two more panel interviews before an offer. However, there were four additional interviews: two technical and two behavioral. This was the most extensive interview process I've encountered. I was ultimately rejected without specific feedback on why. I'd only recommend this process if you have a referral or are exceptionally passionate about CMT.