Site Reliability Engineer

Oplane; Malmö kommun; On-site; SEK 900,000 - 1,100,000; Full time

Benefits offered by this job

SOC 2 certified

Malmö office

Seed Capital backing

Job summary

Oplane is hiring for a dedicated reliability engineer to own uptime, performance, and the safe delivery of changes. You will build observability, define meaningful metrics, and ensure the CI/CD pipeline across containers is fast and safe.

You’ll own cloud infrastructure defined as code, manage production AI workloads with security in mind, and grow the automation through coding agents. This is a Malmö on-site role.

Qualifications

• Around 8 years in SRE, platform, or infrastructure engineering with real prod systems.
• Cloud infrastructure defined as code on at least one major cloud.
• Observability built and used by a team; incident prevention mindset.
• Strong CI/CD experience; treat the pipeline as a product.
• Automation-first mindset; use coding agents in work.
• Security-minded, especially handling sensitive data and access.
• Startup or scale-up background; comfortable alone initially.
• Working language is English.

Responsibilities

• Own reliability: uptime, performance, and failure behavior, define targets.
• Make the system observable with metrics, logging, tracing, alerts.
• Own CI/CD path from merged change to production across containers.
• Own the infrastructure with code, reproducible and cost-aware.
• Operate AI/agent workloads in production with proper isolation and security.

Skills

SRE

Cloud IaC

CI/CD

Observability

Automation

Security-minded

Tools

Kubernetes

Terraform

CI/CD pipelines

Monitoring

Job description

Own reliability, observability, CI/CD and the cloud infrastructure behind a product enterprises depend on.

Oplane sits inside enterprise customers’ coding loop, holds their source code, and produces the security findings their teams act on. That is a high trust position, and it comes with a high bar for reliability: when Oplane is down or slow, we are in the way of how a customer ships. Today reliability, infrastructure and CI/CD are handled by the engineering team alongside building the product, and it is time to give them a dedicated owner.

You are the first dedicated reliability hire. There is infrastructure running in production with real customers on it, but the systems that keep it healthy, observable and safe to change are still early, and you are here to build them properly.

What you’ll own

Reliability, observability, CI/CD and the cloud infrastructure the product runs on. Whether Oplane is up, fast, safe to deploy, and possible to reason about when something goes wrong.

What the job actually is

• Own reliability. Uptime, performance, and the failure behavior of a product enterprises depend on. You define what good looks like and build toward it, rather than reacting to whatever broke last.
• Make the system observable. Metrics, logging, tracing and alerting, good enough that anyone on the team can understand production and get paged for the right things, not the noise. When something breaks, the goal is that we can see why quickly.
• Own CI/CD. The path from a merged change to production, fast and safe, across containers and infrastructure changes. We ship often, a lot of code is now written with coding agents, and an agent reviews our pull requests, so the pipeline that gates and delivers all of that matters more here than at most companies.
• Own the infrastructure. A cloud footprint defined as code, built so it is understandable, reproducible and cost-sane rather than a pile of manual state. You care that handling customer code and secrets is done correctly, because for us that is a security property, not just an ops detail.
• Operate AI and agent workloads in production. A lot of what Oplane does runs as AI and agent workloads in production infrastructure, over sensitive customer input. Running that safely and affordably (isolation, tightly scoped credentials, egress control, and cost caps that actually hold) is a genuinely unusual problem, and here it is core rather than a side quest.
• Build the function as a system. We grow through agents rather than headcount, so the point is not to become the human who keeps the lights on, it is to build the automation, guardrails and tooling that keep them on without you watching. You use coding agents to build that tooling, as everyone here does, and you should want to work your way out of the pager.

Who this is for

• Around 8 years in SRE, platform, or infrastructure engineering, running real production systems that mattered when they went down.
• Real depth in cloud infrastructure defined as code, on at least one major cloud.
• You have built observability that a team actually used, and you can talk about an incident you made less likely to happen again.
• Strong CI/CD experience, and you treat the pipeline as a product other engineers depend on.
• You are a strong engineer who automates by default, and you use coding agents seriously in your own work.
• Security-mindedness is a real plus, especially anything around handling sensitive data, secrets, and access.
• Startup or scale-up background, and comfortable owning this function alone at first.
• Working language is English.

What you get

• A product with paying enterprise customers already running in production, so reliability here has real stakes from day one. Teams like Miro, Tandem Health, Lightbringer, and many more already run Oplane, and we are SOC 2 certified.
• Full ownership of reliability, observability, CI/CD and infrastructure, working directly with the founders.
• Backed by Seed Capital and Icebreaker.vc, with angel investors from Neo4j and Google, including Emil Eifrem. $5.2M seed.
• Based at our Malmö office, on-site five days a week. This is an in-person engineering team by design, not a distributed one.

How we work

Small team, ten of us today, real autonomy, and nothing between deciding something and doing it. We are honest about what is hard, including in this ad. We grow through agents rather than do the work by hand forever. Nobody here asks permission first. If you see it, do it, and tell us afterwards.