Tomtom Interview Questions (2026)
3 questions · 1 experiences · LeetCode (3) · GeeksforGeeks (1)
Browse by role
Top topics
TomTom Interview Experience | Set 1 (On Campus)
Question Details
There were 16 candidates from our college shortlisted for the internship drive.
Round 1 Coding round: 1 hour time was given to solve the problems which was quite enough. 1).Simple array index based question - Given an array(zero indexed)containing only one -1 and all remaining elements are between 1 to n-1.Find the number of elements required to reach -1(including -1) starting from index 0,considering array elements as an index for next iterations (eg. In A:(2,4,3,-1) ,the function will return 3) 2).Find number of perfect squares from A and B (both inclusive)(Max Range -1000000 to 1000000) Suggestion: I would suggest to do practice from sites like hackerrrank, codechef, codility as it will give confidence to solve problems. They decided to take interviews of all the candidates. :)
Round 2 Technical Interview ( 2 members' Panel ) : ( 1 hr 15 minutes ) 1).Greetings (both were very cool and funny). 2).Tell me about yourself and about your technical background. 3).What is the first coding problem asked in round 1 ? I had used while loop to solve the problem. He further asked to solve the same using recursion. I solved it using static variable that stores the count. He asked why static variable. Basically I did it for avoiding revert recursive back calls from stack (tail recursion). Can you do it without using static variable? I did it. 4).Given an array A and number K. Find number of distinct pairs of elements ( A,B ) in which A-B=K. First applied brute force logic O( n2 ). He further asked to optimize the code. Used logic of sorting and binary search (i.e for every A we need to search B=(A-K) from remaining array) O( nlogn ). 5).Project discussion (last for 15-20 minutes). 6).What is Jason? Write an empty jason for any object. Then he asked to write jason for Employee object. 7).What was your role in Project? 8).My project was in Python. He asked the difference between C++ and Python. Why not C++ to do the same project. Why machine learning why not other technologies? And many questions like that. 9).They checked my hackerrank profile. I had commented on SQL question on hackerrank. They asked questions regarding that. 10).Given an Employee table having employee ID,employee name and Gender. Database has wrong data having all males marked as female and all females marked as males. Write an SQL query to correct the database. --Used CASE in SQL to update the database as per their expectation. :) 11).Discussion regarding work in the company. I was told to wait for some time. Further they conveyed that results will be declared within two days. Finally 3 candidates got selected for the internship and I was one of them :) Suggestion : Be precise. Only tell whatever you know.Know yourself before the interview. Be calm & answer politely. All the best!
Topics
More from Tomtom
Related companies
Tomtom Interview Process Overview
The Tomtom interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Tomtom runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Tomtom coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Tomtom Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Tomtom updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Tomtom reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Tomtom's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Tomtom Interview Mistakes
Reports tagged "no hire" at Tomtom consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.