Interested in this AI/ML Engineer role at Cerby?
Apply Now →Skills & Technologies
About This Role
About Cerby
At Cerby, security is everyone's business.
Cerby extends your security perimeter to include your disconnected applications, providing identity automation and eliminating manual processes. It's one of the biggest blind spots in enterprise security, and we're the team closing it. If you want to work alongside the team solving one of the hardest, most overlooked problems in security, you're in the right place.
Founded in 2020, Cerby is backed by leading investors and trusted by enterprises across the globe.
OVERVIEW & IMPACT
Every application Cerby protects needs Cerby to know how it works — its API, or the clicks behind its login, password rotation, MFA setup, or access change — and that knowledge breaks whenever a vendor redesigns its site or changes its API. We are looking for a Staff AI Engineer to own the AI agents that onboard new applications and repair automations when they drift. You will start with two agent systems we have already built and benchmarked:
API catalog generation: reads a vendor’s public API docs in a headless browser and produces a validated OpenAPI spec, with per-job cost ceilings and an accuracy benchmark.
Browser workflow generation: performs a task in a SaaS app’s web UI and writes a replayable automation workflow, handling MFA, one-time codes, and CAPTCHAs along the way.
Your job is to take them to production, make them self-healing, and set the direction for agentic automation at Cerby. These agents handle real customer credentials and browse untrusted sites, so security is part of the job, not an afterthought.
KEY RESPONSIBILITIES
Ownership and Production
- Own agentic onboarding and self-healing end to end: architecture, roadmap, and on-call once live.
- Take the existing systems to production on durable workflows (Temporal), with the observability to run them.
Self-Healing Automation
- Detect drift — a changed login page, a moved button, a renamed API field — from failed runs, before customers notice.
- Build agents that diagnose the break, repair the workflow or spec, and re-validate the fix against real runs before it goes back into service.
- Decide what heals automatically and what needs human review.
Evaluation and Cost
- Own the benchmarks for generated specs, workflows, and repairs, and make “good enough to ship” a measured threshold.
- Own cost and latency per output, choosing between frontier and open-weight models on measured accuracy versus cost.
Security
- Own the threat model: prompt injection from page content, credential isolation, token handling, sandboxed browsing, and egress.
- Keep credentials out of prompts, logs, queues, and stored run state.
Collaboration
- Partner with the integrations, automation-runtime, and platform teams; write the design docs they build on, and mentor contributors.
QUALIFICATIONS & REQUIRED SKILLS
Experience
- You have shipped an LLM agent with tool use that ran unattended for real users, and owned a backend system in production.
Technical Skills
- Strong in Python or TypeScript, and productive in both.
- LLM agents and tool use: agent loops, structured outputs, retries, and the failure modes they create.
- Eval discipline: you have built benchmarks or eval harnesses and used them to make decisions.
- Depth in browser automation (Playwright or similar) or backend and API-integration systems, and comfort in the other.
- Distributed systems: queues, idempotency, and durable workflow engines (Temporal, Step Functions, or similar).
- Security judgment for systems that handle secrets, including agent-specific threats such as prompt injection.
Desirable
- Temporal in production; Pydantic AI or a comparable agent framework.
- Open-weight model serving (Fireworks, Together, Bedrock) and LLM cost modeling.
- Computer-use agents or browser extensions (Chrome MV3); OpenAPI tooling.
- Identity, IAM, or credential-management experience; AWS and Terraform.
Soft Skills
- Clear technical writing and trade-offs other teams can depend on.
- You take an early system to production without waiting to be told how, and care that it keeps working after launch.
WHAT SUCCESS LOOKS LIKE
- 6 months: both systems run in production for real workloads, with improving error rates and cost per output, and drift is detected automatically.
- 12 months: onboarding a new application is predominantly automated, and most drift-driven breakages heal without a human.
Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Cerby, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills Required
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Senior-level AI roles across all categories have a median of $230,000.
Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.
Cerby AI Hiring
Cerby has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in Remote, US.
Remote Work Context
Remote AI roles pay a median of $188,000 across 2,811 positions. About 6% of all AI roles offer remote work.
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.
The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.