MLOps Engineer hiring kit

Every step to hire the engineer who moves models from a notebook into production and keeps them healthy once they are live.

About this kit — the 5Ws

An MLOps engineer owns the path a model takes from a data scientist's notebook to live traffic, and everything that keeps it working afterwards: packaging and deploying it, versioning the model and the data it learned from, watching for drift and falling quality, keeping serving cost and latency in check, and leading the response when a prediction goes quietly wrong. The job sits between machine learning and platform engineering. A good hire cares less about which orchestration tool is fashionable and more about whether a bad release can be undone in minutes, and whether anyone would notice that the data feeding a model changed shape last Tuesday.

Calibrated for:: Mid-level to senior individual contributors who have already run software in production; on-call experience with any live system is a better foundation than research depth.
Timeline:: Set an approval-to-offer target at intake, allowing for panel availability, candidate adjustments, references and any lawful checks.

Who: Engineering leaders and recruiters at companies that already run models in production, or are about to, and need one person to own deployment, monitoring and rollback for them.
What: Use this kit to agree what production-ML ownership looks like, test how candidates diagnose a quietly degrading model, interview against the same rubric, and time how the search itself ran.
When: Pick it up once more than one model is live, or one model has failed silently and nobody owned the fix, and carry it through from approving the role to reviewing how the search went.
Where: Technology teams serving machine learning models to real users or internal systems.
Why: A shared work sample and rubric give every candidate the same chance to show how they find the real cause of a degraded model, decide what to roll back, and design the monitor that would have caught it sooner, instead of comparing tool lists on a CV.

The competency model · 6

Use these competencies to compare job-related evidence. Review any apparent gap in a must-have before deciding.

Deployment and rollback engineeringMust-have · 20
Ships a model version through staged steps with clear gates, and can return to the last known-good state quickly, including the feature code and configuration that went out with it, not just the model file.
Monitoring and drift detectionMust-have · 20
Watches what goes into a model and what comes out, not only whether the endpoint is up; sets alerts that track real quality changes, and knows what each signal can and cannot show when true outcomes arrive late.
Versioning and reproducibilityMust-have · 15
Can say exactly which code, data snapshot, features and settings produced the model serving traffic today, and can rebuild or replay it when a question comes up weeks later.
Incident response and communicationMust-have · 15
Contains a model incident calmly, decides between rollback, fallback and waiting on evidence, keeps the people affected informed in plain words, and turns the review into changes that stick.
Pipeline automation and testingCan learn · 15
Turns hand-run training and release steps into automated pipelines with checks at each stage, so a broken data batch or a bad change fails early and loudly rather than reaching production.
Serving cost and latencyCan learn · 15
Knows what each model costs to serve and how fast it answers at the slow end, not just on average, and changes hardware, batching or model size only after checking quality still holds.

What's required and what's optional

Your hiring journey for MLOps Engineer. Select a stage to jump to it.

Required for every hire
Optional — use when it adds evidence
AI boost — a big drafting win
Colour = phase

Phase 1
Plan
1. 01Plan the roleRequired
2. 02Agree successRequiredAI boost
Phase 2
Attract
1. 03Write the jobRequiredAI boost
2. 04Find candidatesOptionalAI boost
Phase 3
Select
Phase 4
Decide
Phase 5
Onboard & learn
1. 12Help them settle inRequired
2. 13Measure time to hireRequiredAI boost

AI drafts, people decide: Use AI to draft, rewrite and summarise your own material — never to rank, score, screen out or decide on candidates, and never with a candidate's personal data.

Plan

Attract

Select

Decide

Onboard & learn

Solid = required · dashed = optional · arrow keys move between steps

Stage 1 of 13Required

0 of 3 done

Plan the role

Workforce planning and requisition approval

Who runs it: Hiring manager + finance / HR business partner
Done when: An approved requisition with a written business case, budget and a named decision-maker.

Key tool

Answer these before the role is approved

1Which models will this person deploy and watch in their first year, and which ones drive an automatic decision rather than a suggestion?
2When a model last got worse, how long passed before anyone noticed, and who noticed first?
3Could someone on the platform or site reliability team grow into this with time set aside and a mentor?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the business case and the build / borrow / buy comparison. The decision, the budget and the sign-off stay with people.

Show the prompt and the checks

Describe: You are helping a hiring manager write a business case for a MLOps Engineer role. Context: I will paste the problem the hire solves, the work it involves, the capacity we already have and the time we have. Produce: (1) a one-sentence problem statement in business terms; (2) a build / borrow / buy comparison with the strongest argument for each; (3) the questions a finance partner would ask; and (4) a short recommendation with the evidence it rests on. Use British English and plain language. Do not invent figures — leave [brackets] where I need to supply numbers. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check every number and claim against your own notes and strike anything the draft assumed. Make sure 'buy' is argued from ongoing work, not from a job title.
Diligence: The hiring manager owns the final case and the budget request. No candidate information belongs here; AI drafts the case, people decide whether to open the role.

Don't miss: Expecting this person to also build the models. If most of the work is choosing features and training, you want a machine learning engineer; if it is getting models live and keeping them healthy, you want this role.

Framework

Build · Borrow · Buy

Before opening a role, decide whether to build the capability in your current team, borrow it (contractor, agency, partner), or buy it (a permanent hire).

Write the problem the hire solves in one sentence, in business terms — not the job title.
Test Build: could an existing person grow into this within the time you have?
Test Borrow: is the need time-boxed, or does it end once a system is shipped?
Choose Buy only when the work is ongoing, core to the product and nobody inside can absorb it.
Record the decision, the budget and the one person who signs off the final hire.

Why it works: Writing the build, borrow or buy decision down exposes a vague or temporary need before it becomes a permanent requisition — and gives every later stage an anchor to check against.

• Name the decision-maker, usually the leader who owns platform or machine learning infrastructure.

Is this a dedicated role?

Decide whether the work is sustained and substantial enough for a dedicated owner by writing down the workload, the risk, the capacity you already have and the outcomes you expect.

Answer these before the role is approved

1.Which models will this person deploy and watch in their first year, and which ones drive an automatic decision rather than a suggestion?
Listen for: Named models, where their output goes, and which ones act without a person checking.
Red flag: 'We'll have lots of models eventually' with none live or scheduled.
2.When a model last got worse, how long passed before anyone noticed, and who noticed first?
Listen for: An honest timeline. If customers or another team spotted it first, that gap is the case for the hire.
3.Could someone on the platform or site reliability team grow into this with time set aside and a mentor?
Listen for: A named person and a realistic path, or a clear reason why that would leave another gap.
4.Is the work ongoing, or does it end once one deployment pipeline exists?
Listen for: New models arriving and existing ones needing care point to a permanent role; one pipeline built and handed over may suit a contractor.
5.What does an unwatched model cost us each month this seat stays empty?
Listen for: A concrete consequence, such as wrong prices shown, wasted serving spend or data scientists doing deployments by hand.

Build, borrow or buy?

