Senior Platform Engineer

Reports to: CTO Works closely with: backend and data engineers, security, customer support, and the on-call rotation. The shift we are building for Four things are happening in EV charging operations that change what a platform team has to do, and they are all landing on us at the same time. EV charging is becoming infrastructure. The chargers our customers run are no longer pilots. A fleet manager needs them to work at 06:00 on a Tuesday and a parking operator’s customers expect them to work at 23:00 on a Saturday. Uptime is a product feature, not a devops detail. The volume curve is steep. Sessions, sites, and integrations are growing faster than headcount. We get one chance to put the platform on rails that scale before the operational load eats the engineering team’s calendar. Customers buy on integration. Energy retailers, fuel retailers, parking operators, and grocery chains expect APIs that plug into the systems they already run, plus stack-level evidence (ISO 27001, audit trails, observable SLAs) that lets their security teams sign off in a quarter, not a year. AI changed how engineering teams ship. We write code with AI by default. The result is more code, faster, in fewer hands. The platform discipline that catches a bad change before it wakes someone up matters more now, not less. About eMabler eMabler is the EV charging software company behind an open platform used by energy companies, retailers, and parking operators across Europe. Our customers add EV charging to a service they already run: energy retail, fuel retail, grocery, parking. They use our APIs to launch a charging service in weeks as an integrated part of the user experience they offer. We just closed our Series A and are scaling our product, engineering, and data teams. Where the platform is today We run on Azure. App Service is the primary runtime. Azure Data Explorer (ADX) is where the operational data sits, and we use Microsoft Fabric in places. There is no infrastructure-as-code yet. That has been a deliberate trade-off for speed; it stops being a trade-off and starts being a tax soon. We are ISO 27001-certified. Pen-tests and audits are part of the calendar. Compliance is real work here, not a checkbox. Why this role exists The platform has grown faster than the discipline around it. We need a senior platform person who fixes that without turning the team into a Terraform pull-request queue. Someone who decides what to codify first, what to leave alone, and what to migrate. Someone who treats reliability and security as engineering work, not paperwork. We write code with AI by default. We still hire seniors because picking the right shape, scoping the blast radius, and rejecting the wrong output is the work that decides whether what we ship runs at scale. Product management without senior engineering judgment is not how we run. What you will own Build infrastructure-as-code from zero. Pick the tooling (Bicep, OpenTofu, or Pulumi; defend your choice), codify what we run today (App Service, Container Apps, networking, Key Vault, Service Bus, ADX, identity, storage), and put the result behind a deployment pipeline the team uses without thinking about it. Run production reliability. SLOs, observability, alerting, on-call rotation, incident response, and post-incident change. You read postmortems and modify the system so the same thing does not happen twice. Be the technical owner of security and compliance. Identity, secrets, network segmentation, supply chain, secure SDLC, and the engineering response to penetration tests and ISO 27001 audits. You decide what is a real requirement and what is theatre. Ship product code when it matters. About 70% platform, 30% product. Our code is .NET and C#. When the team needs another pair of hands on a service, you are in. Own cost engineering. Azure spend is real money. Watch it, cut where you can without breaking anything, and make sure new services have a sensible cost shape from day one. Who you are Five to eight years in cloud platform, DevOps, SRE, or platform engineering roles, including at least three years on Azure in production. You have stood up infrastructure-as-code from scratch in a small or mid-sized engineering org, and you know how to do it without overshooting (no service mesh on day one for a small team). Strong with Azure: App Service, Container Apps, Service Bus or Event Hubs, Key Vault, networking, identity. Comfortable making the call between PaaS and containers based on what the workload actually needs. Working knowledge of .NET and C# and willingness to ship in it. Knowledge of another production language (Python, Go, TypeScript) is welcome. We will not assess you like a backend hire, but if you only ever write YAML this is not the role. Practical security knowledge: identity, secrets, network segmentation, supply chain, secure SDLC, response to external pen-tests and audits. You can explain why a finding is a finding and how you would fix it. You use AI as a default, not a side experiment. Experience with Cursor, Claude Code, Copilot, or similar helps; judgment matters more. You look for where AI multiplies what one person can deliver, and you raise the bar on review and blast radius to match. Working English required. Helsinki HQ preferred, regular on-site presence expected. Bonus, not required EV charging or energy domain: OCPP, OCPI, MQTT or telemetry pipelines at fleet scale, hands-on with ADX (KQL). Multi-cloud awareness. We are Azure today; thinking that does not collapse the moment a customer or partner asks about AWS is welcome. Hands-on with ISO 27001 audits as the technical lead, not the spectator. You have run an incident as the technical IC and written the postmortem yourself. You have cut a five-figure monthly Azure bill without breaking anything.