Obtenez une réponse de cet employeur
Votre CV et votre lettre de motivation, adaptés exactement à ce que l’employeur recherche.
Monte Carlo is seeking a backend/model‑layer engineer to own end‑to‑end ML features that power agent trust. You’ll move from research and prototyping to production, partnering with engineering and data science to ship reliable, scalable components that improve agent behavior and reliability.
You’ll work primarily on the backend with a focus on ML systems, experimentation, and production-grade tooling. A strong Python background and several years in ML or data science are essential, with
Monte Carlo is the agent trust platform that autonomously observes, fixes, and continuously improves agents and the data that powers them — so enterprises can scale trust at the speed of AI. Bayes, our AI teammate, does the work: detecting, triaging, troubleshooting, and fixing issues in AI agents and the data powering them. The result is self‑improving agents that get better with every fix instead of drifting. More than 400 enterprises, including Amazon, PepsiCo, CNN, Nasdaq, and JetBlue, rely on Monte Carlo. Learn more at montecarlo.ai.
We're building the products that tell enterprises whether their AI agents can be trusted — and we need someone who works end to end, from an ambiguous problem statement through research, prototyping, and production. You'd get the problem, not the spec: research the approaches, prototype, prove what works, build it, and integrate it into the platform alongside our engineering and data science teams. This role exists because agent observability moved from roadmap to revenue faster than anyone predicted, and the work is now on the critical path.
You've built agents in production with real users. Not integrated a framework. Not worked on a team that had one. Built them — agents with real autonomy and internal loops, where the model uses tools and decides what to do next without a human in the middle, and you kept them running once real users showed up. RAG with a wrapper doesn't count. Neither does a set of MCP tools point at an API. You've run evals and monitored agents after launch. Agents are non-deterministic, so normal tests don't work on them. You've owned an eval framework — golden datasets, regression suites, offline and online scoring — not a folder of one‑off scripts. And you've watched agents in production, not just in dev.
Python, plus an ML or data science background.
Python is your daily language and you're solid on the backend, though you don't need to be a distributed systems specialist. You understand models well enough to reason about how they behave — you're not an application engineer calling someone else's API.
3+ years in ML, data science, or software engineering — at companies that ship quickly. Startups, AI‑native teams, or high‑growth product companies where the release cadence is measured in weeks, not quarters.
If all of your experience sits inside large, process‑heavy organizations with the platform already built for you, this seat will be a hard adjustment.
You work from a problem, not a spec. Handed an ambiguous problem statement, you design the experiment, build the smallest version to test it, and take what works into production. You use AI tools every day. Claude or its equivalents are part of how you write code and do research, not something you tried once.
This is backend and model layer work, by the way — no frontend. You'd rather ship than polish. Most of this work needs a good answer quickly, not a perfect one eventually. You can tell which problems are the exception and deserve real depth — and you'll say no to the version that demos well and falls apart in production.
statistics and hypothesis testing, applied rather than theoretical.
Building and maintaining MCP servers.
Experience in the data and cloud space — Snowflake, Databricks, dbt, Airflow.
If Your AI work is retrieval with a wrapper, or MCP tools pointed at an API — nothing that decides and acts on its own.
Your LLM experience is prototypes, notebooks, and demos that never carried production traffic.
You need a fully specified problem before you start, or you're uncomfortable with the ambiguity of a category being invented in real time #BI-REMOTE.
We created the data observability category, and we're doing it again with agent trust — you'll build where the market is forming, not where it's settled.
Remote‑first by design since day one, and recognized as a Best Workplace for it.
Competitive compensation, equity, and a remote‑first environment.
Come As You Are.
Equality is a core tenet of Monte Carlo's culture.
We are committed to building an inclusive global team that represents a variety of backgrounds, perspectives, beliefs, and experiences.
Monte Carlo is an equal‑opportunity employer.
We celebrate diversity and are committed to creating an inclusive environment for all employees.
Monte Carlo Named 2025 Databricks Data Governance Partner of the Year.
We were recently recognized as the #1 Data Observability Platform by G2 for the 4th consecutive quarter. See our G2 reviews here!
Monte Carlo Named to G2's Best Software Products of 2026.
Monte Carlo was featured on Database Trends and Applications (DBTA’s) Trend‑Setting Products for 2025!
We are super proud to be named the 2026 Best Place to Work by Built In!