Interested in this MLOps Engineer role at Later?
Apply Now →Skills & Technologies
About This Role
Later is the world’s most intelligent influencer marketing company, built to give brands the confidence to create unforgettable campaigns. By combining real creator relationships, trusted intelligence, and expert guidance, Later removes fear and guesswork from one of marketing’s most visible investments.
Built on a native, AI-powered platform and more than a decade of proprietary data—including billions of social interactions, impressions, and $2.4B+ in verified influencer-driven purchases—Later helps teams understand what will work before they launch.
By combining trusted insight with expert guidance, Later removes guesswork from influencer marketing, enabling brands to choose the right creators, execute fully managed campaigns, and drive meaningful growth across awareness, engagement, and revenue. Trusted by leading enterprise brands including Nike, Wayfair, Unilever, and Southwest Airlines, Later bridges creativity and performance so campaigns don’t just look good—they deliver results. Learn more at later.com.
Senior MLOps Engineer Later is the world’s most intelligent influencer marketing company. Built on a native, AI-powered platform and more than a decade of proprietary data, including billions of social interactions and $2.4B+ in verified influencer-driven purchases, Later helps brands choose the right creators, run fully managed campaigns, and know what will work before they launch.
Trusted by leading enterprise brands including Nike, Wayfair, Unilever, and Southwest Airlines, Later bridges creativity and performance so campaigns don’t just look good, they deliver results. Learn more at later.com.
About this position We’re looking for a Senior MLOps Engineer to build and scale the infrastructure that takes Later’s machine learning and AI systems from prototype to production. You’ll own the pipelines that train, retrain, deploy, and serve the models behind our products, including forecasting, recommendation, and LLM-based and agentic features, across AWS and GCP.
You’ll join the Infrastructure team alongside our DevOps engineers and work closely with Data Science, Data Engineering, Platform, and Product Engineering. Data Science builds and iterates on models; you make sure they ship reliably, scale with demand, and retrain on the right cadence.
At first, expect roughly half your time on ML platform work and half on shared infrastructure. The split will shift toward ML as the practice grows into its own team. The role is mainly infrastructure and automation, with hands-on coding where it counts.
This is a strong fit for a senior engineer with a solid DevOps and cloud foundation and real experience putting ML systems into production, who wants to set the standard for MLOps at Later.
What you’ll be doing Strategy & Architecture
- Own the MLOps roadmap with Infrastructure, Data Science, and Data Engineering leaders, aligned to product and AI growth plans.
- Evaluate and select tooling for orchestration, model registry, experiment tracking, LLM serving, and observability, and make clear build-or-buy recommendations.
- Shape the long-term architecture of our multi-cloud ML and data platform, with scalability, security, and cost built in from the start.
Building & Operating
- Design, build, and operate infrastructure that deploys and scales ML models in production, using CI/CD, GitOps, Kubernetes, and orchestration tools such as Airflow, Kubeflow, or Argo Workflows.
- Own automated training and retraining pipelines, including model registry, validation, deployment, and rollback, and agree on the retraining cadence with Data Science.
- Deploy and operate LLM inference (self-hosted on AWS Bedrock or managed APIs), including GPU capacity, cost controls, and performance monitoring.
- Manage training and inference infrastructure across AWS and GCP, including GPU workloads, using Terraform.
- Work with Data Engineering to source and prepare training data from BigQuery and S3, building pipelines and light transformations as needed.
- Build monitoring for model performance, latency, data drift, cost, and resource usage, using tools such as CloudWatch, Prometheus, and Grafana.
- Support model versioning, experiment tracking (e.g., MLflow, SageMaker), and reproducible training workflows.
- Lead troubleshooting of complex production and deployment issues, and take part in the Infrastructure on-call rotation.
Leadership & Collaboration
- Set and document standards for infrastructure-as-code, CI/CD, observability, secure deployment, and ML workflow automation.
- Write runbooks and self-serve guides so Product and Data teams can deploy, monitor, and troubleshoot with more autonomy.
- Lead incident reviews and post-mortems that improve how we operate.
- Mentor engineers through pairing, code review, and feedback.
- Explain technical tradeoffs clearly to both technical and non-technical stakeholders.
What success looks like First 30 days: Learn and support. You learn Later’s cloud infrastructure, Kubernetes environments, CI/CD workflows, and the data and ML platform, including how models are trained and deployed today. You start supporting existing pipelines and observability tools. By day 30 you know where the platform’s biggest gaps are and how Product and Data teams use it.
First 60 days: Contribute and improve. You own infrastructure and automation work across Kubernetes, AWS, CI/CD, and the ML platform. You make deployment pipelines more consistent and automated, improve GPU provisioning and monitoring for training and inference, and close gaps in alerting and runbooks. You’re already mentoring teammates on the patterns you’re introducing.
First 90 days: Own and scale. You own the path from a finished model to production. By day 90:
- At least one production model is deployed, retrained, and rolled back through an automated pipeline, with no manual steps.
- Drift, latency, and cost alerts are live for production models.
- A first MLOps roadmap has been reviewed with Infrastructure, Data Science, and Data Engineering leads.
- Security and compliance checks are built into the ML deployment path.
What you bring
- 7+ years of DevOps, cloud, or software engineering experience in production environments, including technical leadership: leading projects, setting direction, and mentoring others. People management is not required.
- Deep expertise with Kubernetes (EKS), Helm, and microservices, including running GPU workloads on Kubernetes.
- Hands-on AWS experience and a track record of using Terraform for scalable, auditable infrastructure as code.
- Experience deploying, serving, and scaling ML models in production, including CI/CD for ML.
- Experience building data and training pipelines in partnership with Data Science and Data Engineering teams.
- Strong system design skills, including designing ML systems end to end and explaining the tradeoffs.
- Clear communication with technical and non-technical audiences.
Nice to have
- GCP experience, especially BigQuery.
- Amazon SageMaker.
- Self-hosted LLM deployments on Kubernetes (e.g., vLLM, KServe).
- Orchestration and experiment tracking tools such as Airflow, Kubeflow, Argo Workflows, or MLflow.
If you don’t meet every requirement but this role sounds like you, we’d still love to hear from you. How we work:
- We will do whatever it takes to win: We win when our customers and creators win. We bring full commitment to outcomes that matter, not just effort.
- We have no limit to our aspiration: We think big, push beyond what seems possible, and refuse to let conventional thinking set the ceiling.
- We are relentless: We keep going through ambiguity, setbacks and competing priorities, and we find a way forward.
- We deeply understand our business: If we don’t have the knowledge, we figure it out. We take ownership of understanding how Later works and what drives results.
- We take our work seriously, but not ourselves: We bring rigor and accountability without ego, and we make space for each other to do our best work.
Our approach to compensation: We take a market-based & data-driven approach to compensation. We leverage data from trusted third-party compensation sources to help us understand the market value of a role based on function, level, geographic location, and scope. We evaluate compensation bi-annually, including performance and market-related factors.
Our salaries are benchmarked against market Total Cash Compensation for the geographic location of our job posting. Compensation for some roles is structured as On Target Earnings (OTE = base + commission/variable) while for others it is structured as Salary only. The salary range listed for this role reflects the zones that applies to the location of this posting.
To comply with local legislation and ensure transparency, we share salary ranges on all job postings. Skills, experience and other factors help determine the final salary we offer which may vary from the original range posted.
Additionally, all permanent team members are eligible to participate in various benefits plans as part of their overall compensation package.
Salary range:
For candidates located in the US: $125,000-205,000 USD
For candidates located in the Canada: $110,000-160,000 CAD
Where we work: We have offices in Boston, MA; Vancouver, BC; and Vancouver, WA. For select positions, we are open to hiring fully remote candidates. We post our positions in the location(s) where we are open to having the successful candidate be located.
Diversity, inclusion, and accessibility: At Later, we are committed to fostering a culture rooted in an inclusion-first mindset at every level of the company, embracing the importance of hiring and building teams for culture add rather than culture fit . We openly build and maintain unbiased hiring, pay, and promotion practices to create a foundation for an equitable workplace, paving the way for systemic change.
We are committed to creating a diverse environment and are proud to be an equal opportunity employer . All applications will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, national origin, disability, or age. Please let us know if you require any accommodations or support during the recruitment process.
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 10,419 AI roles we're tracking, MLOps Engineer positions make up 2% of the market. At Later, 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 $206,600 based on 205 positions with disclosed compensation. Senior-level AI roles across all categories have a median of $230,000.
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.
Later AI Hiring
Later has 1 open AI role right now. They're hiring across MLOps Engineer. Based in Boston, MA.
Location Context
AI roles in Boston pay a median of $215,000 across 484 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 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
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.