Senior Data Science Engineer I, Claims
Turquoise · San Diego, CA
$170,000–$190,000
Jul 23, 2026
San Diego, CA
Jul 25, 2026
What this job asks for AI summary
A data engineering role focused on healthcare claims data — building and maintaining pipelines that take raw claims from varied sources through to enriched, standardized formats, while also handling de-identification, PHI/PII reduction, and data quality observability. The work spans ELT/ETL orchestration, data modeling for both analytical and transactional workloads, and API or data-store integrations. It suits someone with hands-on claims data experience and strong Python, SQL, and cloud fundamentals.
Mid level · 4+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 800 people nationally plausibly meet what this posting asks for (database architects). range 230–1,200
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $142,568 (middle half $111,775–$173,013).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
The role sits at the intersection of data engineering (pipeline/warehouse building) and software development; 15-1243 (Database Architects) was chosen because the primary deliverables are data pipelines, data models, ELT/ETL workflows, and data lifecycle ownership, but 15-1252 (Software Developers) is a genuine runner-up given the software engineering rigor, OOP/functional programming, and automated testing expectations.
The title carries no seniority level. With 4+ years required and scope limited to owning a data domain on a team (not setting cross-team direction), this maps to Mid rather than Senior.
Python, SQL, PostgreSQL, Trino, ClickHouse, Airflow, Datadog, and AWS are all listed in the Responsibilities section as tools used to build pipelines — treated as hard gates given their explicit enumeration in the role's core work description.
Healthcare claims data experience (EDI 837/835, CMS VRDC, Komodo, MarketScan, etc.) is listed under 'What you'll bring' with firm language but names domain knowledge rather than a concrete named technology, so it is omitted per the generic-concepts rule.
LLMs appear under 'What you'll bring' with soft framing ('thoughtful use of AI coding agents and LLMs') — treated as preferred.
AWS S3, EC2, and RDS are listed under 'Bonus points' alongside Azure/GCP as alternatives — all treated as preferred.
Version control is mentioned under 'What you'll bring' as part of 'software engineering rigor including automated testing, version control' — included as preferred since no specific tool (Git, etc.) is named.
No compensation figures were provided beyond 'competitive pay with equity options'.
Bachelor's degree is listed as 'or equivalent experience' and explicitly notes 'non-traditional backgrounds welcome' — the degree requirement set to None.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.