Software Engineer - Customer Engineering
What you'll do
-
Integrate our stack into theirs. You get TomTom navigation and ADAS products running inside customer applications and vehicles. That means understanding their architectures, and making our software fit a system we did not design.
-
Co-develop and co-solve. You sit with customer engineers on problems neither side can crack alone: performance on their silicon, behaviour their use case demands, the gap between what our product does today and what their vehicle needs next quarter. You prototype, measure and iterate in the open with them.
-
Support what ships. You own second line product support and, as you build depth. Reproduce it, diagnose it, fix it where you can, and route it with a clear technical story attached to the product organization when you can't.
-
Close the loop with Europe. You are the shortest path between a customer's reality and our roadmap. You turn what you see in the field into input our product and engineering teams can act on: reproducible bugs, requirements grounded in evidence, and the patterns worth building into the product for everyone.
-
Work where the customer is. Depending on the customers, expect real time on customer sites, in their labs and in their vehicles.
What you'll need
-
Strong software engineering, and the instinct to debug systems you did not build. C++ or Kotlin is essential.
-
Real depth in at least two of: embedded development, Android applications, Android framework or AOSP, connected and cloud services, automotive platforms.
-
Fluent Chinese and English, spoken and written. You will translate between a customer in China and a product team in Europe, in both directions.
-
Writing that gets to the point. Dense, clear and logical: the kind of issue report or design note someone can act on without a follow-up call.
-
The confidence to be the TomTom expert in the room. Technical credibility backed by experience, delivered with patience and empathy.
-
Accountability for your own delivery, and for using the team's processes, policies and governance the way they were meant to be used.
What's nice to have
-
Automotive experience: QNX, Automotive SPICE, functional safety, Android, or an OEM release cycle you have participated in.
-
Navigation or ADAS domain knowledge: routing, positioning, map data formats, autonomous driving.
-
Performance profiling and optimisation on constrained hardware.
-
Time spent as a forward deployed, solutions or customer engineer, 'or in any role where your product was integrated by another company into their product.
