Durham, NC
ML engineering recruiting for production model teams. Crosscheck recruits AI/ML & LLM Engineering candidates for contract, contract-to-hire, and permanent roles tied to Durham.
What We Place
Representative roles
Platforms and technologies
Our Approach
This editorial hiring guide starts with sourced Durham business context. Durham's FY 2025 Strategic Plan Impact Report tracks workforce activity around life sciences and health care, information technology, and advanced manufacturing. The mix gives local hiring briefs concrete research, service, and production settings without implying that every employer is recruiting. A Machine Learning Engineer search needs a defined prediction task, training data owner, deployment path, and measure of useful performance. The same title can describe notebook research, feature engineering, backend development, or ownership of an inference service.
Screen ML engineers on modeling fundamentals and production tradeoffs
Match experience to the ML stack, data, and problem defined in the brief
target a first candidate slate within 48 hours for qualified exclusive searches in our core disciplines after a completed intake
Permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Start the search
Include the business context, systems, delivery phase, work model, compensation, and interview timeline. A Crosscheck search lead will use that context to calibrate the role before sourcing begins.
Local Market Brief
Write the brief around the model lifecycle. Include label creation, feature pipelines, experiment tracking, service integration, monitoring, and retraining duties that belong to this hire. Separate those duties from work owned by data, platform, or research teams. The three sourced Durham contexts below turn that scope into intake and screening decisions. They do not measure current vacancies, candidate supply, or Crosscheck client activity.
Editorial market scenario
Ask candidates to show how they moved technical work into a maintained system. Record the handoff, monitoring, documentation, and operating constraints. This is planning guidance, not measured local demand.
Editorial industry scenario
A health-sector brief should name the protected data, validation, availability, and user-workflow requirements the person will handle. Confirm that this context applies to the employer before using it in the search.
Screening focus
We test for model or application ownership, evaluation discipline, data judgment, and evidence that the candidate has shipped reliable AI systems.
Published labor benchmark
BLS does not publish an occupation matching ML Engineer. Crosscheck uses Data Scientists (15-2051) as the closest published broad benchmark; it is not a count or pay estimate for this exact specialty.
BLS OEWS May 2025, published May 15, 2026
Published metro employment
1,320
BLS publishes a narrower metro employment estimate for the proxy occupation. Screen for adjacent experience that transfers without lowering the production bar. The estimate equals 3.841 jobs per one thousand across the metro workforce.
Employment concentration
2.28 location quotient
Durham-Chapel Hill, NC reports more than twice the national employment concentration for this proxy occupation. Treat that as occupational context, not proof of available candidates.
Annual wage reference
$60,060 to $182,020
The metro median is 11% below the national Data Scientists median. Do not use the gap to discount niche platform or domain experience. BLS reports a $106,500 median for the proxy occupation in Durham-Chapel Hill, NC.
Hiring brief scenarios
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Durham demand, clients, or candidate supply.
Sourced life sciences and health care context
Durham's FY 2025 Strategic Plan Impact Report identifies life sciences and health care as high-demand industries used to align workforce programs and employer engagement. Tie the sector scenario to a concrete outcome and data-generating process. Ask how the engineer would detect label leakage, sampling bias, missing history, and a metric that looks strong but fails the business use case. Life-sciences and care platforms may join research samples, clinical records, laboratory instruments, trials, patient access, quality events, validation, and regulated retention.
Evidence to request: Review a feature or training pipeline and ask the candidate to trace one record from source through validation, training, and evaluation. Define the research or care workflow, sample or patient identity, protected fields, instrument or clinical interface, validation evidence, quality gate, retention rule, and approval owner.
Sourced information technology context
The Durham report also identifies information technology as a high-demand industry in the city's workforce and business-support work. Define the inference environment before screening. Batch scoring, low-latency APIs, edge deployment, and analyst-facing tools require different software design and operating evidence. Information-technology roles can sit in product engineering, enterprise applications, data platforms, security, managed services, or public systems with different delivery evidence.
Evidence to request: Use a production scenario with throughput, latency, and reliability limits. Require an API or batch design plus a test plan. State the product or service boundary, users, data ownership, production authority, integration surface, reliability target, release evidence, and after-launch responsibility.
Sourced advanced manufacturing context
Advanced manufacturing is another high-demand industry named in Durham's FY 2025 impact report and related workforce alignment activity. Assign responsibility for drift, retraining, and model retirement. Candidates should explain the thresholds, review cadence, and human decision that follows an alert. Advanced production can connect designs, bills of material, suppliers, equipment, work orders, quality results, serial or lot records, inventory, maintenance, and cost.
Evidence to request: Ask for a model degradation example and the evidence used to separate data change, code change, and user-behavior change. Trace the product from released design and sourced material through equipment, production, inspection, traceability, inventory, shipment, variance, and accountable process owner.
Interview scorecard
Ask each candidate the same core questions. Score the evidence, ownership, and judgment in the answer instead of relying on job-title or keyword matches.
1. ML Engineer: PyTorch
Choose a PyTorch decision from your work as ML Engineer. Which constraint changed the design, and what evidence supported the result?
Use the answer to assess data provenance, evaluation by use case, human review, privacy, and production monitoring. The healthcare and life-science systems context is an editorial scenario, not a measured claim about Durham.
2. Senior ML Engineer: TensorFlow
Describe project work you completed as Senior ML Engineer involving TensorFlow that did not follow the original plan. What did you own, and how did you correct it?
Use the answer to assess experiment design, evaluation, reproducibility, deployment, monitoring, and product ownership. The research and technical commercialization context is an editorial scenario, not a measured claim about Durham.
3. Staff / Principal ML Engineer: JAX
For a JAX system you supported, explain the handoff, operating limits, and measures used after launch. Where did your responsibility begin and end?
Use the answer to assess data provenance, evaluation by use case, human review, privacy, and production monitoring. The healthcare and life-science systems context is an editorial scenario, not a measured claim about Durham.
Need the full ML Engineer evaluation guide?
The role guide covers technical scope, interview questions, and evidence checks once, without repeating the same material on every city page.
FAQ
For qualified exclusive searches in our core disciplines, Crosscheck targets a first candidate slate within 48 hours after a completed intake. Contract placements include a 40-billable-hour replacement guarantee, and permanent placements include a 90-day replacement guarantee, subject to the signed agreement.
Continue your research