Candidates describe TomTom's Software Engineer interviews as a recruiter or HR contact, a coding assessment or screen, and a loop of coding, design and behavioral rounds. Expect LeetCode-style problems, small OOP design tasks and repeated behavioral questions.
$105K
Avg. Base Comp
$125K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for TomTom software engineering roles describe a mix of coding, small-scale design and behavioral questions, and the balance is not the same for everyone. Several report object-oriented design prompts such as a pizza ordering system or a Battleship-style game. Others mention a parking garage design, a board game design, and LeetCode-style problems such as interval scheduling or finding the first non-duplicate number in an array. Practice explaining time and space complexity aloud, because candidates describe talking through the approach as part of each round.
Behavioral questions carry real weight. Several candidates describe questions about conflict with colleagues, mistakes, ownership, and impact beyond their own code, and a few say the same themes came up across multiple rounds. One candidate said they ran out of distinct stories by the fourth interview, so prepare more than one example for each theme.
Language depth varies by team. One C++ candidate was asked for compilable pointer and smart-pointer code with no pseudocode. A Java-focused round covered the memory model, HashMap internals, concurrency and garbage collection. A senior candidate was asked about MVVM and gRPC. Check the job description for the stack and review that language's fundamentals.
Communication after the interviews was a frequent complaint. Two candidates report silence after final rounds, so follow up and keep your own records. Offers were reported alongside rejections, and one rejected candidate said their solutions needed to be more optimal.
Synthesized from 13 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tomtom process.
Terrible experience. Red flag. The whole process was spread across five one-hour interviews: one with HR, one with my future manager, and three with technical staff. On paper it sounded pretty standard, but in practice it was mostly behavioral questions mixed with a few Codility-style exercises, and none of it was especially difficult. The technical part was more about how I think and communicate than deep algorithm work. I was asked things like what I did when I didn’t deliver on time, an achievement I’m proud of, a time I took ownership of a critical system or project, a tough technical decision I had to live with, how I’ve multiplied my impact beyond my own code, and a situation where I shared knowledge that helped the team or organization.
What stood out most was how enthusiastic they were at the beginning versus how it ended. I also went through a screening process, system design, and technical rounds that added up to about four hours total, and after that it was just radio silence. No rejection, no feedback, no response to follow-ups. That part was honestly the worst, because I put real effort into preparing and expected at least a basic reply. The interviews themselves were fine and not very hard, but the lack of communication afterward was extremely unprofessional. My takeaway is that if you’re considering TomTom, be ready for a fairly behavioral-heavy process with some coding and system design, and don’t expect much closure at the end.
Prep tip from this candidate
Prepare for behavioral questions that probe ownership, missed deadlines, impact beyond your own code, and knowledge sharing, not just coding. It also helps to be ready for a system design round and a few Codility-style exercises, even though the coding itself was described as fairly straightforward.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tomtom
Describing a data project and its challenges
| Question | |
|---|---|
| Descending Alphanumeric Sorting | |
| Deciding Between Solutions | |
| 2nd Highest Salary | |
| Retailer Data Warehouse | |
| Prime to N | |
| Find the Missing Number | |
| Recurring Character | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Size of Joins | |
| The Brackets Problem | |
| Get Top N Frequent Words | |
| Flatten N-Dimensional Array to 1D Array | |
| Total Time in Flight | |
| Clickstream Data | |
| Ticket Agent Analysis | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Success Measurement | |
| Target Indices | |
| Transformer Encoder Layer | |
| Customer Success vs. Free Trial | |
| Digit Accumulator | |
| Slow SQL Query | |
| FAQ Matching | |
| Time Difference | |
| Duplicate Rows | |
| Walking Robot | |
| Concurrent LLM Serving |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR conversation about their background, projects and team experience. Some were approached on LinkedIn. Prepare a concise career summary and confirm the stack and level for the role.
Several candidates describe a timed online coding assessment, including Codility and a roughly 70-minute medium-plus-hard LeetCode pair. Others report a C++ and CS fundamentals phone screen covering OOP, operating systems and data structures. The format may vary by team and level.
Some candidates report a conversation with the hiring manager, or with a manager and an engineer, that mixed experience, behavioral prompts and some technical questions. It typically came early, before the main technical interviews, though the order is not identical in every report.
Candidates report four or five interviews, often an hour each, sometimes grouped into a single morning or spread across days. Reported topics include algorithms and data structures, OOP design (pizza ordering, Battleship, parking garage), small-scale system design, and language-specific questions in Java or C++.
Behavioral questions appear in several reports, sometimes in every round. Candidates mention conflict, mistakes, ownership, leadership and impact. Prepare several distinct STAR stories, because repeated questions may require different examples.
Outcomes in the reports are mixed. Some candidates received offers, one was rejected two days after a C++ round, and others reported no response after final interviews. Follow up politely if you hear nothing, since timing can be uneven.
