Senior Cloud Engineer; d​/f​/m

Short Facts

flexa runs a virtual power plant. We control the home batteries, heat pumps and EVs across the Enpal customer fleet and trade their flexibility on European energy markets in real time. Every dispatch decision is money - for the customer and for us - and it has to land within seconds, on hardware we don't own, under regulation that is paying attention.

You would own the AWS platform underneath that.

• Location: Munich, Germany, Office-first work setup
• Employment Type: Full-Time, indefinite term
• Salary Range:€ 95. per year gross depending on the seniority level
• Language Requirement: C1 Level English

• Own the AWS platform. Architecture and evolution of the AWS-native platform that ingests asset telemetry, runs our dispatch and optimisation workloads, and serves the customer-facing applications. You set the direction, and you build.
• Make shipping boring. Infrastructure-as-Code, CI/CD, environments and guardrails good enough that engineers deploy without asking you first.
• Reliability where it counts. SLOs, observability and incident practice for systems where minutes of downtime are lost revenue and missed market commitments.
• Security and compliance as design constraints. We touch critical energy infrastructure. IAM, secrets, network boundaries and audit trails get designed in, not retrofitted before an audit.
• Raise the bar around you. Standards, reviews and mentoring across the tech team — at the Staff end of this role, that's a large part of the job.

What we need

• 5+ years building and operating production infrastructure, at least 4 of them deep in AWS
  -and you've been on call for what you built.
• Real Infrastructure-as-Code ownership (Terraform, Pulumi or CDK), including the unglamorous parts: state, module design, drift, provider upgrades.
• Strong judgement about AWS services - Lambda, ECS/EKS, API Gateway, DynamoDB, IAM
  -including when the right answer is a plain EC2 instance or RDS rather than something clever.
• You've run AWS at the account level, not just the resource level
  -multi-account setups with Control Tower or Organizations, SCPs, centralised logging, and the boring discipline of keeping new accounts consistent with the ones that came before.
• Security is part of how you build, not a review gate at the end: least-privilege IAM you actually enforce, findings from Security Hub / Guard Duty / Git Hub Advanced Security triaged rather than accumulated, secrets and supply chain handled properly. Bonus if you've worked under a formal regime (ISO 27001, KRITIS or similar).
• You write code, not just config. Python or Go to a standard where other engineers want to use your tooling.
• Containers and CI/CD in production, including rollbacks and how they fail.
• You've run monitoring and alerting that people actually trust (Data Dog, Grafana, Prometheus or equivalent) and can tell a useful alert from noise.

• Energy, grid, trading, or any domain where being late costs money.
• Time-series data at scale.
• Fleets of devices you don't physically control
  -IoT, edge, intermittent connectivity.
• Streaming and data platforms (Kafka, Kinesis, Flink).
• Working in an audited or regulated environment.

• You want to join a finished platform. Parts of this are greenfield, parts need replacing, and you'll have real influence over which is which - but nothing is handed to you tidy.
• On-call is not a formality here. These systems move money, and you'd share the rotation.
• Compliance is genuine engineering work in this role, not a checkbox someone else ticks.
• The team is small enough that you own your own operations, which some weeks means unglamorous work.
• You need remote or hybrid-heavy. This is an office-first role in Munich.

At flexa, we are committed…