Platform Engineer (m/f/d)

ecoplanet builds the operating system for the energy transition. Our software helps European businesses cut energy costs, run more efficiently, and take the pain out of managing energy day to day. We are around 40 people and backed by EQT Ventures, HV Capital and others. You build and run the platform the whole product sits on: the event streams, the backend services and the cloud infrastructure everything else is built on. Meter readings arrive from industrial sites across Europe, through messages or us accessing APIs. Your job is to make sure that traffic lands reliably, moves through the system in a shape other teams can build on, and keeps doing so as the number of sites grows.
You join a team of 12 engineers in two squads. Small team, real ownership, and what you build reaches customers in weeks rather than quarters.

What you will work on

• Event streaming. Kafka is the spine of the system. You own topic and schema design, partitioning, retention and delivery semantics and the everyday reality behind them: consumers falling behind, replays, backfills, late and duplicated readings.
• Backend services in TypeScript. The ingestion services, integrations and APIs around that stream. Every site is a little different, so a good part of the job is turning that variety into one consistent interface the product squads can rely on.
• Cloud infrastructure on GCP. Compute, networking, IAM, infrastructure as code, CI/CD and observability. The goal is a paved road: other engineers ship and debug their own services without going through you.
• Technical direction. You are senior enough to set it. Where we invest in the platform, what we standardise, what we deliberately leave rough for now and bringing the rest of the team along with it.

Must have:

• At least 6–8 years building and running backend systems in production, including real time in a platform or infrastructure role that other engineers depended on
• Strong backend engineering in TypeScript. You have designed, shipped and operated services and APIs in it — not just touched it around the edges of a frontend
• Hands-on with Kafka in production. Topic design, consumer groups, ordering and delivery guarantees, and what you actually do at 3am when a consumer group is hours behind. A comparable streaming platform is fine if you know it at that depth
• Solid on GCP or an equivalent cloud: containers, networking and IAM basics, infrastructure as code, CI/CD, monitoring and alerting. You have owned infrastructure, not just deployed onto it
• Comfortable with high-volume time-series data: ingestion, data quality, backfills, and the everyday reality of late, missing and duplicated readings
• You have seen a few things. Enough production years behind you to know which trade-offs come back to bite, when the boring option is the right one, and how to make a call with incomplete information instead of waiting for certainty
• Kubernetes knowledge at the level of running it, not only deploying to it.
• Clear written and spoken English. German is a plus

Nice to have:

• Energy, industrial, IoT or another domain where the data comes off real hardware
• Metering or device protocols, telemetry at scale, or streaming pipelines
• Knowledge of a second programming language, like Python, Go or Kotlin
• You run what you build: monitoring, alerting, and the occasional early morning debugging a pipeline

• Top-of-market team, flat hierarchy — work alongside people who push you to get better
• Competitive salary
• Full ownership from day one — you actively shape our company
• Central office, easy commute — free lunch every Tuesday and Thursday
• Wellpass membership
• Regular 1:1s and retros focused on your growth
• Real impact — your work supports Europe's transition to a smarter energy system