Analytics Engineer

Meridian
United States
7 days ago
Apply on jobs.lever.co
Prepare application

Role details

Contract type
Permanent contract
Employment type
Full-time (> 32 hours)
Experience level
Expert
Experience required
5 years minimum
Compensation
$142,000.0 - $167,000.0
Working hours
Regular working hours
Job source

Tech stack

Artificial Intelligence Amazon Web Services Data Analysis ASC X12 Standards Big Data Health Informatics Code Coverage Python (Programming Language) Reference Data SQL Databases Fast Healthcare Interoperability Resources Pyspark
+2 more
Health Level Seven International Data Pipelines

Job description

Remote Hiring Remotely in US 142K-167K Annually Senior level Remote Hiring Remotely in US 142K-167K Annually Senior level Own healthcare analytics data methodology, including episode grouping, provider attribution, cost standardization, quality measures, reference data, pipelines, QA, and production delivery. Translate feature requests into specifications and validated analytics. Reconcile results, establish recurring data-quality coverage, investigate failures, and collaborate with engineering, data science, product, clinical informatics, and customer teams. Advanced SQL and healthcare claims expertise are central to ensuring accurate, defensible customer metrics. The summary above was generated by AI

Clarify is an outcomes company. We partner with 60+ health systems to do the work that most analytics vendors walk away from. Across 900 million annual referrals and $1 trillion in downstream spending, we identify where mission and margin are falling out of alignment, and then we embed with the people who can change it: the liaison in the field, the contract negotiator at the table, the service line leader running the plan.

We bring the most complete picture of care economics in healthcare. 300 million patient journeys. 5.6 trillion price transparency rates. Episode-level quality across every major payer contract. Clarify Meridian puts that picture to work at the point of every decision. But the picture is not what we deliver. The outcomes are.

We are looking for a Senior Analytics Engineer to own the analytics behind the metrics customers see. This role will advance the technology that groups Clarify’s standardized healthcare claims into units of analysis such as patient years, surgical episodes, and referral relationships, then them into the metrics and categories the products run on. Every metric traces back to a grouping someone on this team defined, populated, and validated.

You will own pieces of that layer from pipeline development, QA and test coverage, and promotion into production. Feature requests arrive from product and customer-facing teams, and you will scope them, write the logic, and validate the result.

This is a hands-on role that is an ideal fit for an analyst who knows healthcare data, understands what the codes on a claim represent, and treats a wrong number as their own problem. SQL is the daily tool, and the scripting and pipeline tooling can be picked up here., The Senior Analytics Engineer will be responsible for a range of responsibilities, including (but not limited to): Own the data methodology

  1. Carry derived data points through from development through QA into production, including the logic that defines them and the tests each one has to pass before they are consumed downstream.
  2. Write the data methodology and logic customers ultimately see: episode triggers, provider attribution, cost standardization, and quality measure numerators, denominators, and exclusions.
  3. Manage and build upon Clarify’s reference data library. This spans physician and facility affiliation mappings, codesets and their derivative mappings (ICD, HCPCS, NDC, DRG, etc. and their mappings to service lines/higher level categories), geographical info, etc.

Validate the numbers

  1. Prove a number before anyone else has to, using reconciliation SQL, version-over-version comparisons that show what moved, and impact analysis run before a logic change ships.
  2. Turn one-off QA into standing coverage: the data tests, the comparisons against a known-good baseline rather than the previous run, and the completeness thresholds that have to pass before data reaches a customer.
  3. Run the data refresh and delivery cadence for customer environments once ingestion is complete, working test failures to root cause with engineering and handing off validated groupings to data science and product.

Turn requests into delivered analytics

  1. Scope feature requests from product, clinical informatics, and customer teams, write the specification and acceptance criteria, decide what you do yourself and what goes to an engineer, and follow it to release.
  2. Settle methodology that crosses teams, including attribution logic, referral definitions, and provider reference data, where data quality, run time, and scope get traded against each other.
  3. Hold AI-assisted tooling to the same standard as your own work. Clarify uses agentic tooling for data sourcing, specification drafting, and triage, and this role checks generated output against source data and sets the review it has to pass.

What we are looking for We are always looking for new team members who will add to our culture and have a strong passion for impact. In particular, the Senior Analytics Engineer will have

Requirements

  1. Bachelor’s degree in a quantitative, technical, or health-related field, or equivalent practical experience
  2. Five or more years in data analysis, healthcare analytics, or a comparable data-heavy role
  3. Advanced SQL. You query large datasets without help, build a metric from raw source records, define its grain, and defend every value in it
  4. Experience in the AWS ecosystem, experience with industry-leading AI models, especially in their use for code development
  5. Working knowledge of healthcare data and the context around it, such as claims, provider, or network data, and what the codes on a claim represent
  6. Experience with data in a production setting, where tables refresh on a schedule, other teams depend on your output, and changes move through QA before release
  7. Clear writing. Specifications, acceptance criteria, and decision records an engineer can act on and an auditor can follow six months later, 1. A high bar and the work ethic to hold it. You do whatever it takes to get there - chasing down the missing answer, filling the gap no one owns, staying with it until it is right. You expect the same standard from the work around you.
  8. Ownership mindset. You treat the components you own as yours, and you carry a problem to its outcome rather than handing it off halfway.
  9. Comfort with ambiguity. The problems may be clear but not yet well defined. You make a reasonable call, state your assumptions, and keep moving.
  10. A bias toward action. You are a doer. When something needs to be built, validated, or unblocked, you go do it, and you prototype your way to an answer., 1. Depth in a healthcare domain such as episode grouping, risk adjustment, quality measurement, or provider and network reference data, including CMS or NCQA measure specifications, clinical value sets, or standards such as HL7, FHIR, and X12
  11. BI and dashboarding tools, and a record of explaining an analysis to an audience that does not work in the data
  12. Recurring data quality checks you set up yourself rather than one-off validations
  13. Python/Pyspark experience

Benefits & conditions

  • Competitive compensation (base + bonus + equity)
  • Quality health insurance
  • Traditional 401K plan
  • Vision, dental, disability and life insurance
  • Flexible Spending Accounts and Commuter Benefits
  • Generous PTO
  • Flexibility
  • Monthly work-from-home stipend
  • Remote friendly
  • A collaborative workplace, which will challenge you and celebrate your work
  • A chance to learn with and from interesting and enthusiastic colleagues

Apply for this position

This job is hosted externally. Click below to view the full posting and apply.

Apply on jobs.lever.co
Prepare application

Good distractions

Talks and stories from around this role — technically off-topic, practically not.

3:28 min

Defining big data and machine learning fundamentals

Ayon Roy · LIVE

4:32 min

Harnessing Spark with Python using PySpark and Py4J

Ayon Roy · LIVE

1:48 min

Automating exploratory data analysis within training pipelines

Dora Petrella · World Congress 2023

1:20 min

Identifying multi-disciplinary talent for developer experience engineering roles

Hazal Mestci +1 · Coffee With Developers

2:10 min

Why organizations combine big data and machine learning

Ayon Roy · LIVE

1:36 min

Performing exploratory data analysis to uncover underlying patterns

Julian Joseph · LIVE

Videos

See all

Related articles

See all