Talent Map Brief: Healthcare Data & Analytics in Minneapolis–St. Paul
A worked market hypothesis for healthcare analytics, clinical data, payer/provider data engineering, and adjacent talent in the Twin Cities.
Role: Healthcare Data / Analytics Engineer or Analyst · Geography: Minneapolis–St. Paul, Minnesota · Last reviewed: 2026-09-06
Ask SourcingOS about this page
Literal role requirements
- Healthcare-domain experience only if explicitly required
- Required analytics/data engineering stack
- Location/hybrid constraints
- Any credential or regulated-data requirements explicitly stated by the role
Title families to test
- Healthcare Data Analyst
- Clinical Data Analyst
- Data Engineer
- Analytics Engineer
- BI Developer
- Population Health Analyst
- Healthcare Informatics Analyst
Donor categories
- Health systems and hospitals
- Health insurers and managed-care organizations
- Medical-device and healthcare technology companies
- Healthcare consulting/analytics firms
- Digital health and care-management platforms
Geography bands
- Minneapolis
- St. Paul
- Bloomington / Edina / Richfield
- Minnetonka / Eden Prairie / western suburbs
- Remote-capable healthcare teams where the actual role permits
Evidence and source lanes
- Direct-title search
- Healthcare-domain employer mapping
- Technical stack evidence
- Public professional association/credential evidence where relevant
- ATS rediscovery
- Conference/publication evidence for informatics specialists
- Licensed people-data expansion
Questions that determine whether the market is actually scarce
- Is healthcare experience mandatory or can regulated-industry data experience transfer?
- Is the role analytics-heavy or platform/data-engineering-heavy?
- Are Epic, claims, FHIR, HL7, or other domain signals actual requirements?
- Is a clinical credential required?
- Does hybrid attendance materially reduce the viable pool?
Actionable search plan
- Split clinical/informatics and pure data-engineering archetypes.
- Map provider, payer, medtech, and digital-health donor categories separately.
- Keep licensure/credential evidence distinct from ordinary domain experience.
- Use stack evidence to distinguish analyst/BI work from engineering work.
- Calibrate on domain depth versus technical depth after the first slate.