Lediga job som Databasspecialist/Databasadministratör

Avalanche Studios Group is looking for a Senior Data Engineer to join our Data and Insights team!

This role is responsible for designing, developing and maintaining scalable data pipelines and state-of-the-art data processing technologies. You will play a key role in our Data Engineering team, ensuring that our data infrastructure is reliable, performant, and successfully tied to delivering better data systems for our games and publishing activities. This role requires a deep understanding of data engineering methodologies/frameworks in a big-data environment ; coupled to a strong collaborative spirit.

What you'll do:

• Develop and implement processes to extract, clean, and transform data from various sources to ensure it is ready for modelling/consumption.
• Collaborate with analytics engineers, data scientists/analysts and product stakeholders to understand their data needs and provide them with reliable data solutions ; capturing a complete ecosystem view of in- and out-of-game user behaviors.
• Architect and implement robust, maintainable, and high-performance ETL/ELT pipelines and data systems ; ensuring accuracy, compliance, scalability, and long-term usability.
• Create and maintain comprehensive data documentation, including data dictionaries, schemas, and metadata. Ensure that data definitions are consistent and easily accessible to all stakeholders.
• Monitor data pipelines and systems to ensure high availability and performance alongside our analytics engineer ; implement automated data quality checks, validation processes and alerts ensuring the accuracy and reliability of data.
• Write efficient, maintainable, and scalable code using best practices. Conduct code and SQL reviews and provide feedback to ensure high standards of code quality within the team.
• Stay updated with the latest trends, technologies, frameworks and best practices in data engineering / analytics / AI and share knowledge with the team.

Who you are:

• Bachelor’s or Master’s degree in Computer Science, Data Engineering, or a related field ; with 8+ years experience in data engineering or a related field.
• Strong proficiency in big-data technologies and languages, such as Python, Spark, Scala, SQL, and Java.Experience with ETL/ELT processes and tools (e.g. Apache Airflow, Talend, DBT… DBT being a big plus).
• Familiarity with cloud-based data platforms (e.g. AWS, GCP, Azure… GCP being a big plus) ; and experience with “Infrastructure as Code” process (e.g. Terraform).
• Excellent problem-solving skills and attention to detail ; coupled with strong communication skills and the ability to work collaboratively with cross-functional teams.
• Passion for gaming and a deep understanding of the gaming industry is a plus!

Note: Research shows under-represented groups in the industry might not apply to a job if they don’t check off every requirement. At Avalanche, we’re more about your drive to learn and interest in tackling challenges than what’s on your resume! So don’t stress if you don’t tick every box— shoot us your application anyway! Diverse opinions and different experiences are what make our teams so great, not itemized lists of qualifications.

The Stockholm location

Our Stockholm office is situated in Södermalm, the beating heart of the city’s game industry. It’s a physical representation of our games – the lush vegetation of Just Cause and theHunter: Call of the Wild meets corroded metal straight out of Mad Max. Our hybrid model requires you to be in the office on Mondays, Tuesdays, and Thursdays to foster collaboration and creativity.

Our values

At Avalanche Studios Group, we create worlds beyond limits. But that’s not exclusive to our games, so we’re committed to developing a diverse and inclusive workplace. All Avalanchers have a shared responsibility to create an open work environment where everyone is treated equally and respectfully. Being part of our world is not contingent on your heritage, your gender, or sexual orientation. It’s all about your passion and creativity.

How to apply

To apply for this position, please register below and provide your CV in English. We review applications continuously. All further studio-related information is provided under a non-disclosure agreement.

At Avalanche Studios Group we're always on the lookout for talented individuals to join our passionate team, but please note that relocation assistance is not available for this role.

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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: Karin Bergström, Head of Product and technology

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