AI & ML Ops Engineer

$109K - $154K Minneapolis, MN, US Mid Level MLOps Engineer

Interested in this MLOps Engineer role at Fairview Health Services?

Apply Now →

Skills & Technologies

AwsAzureGcpMlflowMulesoftPythonSagemakerVertex Ai

About This Role

AI job market dashboard showing open roles by category

Responsibilities/Job Description:

The AI & ML Operations Engineer designs, builds, and maintains the engineering processes and platform capabilities needed to deploy, monitor, govern, and maintain deployed AI/ML solutions at scale. The role converts validated analytical work into reliable production solutions and manages the operational lifecycle of models and related services while meeting enterprise privacy, security, and support standards.

The engineer partners with data scientists, data engineers, central cloud and infrastructure teams, API and Interoperability teams, Cybersecurity, service owners, and relevant engineering teams to deliver maintainable solutions. The role remains hands-on in engineering, testing, deployment, and troubleshooting while using enterprise-managed capabilities for production data movement, integration, and infrastructure. Scientific method validation remains with the Data Scientist and designated reviewers; this position implements the operational controls for deployed solutions.

This role is part of a new AI & Automation engineering team and will directly design, build, deploy, and support production AI applications and services. Work may include agents, retrieval-augmented generation, orchestration, APIs and integrations, automated evaluation and testing frameworks, observability, monitoring, release and rollback processes, and model/application lifecycle management. Responsibilities Model deployment and orchestration. Deploy batch and real-time models and related AI services using approved CI/CD, containers, APIs, and workflow patterns. Build and maintain assigned model deployment and runtime components and coordinate dependencies with enterprise platform owners. Release management. Automate packaging, versioning, testing, promotion, rollback, and recovery for models and services. Implement retraining or recalibration workflows using criteria defined with data scientists and the required validation and release approvals. ML platform capabilities. Implement, integrate, configure, and operate approved feature stores, model registries, experiment tracking, and related ML lifecycle capabilities with enterprise platform owners. Partner with Cloud & AI Deployment Engineering and central cloud teams on compute, storage, networking, and deployment. Deployed-model governance. Implement approved lifecycle controls, access restrictions, lineage, audit trails, change records, and release approvals for deployed models. Maintain traceability across data, code, model, and configuration versions. Monitoring and reliability. Implement logging, alerts, and monitoring for model performance, drift, data quality, latency, availability, and errors. Work with data scientists, service owners, and relevant engineering teams on measures, thresholds, incident response, and service objectives. Data and API integration. Work with central data-engineering teams on managed data pipelines and with enterprise API and Interoperability teams on real-time and application integrations, including MuleSoft or other approved API capabilities. Coordinate monitoring, recovery checkpoints, restart procedures, security, and support ownership. Enterprise support and maintainability. Ensure production solutions have documented dependencies, operational procedures, escalation paths, and ongoing ownership before release. Arrange support with the responsible enterprise teams, including 24/7 coverage where required for critical services, rather than relying on an individual project owner. AI application operations. Operate assigned LLM, retrieval-based, and agent applications using automated quality checks, model/tool tracing, prompt and configuration versioning, and usage/cost monitoring within the common production lifecycle. Security and engineering standards. Apply enterprise privacy, security, encryption, role-based access, and sensitive-data controls. Follow common infrastructure-as-code, pull-request, and deployment practices with the responsible teams; bring needed tooling or design exceptions through established review processes. Collaboration and improvement. Help scientists and partner teams move prototypes into supported production solutions. Review code, tests, and documentation, resolve incidents across dependencies, provide constructive technical feedback, and improve reliability, reproducibility, performance, and efficiency. Required Qualifications* B.S./B.A. in Computer Science, Engineering, Information Systems, or a related field, or an equivalent combination of education and relevant experience.

  • At least three years of experience in software engineering, DevOps, or MLOps, including work with production systems.
  • Proficiency in Python or another modern programming language, such as Java or Go, sufficient to build, test, troubleshoot, and maintain production components.
  • Hands-on experience deploying and operating batch and/or real-time machine-learning models in production.
  • Experience with CI/CD tools such as GitHub Actions, GitLab CI, Jenkins, or Azure DevOps; source control, code review, automated testing, and controlled releases.
  • Hands-on experience with containerization and orchestration technologies using enterprise-approved platforms and tools.
  • Experience in cloud and/or hybrid environments such as AWS, Azure, or GCP.
  • Working knowledge of SQL and experience with large datasets and data-workflow orchestration; ability to integrate model services with enterprise-managed pipelines and APIs.
  • Experience implementing logging, metrics, monitoring, alerts, and operational diagnostics and investigating failures across model, application, data, and infrastructure dependencies.
  • Understanding of security best practices, role-based access control, secrets management, and handling sensitive data.
  • Ability to independently deliver assigned engineering work, communicate technical tradeoffs, and collaborate with data scientists, clinicians, data/API teams, cloud/DevOps, security, and support functions.

