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.
Location type: RemoteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: TechnologyFrom the employer’s posting
Most of what matters in a health record isn't in a structured field - it's in the note, the discharge summary, the pathology report, the scanned fax.
You'll be our first ML hire, joining Platform Engineering and reporting to the Head of Platform Engineering, as technical owner of this multi-quarter effort.
Own the full lifecycle of extraction models, from framing to retraining
Build the evaluation harness that defines whether extraction is accurate enough
Build clinical NLP pipelines on messy real-world data with backend engineers
Partner with Clinical Data Managers on curation design and technical QA/QC
Use LLMs with versioned prompts, real evals, and tracked cost and latency
Most of what matters in a health record isn't in a structured field - it's in the note, the discharge summary, the pathology report, the scanned fax. Turning that unstructured clinical text into trustworthy, structured features is what makes a longitudinal health history usable for research, and it's one of the highest-leverage capabilities Novellia can own.
You'll be our first ML hire, joining Platform Engineering and reporting to the Head of Platform Engineering, as technical owner of this multi-quarter effort. The interesting decisions are still open - what we extract first, how we know we're right, what a mature extraction pipeline looks like at our scale. There's no existing approach to inherit or defend.
Own the full lifecycle of extraction models - framing, data/annotation strategy, model selection, training/fine-tuning, evaluation, deployment, monitoring, retraining.
build the evaluation harness that makes the answer defensible - the first deliverable, not a follow-up.
Build clinical NLP pipelines against messy real-world data and work with backend engineers to productionize what you build.
Partner with Clinical Data Managers on curation design and own the technical half of QA/QC alongside them
Use LLMs with the same rigor you'd apply anywhere: versioned prompts, real evals, tracked cost/latency, known failure modes.
Will you now or in the future require sponsorship for employment visa status (e.g., H-1B visa status)? Novellia is not able to sponsor visas at this timeFrom the employer’s application form
From the employer’s posting.
Novellia is the first and only company that lets anyone in the U.S. gain access to nearly a decade of their health data in under 30 seconds — 100% free.
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 84
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.
2 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.
- Practical, current experience with LLM-based approaches: prompt development, structured output, retrieval, fine-tuning where warranted, evals and observability for generative systems - enough to know where they help, and where they quietly don't. - Strong engineering fundamentals in Python. Your work runs in production, not only in a notebook. - Strong collaboration instincts across the ML boundary: you define problems with stakeholders before solving them, write clearly, and bring people along.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Since 2023, our mission has been clear: to be the north star of patient equity.
Every day, we strive to bridge the gaps in healthcare access and outcomes to ensure that every patient, regardless of background or circumstance, receives the care they deserve. As a member of our team, you'll be at the forefront of innovation, working alongside passionate individuals who share your dedication to creating best-in-class, patient-centric products in healthcare. Together, we're revolutionizing the way people understand their health and working with the world's top researchers to accelerate innovation.
Novellia is the first and only company that lets anyone in the U.S. gain access to nearly a decade of their health data in under 30 seconds — 100% free. All your health records, across every doctor, in one place, always up to date.
We are the only patient-powered real-world data platform delivering comprehensive, patient-authorized longitudinal health insights to accelerate biopharma innovation. Unlike traditional RWD providers who deliver fragmented institutional data, we empower patients to access 20+ years of their health records, then transform these complete health journeys into fit-for-purpose datasets for evidence generation, regulatory submissions, and market access. We are growing 5x year over year, have raised close to $30M in funding, and are backed by tier-1 investors including Spark Capital, Khosla Ventures, and Bling Capital.
Working with the world's top researchers, we turn health insights into life-changing action for millions of people around the world.
Most of what matters in a health record isn't in a structured field - it's in the note, the discharge summary, the pathology report, the scanned fax. Turning that unstructured clinical text into trustworthy, structured features is what makes a longitudinal health history usable for research, and it's one of the highest-leverage capabilities Novellia can own.
You'll be our first ML hire, joining Platform Engineering and reporting to the Head of Platform Engineering, as technical owner of this multi-quarter effort. The interesting decisions are still open - what we extract first, how we know we're right, what a mature extraction pipeline looks like at our scale. There's no existing approach to inherit or defend.
The work draws on two toolkits. Roughly 70% is applied ML on clinical text: entity extraction, classification, sequence labelling, annotation strategy, error analysis, calibration, and the evaluation discipline that tells you whether your numbers mean anything. Roughly 30% is LLM-based: prompt development, structured output, retrieval, and the evals and observability that keep generative approaches honest. Deciding which approach a given problem calls for is the most interesting part of the job, and that call is yours.
We're looking for a leader in this seat: setting technical direction rather than waiting to be handed a problem. If this grows the way we think it will, leading the team we build around it is on the table.
Own the full lifecycle of extraction models - framing, data/annotation strategy, model selection, training/fine-tuning, evaluation, deployment, monitoring, retraining. Not a research seat, not a hand-off seat.
Define what "accurate enough" means with clinical and customer-facing stakeholders, and build the evaluation harness that makes the answer defensible - the first deliverable, not a follow-up.
Partner with Clinical Data Managers on curation design and own the technical half of QA/QC alongside them: which variables are extractable, how an instruction becomes a model spec, and the tooling/sampling/error analysis behind human-in-the-loop review.
Build clinical NLP pipelines against messy real-world data and work with backend engineers to productionize what you build.
Use LLMs with the same rigor you'd apply anywhere: versioned prompts, real evals, tracked cost/latency, known failure modes.
Make extraction quality legible to non-ML colleagues, and treat de-identification, PHI handling, audit trails, and access controls as part of the modelling problem, not someone else's checklist.
Help shape the roadmap around the problems you see - a mission and a close working partner, not a backlog.
Healthcare or life sciences experience with real clinical data - clinical notes, EHR data, claims, registries, or similar. This one is not negotiable for us.
6+ years in applied ML, with models you personally took from problem statement to production and kept working - you know what degraded, how you found out, and what you did.
Depth in applied ML on text: information extraction, NER, classification, sequence labelling, weak supervision, and the evaluation practice around them, including annotation guidelines and inter-annotator agreement you've had to act on.
Practical, current experience with LLM-based approaches: prompt development, structured output, retrieval, fine-tuning where warranted, evals and observability for generative systems - enough to know where they help, and where they quietly don't.
Strong engineering fundamentals in Python. Your work runs in production, not only in a notebook.
Strong collaboration instincts across the ML boundary: you define problems with stakeholders before solving them, write clearly, and bring people along.
A track record of solving problems rather than closing tickets. Self-directed, comfortable without a playbook, and comfortable being wrong in public when the evidence says so.
Fluency with clinical terminologies and standards: SNOMED CT, ICD-10, LOINC, RxNorm, CPT, FHIR
Experience with HIPAA, SOC 2, de-identification methodology, or IRB and regulatory-grade data work
Experience as an early or first ML hire
Experience building or running human-in-the-loop annotation and QC operations at scale
OCR and document-understanding experience on low-quality real-world documents
Experience mentoring or leading ML engineers, or interest in growing that way
Not a research role. The bar is extraction quality in production, not publications.
Not an LLM-wrapper role. If your instinct is that every problem is a prompt away from being solved, we'll frustrate each other.
Not a large-team role yet. You'd be the first ML engineer in a small Platform Engineering function - breadth and influence, and fewer specialists to lean on.
Not a role where someone hands you a clean labelled dataset. Building it is the job.
Ground-floor ownership of a capability with direct commercial weight, with influence over architecture, roadmap, and eventually hiring.
Both halves of the modern ML toolkit in one seat, on a problem where the choice between them genuinely matters.
A manager who treats process and people work as legitimate engineering work, and intends for this seat to grow.
Health tech means the work has stakes - better extraction means higher quality research
Equity in Novellia
Medical, dental, and vision coverage
401(k)
Flexible time off
Wellness stipend
Up to 12 weeks of parental leave
Don't meet every requirement? Studies show women and people of color are less likely to apply unless they meet every qualification. If you're excited about this role but your experience doesn't align perfectly, we encourage you to apply anyway - you may be the right fit for this or another role.
U.S. Applicants Only
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.
USA
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.