SRE / Platform Engineer (all genders) - Remote Germany

Linro

Germany

Remote

Who this role is best for

A natural match if you have hands-on experience with cloud infrastructure and production Kubernetes.

Best fit for

Candidates with hands-on cloud production experience and a background in Kubernetes operations
— “Hands-on operation of AWS, GCP or Azure in production, AWS preferred.”
Individuals who have worked on infrastructure in regulated systems or compliance environments
— “Running cloud security at scale, building the platforms underneath it, and shipping in regulated systems where a wrong change isn't an option.”
Engineers who enjoy ownership and influence over platform design and reliability
— “You own production and the platform underneath it, with direct contact with the engineers and a say in how we build.”

Things to consider

On-call responsibilities are expected, with no mention of flexibility in rotation schedules
— “On-call is part of this role.”
The infrastructure is still evolving and may not be fully polished or CI/CD integrated
— “Our infrastructure is defined as code, but parts of it are still being moved into CI, runbooks are thin, and some environments are rougher than others.”

How to stand out

Highlight your experience with production Kubernetes and debugging OOMs in your resume and interviews
— “3+ years running production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts.”
Emphasize your ability to manage cloud infrastructure in regulated systems
— “shipping in regulated systems where a wrong change isn't an option.”
Showcase your skills in audit-ready operations and compliance frameworks
— “Produce audit-ready operations: backups, disaster recovery and continuity tests with evidence for SOC 2 and ISO 27001.”
Demonstrate your experience with Terraform in multi-environment setups with CI/CD integration
— “Terraform in multi-environment setups, with CI/CD in GitHub Actions and short-lived credentials.”
Demonstrate comfort with AI agents in infrastructure tasks and your ability to trust them selectively
— “You work with AI agents every day, including for infrastructure changes, and know where to trust them and where to check their output.”

Pace · Fast PacedCollaboration · HighAutonomy · HighDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

Own production reliability
Make install fleet boring
Fix open reliability work
Produce audit-ready operations

Typical background

3+ years running production KubernetesHands-on operation of AWS, GCP or Azure in production

Skills & requirements

Required

AWSKubernetesTerraformGoPythonObservabilitySlosPostgreSQLIncident OwnershipSecurity-minded Operations

Preferred

TemporalClickhouseCompliance Operations

Stack & domain

AWSGCPAzureKubernetesHelmTerraformGithub ActionsGoPythonPostgreSQLClickhouseTemporalObservabilitySlosAlertingOn-callBlameless PostmortemsProduction ReliabilityBackupDisaster RecoverySOC 2ISO 27001AI AgentsProblem-solvingTeamworkCommunicationAdaptabilityLeadershipAttention To DetailInnovationCloud SecurityInfrastructure ManagementProduction OperationsReal-time DetectionEnforcementAuto-remediationAgentic Cloud-security Platform

About the role

Original posting from Linro via Ashby

ABOUT LINRO
Linro is a Berlin-based cloud security company building a real-time, agentic cloud-security platform. Teams ship with AI. AI ships with Linro.
Infrastructure changes constantly, and increasingly it's AI agents making the changes. Tools that scan snapshots and flag risk after the fact can't keep up. Linro enforces intended state across the whole lifecycle instead, from commit to runtime: MCP and pre-commit hooks at commit time, blast-radius simulation that blocks bad changes before they ship, and real-time detection, enforcement and auto-remediation in production. Most tools tell you what's wrong. Linro stops it.
We have each been on the receiving end of this problem: Running cloud security at scale, building the platforms underneath it, and shipping in regulated systems where a wrong change isn't an option. Founded in Berlin in 2026 and built fully remote across Europe, Linro has a platform that's real and working, with plenty still to shape.
THE ROLE
You would be one of our first infrastructure hires, taking day-to-day operation of the platform off the CTO. Linro enforces policy on other people's cloud infrastructure, so our own has to be reliable, reproducible and auditable. You own production: how Linro runs for each customer, how it upgrades, and how we know it is unhealthy before a customer does.
WHAT YOU WILL DO
Own production reliability: SLOs, alerting, on-call and blameless postmortems for the control plane and every customer installation.
Make the install fleet boring: provisioning, maintenance windows and safe auto-upgrades across SaaS and self-hosted installs.
Fix the open reliability work: sensor memory ceilings and OOM visibility, ClickHouse cost and capacity, and the health of Postgres, PGMQ and Temporal.
Evolve the platform: Terraform and Terragrunt, Helm, GitHub Actions with short-lived OIDC credentials, local development (Tilt, Coder), and staging and production environments, with guardrails for humans and AI agents alike.
Produce audit-ready operations: backups, disaster recovery and continuity tests with evidence for SOC 2 and ISO 27001.
WHAT WE ARE LOOKING FOR
Hands-on operation of AWS, GCP or Azure in production, AWS preferred. Not just deploying to it, actually running it: accounts and access management, networking and the failure modes. We run across several clouds, so you pick up the others quickly.
3+ years running production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts.
Terraform in multi-environment setups, with CI/CD in GitHub Actions and short-lived credentials.
Go, or Python and a wish to learn Go. You read and write code in the services you operate.
Observability and SLOs: symptom-based alerting with Prometheus, Grafana or OpenTelemetry, and the discipline to delete noisy alerts.
Production Postgres: backups, point-in-time recovery, migrations and upgrades.
Incident ownership: on-call, leading incidents and writing postmortems that change something.
Security-minded operations: least privilege, secrets handling, access reviews and audit trails.
You work with AI agents every day, including for infrastructure changes, and know where to trust them and where to check their output.
NICE TO HAVE
Operating Temporal, queues or ClickHouse, including cost tuning.
Shipping and upgrading software in customer-run or self-hosted environments.
Compliance operations: SOC 2, ISO 27001 or PCI DSS evidence.
Using AI coding agents safely for infrastructure work.
Early-stage startup experience, or having been a founding infrastructure engineer.
HOW WE WORK
We work remotely across Europe. On-call is part of this role. We will be open about how the rotation works and compensate it. We get the whole team together in person somewhere in Europe once a quarter for a few days. We work async by default, write things down, and protect people's focus time.
WHAT WE OFFER
Real ownership. You own production and the platform underneath it, with direct contact with the engineers and a say in how we build.
Meaningful equity. You are an early employee, and your stake reflects it.
Competitive salary, benchmarked to the market.
A quarterly European offsite, and a team that takes both the mission and each other's time seriously.
THE HONEST VERSION
This is early. Our infrastructure is defined as code, but parts of it are still being moved into CI, runbooks are thin, and some environments are rougher than others. You would inherit something that works, not something polished. If you want a mature platform team with a clear roadmap for the next two years, this is not it. If you want to build the operational backbone of a security product from close to the start, and you like the idea of running the thing that keeps AI agents from breaking production, we should talk.

Source: Linro careers (Ashby)