Preferred Qualifications* Experience in healthcare, health technology, or another regulated industry handling PHI/PII.

  • Familiarity with EHR/EMR integration and healthcare data standards such as HL7/FHIR, ICD, CPT, LOINC, or SNOMED.
  • Experience with ML lifecycle tools such as MLflow, Kubeflow, SageMaker, Vertex AI, or Azure ML, including model registries, feature stores, and experiment tracking.
  • Experience with ETL/ELT, data warehouse or lakehouse platforms, enterprise API platforms, infrastructure as code, and formal production-support practices.
  • Experience monitoring model drift, fairness, and explainability and implementing healthcare AI governance controls.
  • Experience operating LLM, retrieval-based, or agent applications, including quality evaluation, tracing, prompt/configuration management, and cost monitoring.

Qualifications:

$109,449.60- $154,523.20 Annual

Salary Context

This $109K-$154K range is in the lower quartile for MLOps Engineer roles in our dataset (median: $197K across 25 roles with salary data).

View full MLOps Engineer salary data →

Role Details

Title AI & ML Ops Engineer
Location Minneapolis, MN, US
Category MLOps Engineer
Experience Mid Level
Salary $109K - $154K
Remote No

About This Role

MLOps Engineers build the infrastructure that keeps ML models running in production. They own CI/CD pipelines for model deployment, monitoring for data drift and model degradation, and the tooling that lets data scientists ship faster. If ML Engineers build the models, MLOps Engineers build the roads those models travel on.

The job is fundamentally about reliability and velocity. Data scientists want to iterate fast. Product teams want stable predictions. Your job is to make both happen simultaneously. That means building deployment pipelines that catch regressions before they hit production, monitoring systems that alert on data drift before it degrades model performance, and self-service tooling that lets data scientists deploy without filing a ticket.

Across the 10,419 AI roles we're tracking, MLOps Engineer positions make up 2% of the market. At Fairview Health Services, this role fits into their broader AI and engineering organization.

MLOps demand tracks closely with production ML adoption. As more companies move models from notebooks to production, the need for MLOps grows. The role is well-established at large tech companies and growing fast at mid-stage startups that are hitting the 'our models work in notebooks but break in production' phase.

What the Work Looks Like

A typical week involves: debugging a model deployment that's serving stale predictions, building a new monitoring dashboard for a feature team, writing Terraform for GPU-enabled inference clusters, reviewing pull requests for the ML platform's CI/CD pipeline, and meeting with data scientists to understand their pain points. You're the bridge between ML and infrastructure.

MLOps demand tracks closely with production ML adoption. As more companies move models from notebooks to production, the need for MLOps grows. The role is well-established at large tech companies and growing fast at mid-stage startups that are hitting the 'our models work in notebooks but break in production' phase.

Skills Required

