Software Engineer - Platform

📋 Description

• • Own the heart of Enode’s connectivity layer. As a Mid-Level Backend Engineer on the EVC Platform team you will design, build and harden the API integrations that link 250 million end-users to their electric vehicles, chargers and OEM back-ends. Every line of code you ship directly determines whether a driver can start a smart-charging session that favours renewable energy or whether a utility can balance the grid at peak times.
• • Extend and stabilise our fleet of 30+ live integrations. You will write TypeScript services that speak OAuth 2, REST, GraphQL and proprietary binary protocols to car manufacturers, charge-point operators and energy retailers. You will add new endpoints, normalise inconsistent data models and wrap flaky third-party APIs in resilient adapters that never drop a kilowatt-hour of flexibility.
• • Turn firefighting into foresight. You will instrument our connectivity layer with metrics, traces and structured logs that expose latency, error budgets and SLA adherence in real time. When an OEM pushes a breaking change at 2 a.m., your runbooks, circuit breakers and automated canary tests will page the right person with the right context and a one-click rollback.
• • Automate the toil away. You will build internal CLI tools and self-service dashboards that let any engineer open a sandbox vehicle, replay yesterday’s traffic and ship a regression test in minutes instead of hours. Your scripts will generate mock chargers, simulate grid events and keep our test coverage above 90 % without human intervention.
• • Champion reliability as a product feature. You will collaborate with product managers to define SLAs (e.g., 99.9 % successful session initiation within 500 ms) and with customer success to translate user pain into backlog priorities. You will run post-mortems that end in concrete tickets, not slide decks.
• • Shape the architecture for the next 10× scale. As we onboard new OEMs across three continents you will refactor synchronous flows into async queues, partition data by region and introduce idempotent retry patterns that survive regional outages. You will debate trade-offs in weekly architecture guilds and leave a trail of ADRs (Architecture Decision Records) for future teammates.
• • Grow a culture of craft. You will review pull requests with empathy, pair program with juniors and run internal tech talks on topics like “Type-Safe API Contracts” or “Observability for Polyglot Integrations.” Your documentation will be so good that onboarding a new hire takes hours, not days.
• • Work remotely across Europe while staying tightly knit. You will join daily stand-ups, weekly demos and quarterly off-sites in places like Lisbon or the Lofoten Islands. You will share memes, celebrate releases and occasionally debate whether heat pumps or EVs will save more CO₂ this decade (spoiler: both).
• • See the real-world impact of your code. When a utility uses our load-shifting API to cut peak demand by 15 %, you will watch the carbon intensity of the grid drop in real time. When a driver wakes up to a fully charged car and a lower electricity bill, you will know your retry logic made it happen.