Mobile Engineer

Senior Mobile Engineer — Swift & Kotlin

EV charging | Arnhem | Hybrid

Four per cent battery. Rain coming in sideways. You’ve found a charger, and all you want to know is whether it’s available, what it costs and if your session has actually started.

At that point, the app matters quite a lot.

I’m helping a growing EV charging software business in Arnhem find a Mobile Engineer. Its product brings public and home charging into the same experience, with live sessions, smart charging and rewards in the mix. Behind that screen sit charging networks, cars, tariffs, energy data and plenty of things a driver should never have to think about.

That’s what makes this an interesting mobile problem.

It began with three founders who knew the energy and mobility world and wanted to make charging cheaper, cleaner and less of a faff. A few years on, the platform supports mobility businesses across Europe. That’s exciting growth, but it also means the engineering approach that worked when they were small has to keep evolving.

The mobile brief is part of that next step. The important technologies are Swift for iOS and Kotlin for Android . They want someone who has genuinely built with both. React Native experience is useful alongside that native work.

Do you need to be equally strong in both?

No. If Swift is where you’ve spent most of your time and you’ve shipped meaningful Android work in Kotlin, let’s talk. Same the other way around. I don’t expect your career to divide itself neatly into two columns.

I do want to hear what you’ve built, where you made the technical calls, what happened when it reached users and which platform you would back yourself on tomorrow.

The tool list is deliberately short. Show me real Swift and Kotlin work and tell me where React Native fits, if it does. An impressive list of frameworks won’t tell me as much as a mobile product you’ve actually shipped.

Why take a look?

Because mobile is right at the point where this business meets its users. A clear price, a charging point you can find, a session you can follow and a better way to charge at home all sound simple from the driver’s side. Making a complicated system feel that way is the interesting part.

It’s also a useful moment to join. The company is scaling and becoming more deliberate about the mobile expertise it needs. There is room to learn and contribute as that takes shape.

I’ll be straight about the growing pains too. Priorities can move, and I won’t pretend every detail of the next 12 months has already been mapped out.

Based in Arnhem, with hybrid working. We’ll cover the package and practicalities early.

If you’ve worked with both Swift and Kotlin .

Tell me which one is your stronger suit, what you’ve built with the other, and what would make your next move worthwhile. I’ll give you the full picture.