> Markdown version of [/jobs/ext/3877202-technical-solutions-engineer-connected-vehicle-integrations-eevee-mobility](https://www.wearedevelopers.com/jobs/ext/3877202-technical-solutions-engineer-connected-vehicle-integrations-eevee-mobility). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Solutions Engineer - Connected Vehicle Integrations - EEVEE Mobility

- **Company:** Wisemen
- **Location:** Diepenbeek, Belgium
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Databases, Laravel, PostgreSQL, MySQL, Node.Js, Systems Integration, TypeScript, Tailwind, ReactJS, Backend, Vue.js, Webpack, Front End Software Development
- **Published:** October 23, 2026
- **Apply:** https://www.adzuna.be/details/5938982446

## About the Role

4-6 years of full-stack experience, owning features from database to interface.

Frontend: TypeScript, React, Vue.js, Vite, Tailwind CSS. Backend: PHP Laravel, Node.js, MySQL, PostgreSQL. Being strong on both sides matters more than ticking every item.

Able to design as well as build: you turn a vague partner capability into an interface specification, and explain it to engineers and non-engineers alike.

Experience with third-party APIs you do not control: authentication, rate limits, breaking changes, thin documentation and silent failures, plus the instinct to chase why a number is wrong, not only that it is.

At ease with an operational load and with setting your own priorities: part of your week is support and incidents, and you treat that as roadmap input.

Clear communicator in English, in writing and in a technical review with a manufacturer's team. Dutch is a plus.

Affinity with EV, energy or mobility technology is a plus, not a requirement. Curiosity is.

Ready to join us?

## Description

* Run the technical discovery with our OEM partners: establish what a brand can expose, translate it into what fleets need, and design the integration before it is built.
 * Set the architecture of the OEM layer with our CTO and senior engineers, so that each new integration lands inside it rather than beside it, and shape the products we build on top of it.
 * Build and extend the integrations themselves: onboard new brands, deepen existing connections, and turn repeated patterns into reusable building blocks instead of per-brand exceptions.
 * Own the quality of the data that comes in: the monitoring, alerting and diagnosis that finds a broken or drifting signal before a customer does.
 * Act as the technical escalation point for OEM issues raised by Support and Operations, remove the cause rather than the symptom, and build the internal tooling that lets both teams see the state of an integration at a glance.
 * Partner with your OEM counterparts: specify what we need, test what they ship, report defects with evidence, and keep the relationship concrete.
 * Help shape the next generation of OEM integration products: what we can offer fleets once the connection reaches further than the charging session.