Pay
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
San Francisco · San Francisco, California, United States
Live, first seen by us 77 days agoLocation type: HybridFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Build predictive models on clinical data: risk stratification, utilization, care gap detection
Own the full ML lifecycle, including evaluation, deployment, and drift monitoring
Turn unstructured clinical data like PDFs, scans, and doctor notes into structured records
Stand up training and inference pipelines, experiment tracking, model versioning, and evals
Building predictive models on clinical data at scale: risk stratification, expected utilization / prediction, care gap detection.
Owning the full ML lifecycle: problem framing, feature engineering over sparse and high dimensional clinical data, training, evaluation, deployment, and monitoring for drift and degradation in production.
Turning unstructured clinical data into structured, usable records: parsing PDFs, images, doctor notes, etc.
Standing up our ML infrastructure: training and inference pipelines, experiment tracking, model versioning, and evals
7+ years building ML systems that run against real data at scale.
From the employer’s posting.
We're a technology company that happens to operate in healthcare, and we build every layer ourselves: connect, transform, and insight.
In the employer’s words · Read in context · Company website ↗
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
Day 77
Up longer than most. Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- You've shipped models to production and lived with them: you have opinions about evaluation, monitoring, retraining, and what can break after launch. - You're deeply experienced with ML, but still have strong eng chops: you can stand up a service, write the IaC, instrument it, and own it end to end. Python is home; TypeScript, AWS, and SQL aren't going to scare you. - You're pragmatic about LLMs. You've used them where they win and you know where a smaller, cheaper, more reliable model wins instead.
Our tech Core business logic in Node.js and TypeScript, with Python in data and ML workflows. AWS across the board (ECS, Lambda, SQS, SNS, Batch, etc.), infrastructure as code with CDK. Data lives in S3, PostgreSQL/Aurora, DynamoDB, Snowflake, and our FHIR server with Athena for querying S3 and SageMaker for Analytics/ML. The ideal person for this role is a generalist who picks the best tool for the job. Metriport provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.
- Strong software engineering fundamentals: you've built or operated large scale backend systems on the cloud (ideally AWS) and can own training pipelines, model serving, and monitoring end to end. - Strong data skills: SQL, working with large datasets, and building the pipelines that feed your models. - You're located in San Francisco or the Bay Area (or willing to relocate).
- A track record of ML delivering measurable results in production. - Strong software engineering fundamentals: you've built or operated large scale backend systems on the cloud (ideally AWS) and can own training pipelines, model serving, and monitoring end to end. - Strong data skills: SQL, working with large datasets, and building the pipelines that feed your models.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Medical data exchange is one of the biggest unsolved problems in US healthcare. If you've spent any real time in the healthcare system, you've felt it, and it only gets worse the sicker and older you get. Metriport exists to fix that. We connect to the data sources the healthcare providers of tomorrow need, take raw data that's unusable in its source form, and turn it into a single clean format that care teams, and their agents, actually use to improve outcomes. Record retrieval across thousands of legacy systems and antiquated data pipes that used to take weeks now takes seconds. Clinicians walk into appointments with the full patient picture already in hand, and that speed can mean spotting a condition early enough to actually treat it.
We're not a healthcare company. We're a technology company that happens to operate in healthcare, and we build every layer ourselves: connect, transform, and insight. Legacy EHRs were built to get providers paid, not to serve the clinical experience. We're building what should have existed instead: the system of record for all of US healthcare. We started in data exchange. Today we compete with the largest data platforms in the space. Tomorrow we will be the infrastructure layer healthcare runs on.
We’ve raised $28.4 million from top tier VCs (including Matrix, ARTIS and Y Combinator), found product market fit (multi million dollar ARR, 100+ customers including Amazon One Medical, Circle Medical, Color Health, and Strive Health), and have years of runway ahead of us. If you’ve had a good healthcare experience in the past few years, there’s a good chance Metriport was behind it. That’s the version of healthcare we want people to not just expect, but demand. Join us and build the future.
About You
We're a small, high output team, mostly former founders including YC alumni, and we operate with real autonomy and almost no bureaucracy. We hire based on competence, not pedigree. Leaders are in the office six days a week, and we generally expect the team to be available six days a week too. Not because we count hours, but because there's always more wood to chop when revolutionizing how tomorrow’s healthcare providers deliver care to their patients today. We trust our team to take the time off they need and we've never said no to a time off request.
You have an entrepreneurial mindset and a strong sense of ownership. You don't wait to be told what's broken. Instead, you believe you can figure out any problem that lands in your lap even outside your exact domain. When someone scopes something for three weeks, you ask why it can't be done in three days, and you also know the difference between shipping a fast v0 and cutting a corner that comes back to bite you. You walk the tightrope between craft and speed without falling off either side.
This is the first Machine Learning Engineer role at Metriport. We have access to the richest clinical datasets in the country longitudinal medical records for hundreds of millions of individuals and we've barely scratched the surface of what can be learned from it. You'll own machine learning at Metriport end to end: from framing the problem with customers, to training the models, to serving them in production and keeping them honest.
This is applied ML on messy, high dimensional, real world healthcare data, not a research role, and not an LLM wrapper role.
You have deep ML fundamentals, from classical methods through deep learning. You can take a prediction problem from a linear baseline to gradient boosted trees to a neural network and you know when each one is the right answer.
You've shipped models to production and lived with them: you have opinions about evaluation, monitoring, retraining, and what can break after launch.
You're deeply experienced with ML, but still have strong eng chops: you can stand up a service, write the IaC, instrument it, and own it end to end. Python is home; TypeScript, AWS, and SQL aren't going to scare you.
You're pragmatic about LLMs. You've used them where they win and you know where a smaller, cheaper, more reliable model wins instead.
You're comfortable with messy, real world data: sparse, inconsistent, high dimensional, and full of surprises. Healthcare data is all of these at once.
You're entrepreneurial minded with an olympian level work ethic (about half our engineering team are former founders).
When someone scopes a project for 3 weeks, you ask "why can't it be done in 3 days?" and you help others develop that same instinct.
You're a hacker at heart, with a good sense of which rules should, and shouldn't, be broken.
You'll build the models, and the ML platform underneath them, that turn raw clinical data into intelligence our customers act on.
Day to day, that looks like:
Building predictive models on clinical data at scale: risk stratification, expected utilization / prediction, care gap detection.
Owning the full ML lifecycle: problem framing, feature engineering over sparse and high dimensional clinical data, training, evaluation, deployment, and monitoring for drift and degradation in production.
Turning unstructured clinical data into structured, usable records: parsing PDFs, images, doctor notes, etc.
Standing up our ML infrastructure: training and inference pipelines, experiment tracking, model versioning, and evals so that every model we ship is measurable, debuggable, reliable.
Working directly with founders, engineers, and customers to figure out which ML problems are highest leverage to solve next.
Example projects you could own:
Building a model that predicts expected hospitalizations for new patients from their medical history.
Turn freeform doctors' notes and scanned documents into structured data we can add to patients' medical records.
Build classifiers to categorize billions of clinical documents with incomplete metadata.
7+ years building ML systems that run against real data at scale.
Strong grounding across the ML spectrum: regression and tree based methods, feature engineering and dimensionality reduction, and deep learning. You've built and trained models yourself, not just orchestrated APIs.
A track record of ML delivering measurable results in production.
Strong software engineering fundamentals: you've built or operated large scale backend systems on the cloud (ideally AWS) and can own training pipelines, model serving, and monitoring end to end.
Strong data skills: SQL, working with large datasets, and building the pipelines that feed your models.
You're located in San Francisco or the Bay Area (or willing to relocate).
Bonus:
Healthcare standards/technologies: FHIR, HIE, IHE, EHR/EMR, NPI, TEFCA, ADT, HL7, HEDIS, RAF, SNOMED, LOINC, ICD 10, etc.
Founder experience, or being the first/only ML hire at an early stage startup.
Competitive equity + compensation package 🚀
Full family Platinum health insurance, dental, and vision coverage 🦷
401(k) retirement plan + matching 💰
Flexible work from home or in office 🏢
Healthy lunches are complimentary when working in office (and breakfast + dinners as needed) 🍏
MacBook provided by us 💻
Unlimited PTO (we work hard, but trust you to take time you need to be at your best) 🧘♂️
Core business logic in Node.js and TypeScript, with Python in data and ML workflows. AWS across the board (ECS, Lambda, SQS, SNS, Batch, etc.), infrastructure as code with CDK. Data lives in S3, PostgreSQL/Aurora, DynamoDB, Snowflake, and our FHIR server with Athena for querying S3 and SageMaker for Analytics/ML. The ideal person for this role is a generalist who picks the best tool for the job.
Metriport provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.