> Markdown version of [/jobs/ext/3186386-machine-learning-engineer](https://www.wearedevelopers.com/jobs/ext/3186386-machine-learning-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Machine Learning Engineer - **Company:** Metriport Inc. - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Artificial Neural Networks, Big Data, Clinical Data Repository, Healthcare Effectiveness Data and Information Set, Python (Programming Language), Machine Learning, Azure Machine Learning, SQL Databases, TypeScript, Feature Engineering, Fast Healthcare Interoperability Resources, Delivery Pipeline, Large Language Models, Deep Learning, Backend, Health Level Seven International, Machine Learning Operations, Software Version Control - **Published:** September 3, 2026 - **Apply:** https://startup.jobs/senior-ai-ml-engineer-metriport-9922224 ## About the Role 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., * 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. ## Description 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. What you'll be doing 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.