IT-artist - Lediga jobb

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.

Vår kund är mästare på att samla och optimera sina kunders data. Med sin egenutvecklade plattform och specialister på databasutveckling har de byggt upp ett framgångsrikt företag som nu håller på att dra in nya affärer och behöver växa till hösten.

Om tjänsten

Vår kund utvecklar kundanpassade lösningar som genererar full potential av befintlig data. Genom effektiv insamling, strukturering, inmatning och visualisering av data på sin egenutvecklade plattform, får organisationen kvalitetssäkrad data som möjliggör effektivare processer och bättre beslutsunderlag.

Framtiden ser ljus ut på företaget och av den anledningen tar de nu in en till utvecklare. De är sammanlagt tio kollegor i Stockholm där alla arbetar i eller nära utvecklingen. I rollen jobbar du nära era kunder men ännu närmre deras data. Det är viktigt att du trivs i en interaktiv roll där du är social och närvarande i dialoger och diskussioner.

Du erbjuds

• En långsiktig tjänst som börjar som ett konsultuppdrag genom oss på Academic Work men där anställningen kommer övergå till en direktanställning hos kundföretaget
• Möjlighet till att bli delägare i företaget på sikt om du är intresserad av det
• Att arbeta på ett litet familjärt bolag men vars kunder är bland de största bolagen i Sverige

Arbetsuppgifter

Som databasutvecklare hos vår kund kommer du arbeta tillsammans med en eller två kollegor i ett projekt. Ni arbetar projektbaserat och ofta mot två företag samtidigt för att vara så effektiva som möjligt.

En vanlig vecka på jobbet startar ofta med att du tillsammans med ditt team har möte med er kund för att krävställa en ny funktion som ska utvecklas eller en befintlig som ska förbättras. Sen lägger ni en gemensam plan för hur ni ska arbeta och därefter börjar jobbet med att utveckla/uppdatera olika databasfunktioner och kringliggande program. Alla lösningar som ni utvecklar hos kunden bygger på er egen plattform och det mesta av programmeringen sker i Microsoft SQL Server. Du kommer även att ta fram användargränssnitt i CMS verktyg, designa rapporter i SQL Server Reporting Services och Power BI, samt bygga analyskuber i SQL Server Analysis Services.

Vi söker dig som

• Har erfarenhet från tidigare roller av programmering i relationsdatabaser och med SQL och T-SQL
• Är duktig på programmering i ett eller flera programmeringsspråk
• Har jobbat med hela processen från att offert till betalning, alltså "Quote-to-cash"
• Språk: Svenska och Engelska i tal och skrift

Vi tror att du som söker den här tjänsten har arbetat som databasutvecklare eller databasadministratör (DBA) i minst 2-3 år för att passa bra i rollen.

Det är meriterande om du har

• Eftergymnasial utbildning inom IT såsom systemvetenskap eller datateknik
• Erfarenhet av att arbeta med PowerBI och QlikSense för att transformera och visualisera data
• Arbetat som konsult tidigare och är van att ta ansvar för det arbete du utför

För att lyckas i rollen har du följande personliga egenskaper:

• Ordningsam
• Ansvarstagande
• Socialt självsäker

Vår rekryteringsprocess

Denna rekryteringsprocess hanteras av Academic Work och vår kunds önskemål är att alla frågor rörande tjänsten skickas till Academic Work.

Vi tillämpar löpande urval och kommer plocka ner annonsen när tillräckligt många kandidater har nått slutskedet i rekryteringsprocessen. Vid ansökan efterfrågas ett CV. Personligt brev använder vi inte som urvalsmetod och behöver därför inte bifogas. Rekryteringsprocessen innehåller två urvalstest: ett personlighetstest och ett test i kognitiv förmåga. Testerna är ett verktyg för att kunna hitta den kandidat med högst potential för tjänsten samt främja jämlikhet, mångfald och en rättvis rekryteringsprocess.