TomTom Cut 200. Only 16 Dutch Profiles Even List OpenStreetMap

TomTom cut about 200 people on October 15, 2026, and its shares fell more than 5% when a revenue miss outweighed a better margin forecast. If you recruit for AV, logistics, drone or defense companies, this is the one October layoff that isn't generalist. It's a small pool of routing, map-matching and geospatial specialists. The catch is that most of them show up on LinkedIn as "Software Engineer," so you have to find them where their work is public.

What did TomTom cut in October 2026?

TomTom is cutting about 200 roles, roughly 6% of its ~3,300 staff, by year-end. At the same time it is reorganising into three divisions: Automated Driving, Location Intelligence and Navigation. The cut came alongside a revenue miss: Automotive operational revenue fell 19% to €68M against a €77M consensus.

The rest of the picture:

• 2026 revenue guidance narrowed to €505 to 530M.
• Margin guidance rose from 3% to about 4%, partly because of "lower expected salary costs" from the reorg.
• A €15M restructuring charge lands in Q4, with €21M in targeted annual savings.
• This is the second round. TomTom cut 300 jobs in 2025 in an AI realignment.
• Headcount peaked above 4,500 in 2019.

Compare that with the rest of October. HubSpot cut about 660 (7%), Netflix about 1,000 (6%), and Airtable an unspecified "large part" of the company. Those pools are big and full of generalists. TomTom's is small and specialised, and very few employers outside mapping produce the same skills.

How many of the 200 are actually engineers?

Nobody outside TomTom knows. The company's only public detail was "fewer management layers." Any count of engineers is a guess, so plan your search around that uncertainty.

The reports conflict. Policy Wire says the cuts hit route planner development, sales and customer service. NL Times says TomTom didn't specify. Policy Wire's list closely matches the areas hit in the 2025 round, so treat it as unconfirmed. If route planner development really is in scope, that's the best news an AV or logistics recruiter could get. If it isn't, the people you want are still worth approaching. A company that has shrunk about 27% from its peak and restructured twice in two years is a company where good engineers start taking calls.

The savings math points senior

Divide €21M in annual savings by 200 roles and you get about €105k fully loaded per role. An average that high is much easier to reach when managers and senior leads are in the mix than when the cut is mostly customer service. Add the stated goal of removing management layers, and the fact that folding everything into three divisions creates overlapping management. The cut probably reaches higher up than the headlines suggest.

€105k

For AV and defense buyers, that's often the exact hire: an engineering manager who has shipped navigation software to automotive customers.

Why can't LinkedIn search find TomTom's routing engineers?

They don't describe themselves in the words recruiters search for. In Refolk's index of professional profiles, only 16 people in the entire Netherlands list OpenStreetMap as a skill, and TomTom isn't among their top 10 employers.

Look at who does list it. The top employers are municipalities, Rijksoverheid, ALTEN and VU Amsterdam, and the titles are things like "Software Developer" and "GIS Technisch beheerder." These are GIS administrators and consultants next to the field, not the core routing people at the country's best-known mapping company.

16

A second query makes the same point more sharply. A headline search for "routing map matching geospatial navigation" in Refolk's index returned 0 profiles in the Netherlands and 0 in Germany. All four terms had to match, so this doesn't count how many such engineers exist. It shows that nobody writes their headline that way.

The reason is simple. Inside a mapping company the domain goes without saying. Everyone around you works on maps, so nobody lists "maps" as a skill, just as nobody at a bank lists "money." Titles follow the internal ladder, not the problem the person solves. Keyword search on titles and skills will mostly turn up the adjacent GIS crowd.

The evidence is in changesets, commit logs and patent filings, not in anyone's LinkedIn headline.

Are you hiring map-data operators or routing engineers?

These are two different pools, and you need to know which one you want before you search. Map-data operations staff are the visible ones on OpenStreetMap. Routing and map-matching engineers mostly work on TomTom's internal stack and often have no public commits.

Two definitions help here:

• A routing engine computes the best path across a road graph under constraints like turn restrictions, tolls and vehicle profile.
• Map matching snaps noisy GPS traces to the right road segments, which is the core of any fleet, AV or telematics product.

Recruiters often get this wrong. The OSM accounts are the easy trail, so they end up with a shortlist full of data-quality editors when the req calls for a C++ routing engineer. Both are good hires, but for different jobs.

How do you find TomTom's mapping team in OpenStreetMap records?

Start with OSM's organised-editing records. Organised editing is any coordinated mapping effort by a company or group, and the community's best practices ask those teams to list their accounts and declare their employer on mapper profiles. In effect, that's a semi-public roster.

A workable sequence:

1. Open the TomTom page on the OSM wiki. It documents organised editing since 2021 and data-improvement projects across more than 200 countries.
2. Read the individual activity pages. The Global Building Height Imports page, for example, names Salim Baidoun as project lead. Pages like this tie real names to specific projects.
3. Trace the bot. TomTom's automated edits run from the account TTmechanicalupdates. The bot isn't a candidate, but the people who document it and answer community questions about it are.
4. Check mapper profiles for declared employers. The public profile MG_TT describes its owner as a TomTom team leader. Don't assume the "_TT" suffix is a company-wide naming convention until you've checked several accounts.
5. Cross-reference GitHub. Look at who contributes to the tomtom-international/open-data repo and compare those accounts with the OSM handles you've collected.
6. Resolve handles to people. An OSM username is a string, not a person. Match it to a GitHub account, then to a LinkedIn profile, before you count it.

