Мы используем технические cookie и статистику посещений: Яндекс Метрику и собственный обезличенный журнал Zorky (cookie zk_aid). Не собираем содержимое форм, текст поиска и полный IP; данные не продаём. Отказаться можно кнопкой ниже, а также через Global Privacy Control или Do Not Track в браузере. Подробнее о cookie и статистике.
Zorky CRMZorky CRM
EN|RU
@termdocs
← Все вакансии

Senior Applied ML Engineer | Kimchi (Model Router)

seniorofficeAustria; European Union; Germany; Italy; Netherlands; Poland; Spain; United Kingdom, GBСкор 75.5/1001д назад
Аналитика рынка
📊 AI / ML / DS: зарплаты и спрос на рынке
Стек
clickhousecloudgitlabkubernetesllmpythonpytorchsql
Откликнуться
Загрузите резюме — мы свяжем вас с работодателем напрямую через нашу базу.
Отправить резюме →
Описание
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 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. About the role 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 ever
Контакты работодателя (email/phone/telegram) скрыты из публичного превью — отправьте резюме, чтобы мы связали вас напрямую.
Срочный вопрос? Напишите @termdocs