Build: give a platform or site reliability engineer protected time and a mentor who has run model serving, starting with one model.
Borrow: bring in a contractor to set up a deployment pipeline and monitoring for the riskiest model, with a written runbook and a handover date.
Buy: hire a permanent MLOps engineer once several models need ongoing release, monitoring and rollback, and data scientists are spending real time on deployments.

Watch out for

Opening the role when only one model exists and it changes twice a year; a platform engineer with some guidance may cover that.

Stage 2 of 13Required

0 of 2 done

Agree success

Intake meeting and competency model

Who runs it: Recruiter + hiring manager
Done when: A signed-off competency model: 5–7 competencies, each marked must-have or trainable, with weights.

Key tool

Ask the hiring manager

1Which of the systems or areas this person will own worries you most, and why?
2When something there went wrong recently, how did you find out?
3In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
4Who will they work with most closely?
5What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.

AI as an advantageAI boost4D framework

Delegate: Hand AI your raw intake notes to turn into a draft competency model. Choosing the must-haves and the weights stays with the hiring manager and recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager build a competency model for a MLOps Engineer role. Context: I will paste the notes from our intake meeting, including the 12-month outcomes and what the hiring manager worries about most. Produce a table of 5–7 observable competencies with, for each: a one-line definition; whether it is a must-have or trainable, with the reason; what evidence of it looks like in real work; and a suggested weight so the weights total 100. Use British English and inclusive wording, avoid years-of-experience or named employers as evidence, and keep every competency job-related. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each competency is observable and job-related, that nothing describes a type of person rather than the work, and that trainable items haven't been marked must-have.
Diligence: The hiring manager signs off the final model and weights before anyone meets a candidate. No candidate data goes into the prompt; AI drafts, people decide.

Don't miss: Writing one cloud vendor's ML platform in as a must-have. The habits of versioning, gating and watching carry across vendors; the console layout does not matter.

Framework

Competency model (must-have vs trainable)

A short list of the observable capabilities the job needs, split into what the hire must bring on day one and what you will teach.

Start from the 12-month outcomes, then ask which capabilities produce them.
Keep 5–7 competencies. With more, interviewers struggle to score each one separately.
Mark each must-have or trainable. Only must-haves can count against a candidate.
Give each a weight so they sum to 100, agreed before anyone meets a candidate.
Write what evidence of each looks like, so interviewers know what they are listening for.

Why it works: Agreeing the criteria before meeting candidates stops the bar moving from one candidate to the next, and makes it harder for 'I'll know it when I see it' to decide the hire.

Core intake questions (ask for every role)

Book 45 minutes with the hiring manager before anything is advertised, and write the answers down.
Which of the systems or areas this person will own worries you most, and why?
When something there went wrong recently, how did you find out?
In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
Who will they work with most closely?
What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.
Who is on the interview panel, and is their time held for the next four to six weeks?

Questions specific to this role

1.If the model with the most traffic had to be rolled back right now, who would do it, and how long would it take?
Listen for: Whether a tested rollback exists. A vague answer means early months go on making releases reversible.
2.When true outcomes for your models arrive, such as a confirmed delivery time or a chargeback, how long after the prediction is that?
Listen for: The label delay, which decides how much monitoring must rely on inputs and output patterns rather than accuracy.
3.Who owns the upstream data your models depend on, and do they tell you before changing it?
Listen for: Whether data changes are announced or discovered. Undeclared changes call for stronger input checks and a data-contract conversation.

What success looks like in 12 months

Every production model can be rolled back to its last good version, and the team has rehearsed it at least once.
Input and output monitoring runs on each model, with alerts the on-call engineer trusts enough to act on.
Data scientists hand over a model through a repeatable pipeline instead of a bespoke deployment each time.
Serving cost and slow-end latency per model are tracked, with at least one measured reduction.

Watch out for

Treating Kubernetes depth as the core of the job when the team's real pain is that nobody notices a model going wrong.

Stage 3 of 13Required

0 of 3 done

Write the job

Job description and pay band

Who runs it: Hiring manager (content) + recruiter (publishing)
Done when: A published job description that states outcomes, the must-haves, how AI tools are used and the pay information the law requires.

Key tool

MLOps Engineer

We're hiring an MLOps engineer to own how models behind [product] reach production and stay healthy there. You'll build the release pipeline, version models and data, set up monitoring that catches drift before customers do, and lead the response when a model misbehaves, working with [data science/ML] and [platform] teams.

What you'll do

•Build and run the pipeline that takes a trained model through checks, staged release and full traffic, with a rollback that works when it is needed.
•Version models, training data snapshots, features and configuration so any live prediction can be traced to what produced it.
•Monitor model inputs, outputs and, when they arrive, real outcomes; tune alerts so they reflect quality rather than noise.
•Automate training and release steps with tests at each stage, so a bad data batch fails before it reaches users.
•Track and reduce serving cost and slow-end latency without letting quality slip.
•Take part in on-call for model serving, lead model incident reviews and write the runbooks others follow.

What you need

•You have deployed a model to production and been able to roll it back, not only handed it to someone else to run.
•You have built or extended monitoring for a live model and can describe a problem it caught, or one it missed and what you changed.
•You can show how a model you ran could be traced back to the versioned code, data and settings that produced it.
•You have handled a production incident on any live system and can walk through what you did and what changed afterwards.

Nice to have

•Experience with container orchestration and infrastructure as code.
•Experience with a feature store or a model registry.
•Experience serving large language models or GPU-backed models.
•Awareness of applicable AI regulation, including logging and monitoring duties where relevant.

How we use AI tools

•We expect you to use approved AI tools where our policy allows, for example to draft pipeline code or runbooks, and to check what they produce before it touches production.
•You can tell when an AI assistant's suggested config change or query looks right but would alter what a monitor measures.
•AI tools are allowed in the work sample; tell us briefly which you used and what you checked yourself.

Pay

Salary range: [currency, minimum–maximum], plus [equity/bonus/benefits]. The range reflects [location/working pattern]. We place every offer within it using the same pre-set, job-related, gender-neutral factors — level and the number of production models they would own, depth of on-call and incident experience with live systems, breadth across deployment, monitoring and pipeline automation rather than one of them — never previous salary or negotiating style.

AI as an advantageAI boost4D framework

Delegate: Hand AI the first draft of the job description from your signed-off competency model. The must-haves, the pay range and the final wording stay with people.

Show the prompt and the checks

Describe: You are helping write an outcome-based job description for a MLOps Engineer role. Context: I will paste the competency model (must-have and trainable, with evidence), the 12-month outcomes, how the team uses AI tools, the location and working pattern, and the pay range. Produce: a summary paragraph that leads with the problem and what the hire will own; 'What you'll do' as outcomes, not tasks; 'What you need' containing only the must-haves; 'Nice to have' for the trainable items; 'How we use AI tools'; and a pay section that states the range. Use British English and inclusive, gender-neutral wording, avoid hype, and replace any 'X years' with the capability it stands for. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that 'What you need' contains only the must-haves, that no degree, employer or years requirement crept in, and that the pay range and location are exactly what was approved.
Diligence: The hiring manager owns the content and the recruiter owns publishing, including the pay information the law requires for each location. AI drafts the advert; people decide what it says.

