Back to jobs

Senior ML Data Engineer - Matching & Recommendation

Reads like an ML Engineer role: training models and running them in production.

Pay
Pay not listedSimilar roles state $166K–$237K
Work setting
Hybrid — work setting source
Details Location: Nashville, TN, hybrid preferred. We'll consider strong remote candidates with directly relevant matching/ML or healthcare-data experience. Experience: Senior-level: we care about demonstrated depth in matching and applied ML more than a year count.
Read the full posting
Employment
Full-time — employment source
Employment type in the employer’s posting: FULL_TIME
From the employer’s posting

What you’ll work on

Full posting
  • Move the matching engine from rules and weights toward semantic matching and vector search

  • Decide how physicians and organizations are represented as embeddings

  • Build evaluation sets and precision/recall comparisons to prove match quality is improving

  • Run entity resolution across 8M+ NPI records into one trustworthy record per organization

  • Ingest, master, enrich and serve data through a simple, reliable pipeline

From the employer’s posting
Take it from rules-and-weights toward semantic matching and vector search.
Decide how we represent physicians and organizations as embeddings
Precision/recall, evaluation sets, real comparison so "better" means something.
Entity resolution across 8M+ NPI records into one trustworthy record per organization.
Ingest, master, enrich, serve - reliable enough to trust without babysitting.

Before you apply

Work authorization
Must already have the right to work in the USYou must be authorized to work in the US without sponsorship, now and in the future

About Tessellate

We're an early-stage healthcare tech company, physicians-first in everything we do.

In the employer’s words · Read in context

Apply at Tessellate

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

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.

Time since we first saw it

Day 3

Early. 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.

Tessellate is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add 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.

  • Python
  • SQL
  • AWS
  • BigQuery
  • DuckDB
  • Looker
  • Metabase
  • PostgreSQL
  • Power BI
  • S3
  • Snowflake
  • Spark
  • Terraform
  • Trino
Where the posting names them
Our Stack Python 3.12 · DuckDB · Athena + Glue · S3 / Parquet · Aurora PostgreSQL · AWS (Lambda, EC2 Graviton, ECS) · Terraform · GitHub Actions Vector search and embedding infrastructure are still open decisions, likely among your first. The platform is young, which means little legacy and real architecture calls that are genuinely yours.
• Know embeddings and vector search in practice, or clearly can and want to get us there. • Write strong Python and expert SQL, with hands-on time in a columnar/OLAP engine at scale (DuckDB, Spark, Trino/Presto/Athena, BigQuery, Snowflake). • Can own your own pipeline without a platform team behind you, but you're not looking for a job that's mostly building DAGs.
• Vector database experience (pgvector and the tradeoffs of dedicated stores vs. Postgres-native). • Customer-facing reporting: dashboards or reports people outside engineering rely on. Our customers increasingly want this; BI tooling (Looker, Metabase, Mode, Power BI) helps. • Graph-based entity clustering and hierarchy inference.
• Production LLM/RAG or agentic AI, and honest views on where it helps versus where it's theater. • Vector database experience (pgvector and the tradeoffs of dedicated stores vs. Postgres-native). • Customer-facing reporting: dashboards or reports people outside engineering rely on. Our customers increasingly want this; BI tooling (Looker, Metabase, Mode, Power BI) helps.

Your next step

Complete your application on jobs.gem.com. The employer’s form will show what is required.

Already applied? Track this application

Job description

View original posting ↗

Physicians make some of the biggest decisions of their careers with almost no trustworthy information: job posts, recruiter calls, and vague promises about culture. Tessellate is building something better: a physician-first platform that helps doctors see where they'd actually fit, using real clinical data instead of recruiter intuition.

At the center of the product is a matching engine that pairs physicians with organizations. Making it genuinely intelligent is your job.


About Tessellate

We're an early-stage healthcare tech company, physicians-first in everything we do. We combine claims data, provider and facility data, physician preferences, and AI-assisted enrichment to help doctors evaluate opportunities with more clarity and less noise. For employers, we're a better way to understand fit; no placement fees, no transactional recruiting games. This isn't a whiteboard idea. We have a working product, real users, a live matching engine, and early commercial demand.


The Work

Our matching engine works today, but it's mostly rules and weights. Over the next year we want to make it genuinely smart; real semantic matching and vector search over physicians, organizations, and clinical profiles - with the rigor to actually measure whether it's getting better. That's the heart of this role.

Two things make it hard. The matching is only as good as the identity underneath it: if one health system shows up as three fragmented records, you get three bad embeddings instead of one good one. And healthcare data is a mess, fragmented across sources that don't agree, so reasoning about fit from it is a genuinely deep problem.

You'll own:

