> Markdown version of [/jobs/ext/4807973-new-platform-operations-engineer-emobility-saas](https://www.wearedevelopers.com/jobs/ext/4807973-new-platform-operations-engineer-emobility-saas). 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). --- # NEW Platform Operations Engineer - eMobility (SaaS) - **Company:** Deftpower - **Location:** Arnhem, Netherlands (Remote available) - **Experience:** Expert - **Salary:** €6,240 - €6,933 - **Contract:** Permanent contract - **Skills:** .NET Framework, Application Programming Interfaces (APIs), Artificial Intelligence, Microsoft Azure, Software as a Service, JSON, Nagios, SQL Databases, Claude, Zendesk - **Published:** November 21, 2026 - **Apply:** https://www.adzuna.nl/details/5973143511 ## About the Role * You have 5+ years of experience in operations, SRE or application support on a SaaS platform, including leading major incidents, although attitude counts more than years * You think from the client's side. Under pressure, you keep clients informed with updates they understand, and you know when a call beats another email. * You take initiative beyond your own queue. You spot patterns in the tickets and fix the process, not just the ticket. * You turn technical findings into clear choices for development leads, account managers and clients, and you help colleagues get better at incidents. * You work in English every day. Dutch is nice to have. Must-have: incident management and root cause analysis, SQL, reading logs and API traffic (REST, JSON), monitoring and alerting tools, and building automations with AI tools such as Claude. Nice to have: C# and .NET, Azure, Better Stack, Freshdesk, Linear, and EV charging protocols (OCPP, OCPI). ## Description The team. Operations keeps Deftpower running for the brands we power. When a driver can't start a session or a charge card is refused, the client's ticket lands with us, and we make sure drivers keep charging. You report to Ernst-Jan Slot, Head of Operations. Why now. Every new brand brings more drivers, sessions and tickets. Operations has to scale without the ticket queue scaling with it: fewer repeat tickets, earlier alerts and more automation, with AI wherever it helps. That needs someone who looks beyond the next ticket. What you do. Keeping clients up and running is the core of this role, on two levels. Per incident, you lead: when charging stops for a large group of drivers, you coordinate the response and make sure the cause is fixed, not just the symptom. Across the platform, you decide where operations gets stronger: what we should detect earlier, which processes break as we scale, and which work we stop doing by hand. You own both. * Lead major incidents from first alert to root cause analysis, working with development leads, third parties such as roaming hubs, and the client * Own our monitoring: decide what we alert on, build the SQL alert rules and Better Stack checks, and watch new releases once they're live * Redesign processes that won't hold at scale, and flag scalability risks to development leads before they reach clients * Drive AI automation across operations: build Claude skills and scripts for ticket triage and recurring requests, and help colleagues use them