Back to jobs

ML Engineering Lead (LLM Ops)

Stockholm · Berlin · London · Stockholm, Sweden

Actively hiring, first seen by us 3 days ago
Pay
Pay not listed
Work setting
Hybrid — work setting source
Location type: Hybrid
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering › Data & AI — team source
Department: Engineering › Data & AI
From the employer’s posting
Apply by
2 Nov 2026, 00:00 UTC — apply by source
Application deadline: 2026-11-02T00:00:00.000Z
From the employer’s posting

What you’ll work on

Full posting
  • Set up MLflow Tracing for prompts, tool calls, retrievals, latency and cost in production LLM pipelines

  • Build an LLM evaluation suite with custom judges and a human-feedback review loop

  • Ship at least one RAG or agentic pipeline to production with versioning and rollback

  • Document a cost, latency and GPU capacity framework for choosing a serving strategy

  • Integrate LLM Ops with the existing MLOps team to protect reliability on clinical workflows

From the employer’s posting
Stand up MLflow Tracing observability, prompts, tool calls, retrievals, latency and cost, live across production LLM and agent pipelines.
Build an evaluation suite combining built-in and custom LLM judges and scorers, with a human-feedback loop via review apps
Ship at least one RAG or agentic pipeline to production with prompt and application versioning through the MLflow Prompt Registry and Unity Catalog
Produce a documented cost, latency and GPU capacity framework for choosing serving strategy
Integrate LLM Ops tightly with the existing MLOps team so it operates as a natural extension of the platform

Before you apply

Sponsorship
Visa sponsorship not confirmed — sponsorship source
Will you now or in the future require sponsorship or other support to obtain or maintain work authorisation in that country?
From the employer’s application form

Tools in this posting

  • Python
  • Databricks
  • Kubernetes
  • MLflow
  • Terraform
  • PyTorch
Source — Tool mentions in context
● Solid MLOps fundamentals across the full lifecycle, experiment tracking, training and monitoring, demonstrated through independent ownership of complex, production grade work. ● Fluent in Python and core ML concepts, with a track record of shipping end-to-end production ML systems and platformisation initiatives. ● Practical, hands-on experience building LLM or GenAI applications: prompt engineering, RAG, agents or chains, using frameworks such as LangChain, LangGraph, or comparable orchestration tools.
● Ship at least one RAG or agentic pipeline to production with prompt and application versioning through the MLflow Prompt Registry and Unity Catalog, enabling safe rollout, A/B testing and rollback. ● Produce a documented cost, latency and GPU capacity framework for choosing serving strategy: third party API versus Databricks External Models versus self-hosted. ● Integrate LLM Ops tightly with the existing MLOps team so it operates as a natural extension of the platform rather than a separate track, protecting reliability on clinical workflows.
● Kubernetes and Terraform, useful for infrastructure as code or self-hosting fine-tuned or open-source models outside managed serving. ● Exposure to LLM evaluation and observability practices: tracing, LLM-as-judge, guardrails and safety scorers. Databricks MLflow 3 for GenAI experience is a strong plus. ● Comfort navigating a fast-moving tools and platform ecosystem, and distilling recommendations relevant to Neko's specific context.
● Experience with agentic or AI-assisted coding workflows, provided you retain full ownership and understanding of the resulting output. ● Kubernetes and Terraform, useful for infrastructure as code or self-hosting fine-tuned or open-source models outside managed serving. ● Exposure to LLM evaluation and observability practices: tracing, LLM-as-judge, guardrails and safety scorers. Databricks MLflow 3 for GenAI experience is a strong plus.
What You'll Deliver in the First 6-12 Months ● Stand up MLflow Tracing observability, prompts, tool calls, retrievals, latency and cost, live across production LLM and agent pipelines. ● Build an evaluation suite combining built-in and custom LLM judges and scorers, with a human-feedback loop via review apps, replacing today's ad hoc review.
● Build an evaluation suite combining built-in and custom LLM judges and scorers, with a human-feedback loop via review apps, replacing today's ad hoc review. ● Ship at least one RAG or agentic pipeline to production with prompt and application versioning through the MLflow Prompt Registry and Unity Catalog, enabling safe rollout, A/B testing and rollback. ● Produce a documented cost, latency and GPU capacity framework for choosing serving strategy: third party API versus Databricks External Models versus self-hosted.
● Practical, hands-on experience building LLM or GenAI applications: prompt engineering, RAG, agents or chains, using frameworks such as LangChain, LangGraph, or comparable orchestration tools. ● Working knowledge of PyTorch, distributed systems and ML orchestration. ● Conceptual understanding of LLM-specific MLOps trade-offs: fine-tuning versus prompting versus RAG, vector databases, embedding models, and human-feedback loops for non-deterministic outputs. Hands-on fine-tuning ownership is not required, as execution sits with a separate track.