Step six is where most searches stall. You end up with a pile of browser tabs and a spreadsheet of usernames you can't link to anyone. Refolk closes exactly that gap: you describe the person in plain English and get back a ranked shortlist that links each person across GitHub, LinkedIn and the open web.

Which routing-engine repos should you search?

Search three: OSRM, GraphHopper and Valhalla, the main open-source routing engines by GitHub stars as of April 2026. GraphHopper is the closest public match for map-matching talent, because map matching ships in its main repo.

• OSRM: 7,665 stars
• GraphHopper: 6,416 stars, with map matching bundled in
• Valhalla: 5,647 stars, with a Google Summer of Code project in 2026

Beyond the core repos, look at HeiGIT at Heidelberg University, which maintains openrouteservice on top of GraphHopper. Its contributor graph is a good place to find routing people in Germany.

The history explains why speed matters. Mapbox hired OSRM's lead developer, Dennis Luxen, then most of Mapzen's Valhalla engineers, and stopped maintaining OSRM in 2019. These contributor groups are so small that one employer can absorb a whole team. If an ex-TomTom engineer starts sending patches to Valhalla, every routing team in the industry can see it too.

When you screen these repos, look past the star count and read the PRs. A merged change to contraction hierarchies or turn-cost handling tells you more than any job title. Someone who only fixed docs is a different hire from someone who reworked the graph builder.

How do you find engineers who have no public commits?

Use patents and conference talks. Routing and map-matching engineers who spent years on TomTom's internal stack may never have pushed a public line of code, but their names can show up as inventors and speakers.

Practical steps:

• Google Patents: search with TomTom as assignee and terms like route planning or map matching, then collect the inventor names. The research behind this article didn't verify specific TomTom patents, so check every name yourself.
• Public interviews: Willem Strijbosch (VP of Product, Maps and Search) and Mike Harrell (SVP of Engineering, Maps) have both spoken publicly about Overture. Interviews and talks like theirs name the teams and projects underneath them.
• Overture context: TomTom's Orbis Maps uses the Overture schema (Overture was co-founded by Amazon, Meta, Microsoft and TomTom) and uses OSM selectively. An engineer with Orbis experience knows an open map schema that three of the largest tech companies also back, so expect competition.

A patent gives you a name and a date but not a current employer. Turning a list of inventor names into current profiles is the same handle-to-person problem as step six above, and Refolk handles it the same way: paste the names in instead of checking them one at a time.

How should you approach them without burning the OSM community?

Don't use OSM's messaging system for cold outreach. The community has recently pushed back on TomTom's own mass edits, including the undiscussed removal of toll booths, and recruiters who spam mappers will get the same reaction.

What works better:

• Meet them in person. TomTom's OSM team said it planned to attend State of the Map in Paris. That's a far better way in than a cold OSM message.
• Reach out through professional channels. Use LinkedIn or a work email once you've resolved the handle to a real person.
• Cite the work. Mention a specific changeset project, PR or patent. "I saw your work on the building-heights import" gets a reply. "Exciting opportunity in geospatial" doesn't.
• Lead with the problem. Drone path planning under airspace rules or last-mile routing at fleet scale is more interesting to these engineers than a company pitch.
• Don't assume they were cut. About 94% of TomTom staff stay. Frame the message as an opportunity, not as sympathy.

Timing matters too. The cuts are due by year-end and the restructuring charge lands in Q4, so the coming weeks are when people learn their status and start deciding. Engineers who have lived through two rounds in two years are more open to a call than the headcount figure suggests.

FAQ

Did TomTom's 2026 layoffs hit engineering?

TomTom hasn't said. Its only public detail was fewer management layers. Policy Wire reported cuts in route planner development, sales and customer service, but that list closely matches the 2025 round and is unconfirmed. The roughly €105k in savings per role suggests managers and senior staff are included.

Why not just search LinkedIn for TomTom software engineers?

You'll get a long list of identical "Software Engineer" titles with no way to tell a routing specialist from a web developer. In Refolk's index, only 16 Netherlands profiles list OpenStreetMap as a skill, and a four-term routing headline search returned zero in both the Netherlands and Germany. The domain signal lives in OSM records, repos and patents.

Is it acceptable to contact OpenStreetMap mappers about jobs?

Not through OSM messages. The community is already sensitive about corporate behaviour after the TomTom toll-booth dispute. Resolve the handle to a real person, contact them through LinkedIn or email, and cite their specific work. Conferences like State of the Map are a better in-person route.

Which companies are best placed to hire this pool?

AV teams need map matching. Logistics companies need routing at fleet scale. Drone makers need path planning, and defense contractors need geospatial data skills. Engineers with Overture and Orbis experience will also interest the other Overture co-founders, Amazon, Meta and Microsoft, so smaller buyers should move first.