Don't miss: Listing every tool in the MLOps landscape. A long stack list attracts people who have tried many tools and deters people who ran one well.

Stage 4 of 13Optional

0 of 3 done

Find candidates

Sourcing strategy

Who runs it: Recruiter / sourcer
Done when: A shortlist-ready pipeline from at least three channels, with outreach tracked.

Use when:: Inbound applications won't give you enough qualified candidates.
Skip when:: Your shortlist already comes from inbound applications or referrals.

Key tool

Search query

("MLOps" OR "ML platform" OR "model serving" OR "ML infrastructure") AND ("monitoring" OR "drift" OR "model registry" OR "rollback") AND ("production" OR "on-call" OR "deployed") AND (Python OR Kubernetes OR Terraform) NOT ("intern" OR "student")

First outreach message

AI as an advantageAI boost4D framework

Delegate: Hand AI the search queries and the first draft of the outreach template. Choosing channels, personalising to a candidate's public work and sending stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter source candidates for a MLOps Engineer role. Context: I will paste the must-have competencies, the kind of work we want evidence of, the channels we are using and the pay range. Produce: (1) one search query per channel, using OR for alternatives, AND for things that must all appear and NOT to exclude, with a one-line note on what each query looks for; and (2) a first-outreach template of under 120 words that opens with a [placeholder for something the candidate built], states the problem we are hiring to solve and the pay range, and ends with a low-pressure question. Use British English and inclusive wording. Do not refer to any specific person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the queries search for evidence of the work rather than job titles alone, and that the template claims nothing about the role or the pay you can't back up.
Diligence: The recruiter personalises every message to something the candidate actually built, and sends it. No names or profile data go into the prompt; AI drafts, people decide whom to contact.

Don't miss: Searching only for 'MLOps engineer' and missing the site reliability engineer who has quietly run the model-serving stack for two years.

Framework

Channel mix + evidence-first outreach

Spread sourcing across channels where the work is visible, and open outreach with the problem, not the perks.

Pick channels where candidates show their work, not only where they list job titles.
Write one search query per channel. OR joins alternatives, AND joins things that must all appear, NOT excludes. Keep the version that works best.
Personalise the first line to something the candidate actually built or wrote.
Lead with the problem and the pay range. Save the perks for later.
Track reply rates by channel each week and drop the channel that isn't working.

Why it works: Searching for evidence of the work can surface candidates whose current title differs from the vacancy, or whose CV undersells what they have done.

Sourcing basics

Adapt the search query for each platform — the same words behave differently on each site.
Candidates with adjacent titles may have relevant evidence. Search for the work and outcomes the role needs, not the current title.
Channel activity is a lead, not evidence. Review linked work and examples against the written competencies.

Where to look

Public repositories for deployment, serving and monitoring tooling

Contributions to these projects show how someone handles versioning, release safety and observability in code you can read.

Incident reviews and engineering blog posts about models failing in production

A written account of a degraded model shows how the author found the cause and what they changed, which is close to the job itself.

Referrals from your platform, data and site reliability engineers

People who shared an on-call rota with a candidate can point you to the incidents and rollbacks worth asking about.

LinkedIn and similar networks, searched for model deployment and monitoring work under platform and reliability titles

Much of this work is done by people whose title never mentions MLOps, so search the described work, not the title.

Meetups and talks on ML platforms and model serving

Speakers and active questioners often run serving stacks themselves, and their talks give you something specific to discuss.

Boolean search string

("MLOps" OR "ML platform" OR "model serving" OR "ML infrastructure") AND ("monitoring" OR "drift" OR "model registry" OR "rollback") AND ("production" OR "on-call" OR "deployed") AND (Python OR Kubernetes OR Terraform) NOT ("intern" OR "student")

First outreach message

Hi [name], [specific detail from their talk, repo or write-up] stood out. At [company], our [model name] went quietly wrong last quarter and we only learned from [how you found out]. We're hiring an MLOps engineer to make sure the next one is caught early and undone fast, paying [range]. Would a 20-minute chat about what that would involve be useful?

Stage 5 of 13Required

0 of 3 done

Check applications

Application screening

Who runs it: Recruiter
Done when: Every application reviewed against the same written knockouts within five working days.

Key tool

Reject only if one of these is missing

•Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
•Describes at least one model they deployed to production or ran in production after someone else trained it.
•Has operated a live software system of any kind, with some share of responsibility when it broke.

AI as an advantage4D framework

Delegate: Hand AI the job of turning your written knockouts into a consistent checklist with reason codes. Reviewing each application stays with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter prepare an application-screening checklist for a MLOps Engineer role. Context: I will paste the must-have competencies and our written knockout criteria. Produce: (1) each knockout as a yes/no question answerable from an application alone; (2) a short list of reason codes for a 'no'; and (3) a note of any criterion that looks like a proxy — a degree, employer brand or employment gap — rather than a job-related requirement, with a suggested rewrite. Use British English. Do not evaluate any applicant and do not ask for applicant details. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each question is binary and job-related, and that every flagged proxy has been removed or justified in writing.
Diligence: A person reviews every application against the checklist and records the reason. Never paste CVs or applicant details into an AI tool, and never let a tool screen anyone out — in New York City and the EU that can bring automated-decision rules into play.

Don't miss: Marking down someone who used a different orchestrator or cloud from yours; ask how they gated and rolled back releases instead.

Framework

Knockout criteria

A small set of yes/no requirements, written in advance, applied to every applicant the same way.

Derive knockouts only from must-have competencies and genuine legal requirements.
Keep them binary and answerable from the application itself.
Apply them in the same order to every application and log the reason for each rejection.
Do not use proxies such as university, employer brand or employment gaps as knockouts.
Anything ambiguous gets a second review or moves forward to the skills stage.

Why it works: Early screening rejects people before richer evidence exists, so its criteria need the most care. Written criteria make decisions reviewable — but each one must also be job-related, applied consistently and checked for unjustified adverse impact.

Screening rules

Do not use degrees, employment gaps or certifications as filters unless they are demonstrably job-related and justified for this role.
Judge the claims in a CV, not how polished it is — a well-written CV may or may not have had AI help, and either way it is the evidence that matters.

Knockout criteria

Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
Describes at least one model they deployed to production or ran in production after someone else trained it.
Has operated a live software system of any kind, with some share of responsibility when it broke.

Green flags

Mentions a rollback, a staged release or a canary for a model, not only for application code.
Describes monitoring that went beyond uptime, such as input checks, prediction distributions or delayed accuracy.
Links to a pipeline, a runbook, an incident write-up or code that can be reviewed.

Red flags

Lists a dozen pipeline and serving tools but cannot say what happened after any model launched.
Describes deployment as copying a model file to a server, with no versioning or way back.
Every project is a tutorial or course exercise with no live users, which is reasonable early in a career but a mismatch at this level.

Watch out for

Reading a certification in a cloud ML service as proof of production ownership; it shows study, not a model kept healthy under load.

Compliance checkpointNew York CityEU

