Interested in this MLOps Engineer role at PathAI?
Apply Now →Skills & Technologies
About This Role
PathAI's mission is to improve patient outcomes with AI-powered pathology.
Our platform promises substantial improvements to the accuracy of diagnosis and the efficacy of treatment of diseases like cancer, leveraging modern approaches in machine learning and artificial intelligence. We have a track record of success in deploying AI algorithms for histopathology in translational research, pathology labs and clinical trials. Rigorous science and careful analysis is critical to the success of everything we do. Our team, composed of diverse employees with a wide range of backgrounds and experiences, is passionate about solving challenging problems and making a huge impact on patient outcomes.
We're looking for intellectually curious and driven engineering students to help lay the groundwork for our growing machine learning automation systems.
Our MLOps team builds and scales the machine learning infrastructure that powers PathAI's enterprise AI systems in research and production production — spanning cloud infrastructure (AWS and on-prem), Kubernetes, distributed systems, and observability. We care as much about reliability and reproducibility as we do about speed: everything we ship should be dependable, well-tested, and easy for other engineers to build on. As a co-op, you'll get a broad, hands-on introduction to ML automation.
Timeline: This opportunity is for Fall 2026 / Winter 2027. We are looking for interns/co-ops who can commit to 3 - 6 months at PathAI. (4 - 6 months preferred)
Location: Boston, MA
This is a hybrid position, with the expectation of 3 days onsite.
What You'll Do
- Solve interesting problems with code.
- Build new features for internal users, and refactor existing ones to make them better.
- Interface directly with team members of all levels
- Work with a wide range of systems, processes, and technologies to solve problems in sustainable ways. Sometimes you'll be neck- deep in low-level systems, and other times you'll be pairing up with to build developer features.
- Collaborate with machine learning and infrastructure teams.
- Drive and uphold high engineering standards, bringing consistency to the codebases you encounter and ensuring software is adequately reviewed, tested, and integrated.
- Learn and share knowledge with others along the way.
Who You Are:
- You are enrolled in a Bachelor's or Master's in Computer Science (or related field.
- You have completed at least 50% of your degree program.
- You have previous work experience: internship in this field, volunteer work, or a summer gig waiting tables.
- You are proactive and have demonstrated the ability to learn quickly in a complex space
Preferred:
- You have excellent communication skills and a desire to work in a highly collaborative, cross-functional environment.
- You have participated in student organization and/or other leadership activities
The expected salary range for this position based on the primary location of Boston, MA is $30-50 per hour. Actual pay will be determined on experience, qualifications, geographic location, and other job-related factors permitted by law. This position also qualifies for paid holiday time off.
PathAI is an equal opportunity employer. It is our policy and practice to employ, promote, and otherwise treat any and all employees and applicants on the basis of merit, qualifications, and competence. The company's policy prohibits unlawful discrimination, including but not limited to, discrimination on the basis of Protected Veteran status, individuals with disabilities status, and consistent with all federal, state, or local laws.
Salary Context
This $62K-$104K range is in the lower quartile for MLOps Engineer roles in our dataset (median: $157K across 20 roles with salary data).
View full MLOps Engineer salary data →Role Details
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 9,653 AI roles we're tracking, MLOps Engineer positions make up 2% of the market. At PathAI, 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
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 $205,000 based on 151 positions with disclosed compensation. Entry-level AI roles across all categories have a median of $110,408. This role's midpoint ($83K) sits 59% below the category median. Disclosed range: $62K to $104K.
Across all AI roles, the market median is $213,400. Top-quartile compensation starts at $264,230. The 90th percentile reaches $319,400. For comparison, the highest-paying categories include AI Safety ($253,100) and Research Engineer ($252,000). By seniority level: Entry: $110,408; Mid: $193,200; Senior: $228,700; Director: $272,275; VP: $235,000.
PathAI AI Hiring
PathAI has 6 open AI roles right now. They're hiring across MLOps Engineer, AI/ML Engineer, AI Product Manager. Positions span Boston, MA, US, Boston, MA. Compensation range: $104K - $278K.
Location Context
AI roles in Boston pay a median of $215,000 across 323 tracked positions.
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 9,653 open positions tracked in our dataset. By seniority: 193 entry-level, 4,500 mid-level, 3,455 senior, and 1,505 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (568 positions). The remaining 9,010 roles require on-site or hybrid attendance.
The market median for AI roles is $213,400. Top-quartile compensation starts at $264,230. The 90th percentile reaches $319,400. Highest-paying categories: AI Safety ($253,100 median, 57 roles); Research Engineer ($252,000 median, 419 roles); AI Engineering Manager ($251,622 median, 51 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 9,653 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,301), Data Scientist (441), AI Software Engineer (438). 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 (193) are outnumbered by mid-level (4,500) and senior (3,455) 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,505 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (568 positions), with 9,010 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 $213,400. Top-quartile roles start at $264,230, and the 90th percentile reaches $319,400. 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 $253,100 median, while Prompt Engineer roles sit at $141,440. 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 (1,605 postings), Aws (916 postings), Azure (724 postings), Rag (634 postings), Gcp (522 postings), Pytorch (495 postings), Kubernetes (384 postings), Claude (383 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.