•    The matching engine. Take it from rules-and-weights toward semantic matching and vector search. Decide how we represent physicians and organizations as embeddings, and make the recommendations measurably better.
•    Match quality as a discipline. Precision/recall, evaluation sets, real comparison so "better" means something.
•    The identity layer underneath it. Entity resolution across 8M+ NPI records into one trustworthy record per organization. The bar is "good enough for the model to trust," not perfection, and knowing the difference.
•    The data platform, kept simple. Ingest, master, enrich, serve - reliable enough to trust without babysitting. Our source data refreshes roughly quarterly, so we don't want heavyweight batch tooling the cadence doesn't justify.


Our Stack

Python 3.12 · DuckDB · Athena + Glue · S3 / Parquet · Aurora PostgreSQL · AWS (Lambda, EC2 Graviton, ECS) · Terraform · GitHub Actions

Vector search and embedding infrastructure are still open decisions, likely among your first. The platform is young, which means little legacy and real architecture calls that are genuinely yours.


You're Probably a Fit If You

•    Have built and shipped matching, ranking, or recommendation systems in production, owned a model that had to get measurably better, not just run.
•    Have real applied ML depth: you can frame a problem as precision/recall or ranking, build and validate a model rigorously, and know when a heuristic beats a model.
•    Know embeddings and vector search in practice, or clearly can and want to get us there.
•    Write strong Python and expert SQL, with hands-on time in a columnar/OLAP engine at scale (DuckDB, Spark, Trino/Presto/Athena, BigQuery, Snowflake).
•    Can own your own pipeline without a platform team behind you, but you're not looking for a job that's mostly building DAGs.
•    Have first-principles instincts for entity resolution, you get why identity quality makes or breaks everything above it, and can invent and test approaches rather than reach for a framework.
•    Are comfortable being the data/ML team: small company, no handoffs, you ship and own it.


Nice to Have

•    Healthcare data: NPPES/NPI, NUCC taxonomy codes, claims, CMS files, provider directories.
•    Production LLM/RAG or agentic AI, and honest views on where it helps versus where it's theater.
•    Vector database experience (pgvector and the tradeoffs of dedicated stores vs. Postgres-native).
•    Customer-facing reporting: dashboards or reports people outside engineering rely on. Our customers increasingly want this; BI tooling (Looker, Metabase, Mode, Power BI) helps.
•    Graph-based entity clustering and hierarchy inference.
•    Early-stage startup experience.


First 90 Days

1.  Get deep on the current model and data, and give us an honest read on where match quality is strong, weak, and why.
2.  Stand up a first vector-search prototype with a real way to measure it against what we have now.
3.  Tell us whether organization identity is good enough for the model to trust, or quietly degrading it.
4.  Propose where the matching engine goes next, and how we'll know it's working.


Why This One's Worth It

Most ML jobs are tuning a model nobody ships, or maintaining someone else's DAGs. This is the model at the center of a real product, on a hard and messy dataset, with room to take it somewhere genuinely better and the data underneath it yours to shape. You'd build from a working platform, not a blank page, and directly shape a product that decides where physicians spend their careers.

We're early, and startups aren't for everyone. But you'll learn a lot, own work that matters, and share in the upside if we win.


Details

  • Location: Nashville, TN, hybrid preferred. We'll consider strong remote candidates with directly relevant matching/ML or healthcare-data experience.
  • Experience: Senior-level: we care about demonstrated depth in matching and applied ML more than a year count.
  • Work authorization: You must be authorized to work in the US without sponsorship, now and in the future. We are not able to sponsor visas for this role.
  • eVerify: Our company participates in E-Verify. All legal compliance checks, including Form I-9 and E-Verify identity/work authorization confirmation, are conducted strictly post-offer and within the first three days of employment.
  • Compensation: Competitive base benchmarked to Midwest/South markets and set by experience, plus meaningful early-stage equity.
  • Reports to: Head of Product Engineering.

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 508, the most 899, and the latest week had 508.
August 17Last week

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.

About the role

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.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Nashville

Details - Location: Nashville, TN, hybrid preferred. We'll consider strong remote candidates with directly relevant matching/ML or healthcare-data experience. - Experience: Senior-level: we care about demonstrated depth in matching and applied ML more than a year count.
Work authorization
- Experience: Senior-level: we care about demonstrated depth in matching and applied ML more than a year count. - Work authorization: You must be authorized to work in the US without sponsorship, now and in the future. We are not able to sponsor visas for this role. - eVerify: Our company participates in E-Verify. All legal compliance checks, including Form I-9 and E-Verify identity/work authorization confirmation, are conducted strictly post-offer and within the first three days of employment. - Compensation: Competitive base benchmarked to Midwest/South markets and set by experience, plus meaningful early-stage equity.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.