Time since we first saw it
Day 37
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.
Austria; France; Germany; Italy; Netherlands; Poland; Spain; United Kingdom
Live, first seen by us 37 days agoEvery request gets a decision: which model serves it.
This is an applied-ML seat, not an infrastructure one.
Own the routing model end to end: features, objective, training, calibration and release cadence
Build the evaluation that gates every router change, with error bars on pass rates
Turn production outcomes and override feedback into training signal, filtering infra failures
Model the objective as task success times token cost times wall-clock speed
Run the online loop: shadow tests, A/B tests, full rollout, drift monitoring and retraining
Every request gets a decision: which model serves it.
This is an applied-ML seat, not an infrastructure one. Platform engineers own the proxy, the streaming path, and the fleet. You own the model inside them: the training data, the objective, the evaluation, and the iteration loop that ships a better router every cycle.
Own the routing model end to end: features, objective, training, calibration, and release cadence.
Build the evaluation that gates every change: production-parity benchmarks, router-vs-router comparisons, holdouts by task family, error bars on pass rates.
Turn fleet data into training signal: per-request outcomes from production, benchmark rollouts, and override feedback, with failure categorization (infra vs task)
Model the objective the user actually experiences: task success × token cost × wall-clock speed
Run the online loop: shadow, A/B, full rollout, drift monitoring, retrain.
As part of our standard hiring process, we would like to inform you that a background check may be conducted at the final stage of recruitment through our third-party provider, Checkr. Please note that Cast AI does not provide any form of visa sponsorship/work permit.Read the full posting
Strong Python and SQL at scale: you can pull, clean, and interrogate millions of request-level records without waiting on anyone.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 37
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.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
The problem: routing is a prediction problem wearing a product's clothes. For every request you predict the quality each candidate model would deliver, what it would cost, and how fast it would decode, and you have to be right enough, in aggregate, that the savings are real and the quality never dips below frontier. The data is messy: rollout outcomes from benchmark harnesses, per-request records from the live fleet, override signals, and token streams whose speed depends on the serving concurrency at the moment. Speed itself is a correctness variable: on deadline-bound agentic work, a model that decodes three times slower doesn't do the same work slower, it does less work. That's why naive cost-per-token objectives quietly optimize for the wrong thing. And the bar for evidence is high: a router change ships only after production-parity evaluation with error bars, then gets held to its numbers in live traffic. Stack: Python; PyTorch; SQL at scale (ClickHouse); OpenAI- and Anthropic-compatible LLM APIs; benchmark and rollout harnesses (RouterBench-class); GitLab CI. Requirements
- You've spent 5+ years in applied ML or ML research, and you've trained, evaluated, and shipped models that make real-time decisions (ranking, recommendation, bandits, pricing, or LLM routing) and you can tell that story with receipts. - Strong Python and SQL at scale: you can pull, clean, and interrogate millions of request-level records without waiting on anyone. - You know the difference between a model that got better and an eval that got easier.
Why Kimchi? Great models are raw ingredients. Kimchi is what happens when you ferment them with good engineering. We started inside CAST AI helping companies run LLMs on their own Kubernetes clusters; today we run our own coding harness on any model you pick, and the router deciding which model answers each request is ours too. The Auto Router
- Enjoy a flexible, remote-first global environment. - Collaborate with a global team of cloud experts and innovators, passionate about pushing the boundaries of Kubernetes technology - Equity options.
Complete your application on cast.ai. The employer’s form will show what is required.
Already applied? Track this application
Great models are raw ingredients. Kimchi is what happens when you ferment them with good engineering. We started inside CAST AI helping companies run LLMs on their own Kubernetes clusters; today we run our own coding harness on any model you pick, and the router deciding which model answers each request is ours too.
The Auto Router
Our promise is one enforcement layer for your AI: budgets, spend attribution, and model routing, applied before a request ever hits a model. The Auto Router makes the call: for every request, which model serves it. Eight open-source models whose input prices span more than 20×, cached input up to 50× cheaper than fresh, frontier providers on customers' own keys, and a coding agent that fires hundreds of requests before its task is done. Frontier-level task success at a fraction of the token cost: that sentence is the product, and it stays true only if the model inside the router keeps getting better. That model is yours.
Made by Cast AI — a Miami-headquartered, globally distributed team across 34 countries that hit unicorn status in January 2026 with a $50B+ backed investment pushing its valuation past $1 billion.
Every request gets a decision: which model serves it.
This is an applied-ML seat, not an infrastructure one. Platform engineers own the proxy, the streaming path, and the fleet. You own the model inside them: the training data, the objective, the evaluation, and the iteration loop that ships a better router every cycle.
The problem: routing is a prediction problem wearing a product's clothes. For every request you predict the quality each candidate model would deliver, what it would cost, and how fast it would decode, and you have to be right enough, in aggregate, that the savings are real and the quality never dips below frontier. The data is messy: rollout outcomes from benchmark harnesses, per-request records from the live fleet, override signals, and token streams whose speed depends on the serving concurrency at the moment. Speed itself is a correctness variable: on deadline-bound agentic work, a model that decodes three times slower doesn't do the same work slower, it does less work. That's why naive cost-per-token objectives quietly optimize for the wrong thing. And the bar for evidence is high: a router change ships only after production-parity evaluation with error bars, then gets held to its numbers in live traffic.
Stack: Python; PyTorch; SQL at scale (ClickHouse); OpenAI- and Anthropic-compatible LLM APIs; benchmark and rollout harnesses (RouterBench-class); GitLab CI.
As part of our standard hiring process, we would like to inform you that a background check may be conducted at the final stage of recruitment through our third-party provider, Checkr.
Please note that Cast AI does not provide any form of visa sponsorship/work permit.
#LI-Remote
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Austria; France; Germany; Italy; Netherlands; Poland; Spain; United Kingdom
- Competitive salary (depending on the level of experience). - Enjoy a flexible, remote-first global environment. - Collaborate with a global team of cloud experts and innovators, passionate about pushing the boundaries of Kubernetes technology
As part of our standard hiring process, we would like to inform you that a background check may be conducted at the final stage of recruitment through our third-party provider, Checkr. Please note that Cast AI does not provide any form of visa sponsorship/work permit. #LI-Remote
- Culture Check interview with an executive As part of our standard hiring process, we would like to inform you that a background check may be conducted at the final stage of recruitment through our third-party provider, Checkr. Please note that Cast AI does not provide any form of visa sponsorship/work permit. #LI-Remote