About Neko Health

We use a simplified internal title framework that prioritises clarity over hierarchy, so the title on this posting may differ from your internal title.

In the employer’s words · Read in context · Company website ↗

Check the employer’s page ↗

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026
Employer says posted
Oct 2, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Early. Similar jobs usually come down between day 7 and day 76.

From 6,389 similar postings that came down. Coming down is not always a hire.

Neko Health is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

Your next step

Check the employer’s posting for the current role and application details.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

Mission

Neko Health is a health technology company that opened its first clinic in Stockholm in 2018, founded by Daniel Ek and Hjalmar Nilsonne.

In one hour, our scan combines radiation-free imaging, heart and circulation measurements, and same-visit blood results with time to talk it through with a clinician, so people can act on what matters before symptoms appear. We design and build our own hardware, software and clinical protocols, and more than 100,000 members have already had a scan, with 75% booking and prepaying their next one before they leave.

As a team, we chase 10X, not 10%, and we’re looking for people who think the same way to help us scale what we’ve started in Sweden, the UK, and now the US. Join the clinicians, engineers and business builders making prevention a routine part of care.

Role Purpose

This role owns the operational lifecycle of Neko's LLM, GenAI and RAG based systems: deployment, monitoring, evaluation and iteration. It builds the production grade platform that lets clinical ML and GenAI workflows run reliably on proprietary sensor and device data, inside a regulated medical device QMS, across Skin, Cardio and other use cases. The role sits within the ML Engineering Area and integrates tightly with the existing MLOps team rather than as a silo.

What You'll Deliver in the First 6-12 Months

● Stand up MLflow Tracing observability, prompts, tool calls, retrievals, latency and cost, live across production LLM and agent pipelines.

● Build an evaluation suite combining built-in and custom LLM judges and scorers, with a human-feedback loop via review apps, replacing today's ad hoc review.

● Ship at least one RAG or agentic pipeline to production with prompt and application versioning through the MLflow Prompt Registry and Unity Catalog, enabling safe rollout, A/B testing and rollback.

● Produce a documented cost, latency and GPU capacity framework for choosing serving strategy: third party API versus Databricks External Models versus self-hosted.

● Integrate LLM Ops tightly with the existing MLOps team so it operates as a natural extension of the platform rather than a separate track, protecting reliability on clinical workflows.

Minimum Qualifications

● Solid MLOps fundamentals across the full lifecycle, experiment tracking, training and monitoring, demonstrated through independent ownership of complex, production grade work.

● Fluent in Python and core ML concepts, with a track record of shipping end-to-end production ML systems and platformisation initiatives.

● Practical, hands-on experience building LLM or GenAI applications: prompt engineering, RAG, agents or chains, using frameworks such as LangChain, LangGraph, or comparable orchestration tools.

● Working knowledge of PyTorch, distributed systems and ML orchestration.

● Conceptual understanding of LLM-specific MLOps trade-offs: fine-tuning versus prompting versus RAG, vector databases, embedding models, and human-feedback loops for non-deterministic outputs. Hands-on fine-tuning ownership is not required, as execution sits with a separate track.

● Genuine, demonstrable motivation for LLM, GenAI and RAG work specifically, not generic MLOps, and the ability to navigate complex systems spanning the medical domain, regulation, firmware and hardware.

Preferred Qualifications

● Experience with agentic or AI-assisted coding workflows, provided you retain full ownership and understanding of the resulting output.

● Kubernetes and Terraform, useful for infrastructure as code or self-hosting fine-tuned or open-source models outside managed serving.

● Exposure to LLM evaluation and observability practices: tracing, LLM-as-judge, guardrails and safety scorers. Databricks MLflow 3 for GenAI experience is a strong plus.

● Comfort navigating a fast-moving tools and platform ecosystem, and distilling recommendations relevant to Neko's specific context.

About titles at Neko

We use a simplified internal title framework that prioritises clarity over hierarchy, so the title on this posting may differ from your internal title. We’ll be open about the scope and level of the role throughout the process, so you know exactly what you’d be taking on.

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 508, the most 899, and the latest week had 508.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under ML Engineer, by the work the posting describes.

ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.

Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.

A data scientist often works out which model to build; an ML engineer makes it run reliably in production.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Stockholm, Sweden

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting