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.
Reads like an ML Engineer role: training models and running them in production.
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 type in the employer’s posting: FULL_TIMEFrom the employer’s 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
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.
You must be authorized to work in the US without sponsorship, now and in the future
We're an early-stage healthcare tech company, physicians-first in everything we do.
In the employer’s words · Read in context
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
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 3
Early. Similar jobs usually come down between day 7 and day 76.
From 6,398 similar postings that came down. Coming down is not always a hire.
1 open job
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.
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.
Complete your application on jobs.gem.com. The employer’s form will show what is required.
Already applied? Track this application
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.
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.
- 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.