Summary
What you’ll impact
The Senior Machine Learning Engineer designs, builds, and operates the intelligence layer that detects product failures and drives automated root‑cause analysis. They employ large language models, agentic architectures, retrieval‑indexing pipelines, and scalable inference infrastructure to analyze code, logs, and runtime behavior. Responsibilities include creating autonomous agents for code reasoning, LLM‑based triage and fix proposals, anomaly detection, and continuous evaluation loops. Collaboration spans product, design, and engineering teams, establishing evaluation standards and guiding peers in AI observability.
Responsibilities
What you'll do
- You'll own the intelligence layer that makes Interfere work.
- Agents that reason about codebases, traces, logs, and runtime behavior to find and explain bugs before users hit them, including the sandboxes they run in and the browsers and web research they use to investigate
- LLM pipelines for triage, root-cause analysis, and automated fix proposals, with the model routing that sends each job to the right model at the right cost
- Detection systems for anomalies in product behavior, performance, and user experience across noisy real‑world data
- The evals, datasets, observability, and feedback loops that move us from "this prompt feels good" to "this system measurably works and is getting better," architecting the standards for the agentic parts of a product that is still being defined
- The context engineering that lets a model actually understand a customer's codebase: retrieval, indexing, context construction, and the integrations into their stack
- Systems that get sharper over time, turning every bug found and fixed into signal that improves the next detection, so continual learning is a product advantage rather than an afterthought
Requirements
What you’ll bring
- You've shipped ML or LLM-powered systems into production, where real users depend on the output, not just a notebook or a demo
- You move between research and engineering comfortably, and you pick up unfamiliar tech fast. You can go from a new framework or technique on Monday, to a working prototype by Friday, to an eval that tells you whether it's actually better the following week
- You can own something 0→1, beginning to end. You can take an ambiguous AI problem, define the next useful step, and ship without waiting for a fully specified plan
- You treat evals as a first-class engineering problem. When the system is making decisions for users, intuition isn't a substitute for measurement
- Experience with agent architectures, tool use, multi-step reasoning, or autonomous workflows in production