Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

TomTom

Makes digital maps, navigation software and traffic data used in cars, apps and developer location APIs.

Not known6 stage process documentedFounded 1991
Headquarters

Amsterdam, Netherlands

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

Ask for a referral to TomTom

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

This is TomTom’s general hiring process. The online coding task is only used for some roles.

  1. 1

    Application review

    Official
    Application screen

    Your application is checked against the requirements of the role.

  2. 2

    Recruiter call

    Official
    Recruiter screen

    A conversation about your experience, what motivates you and what you expect from the role.

  3. 3

    Online coding task (some roles)

    Official
    Online test

    A short online coding exercise that shows how you approach and solve problems. Whether it is included depends on the role.

    codingproblem solving
  4. 4

    Technical interview, about 60 minutes

    Official
    Technical interview1 hours

    A one to one session with an engineer or the hiring manager on your technical skills, how you structure code and how you handle realistic scenarios.

  5. 5

    Interview loop

    Official
    Panel interview

    Three or four interviews, each with a different person, covering system design, leadership behaviours and fit for the role.

    system designleadershiprole fit
  6. 6

    Decision and offer

    Official
    Offer

    TomTom shares the outcome and, if successful, moves on to the offer and onboarding.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Coding and code structure

    Official

    The coding task and technical interview look at how you solve problems and organise your code.

  • System design

    Official

    System design is one of the areas covered in the interview loop.

  • Leadership Foundation

    Official

    Interviewers look for the behaviours, principles and values set out in TomTom’s Leadership Foundation.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Course
Grokking Data Structures & Algorithms for Coding Interviews

A foundations course that builds eleven core data structures from the ground up (arrays, matrices, stacks, queues, linked lists, trees and BSTs, hash tables, hash sets, heaps, graphs and tries), then covers sorting, searching, greedy and divide and conquer. Every chapter has practice problems, flashcards and an assessment. It suits students and career switchers whose foundations came from tutorials and who find pattern courses move too fast.

  • Job search
  • DSA
  • CS fundamentals
Design Gurus · Interview Prep · 4 to 6 weeks · Beginner
SubscriptionDetails
Platform
Design Gurus Problem Set

A browsable practice library of coding problems that can be filtered by pattern, data structure, difficulty and company, so you can drill exactly the weakness you found this week. Patterns include two pointers, sliding window, hash maps, stacks, backtracking and greedy algorithms, with company filters for Google, Meta, Microsoft, Amazon, Oracle and LinkedIn. Free to browse, with an in-browser editor and solutions.

  • Job search
  • DSA
Design Gurus · Interview Prep · Ongoing
Guide
Design Gurus Newsletter

A free newsletter of short, focused posts on system design and problem solving, from the team behind the Grokking courses. Recent posts cover company interview processes (such as OpenAI and Anthropic roles), the most asked mobile system design questions and preparation plans, each linking to a fuller article on the blog. It suits engineers who want a steady, low-effort way to keep system design and interview topics fresh between deeper study sessions.

  • System design
  • DSA
Design Gurus · System Design
GitHub repo
Grokking System Design

The free, open companion to the Grokking the System Design Interview course, published as a GitHub repository. It teaches a pattern-first approach: learn building blocks such as caching, sharding, replication and queues well enough that any design question becomes a matter of combining them. It includes a seven-step interview framework, 30 patterns, 59 question walkthroughs, company guides, cheat sheets and study roadmaps, all readable in the browser without an account.

  • System design
  • Job search
Design Gurus · System Design · Intermediate
Community
ICPC (International Collegiate Programming Contest)

The official site of the ICPC, the university programming contest where teams of three share one computer for five hours and advance from regional contests towards the World Finals. It is where coaches register teams, where the current regional and World Finals rules are published, and where you find contests, results and past problems.

  • DSA
  • CS fundamentals
ICPC Foundation · Other · A season of qualifying contests each academic year
Video
Abdul Bari (YouTube channel)

Abdul Bari's channel is a classic university-style course on the design and analysis of algorithms, taught on a whiteboard in clear English. It covers complexity, divide and conquer, greedy methods, dynamic programming, backtracking, branch and bound, NP-hard problems and string matching, plus Java programming. It suits computer science students studying algorithms as a subject.

  • DSA
  • CS fundamentals
  • Programming
Abdul Bari · Other · Self-paced · Intermediate
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the TomTom page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the TomTom page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Read TomTom’s Leadership Foundation before interviewing, since the loop tests those behaviours. Be ready to explain why TomTom’s mission matters to you on the recruiter call.

Sources

Whole profile last checked 2026-09-22.

Interviewed at TomTom? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to TomTom

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the TomTom page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.