Baltimore, MD
MLOps engineers who bridge data science and production. Crosscheck recruits AI/ML & LLM Engineering candidates for contract, contract-to-hire, and permanent roles tied to Baltimore.
What We Place
Representative roles
Platforms and technologies
Our Approach
This editorial hiring guide starts with sourced Baltimore business context. Baltimore Together's economic-development materials separate technology, life sciences, and industrial, manufacturing, and logistics work. Each setting changes the data boundary, operating risk, and evidence a hiring manager should request. An MLOps Engineer owns the controls that move models from experiments into supported services. The search brief should name the training environment, registry, deployment targets, approval path, observability stack, and teams that share the platform.
Source MLOps engineers with production ownership of model pipelines and serving infrastructure
Vet on model serving, experiment tracking, feature stores, and retraining workflows
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
Separate platform construction from day-to-day model operations. Some teams need reusable pipelines and infrastructure; others need release governance, incident response, cost control, or migration from manually operated notebooks. The three sourced Baltimore 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
Give candidates the integration, approval, audit, and change-management boundaries during the interview. Ask for comparable decisions from prior work. This is planning guidance, not measured local demand.
Editorial industry scenario
A public-sector brief should identify access, procurement, documentation, security, and stakeholder constraints before sourcing begins. 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 MLOps 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,090
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 0.804 jobs per one thousand across the metro workforce.
Employment concentration
0.48 location quotient
Baltimore-Columbia-Towson, MD reports a below-national employment concentration for this proxy occupation. Decide which requirements justify a wider regional or remote search.
Annual wage reference
$76,820 to $227,250
The metro median is 12% above the national Data Scientists median. Test whether the role's scope and location requirement support that difference. BLS reports a $134,320 median for the proxy occupation in Baltimore-Columbia-Towson, MD.
Hiring brief scenarios
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Baltimore demand, clients, or candidate supply.
Sourced cybersecurity and technology context
Baltimore Together tracks technology as a city growth area and calls for stronger connections between employers, students, and Baltimore's software, data, digital-transformation, and information businesses. Require reproducible training and lineage for the local data setting. The candidate should account for code, configuration, data versions, model artifacts, and approval records without copying sensitive data into uncontrolled tools. Cybersecurity work can cross identity, networks, cloud services, endpoints, protected data, incident response, audit records, and restricted facilities or contracts.
Evidence to request: Ask for a pipeline diagram or repository structure that shows lineage, repeatable environments, and artifact retention. Define the protected service, threat and compliance boundary, user population, data classification, control owner, alert path, evidence retention, response authority, and recovery test.
Sourced life sciences context
Baltimore Together's economic-development strategy sets a city objective to lead in life sciences and medical devices. Define promotion between development, test, and production. Ask who approves a model, which automated checks block release, and how the team handles a failed deployment. Life-sciences delivery may join experiments, clinical work, medical devices, laboratories, quality systems, protected records, manufacturing, and commercial operations with formal traceability.
Evidence to request: Review a release-control example with test gates, registry state, deployment strategy, and rollback steps. Set the research or product stage, regulated boundary, source records, validation method, device or laboratory interfaces, access model, release authority, and reviewer.
Sourced manufacturing and logistics context
Baltimore Together tracks industrial, manufacturing, and logistics work as a distinct part of the city's economic-development strategy. Set operating ownership for model services and training jobs. Include capacity, cost, feature freshness, prediction quality, and rollback signals in the interview scenario. Port and factory systems can connect engineering changes, production, quality, inventory, freight, customs, carriers, maintenance, exceptions, and financial settlement across organizations.
Evidence to request: Use an incident involving stale features, failed training, or degraded predictions and score the candidate's diagnosis path. Trace the product or shipment through plant, warehouse, port, carrier, customer, exception, and accounting steps with system authorities, timing, and support ownership.
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. MLOps Engineer: Kubeflow
Choose a Kubeflow decision from your work as MLOps Engineer. Which constraint changed the design, and what evidence supported the result?
Use the answer to assess approved data use, evaluation records, human oversight, deployment boundaries, and security review. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
2. ML Platform Engineer: MLflow
Describe project work you completed as ML Platform Engineer involving MLflow that did not follow the original plan. What did you own, and how did you correct it?
Use the answer to assess approved data use, evaluation records, human oversight, deployment boundaries, and security review. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
3. AI Infrastructure Engineer: Metaflow
For a Metaflow 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 approved data use, evaluation records, human oversight, deployment boundaries, and security review. The public-sector and security work context is an editorial scenario, not a measured claim about Baltimore.
Need the full MLOps 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