Senior Platform Engineer hos Doktor.se i Stockholm

What you'll do

Our infrastructure works, but it was built to solve yesterday's problems. We need someone who can help us get to where we want to be — not maintain what we have, but reshape it. If you want a place where everything is already figured out, this isn't it. If you want to build something better, here's what you'd own:

Build a deployment platform where teams ship their own services without asking you for permission.

Design infrastructure that is secure by default, so teams don't have to think about encryption, network isolation, or data residency. It just works.

Create deployment pipelines where security scanning, policy checks, and compliance happen automatically, invisible when everything is fine, loud when something needs attention.

Support and scale infrastructure for AI workloads, we run models in production across our platform, and that footprint is growing.

Set up observability that gives teams real insight into their own services, useful dashboards, alerts that mean something, not noise that everyone ignores.

Work closely with developers to understand what slows them down, and then fix it. Not by doing it for them, but by making it easy for them to do it themselves.

Maintain and evolve our cloud account structure, networking, and identity management across multiple regions and products.

Some weeks you'll write infrastructure code. Some weeks you'll pair with a developer to debug a slow service. Some weeks you'll design how a new product gets its own isolated infrastructure. The common thread: you make the teams around you better.

Make developers faster, not more dependent on you.

What we're looking for

You've built and operated Kubernetes in production. Not just deployed a Helm chart once, you've debugged networking issues, designed RBAC policies, and thought about how multiple teams share a cluster without stepping on each other.

You know AWS well. Accounts, networking, IAM, KMS. You have opinions about what should live in Kubernetes and what genuinely needs to be an AWS managed service, and you lean toward keeping things in Kubernetes where possible.

You've worked with GitOps and infrastructure as code. Flux, ArgoCD, Terrafor, specific tools matter less than the principle: infrastructure changes go through pull requests, are reviewed, and are auditable.

You understand developers because you are one. You can read their code, understand their pipelines, and have meaningful conversations about architecture.

You think about security as something you design into systems, not something you review at the end.

You have opinions, and you can change them when someone makes a better argument.

University degree in computer science, engineering, or equivalent experience.

What we offer

Real influence. You'll shape how our platform works, not just operate what someone else designed.

Healthcare context. Patient data, regulatory compliance, and real consequences for getting it wrong. What you build actually matters.

Small team, direct impact. 25 engineers, your work is visible, not lost in a machine.

Autonomy. No micromanagement, no endless approval chains.

AI in production. We're running LLMs in patient and clinician workflows today, the infrastructure needs to grow with that.

Collective agreement, 30 days vacation, wellness allowance, personal development budget.