> Markdown version of [/jobs/ext/4146974-sre-platform-engineer-all-genders-remote-germany](https://www.wearedevelopers.com/jobs/ext/4146974-sre-platform-engineer-all-genders-remote-germany). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# SRE / Platform Engineer (all genders) - Remote Germany

- **Company:** Linro
- **Location:** Germany (Remote available)
- **Experience:** Experienced
- **Salary:** €75,000.0 - €93,000.0
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Microsoft Azure, Software as a Service, Cloud Computing, Continuous Integration, Software Debugging, Disaster Recovery, Github, Identity and Access Management, Python (Programming Language), PostgreSQL, OpenID, PCI Data Security Standards, Prometheus, Grafana, AI Coding Agents, Agentic-AI, Kubernetes, Vertica, Terraform
- **Published:** October 12, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=52d91b00d43a7d35

## About the Role

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

## Description

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., * 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., * 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.