TomTom Interview Questions
& Process

I went through the entire interview process at TomTom, and honestly, it was quite disappointing. The whole thing took about six weeks and included five interviews. Normally, reaching the final stage means a company is really interested in you. But here, the process was messy from start to finish. Even basic logistics were messed up. I was given the wrong interviewer names, which just shows they weren't well-prepared. At one point, two interviews were booked on the same meeting link, causing confusion about who should join and when. While these things can happen sometimes, when they keep happening across several rounds, it indicates a lack of teamwork within the hiring department. The most unprofessional part was at the end. After I finished all the interviews and got to the final stage, they just stopped communicating. No rejection, no feedback, no explanation – just silence. People put in a lot of time preparing for five interviews over more than a month. Ghosting candidates after that kind of commitment is really disrespectful of their time and effort. A company that claims to be great at engineering should be able to manage a structured hiring process and at least follow up with candidates. This experience felt chaotic and poorly handled. If TomTom wants to attract experienced candidates, they really need to step up their coordination, communication, and basic candidate care in their hiring process.

I had to travel to another city for the interview. The HR person was running late. Then we had a meeting that lasted about 20 minutes. It was an okay interview, they seemed interested in learning about me as a candidate.

This interview process is pretty much like FAANG interviews, but the HR experience can be frustrating. It started with an unexpected call from HR after I applied online. I initially thought it was spam, but they followed up with an email. The initial call quality was poor, with dropped connections and an inconvenient time. However, I did receive a Codility assessment, which was easy. I then had to wait over a week for feedback, and emails to HR went unanswered. Eventually, I was asked to provide availability for four interviews. After submitting my slots, there was another delay before the interviews were actually scheduled. The interviews themselves involved four behavioral questions that seemed repetitive, requiring different scenarios for similar themes. The technical questions were manageable, with a coding part expected to be completed in 20 minutes. After the interviews, getting feedback was difficult due to HR's unresponsiveness. After persistently emailing, HR finally called and mentioned they expected more, possibly in terms of soft skills, as I struggled with answering the same behavioral question multiple times across interviews. The technical part was fine, comparable to real FAANG interviews, but the overall HR experience and the company's market position in maps make me question the value.

The interview process had four rounds, each lasting one hour. They started with 20 minutes of questions about soft skills, followed by a live coding test on HackerRank. The first interview was about data structures and algorithms. The second focused on Object-Oriented programming. The third was about solving problems. The last one mixed Object-Oriented programming with some system design. The interviewers were friendly and supportive. After I got the job offer, two of the interviewers called me to say congratulations, that was so nice to hear. A good thing about having four separate rounds is that if you miss one, you can still pass the others and get an offer. If you're nervous or just having a bad day, it doesn’t stop you from moving forward. TomTom schedules these interviews on different days, and sometimes two in one day, to accommodate this. The recruiter asks you to report your availability for 4 interviews.