Datavetare - Lediga jobb

Vill du ta ägarskap för vår CMDB och SACM-process och bygga en plattform som verkligen stöttar verksamheten? Hos oss får du en central roll där du kombinerar strategiskt ansvar med praktiskt arbete i ett framåttänkande team med stark gemenskap, hög kompetens och en kultur som präglas av stöd, samarbete och kunskapsdelning.

Om jobbet

Som Configuration Manager får du det övergripande ansvaret för vår Configuration Management Database (CMDB) och Service Assurance & Configuration Management-processen (SACM). Din roll är att säkerställa att organisationen har rätt, tillförlitlig och lättillgänglig information om våra konfigurationsobjekt, så att olika intressenter kan utföra sina processer effektivt. Du arbetar nära kollegor i verksamheten och IT för att utveckla en modern, stabil och användarvänlig plattform som följer best practice och stödjer våra långsiktiga mål.

Dina arbetsuppgifter kommer bland annat vara:

• Ansvara för att definiera omfattning och syfte för SACM-processen och CMDB-verktyget.
• Skapa, förvalta och vidareutveckla dokumentation för SACM-processen och CMDB.
• Utveckla och underhålla CMDB:s datamodell, inklusive klasser, relationer, formulär, fält och regler.
• Säkerställa mätbarhet genom att definiera och följa upp relevanta nyckeltal (KPI:er).
• Arbeta med att automatisera livscyklerna för konfigurationsobjekt (Configuration Items).
• Sammankalla till och äga agendan för forum med CMDB/SACM-intressenter.
• Samarbeta och kommunicera med andra intressenter, exempelvis business analysts, för att säkerställa att CMDB innehåller rätt information och att gränssnitt för att konsumera denna information är tydliga och kända.
• Ta fram dokumentation och utbildningsmaterial för CMDB och relaterade processer.
• Stötta och vägleda operativ Configuration Manager i det dagliga arbetet.
• Äga policies, modeller och rutiner kopplade till CMDB samt processen för att övervaka och agera på KPI:er.

Följande kommer göra dig framgångsrik i denna tjänst:

• Flera års erfarenhet (ca 4–5 år) av att arbeta med ServiceNow och dess datamodell.
• Djup kunskap om ServiceNow samt service assurance- och configuration management-processer, inklusive CMDB.
• Relevanta certifieringar inom ServiceNow och SACM/CMDB.
• Erfarenhet av att ta ägarskap för processer och verktyg inom konfigurationshantering.
• Förmåga att definiera, följa upp och agera på nyckeltal kopplade till process och plattform.

Meriterande är även om du har:

• Erfarenhet av utveckling i ServiceNow och god förståelse för plattformens funktioner och möjligheter.
• Dokumenterad förmåga att anpassa, förbättra och optimera lösningar i ServiceNow.
• Vana att hålla dig uppdaterad kring nya funktioner och best practice inom ServiceNow.

Som person är du kommunikativ, pedagogisk och trivs med att förklara komplexa samband på ett tydligt sätt för olika målgrupper. Du har ett långsiktigt perspektiv, kan sätta en tydlig riktning framåt och arbetar strukturerat med ständiga förbättringar. Du är bra på att bygga relationer, skapa samsyn och engagera kollegor i förändringsarbete. Samtidigt är du noggrann, ansvarstagande och ser till att beslut omsätts i hållbara lösningar som fungerar i vardagen. I vår kultur, där självledarskap, samarbete och kontinuerligt lärande står i centrum, kommer du till din rätt om du vill växa tillsammans med andra och bidra till starka gemensamma resultat.

KontaktpersonerRekryterande chef: Farhad.Tabari@lansforsakringar.seFacklig representant Forena: Jessica.loow@lansforsakringar.seFacklig representant Akademikerföreningen: Lisa-Maria.Carensjo@lansforsakringar.se

Låter det spännande? Då vill vi veta mer om dig! Välkommen med din ansökan redan idag. Vi arbetar löpande med denna rekrytering och kan komma att tillsätta tjänsten innan sista ansökningsdag.

Observera att rekryteringsprocessen pågår under sommaren. På grund av semesterperioden kan återkoppling och handläggningstider vara något längre än vanligt. Vi tackar för ditt tålamod och ser fram emot din ansökan.

Länsförsäkringar AB är en inkluderande arbetsplats där mod, möjligheter och engagemang står i centrum. Vi erbjuder ett hållbart arbetsliv med flexibla villkor och satsar på att alla medarbetare ska kunna växa och trivas, oavsett bakgrund.

Digital & IT är hjärtat i Länsförsäkringsgruppens digitala utveckling. Vi driver den gemensamma digitala transformationen och levererar förstklassiga IT-lösningar, datadrivna insikter och innovativa digitala tjänster som skapar värde för hela verksamheten. Vårt uppdrag är att bygga en robust och framtidssäker IT-miljö – både på plats och i molnet – som möjliggör kundnära och effektiva affärer i hela gruppen.

Hos oss möts teknik, affär och innovation. Vi arbetar tvärfunktionellt ute i verksamheten i agila team där utveckling, drift och strategi går hand i hand. Vi ansvarar för allt från IT-styrning, enterprisearkitektur och leverantörshantering till applikationsutveckling, cybersäkerhet och verksamhetsberedskap.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.

Doktor.se is Sweden's largest digital healthcare provider. We combine physical clinics with a digital platform serving millions of consultations per year across Sweden, Germany, and Norway. Our 25-person engineering team has startup autonomy inside a profitable, international organization with 1,000+ employees and over 1B SEK in revenue.

We run OpenAI and Anthropic models in production across patient and clinician workflows, and that footprint is growing fast.

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.

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

Cloud - AWS (multi-account, multi-region)

Orchestration - Kubernetes / EKS

IaC - Terraform

CI/CD - GitHub Actions

Languages - Python, TypeScript

AI - OpenAI, Anthropic (in production and tooling)

Observability - Datadog / Grafana (you'll shape this)

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

• Start: As soon as we find the right person. We'll accommodate your notice period.

• Employment: Permanent, full-time. Six month probation period.

• Location: On-site, Monday–Thursday at Sveavägen 63, Stockholm. Fridays are flexible.

• Language: English is our working language in tech. Swedish is a bonus.

• Work permit: You must already have the right to work in Sweden.

• Contact: Andrew Crookston, VP of Engineering

We handle recruitment internally — no agencies, no consultants, no external recruiters.