For a New York City employment decision, work out whether a tool is an 'automated employment decision tool' (AEDT) under Local Law 144 — one that uses covered techniques to substantially assist or replace a discretionary decision. Before using a covered tool, make sure an independent bias audit was completed no more than a year earlier, publish the required summary, and give covered candidates or employees the required notice at least ten business days before use. In the EU, the AI Act (Annex III) lists AI used to recruit, filter applications or evaluate candidates as high-risk, subject to the Article 6(3) exception; the related obligations apply from 2 December 2027 under the amended timetable. A manual screen does not exempt an AI tool used elsewhere in the process.

Sources: NYC DCWP — Automated employment decision tools · EU AI Act — consolidated Regulation (EU) 2024/1689 · checked 2026-09-25

Stage 6 of 13Optional

0 of 3 done

Recruiter call

Recruiter screen

Who runs it: Recruiter
Done when: A 20–30 minute call that confirms logistics, motivation and one or two must-have signals.

Use when:: You are hiring at volume, or pay and logistics need confirming early.
Skip when:: You have only a handful of applicants — fold the pay and logistics questions into application screening instead.

Key tool

Ask every candidate, in this order

1Tell me about the last model you helped get into production. What was your part, and what happened after it went live?
2Have you ever had to undo a model release? How did you decide, and how long did it take?
3How would you have known if that model started making worse predictions?
4Our range for this role is [range]. Does that work for you?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the screening-call script and its evidence anchors. Running the call and taking the notes stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write a 20–30 minute structured screening call for a MLOps Engineer role. Context: I will paste the must-have competencies, the logistics we need to confirm (location, working pattern, notice period) and the pay range. Produce: an opening that explains the process, the timeline and the pay range; 4–6 questions in a fixed order, each with one line on what a strong answer contains; and a closing that asks whether the published range works. Use British English and inclusive wording. Do not include questions about salary history, age, family, health or any other protected characteristic. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that every question is job-related and lawful, that the pay question asks whether the range works rather than for history, and that the anchors describe evidence, not impressions.
Diligence: The recruiter asks the same questions of everyone and writes the notes. No candidate details go into the prompt; AI drafts the script, people run the call and decide.

Don't miss: Asking the recruiter to judge monitoring design. Their part is motivation, logistics and whether the candidate can describe their own work clearly; the panel judges the craft.

Framework

Structured screening call

The same short set of questions for every candidate, with notes taken against what a strong answer contains.

Open by explaining the process, timeline and pay range. No surprises later.
Confirm logistics: location, working pattern, notice period and whether the range works for them.
Ask the same 4–6 questions in the same order, and note evidence, not impressions.
Leave time for the candidate's questions. Don't score their questions unless they test a written, job-related competency.
Decide within 48 hours and tell the candidate either way.

Why it works: Using the same questions and written evidence anchors makes answers easier to compare, and a short, predictable call respects the candidate's time.

Screening call basics

Set the decision timetable before sourcing and tell candidates when to expect each update.
Ask every candidate what draws them to this particular role, and listen for interest in the work described rather than the title.
Confirm notice period and whether they are in other processes, so you can plan the timetable.
End every call by asking whether the published pay range works — never ask for salary history.

Recruiter screen questions

1.Tell me about the last model you helped get into production. What was your part, and what happened after it went live?
Listen for: A specific model, the candidate's own steps and some account of life after launch.
Red flag: Can only describe what the data science team did, or stops the story at launch day.
2.Have you ever had to undo a model release? How did you decide, and how long did it take?
Listen for: A real rollback or a clear account of how one would have worked on their system.
Red flag: Has never considered how a model release would be reversed.
3.How would you have known if that model started making worse predictions?
Listen for: Any signal beyond 'the service was up', such as input checks, output patterns or delayed outcome data.
Red flag: Relies only on users or the business noticing.
4.Our range for this role is [range]. Does that work for you?
Listen for: A clear answer on whether the published range works. Don't ask for salary history — this process sets pay from the published band and pre-set, job-related factors.

Compliance checkpointUS (state and city)EU

Don't ask for salary history. In the EU, national laws implementing Article 5(2) of Directive (EU) 2023/970 must prohibit the question. US rules vary, but jurisdictions including California and New York prohibit employers from seeking salary history. Ask whether the published range works instead.

Sources: EU Pay Transparency Directive 2023/970, Article 5 · California Labor Commissioner — salary history · New York State DOL — salary history ban · checked 2026-09-25

Stage 7 of 13Required

0 of 3 done

Work sample

Skills assessment / work sample

Who runs it: Hiring manager (design) + recruiter (logistics)
Done when: Every shortlisted candidate completes the same job-shaped task, marked against criteria written in advance.

Key tool

Find why a delivery-time model quietly got worse

A parcel company serves a model that estimates delivery times. Over two weeks, late deliveries against the estimate have crept up, yet the endpoint has stayed healthy. You get three files: a monitoring export (day-by-day prediction distributions, input feature summaries including missing and default-value counts, and late-delivery counts as outcomes arrive), a deploy log showing a new model version released partway through, and a data-change log from the upstream team. Work out what really caused the decline, propose what to roll back or fix and in what order, and design the monitor that would have caught it on the first day. Plan for up to three hours of work, as set out in the timebox sent with this brief, and submit within five working days of receiving the files unless you agree a different date with us.

Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the work-sample brief and its marking sheet. Choosing the task, setting the timebox and marking stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager design a work sample for a MLOps Engineer role. Context: I will paste the competency model, a real problem the team solved recently with anything confidential removed, the timebox, and our AI-tool policy for candidates. Produce: a candidate-facing brief (what to do, what to hand in, the time cap, how to request an adjustment, which AI tools are allowed and how to report their use); and a marking sheet with 4–6 criteria tied to named competencies, each with what a 1, a 3 and a 5 look like. Use British English and plain, inclusive wording. Do not design anything that needs more than the stated time. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the task fits the timebox, that every criterion maps to a competency, and that the brief gives all candidates the same starting materials.
Diligence: The hiring manager owns the task and the criteria, and people mark every submission. Do not paste candidate submissions into an AI tool for scoring; AI drafts the brief, people mark and decide.

H-EvaluateH-Evaluate can generate a job-specific assessment from your job description, so you don't have to build the task by hand.How H-Evaluate helps →

Don't miss: Making the obvious suspect the real cause. The sample only tests diagnosis if the newest deploy is a plausible but wrong answer.

Framework

Work-sample test

A small, realistic slice of the job, marked against criteria written in advance. Give candidates equivalent materials and arrange reasonable adjustments where required.

Take a real problem the team solved recently and shrink it to fit the timebox.
Write the marking criteria first, tied to the competency model.
Timebox honestly — for take-home work, a few hours at most — and say so in the brief.
State the AI-tool policy in writing. Where the job permits these tools, use equivalent conditions in the assessment and evaluate how candidates verify their output.
Mark without CV details where you can, and have two people mark borderline submissions.

Why it works: A well-designed work sample gives direct evidence of job-relevant skill rather than a proxy for it, and gives candidates a realistic preview of the work.

Assessment rules for every candidate

