Senior Machine Learning Engineer

We’re hiring an ML Engineer (P3) to build and ship the AI systems that power Checkr’s core products. This role sits on the ML team inside Checkr’s Data & ML organization within Engineering.

Checkr runs millions of background checks a year. The ML team builds the systems that make those checks faster, more accurate, and cheaper to operate: document processing, charge classification, entity resolution, and in-product intelligence. These are production services that Product Engineering depends on daily.

This is not a research role or a notebook role. You’ll own ML services end-to-end: design them, code them, deploy them, monitor them. We need someone who writes production software, builds with LLMs and APIs as first-class tools, and can tell the difference between working code and AI slop. If you’ve spent the last few years building AI-native software and you care deeply about engineering craft, we want to talk.

This role sits in the central Data & ML team within the Engineering organization. You will partner daily with Product Engineering, Product, and cross-functional teams. You’ll also contribute to Checkr’s broader AI strategy, including our initiative to deploy our agentic fleet and build scalable context with our semantic layer.

We are looking for someone based in San Francisco who has built ML systems in fast-moving, impact-first environments. Less process, more shipping. Less paperwork, more results.

Build and deploy ML/AI services. Design, develop, and ship ML models and AI systems that Product Engineering teams rely on. You write the model code, the API layer, the monitoring, and the tests. Not notebooks; production services.

Design with LLMs and APIs. Use LLM APIs (OpenAI, Anthropic, etc.) as building blocks in production systems. You know when to call an LLM, when to fine-tune, when to use a classical model, and when to write a rule. You think about cost, latency, and quality together.

Ship production software. Write clean, well-structured code with solid OOP, proper abstractions, error handling, and tests. Your code gets reviewed by SWEs and passes. CI/CD is how you work, not something you bolt on at the end.