Software Engineer II, MLOps
Whoop · Boston, MA
$125,000–$175,000from the description
Jul 12, 2026
Boston, MA
Jul 21, 2026
What this job asks for AI summary
A mid-level engineering role on an MLOps team, focused on building and maintaining cloud infrastructure that takes machine learning models from research into production. Day-to-day work involves designing CI/CD pipelines for ML workflows, developing APIs and microservices for model integration, and using AWS services to support real-time inference. The role suits engineers with hands-on ML infrastructure experience who collaborate closely with data science teams.
Mid level · 2+ years · Boston, MA · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 3 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 2,150 people in the Boston, MA area plausibly meet what this posting asks for (software developers). range 1,600–2,800
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $169,742 (middle half $134,780–$187,781). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
The role is titled 'Software Engineer II', which maps to a Mid-level band; the 2+ years experience requirement and scope (team-level delivery, no cross-org authority) are consistent with Mid.
The alt SOC 15-1243 (Database Architects) was considered given the MLOps/data pipeline focus, but the primary day-to-day work is building and shipping software systems (APIs, microservices, CI/CD pipelines), making 15-1252 the better fit.
Python and Java are listed as interchangeable examples of an OOP/functional language in the requirements section; Python is named first and is the dominant MLOps language, so it is the primary skill with Java as an alternative.
Cloud computing experience is a hard requirement, with AWS named as the specific platform in the responsibilities narrative (SageMaker, Lambda, ECS); AWS SageMaker, Lambda, and ECS appear in the responsibilities/narrative section rather than a formal qualifications block, so they are marked preferred.
ML lifecycle understanding (training, evaluation, production monitoring) is explicitly listed in the qualifications section and is treated as a required conceptual gate, though no specific tooling is named.
Microservices and API development appear in the responsibilities narrative, not the qualifications block; marked preferred accordingly.
The JD states a Bachelor's degree 'or equivalent practical experience', so no formal degree is hard-required.
The posting explicitly states this is an in-office role in Boston, MA with a relocation requirement; remote=false.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): ML lifecycle.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.