State the planned time cap and how to request an adjustment. At the agreed stopping time, ask candidates to note what they would examine next and what they left out — never reward unpaid overtime.
Give every candidate the same starting materials, and use a second marker for borderline submissions.
Say in writing which AI tools are allowed and ask candidates to tell you how they used them.
Invite every candidate to ask for adjustments, and answer each request promptly.
Pay for anything the task costs the candidate to run, such as model or cloud usage.

The work sample

Find why a delivery-time model quietly got worse

Timebox: Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

What the candidate hands in

Your diagnosis: what caused the decline, the evidence in the files that shows it, and why the most obvious suspect is or is not to blame.
A rollback and repair plan in order, with what you would check after each step to confirm it worked.
One monitor or alert you would add, with what it measures, what would trigger it and who it would notify.

Marking criteria (write these first)

The decline is traced to the change that actually started it, with the timing in the files used as evidence rather than assumed.
The plan recognises whether rolling back the model alone would restore quality, and covers the data side if it would not.
Each step in the plan has a concrete check, not just 'monitor closely'.
The proposed monitor would have fired on the first affected day using signals available before outcomes arrived.
The write-up is clear enough that an on-call colleague could act on it without the author present.
The closing note states what remains uncertain and what the candidate would look at next with more time.

Adjustments: Candidates may ask for more time, or to talk through the files live with an interviewer instead of writing it up. Everything opens in a spreadsheet or text editor; no cloud account or paid tool is needed.

Watch out for

Asking candidates to stand up a full serving stack from scratch; it measures free time and cloud credit, not judgement.

Compliance checkpointUSGreat BritainEU

In the US, covered employers must provide a reasonable accommodation to a qualified applicant with a disability unless it would cause undue hardship (ADA). In Great Britain, the Equality Act 2010 requires reasonable adjustments in recruitment. In the EU, the duty comes from national equality law. Don't ask for more medical information than the law allows.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Stage 8 of 13Required

0 of 3 done

Structured interviews

Structured interview loop

Who runs it: Interview panel (named in advance)
Done when: Every competency has a lead interviewer and at least one second source of evidence, with the same questions for every candidate.

Key tool

Interview questions by pillar

Free in this kit: Domain questions for every round. The other three pillars and the AI-fluency check are measured by H-Evaluate.

Free in this kit

An MLOps or ML platform engineer from outside the hiring team, who has read the submission closely · Monitoring and drift detection · Versioning and reproducibility

1.Whatever timeline your reading of the monitoring export, deploy log and data-change log produced, walk me through it. What evidence in those files pointed you towards the model, the data or both, and what finding would have changed your conclusion?
Monitoring and drift detection
Good answerBuilds the timeline from the files rather than from the order of events they expected, ties each claim to a specific signal such as default-value counts, prediction distributions or the deploy time, separates what the files show from what they infer, and names a concrete finding that would have pointed the other way.
Weak answerBlames the newest change because it is the latest one, asserts a cause the files do not support, or cannot say what evidence would alter the diagnosis.
2.For a model whose real outcomes only arrive weeks later, what would you monitor in the meantime, and what would each of those signals fail to catch?
Monitoring and drift detection
Good answerProposes input checks, prediction-distribution tracking and a small sample of faster proxy outcomes, and is candid that each one can miss a change that leaves inputs looking normal.
Weak answerWaits for accuracy figures, or treats any single drift statistic as proof of quality.
3.Someone asks you to show exactly what produced a prediction the model served on a particular day last quarter. What must have been recorded for you to answer, and where does that usually break down?
Versioning and reproducibility
Good answerLists the model version, feature pipeline code, the feature values or data snapshot at serving time, configuration and dependencies, and names a realistic gap such as features computed from tables that have since been overwritten.
Weak answerSays the model file is versioned so the answer is easy, ignoring the data and feature code.

Optional follow-ups (2)

4.Your drift alert fires several times a week and the on-call team has started ignoring it. What would you change about it?
Monitoring and drift detection
Good answerChecks which alerts preceded a real quality drop, ties thresholds to past behaviour and impact, separates warning from paging, and gives each alert an owner and a first action.
Weak answerRaises the threshold until it stops firing, or turns the alert off.
5.Two data scientists say they trained on 'the same dataset' but get noticeably different models. How would you establish whether the data really was the same?
Versioning and reproducibility
Good answerCompares snapshot identifiers or content hashes, the as-of time of each query, filters and preprocessing versions before looking at training settings.
Weak answerAssumes the training code or random seed is to blame without checking the data.

AI as an advantageAI boost4D framework

Delegate: Hand AI the drafting of probe questions and strong / weak anchors for one competency. Asking, listening and scoring stay with the interviewer.

Show the prompt and the checks

Describe: You are helping an interviewer prepare a structured technical interview for a MLOps Engineer role. Context: I will paste one competency, its evidence description and the core question we ask every candidate. Produce: four probes in this fixed order — what would you do, why that choice, what else did you consider, how would you know it worked — tailored to the question; a one-line description of a strong answer and of a weak answer; and two follow-ups to use only if time allows. Use British English and inclusive wording. Keep everything about the work, nothing about the person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the probes test the named competency rather than trivia, that the anchors describe observable evidence, and that no question touches a protected characteristic.
Diligence: Interviewers ask the same core questions of every candidate and score alone against the rubric. Interview notes and candidate names never go into an AI tool; AI drafts the questions, people interview and decide.

H-EvaluateH-Evaluate can add evidence on Cognitive, Situational judgement, Behavioural and AI fluency for your panel to review alongside these interviews.How H-Evaluate helps →

Don't miss: Rewarding the candidate who names the most monitoring tools over the one who explains what a signal would actually reveal.

Framework

Structured technical interview

Every candidate gets the same job-specific questions, each interviewer leads on specific competencies, and every answer is probed with the same four follow-ups: what would you do, why, what else did you consider, and how would you know it worked.

Give each competency a lead interviewer, plus a second source of evidence — the work sample, another round or an independent marker. Avoid asking the same thing twice, but never let one person's view be the only evidence for a critical competency.
Ask the three core questions for your round, in order, for every candidate. Use an optional follow-up only if there is time.
Probe each answer: why that choice, what else they considered, and how they would know it worked — until you hear the candidate's own technical decision.
Take notes on evidence during the interview. Don't rate until it's over.
Fill in your interviewer sheet and submit it before you talk to any other interviewer.

Why it works: Structured interviews make answers comparable: every candidate faces the same job-related questions and is scored against the same anchors.

Interview rules

Use the same core questions in the same order for every candidate.
In the work-sample review, understand the candidate's decisions against the rubric — don't turn it into a debate about your preferred solution.
Avoid trivia disconnected from a real job decision. Use a realistic debugging, design or evaluation problem instead.

Watch out for

Letting the design round turn into a tour of the interviewer's favourite platform rather than the candidate's reasoning.

Compliance checkpointUSUKEU

Don't ask about protected characteristics — such as age, disability, pregnancy or family plans, religion, race or nationality — unless applicable law permits the question for a specific, necessary, job-related purpose, and HR or counsel has confirmed that basis beforehand. Ask only whether the candidate can meet the role's work-authorisation requirements. If a candidate volunteers protected information, don't probe; record only what is lawfully needed, keep it separate and restrict access.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Where to find more interview questions