Aws (11% of roles) Azure (10% of roles) Gcp (7% of roles) Mlflow (2% of roles) Mulesoft Python (23% of roles) Sagemaker (1% of roles) Vertex Ai (2% of roles)

Kubernetes, Docker, and cloud infrastructure are baseline. Most roles want experience with ML-specific tooling: MLflow, Kubeflow, Weights & Biases, or similar. Strong DevOps fundamentals matter more than ML theory. You need to understand model serving (TorchServe, Triton, vLLM), monitoring (Prometheus, Grafana), and infrastructure-as-code (Terraform, Pulumi).

GPU infrastructure knowledge is increasingly valuable as LLM inference becomes a major cost center. Understanding GPU scheduling, multi-node training setups, and inference optimization (quantization, batching, caching) puts you in the top tier. Experience with model registries and feature stores rounds out the profile.

Good MLOps postings specify their ML stack, infrastructure scale, and the problems they're solving (deployment velocity, cost optimization, monitoring gaps). Red flag: companies that want MLOps but don't have any models in production yet. You'll end up doing general DevOps instead.

Compensation Benchmarks

MLOps Engineer roles pay a median of $206,600 based on 205 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200. This role's midpoint ($131K) sits 36% below the category median. Disclosed range: $109K to $154K.

Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.

Fairview Health Services AI Hiring

Fairview Health Services has 1 open AI role right now. They're hiring across MLOps Engineer. Based in Minneapolis, MN, US. Compensation range: $154K - $154K.

Location Context

Across all AI roles, 6% (580 positions) offer remote work, while 9,776 require on-site attendance. Top AI hiring metros: New York (3,785 roles, $222,480 median); San Francisco (3,262 roles, $261,300 median); Los Angeles (1,896 roles, $210,000 median).

Career Path

Common paths into MLOps Engineer roles include DevOps Engineer, Platform Engineer, Data Engineer.

From here, career progression typically leads toward ML Platform Lead, Infrastructure Architect, Engineering Manager.

DevOps engineers with ML curiosity have the shortest path. You already understand deployment, monitoring, and infrastructure. Add ML-specific knowledge (model serving, data pipelines, experiment tracking) and you're competitive. The career ceiling is high: ML Platform Lead roles at top companies pay well because the infrastructure complexity is enormous.

What to Expect in Interviews

Interviews emphasize infrastructure and reliability. Expect questions about CI/CD for ML models, monitoring for data drift, and how you'd design a model serving platform that handles 10K requests per second. Coding rounds focus on Python and infrastructure-as-code (Terraform, Helm). Be ready to discuss tradeoffs between different model serving frameworks and how you'd handle rollback when a new model degrades performance.

When evaluating opportunities: Good MLOps postings specify their ML stack, infrastructure scale, and the problems they're solving (deployment velocity, cost optimization, monitoring gaps). Red flag: companies that want MLOps but don't have any models in production yet. You'll end up doing general DevOps instead.

AI Hiring Overview

The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.

The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).

MLOps demand tracks closely with production ML adoption. As more companies move models from notebooks to production, the need for MLOps grows. The role is well-established at large tech companies and growing fast at mid-stage startups that are hitting the 'our models work in notebooks but break in production' phase.

The AI Job Market Today

The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.

The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.

Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.

AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.

Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.

The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.

Frequently Asked Questions

Based on 205 roles with disclosed compensation, the median salary for MLOps Engineer positions is $206,600. Actual compensation varies by seniority, location, and company stage.
Kubernetes, Docker, and cloud infrastructure are baseline. Most roles want experience with ML-specific tooling: MLflow, Kubeflow, Weights & Biases, or similar. Strong DevOps fundamentals matter more than ML theory. You need to understand model serving (TorchServe, Triton, vLLM), monitoring (Prometheus, Grafana), and infrastructure-as-code (Terraform, Pulumi).
About 6% of the 10,419 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
Fairview Health Services is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from MLOps Engineer positions include ML Platform Lead, Infrastructure Architect, Engineering Manager. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.