Back to jobs

Healthcare Data Analyst

New York, New York, United States

Actively hiring, first seen by us 9 hours ago
Pay
Pay not listedSimilar roles state $95K–$145K
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting
Apply at airpay

Posting record

Report an error

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

Status in our records
Live
First seen by us
Nov 18, 2026today
Recorded sightings
2
Last seen by us
Nov 19, 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

$95K–$145K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,265 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 5 and day 43.

From 15,095 similar postings that came down. Coming down is not always a hire.

airpay 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
  • Excel
Where the posting names them
Comfort with Python or scripting for data manipulation.
Strong data skills: comfortable in SQL and Excel/Sheets, can write a structured query, build a pivot, and sanity-check a dataset without hand-holding.

Your next step

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

Already applied? Track this application

Job description

View original posting ↗

About AirPay AirPay automates dental insurance verification and revenue cycle workflows for dental practices. We process millions of eligibility and benefit transactions annually, sourcing data from payer portals, EDI pipelines, and direct connections. Our data team sits at the intersection of scraper engineering, payer operations, and product, turning raw benefit data into actionable outputs for practices and their patients. The Role We’re looking for someone whose job is to find what’s silently wrong or missing in our benefit data, before a practice or a patient does. This isn’t a reporting role and it isn’t a dashboard role: the deliverable is catching the problem everyone else’s tidy summary missed. Coverage that reads “active” but lapsed last month. A field that comes back blank and gets quietly treated as “no benefit.” A payer whose data looks clean until you notice an entire location’s records are null. You’ll own a slice of our verification pipeline (a set of payers, a data domain, a monitoring surface) and run it: surface what actually matters, with evidence, without needing every anomaly pointed out to you first. You’ll report to the Head of Data and work as a peer-level collaborator with engineering, customer success, and operations. What You’ll Own Data quality investigations: Run structured investigations into benefit data anomalies across 100+ payers. Triggers are both scheduled (cohort comparisons between data sources: portal-scraped vs EDI vs internal estimates) and signal-driven (customer escalations, operational reports). Output is engineer-actionable findings documents: what’s broken, where, what evidence, and critically, what’s wrong that nobody flagged. Common patterns include coverage-percentage inversions, blank-fill in returned data passed off as a real answer, frequency-normalization gaps (such as “12 months” vs “1 service year”), and stale data carrying across plan changes. Completeness and accuracy monitoring: Own a monitoring surface and define what “healthy” looks like for it, then catch when reality drifts from it. The hard part isn’t building the dashboard; it’s noticing the gap the dashboard doesn’t show. Customer issue triage analysis: Own the weekly pattern analysis on customer-issue tickets. Categorize ticket types, track volume trends, identify recurring root causes, and surface signal that drives parser fixes, product changes, or QA process updates. Ad hoc investigations: When a payer behaves unexpectedly or a hypothesis needs checking, you scope and run the investigation and write up the findings, starting from a vague “something looks off,” not a pre-scoped ticket. Requirements What We’re Looking For Required: 3 to 5 years where finding what’s missing or wrong was the job: data quality, completeness and validation, data audit, reconciliation, or investigative analytics. If your prior work was producing clean reports and dashboards, this is a different role. We’re hiring the person who finds what those reports leave out. Healthcare data, payer analytics, insurance operations, or RCM background: Dental not required, but you need to understand how benefit structures work (coinsurance, deductibles, frequency limits, network tiers). Strong data skills: comfortable in SQL and Excel/Sheets, can write a structured query, build a pivot, and sanity-check a dataset without hand-holding. More important than tooling breadth is the instinct to distrust a clean-looking result and dig until you know why it’s clean. Self-directed ownership of an area. Point you at a payer, a domain, or a surface, and you run it: scope the questions, find the issues, frame them for a business audience, without per-step direction. Clear written communication: Output is findings documents and structured reports, not just raw data. Strong plus: EDI X12 familiarity (270/271 eligibility transactions especially). Experience at a health tech company, payer, or benefits administrator. Comfort with Python or scripting for data manipulation. Experience with parser output, portal data, or unstructured benefit text. Growth Path This is the first analyst hire on a growing data team. Several surfaces you’d eventually own, such as the data quality scorecard, deeper engineering interfaces, and the team’s operating rhythm, are still being built. You’d help shape them rather than inherit fully-formed processes. The role anchors day-one as a data-quality specialist owning a defined slice of the pipeline, with specialization paths opening as the team matures: EDI and payer-depth analysis, customer-facing analytics delivery, or clinical/dental content expertise. Why This Role High-signal, low-noise work: you’ll see anomalies across the entire benefit landscape before anyone else does, and you’re the one trusted to catch them. Direct impact: your findings drive parser fixes, product features, and QA standards. Small team with high ownership: no queuing behind a data engineering backlog. Comp: competitive for mid-level healthcare data roles in NYC.

Demand for Analyst roles

New Analyst postings at the employers we follow are up 25% over the last 6 weeks compared with the 6 before.

Weekly new Analyst postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 990, the most 1,513, and the latest week had 1,366.
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 Analyst, by the work the posting describes.

Analysts answer business questions with data. They pull numbers with SQL, build reports and dashboards, and explain what changed and why to the people making decisions.

Most postings ask for SQL, spreadsheets, a dashboard tool such as Tableau or Power BI, and clear writing.

Unlike a data scientist, an analyst mostly explains what happened rather than building models that predict what will.

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

New York, New York, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

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.