Use web question banks for inspiration only: ask every candidate the same job-related questions, check each one against this kit's competencies, and never ask about protected characteristics. Don't reuse this kit's work sample from a public bank — candidates can find questions that circulate online, so a widely posted question tests preparation more than skill.

Show 7 sites

US OPM — Structured interviews(opens in a new tab)
US federal guidance on building structured interviews, with a guide, training material and sample questions with rating scales.
FreeFor interviewers
Acas — Interviewing job applicants(opens in a new tab)
UK public guidance on preparing fair interviews, asking applicants the same questions and avoiding discriminatory ones.
FreeFor interviewers
Workable — Interview questions library(opens in a new tab)
Sample interview questions for employers, listed by job role, including machine learning, data and engineering roles.
FreeFor interviewers
Indeed for Employers — Interview questions(opens in a new tab)
Sample interview questions for employers by job title and skill, with notes on what to look for in answers.
FreeFor interviewers
Tech Interview Handbook(opens in a new tab)
Open-source software-engineering interview preparation: coding, system design and behavioural questions.
FreeFor candidates and interviewers
Chip Huyen — Machine Learning Interviews Book(opens in a new tab)
Free online book with knowledge questions on maths, computer science and machine learning, grouped by difficulty.
FreeFor candidates and interviewers
Blind — Interview questions channel(opens in a new tab)
Anonymous posts by tech workers about questions they report being asked. Unverified; some content needs sign-in.
Free, some content needs sign-inCandidate reports, unverified

Links checked 2026-10-05. External sites; we don't control their content.

Stage 9 of 13Required

0 of 2 done

Compare evidence

Scoring, calibration and debrief

Who runs it: Hiring manager (chairs) + panel
Done when: A documented hire / no-hire decision traceable to scored evidence against the competency model.

Key tool

Interactive scorecard

Score one candidate against the rubric. Everything stays in your browser. Download it as a spreadsheet for your records.

Deployment and rollback engineering Must-have

Weight

What do 1, 3 and 5 look like?

1: Deploys by hand with no staged release and no clear way back.
3: Uses a staged release and can roll back the model, but forgets features or configuration that changed with it.
5: Designs gated releases with automatic rollback triggers and rehearses the way back before it is needed.

Monitoring and drift detection Must-have

Weight

What do 1, 3 and 5 look like?

1: Watches only uptime and error rates; would not notice a model getting worse.
3: Monitors inputs and outputs when prompted, but alerts are noisy or not tied to impact.
5: Builds monitoring that catches quality changes before outcomes arrive, knows each signal's blind spots, and tunes alerts people trust.

Versioning and reproducibility Must-have

Weight

What do 1, 3 and 5 look like?

1: Cannot say which data or code produced the live model.
3: Versions models and code; data snapshots and feature logic are partly tracked.
5: Can rebuild or replay any served model from versioned code, data, features and settings, and spots where that chain is weak.

Incident response and communication Must-have

Weight

What do 1, 3 and 5 look like?

1: Acts without weighing impact, or keeps affected teams in the dark.
3: Follows a runbook and keeps people updated when reminded.
5: Makes clear containment calls under pressure, communicates plainly and on time, and leads reviews that change things beyond their own team.

Pipeline automation and testing Can learn

Weight

What do 1, 3 and 5 look like?

1: Training and release steps are run by hand from notes.
3: Pipeline is automated with some tests, but bad data can still reach late stages.
5: Pipeline fails early on bad data or code, with cheap checks first, and data scientists can use it without help.

Serving cost and latency Can learn

Weight

What do 1, 3 and 5 look like?

1: Does not know what a model costs to serve or how slow its slowest responses are.
3: Tracks cost and average latency and knows the common ways to reduce them.
5: Watches the slow tail as well as the average, and changes hardware or model size only after checking quality holds.

Weighted score– / 5

AI as an advantage4D framework

Delegate: Hand AI the drafting of a blank debrief worksheet and agenda from the competency rubric alone. People add the evidence locally; the scores and the decision stay with the panel.

Show the prompt and the checks

Describe: You are helping a hiring manager prepare a debrief for a MLOps Engineer role. Context: I will paste the competency rubric only — the competencies, their weights and their 1, 3 and 5 anchors. Produce: (1) a blank debrief worksheet with one row per competency and empty columns for each interviewer's independent score, the evidence they cite, the spread of scores and an 'evidence gap?' box; (2) a 45-minute agenda: confirm every scorecard is in and reveal all scores at once, discuss the widest spreads using evidence only, review any must-have scored 1, then look at the weighted total and decide (hire, no hire or one targeted follow-up), and record the reasons; and (3) neutral questions the chair can ask to draw out evidence rather than adjectives. Leave every evidence and score cell empty. Do not suggest a score, a rating or a recommendation. Use British English. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet follows your rubric exactly — same competencies, weights and anchors — and that the agenda keeps independent scores hidden until the reveal.
Diligence: Interviewers fill in the evidence and scores locally, alone, before the debrief, and the panel decides together. Candidate notes and personal data never go into an AI tool; AI never scores, ranks or compares candidates.

H-EvaluateH-Evaluate gives you a report on each candidate's assessment evidence to bring into this debrief.How H-Evaluate helps →

Don't miss: Letting a strong platform design score cover for weak monitoring evidence; a candidate who deploys well but cannot spot drift misses the point of the role.

Stage 10 of 13Optional

0 of 2 done

Check references

References and background checks

Who runs it: Recruiter (references) + HR (checks)
Done when: At least two references that test specific competencies, plus only the checks that are lawful and relevant to the role.

Use when:: It is lawful where you hire, and specific evidence from a referee would change the decision.
Skip when:: Local law or company policy rules it out.

Key tool

Ask each referee

1When a model [candidate] looked after misbehaved, what did they do in the first hour?
2What did they build or change that made releasing models safer for the rest of the team?
3How did they work with the data scientists whose models they deployed?

AI as an advantage4D framework

Delegate: Hand AI the drafting of reference questions aimed at the competency the panel was least sure about. Choosing referees, making the calls and interpreting the answers stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write competency-based reference questions for a MLOps Engineer role. Context: I will paste the competency model and the one or two competencies where our evidence is thinnest — no candidate details. Produce: 3–4 questions per competency that ask for specific examples ('tell me about a time…') rather than ratings; an opening question about how the referee worked with the person and for how long; and a closing question about what their next manager could do to help them do their best work. Use British English and inclusive wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the questions ask for examples rather than opinions, that they stay on job-related competencies, and that none asks about health, family or other protected matters.
Diligence: References are taken with the candidate's consent and interpreted by people. Referee answers and candidate details never go into an AI tool; AI drafts the questions, people decide.

Don't miss: Accepting 'the platform was very stable' without asking what the candidate did to make it so.

Framework

Competency-based referencing

Treat references as a last structured conversation about the candidate's work, aimed at the competencies where your evidence is thinnest.

