Senior Cloud Engineer (d/f/m)

Flexa; München; Vor Ort; EUR 95.000 - 115.000; Vollzeit

Benefits dieser Stelle

Competitive compensation package

Development budget €3,000 yearly

Health & sport subsidy

Public transportation subsidy

Lunch/dinner vouchers

Work equipment (MacBook or Windows)

Team events

Zusammenfassung

Flexa is seeking a senior infrastructure engineer to own and evolve our AWS-based platform that ingests telemetry, runs dispatch and optimization workloads, and serves customer-facing apps. You will set direction and build.

This role emphasizes IaC, CI/CD, reliability, security, and mentoring. You will lead multi-account setups, implement guardrails, design least-privilege IAM, and drive on-call reliability in a fast-paced energy tech environment in Munich.

Qualifikationen

• 5+ years building and operating production infrastructure, at least 4 of them deep in AWS and on-call.
• Real Infrastructure-as-Code ownership (Terraform, Pulumi or CDK), including 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.
• Account-level AWS management with multi-account setups, Control Tower/Organizations, SCPs, centralised logging
• Security is design constraint: least-privilege IAM, Security Hub/GuardDuty findings, secrets and supply chain handling. ISO 27001/KRITIS exposure is a plus.
• You write code in Python or Go.
• Containers and CI/CD in production with rollbacks.
• Monitoring/alerting (DataDog, Grafana, Prometheus).

Aufgaben

• 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.
• Make shipping boring. Infrastructure-as-Code, CI/CD, environments and guardrails good enough for engineers to deploy without handholding.
• Reliability where it counts. Implement SLOs, observability, and incident practice for revenue-impacting systems.
• Security and compliance as design constraints. IAM, secrets, network boundaries and audit trails designed in from the start.
• Mentor and raise the bar across the tech team; staffing the Staff end of this role with others in the organization.

Kenntnisse

AWS platform ownership

IaC ownership (Terraform/Pulumi/CDK)

Security & IAM design

Multi-account governance

Python or Go coding

CI/CD pipelines

Monitoring & observability

On-call experience

Tools

Terraform

Pulumi

CDK

Lambda

ECS/EKS

API Gateway

DynamoDB

IAM

Jobbeschreibung

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.000 - 115.000 per year gross depending on the seniority level
• Language Requirement: C1 Level English

Your Responsibilities

• 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.

Your Profile

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 / GuardDuty / GitHub 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 (DataDog, Grafana, Prometheus or equivalent) and can tell a useful alert from noise.

What would set you apart

• 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.

This role may not be for you if

• 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 to diversity - of backgrounds and experiences. You don’t need 100% of the preferred qualifications to add incredible value to our team. If you’re passionate about what you could accomplish here, we’d love to hear from you.

Your Benefits

• Competitive Compensation Package: Including salary, benefits, and potential for growth.
• Professional Development: Annual development budget of €3,000 for coaching, training, books, etc.
• Health & Sport Subsidy: Company-subsidized sports facility memberships.
• Public Transportation Subsidy: Monthly subsidy for your public transport ticket.
• Lunch/Dinner Allowance Vouchers: Digital meal vouchers for workdays.
• Work Equipment: Your choice of MacBook or Windows Laptop and ergonomic workplace setup.
• Regular Team Events: Knowledge sessions, afterwork hangouts, sports events, and company offsites.

A Short Note from Your Future Lead

Willi Richert, VP of Technology — flexa

Hi there!

I'm Willi, VP of Technology at flexa. I've spent the last 15 years building engineering teams around systems that have to make good decisions fast and at scale. Most recently at Lyft, where I led the mapping organization — 30+ engineers across five countries — and we moved more than 96% of rides off Google Maps onto our own mapping product. Before that I worked on machine learning and conversational AI at Microsoft Bing, and I did a PhD on learning in heterogeneous robot groups, which is a long way of saying that distributed decision-making has held my attention for a while.

What pulled me to flexa is that it's the same class of problem with something physical at the other end. We dispatch energy of the Enpal customer fleet in real time against energy markets. If our infrastructure is a few seconds late or a few percent off, customers lose money and the grid gets less flexibility than it could have had. That makes cloud engineering a first-order product concern here rather than a supporting function — which is why this role sits close to the decisions that actually matter.

How I work: I'd rather hand you the whole problem, context and constraints included, than a ticket. I care that engineers can see the consequences of what you build, and I'll be direct with feedback and expect the same back — the fastest way to lose a year is for everyone to stay polite about an architecture that isn't working.

You won't find everything already built. Some of it is greenfield, some of it needs replacing, and you'll have real influence over which is which. If that sounds like your kind of problem, I'd like to hear from you — and if you're not sure your profile is a perfect match, apply anyway and let's talk.

Looking forward to meeting you,

Willi