With the candidate's consent, ask for two people who saw their relevant work directly — ideally a former manager and a peer.
Accept suitable alternatives if a manager or peer isn't available, and never penalise a candidate for a former employer's no-reference policy.
Aim your questions at the one or two competencies the debrief was least sure about.
Ask for examples, not ratings. 'Tell me about a time they…' works here too.
Set the timing of each background check by the law and policy that apply.

Why it works: Generic reference questions tend to produce little job-related evidence. Asking for specific examples tied to the role's competencies turns referencing into something you can use.

Core reference questions and checks

Open with: 'How did you work together, and for how long?' — it tells you how much weight the rest can carry.
Ask: 'Tell me about a time something they owned went wrong. What did they do?'
Close every reference with: 'What should their next manager do to help them do their best work?'
Verify only claims that were material to the decision — don't verify a degree the role never required.
Run criminal-record checks only where the role justifies them and local law allows; many roles don't need one.
Schedule formal work-authorisation checks at the legally required time: before employment starts in the UK; for US Form I-9, Section 1 by the first day of paid work and Section 2 within three business days.

Reference questions specific to this role

1.When a model [candidate] looked after misbehaved, what did they do in the first hour?
Listen for: A specific incident and calm, sensible containment steps.
2.What did they build or change that made releasing models safer for the rest of the team?
Listen for: Lasting improvements others still use, such as a pipeline, monitor or runbook.
3.How did they work with the data scientists whose models they deployed?
Listen for: Signs of making deployment easier for others rather than acting as a gatekeeper.

Compliance checkpointUS

If a consumer reporting agency provides a background report, the Fair Credit Reporting Act requires a clear, stand-alone written disclosure and the candidate's written authorisation before you order it. Before rejecting someone because of the report, give them a copy and the FCRA summary of rights and a reasonable opportunity to review and dispute it before any adverse action; if you still reject, send a final adverse-action notice. State and local 'fair chance' laws may delay criminal-history questions or checks until after a conditional offer.

Sources: FTC — Background checks: what employers need to know · FTC — Using consumer reports: what employers need to know · checked 2026-09-25

Stage 11 of 13Required

0 of 2 done

Agree the offer

Offer, negotiation and close

Who runs it: Hiring manager + recruiter
Done when: An accepted written offer within the approved band, with a start date.

Key tool

Build the offer around

•The problem: they will own whether models stay trustworthy after launch, not just whether they launch.
•A fair on-call setup, with a clear rota and compensation agreed up front.
•Room to shape the platform: real say over tooling choices rather than inheriting fixed ones.
•A clear level rationale and what the next level would expect, such as owning the platform for several teams.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the offer message built around what the candidate said matters to them. The figure, the approval and the conversation stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft an offer message for a MLOps Engineer role. Context: I will paste three general priority categories (for example: learning, flexibility, scope) — not the candidate's words, notes or personal details; the parts of the offer; and the start-date options — without the salary figure. Produce: a warm, plain-English message that links each part of the offer to one of their priorities, says what happens next and when the written offer follows, and invites questions. Use British English and inclusive wording, and leave [brackets] for figures and names. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that nothing promised is outside policy or the approved band, that every claim about the role is true, and that the message reads as personal rather than templated.
Diligence: The hiring manager places the offer in the band using the same pre-set factors for everyone and makes the verbal offer personally. Figures and personal details are filled in by people, never pasted into AI.

Don't miss: Leaving on-call expectations vague until after acceptance; for this role it is part of the job, and candidates weigh it.

Framework

Close plan (motivators → offer → objections)

Build the offer around what the candidate told you they care about, anticipate their objections, and make sure the verbal and written offers match.

List the candidate's top three motivators from your notes at every stage.
Make the verbal offer personally, and link each part of it to a motivator.
Ask what else they are weighing and when they have to decide.
Place the offer in the band using the same pre-set, job-related factors for everyone, and record why.
Send the written offer promptly after the verbal one.

Why it works: A close plan ties the offer to the candidate's stated priorities and makes approvals explicit before the final interview.

Offer checklist and negotiation

Stay inside the approved band. If the candidate is worth more, re-level them with evidence rather than stretching the band.
Trade in things that cost less than salary where policy allows: start date, learning budget, working pattern.
Before the written offer, ask: 'What would make this an easy yes?'
Agree approval and the pay band before the final interview, so the offer isn't held up.
The hiring manager makes the verbal offer; the written offer follows within a working day.
Record which pre-set factors placed the offer where it is in the band.
Tell unsuccessful finalists personally, without avoidable delay, with brief feedback.

What will close this candidate

The problem: they will own whether models stay trustworthy after launch, not just whether they launch.
A fair on-call setup, with a clear rota and compensation agreed up front.
Room to shape the platform: real say over tooling choices rather than inheriting fixed ones.
A clear level rationale and what the next level would expect, such as owning the platform for several teams.

Compliance checkpointEUUS

Use objective, gender-neutral, pre-agreed factors to place candidates within the band, apply them consistently and record the decision as an internal pay-equity control. Check the national law implementing Directive (EU) 2023/970 and any local record-keeping rules; this recommendation is good practice, not a universal statutory documentation rule.

Sources: EU Pay Transparency Directive 2023/970 · checked 2026-09-25

Stage 12 of 13Required

0 of 2 done

Help them settle in

Pre-boarding and 30-60-90 onboarding

Who runs it: Hiring manager + buddy + HR
Done when: A new hire who has worked through a written 30-60-90 plan tied to the 12-month outcomes, with a check-in at each milestone.

Key tool

Before day one
Laptop, repository access and read access to dashboards, deploy logs and the model registry before day one.
Days 1–30: learn
Meets the data scientists, platform engineers and product owners who rely on each model.
Days 31–60: contribute
Rehearses a rollback on the highest-traffic model and fixes what the rehearsal reveals.
Days 61–90: own
Owns release and monitoring for at least one model end to end.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the 30-60-90 plan from the 12-month outcomes. Agreeing the plan with the new hire stays with the manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft a 30-60-90 day onboarding plan for a new MLOps Engineer. Context: I will paste the 12-month outcomes from the intake meeting, the systems and people the hire will work with, and anything they will need before day one. Produce: a pre-boarding checklist (equipment, access, a named buddy, a first-week schedule); then three sections — days 1–30 learn, days 31–60 contribute, days 61–90 own — each with 3–4 concrete, checkable expectations and one milestone check-in question. Use British English and plain wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each expectation is realistic for a new starter, ties back to a 12-month outcome, and offers the hire support rather than a test.
Diligence: The manager agrees the plan with the new hire in week one and owns the check-ins. The new hire's personal details stay out of the prompt.

Don't miss: Putting the new hire on the on-call rota in their first fortnight before they have rehearsed a rollback on each model they cover.

Framework

30-60-90 day plan

Three phases — learn, contribute, own — with written expectations for each, agreed with the new hire in week one.

Before day one: equipment, access, a named buddy and a first-week schedule.
Days 1–30, learn: systems, people and the current state of the work.
Days 31–60, contribute: a first scoped piece of work shipped with support.
Days 61–90, own: an area of responsibility with clear outcomes.
Hold a check-in at each milestone against the written plan.

Why it works: Hiring doesn't end at the signature. A written onboarding plan makes expectations and support visible to the new hire and their manager.

Before day one
- Laptop, repository access and read access to dashboards, deploy logs and the model registry before day one.
- A named buddy from the platform or ML team.
- Recent model incident reviews and current runbooks as pre-reading.
- A list of production models with owners, traffic and current monitoring.
Days 1–30: learn
- Meets the data scientists, platform engineers and product owners who rely on each model.
- Checks which models have monitoring and a tested rollback, and which have neither.
- Ships one small change through the release pipeline to learn the path end to end.
Days 31–60: contribute
- Rehearses a rollback on the highest-traffic model and fixes what the rehearsal reveals.
- Adds input and output monitoring to one model that had none.
- Joins the on-call rota with a runbook for each model they cover.
Days 61–90: own
- Owns release and monitoring for at least one model end to end.
- Delivers one measured improvement, such as faster rollback, fewer false alerts or lower serving cost.
- Shares a short plain-English review of what is still fragile and what they would fix next.

Compliance checkpointUSUK

US: the employee completes Form I-9 Section 1 no later than their first day of paid work, and the employer completes Section 2 within three business days after that day (on the first day if the job lasts less than three business days). UK: complete the prescribed right-to-work check before employment starts, and apply it the same way to everyone.

Sources: USCIS — Form I-9 instructions · GOV.UK — Check a job applicant's right to work · checked 2026-09-25

Stage 13 of 13Required

0 of 3 done

Measure time to hire

Measure the process: mean time to hire

Who runs it: Recruiter / talent lead + hiring manager
Done when: A stage-by-stage timing record for this hire, the slowest step named, and one change agreed before the next requisition opens.

Key tool

Record when the hire accepts

•Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
•Time to fill, recorded separately: days from requisition approval to the accepted offer.
•Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
•Offer-acceptance rate: offers accepted divided by offers made.
•Where candidates dropped out, and the reason you were given.
•How long it took to get approval to share an anonymised monitoring export for the work sample.

Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

Read: mean time to hire Read: time to hire vs time to fill

AI as an advantageAI boost4D framework

Delegate: Hand AI the job of building a blank timing worksheet and the instructions for reading it. Entering dates, working out the timings and deciding what to change stay with the recruiter and the hiring manager.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager set up a timing review for a MLOps Engineer hire. Context: I will list the stage names we used, in order (for example requisition approved, sourcing, screening, recruiter call, work sample, interviews, debrief, references, offer accepted). Produce: (1) a blank worksheet with one row per stage and columns for start date, end date, days in stage, days spent waiting (scheduling, approvals, no reply) and number of candidates who entered and left; (2) step-by-step instructions for us to work out, from our own records, time to hire (the successful candidate's entry to the pipeline, by application or first contact, to the accepted offer; average it across hires for mean time to hire) and, separately, time to fill (requisition approval to the accepted offer); (3) five questions we should ask about the slowest stage, separating waiting from working; (4) a short template for recording one change to make before the next hire. Use British English. Do not include benchmarks or example figures. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet covers every stage you actually ran, that the two definitions are not mixed up, and that the questions point at the process rather than at any person.
Diligence: People fill in the dates and do the arithmetic from their own records, choose the one thing to fix and write it down. No dates, names or details about any candidate go into the prompt.

Don't miss: Counting only candidate time on the task and missing the days spent getting sign-off to share real incident data.

Framework

Mean time to hire, by stage

Time to hire is the number of days from the successful candidate entering your pipeline (their application or your first contact) to their accepted offer; mean time to hire is that figure averaged across hires. Time to fill — requisition approval to acceptance — is a separate measure. Record both per stage, so you can see where the time went rather than only the total.

When the hire accepts, write down the date each stage started and ended, and the day the successful candidate entered the pipeline.
Work out the days per stage, the time to hire and the time to fill, and mark the slowest stage.
Note the offer-acceptance rate and the stage where most candidates dropped out.
Separate waiting time (scheduling, approvals, silence) from working time, and decide which one to shorten.
Fix one thing before the next hire, and write down what you changed.

Why it works: A single total hides where the delay sits. Per-stage timing points at the one step to fix, and the acceptance rate and drop-out points show whether candidates kept pace with the process.

Record for every hire

Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
Time to fill, recorded separately: days from requisition approval to the accepted offer.
Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
Offer-acceptance rate: offers accepted divided by offers made.
Where candidates dropped out, and the reason you were given.
Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

What to log for this role

How long it took to get approval to share an anonymised monitoring export for the work sample.
How many candidates the diagnosis work sample removed, and whether they left before starting or after reading the files.
Whether the deployment and platform design round needed rescheduling because the one staff engineer qualified to run it was on call.

Where this role's hiring slows down

Watch for the incident pack being rebuilt from raw data for each search instead of kept ready and reused.
Watch for interview slots clashing with the panel's own on-call duties, which pushes rounds back without warning.
Watch for the work-sample files going out of date as your monitoring setup changes, so the exercise no longer matches the job.

Compliance checkpointUKEU

Under the EU and UK GDPR, tell candidates how long you will keep their data, or the criteria used to decide. Give that notice when you collect data from them directly, or within the Article 14 time limit when it comes from another source (such as a referral or a sourcing tool). Delete or anonymise data when it is no longer needed, keeping only what a documented lawful purpose still requires.

Sources: GDPR — Regulation (EU) 2016/679, Articles 5, 13 and 14 · ICO — UK GDPR guidance · checked 2026-09-25

General information, not legal advice. Rules depend on the employer, the role and where the work is done — confirm what applies with HR or counsel.

Frequently asked questions

What does an MLOps engineer do?

They get trained models into production and keep them healthy there. In practice that means building the release pipeline, versioning models and data, monitoring inputs, outputs and outcomes for drift, managing serving cost and latency, and leading the response when a model goes wrong.

MLOps engineer vs machine learning engineer: what's the difference?

The roles overlap and some teams combine them. A machine learning engineer usually leans towards building and evaluating models; an MLOps engineer leans towards releasing, monitoring and operating them. Decide from where your current pain sits: model quality, or getting models live and keeping them that way.

How do you interview an MLOps engineer?

Start with a work sample built on monitoring output from a degraded model, then run structured rounds on diagnosis, release design and incident handling. Use the same questions and rubric for every candidate, and probe for the reasoning and evidence behind each answer.

Is MLOps just DevOps for machine learning?

It borrows a lot from DevOps: automated pipelines, staged releases, monitoring and on-call. The difference is that a model can fail while every system metric looks healthy, because the data changed. An MLOps engineer has to watch what goes into and comes out of a model, not only whether the service is up.

What should an MLOps engineer job description include?

The models and serving setup the person will own, a short must-have list centred on deployment, monitoring, reproducibility and incident handling, the on-call arrangement, an AI-fluency section and a genuine pay range. Skip the long list of tools.

Go deeper

Related hiring kits

Guides

Skills tests

See your first AI-generated assessment in 5 minutes

No credit card. No question library to learn. Paste a job description and watch H-Evaluate build.

Request early access