Azure Data Engineer + healthcare/patient data experience - Remote - W2 only - 12+ years canidates only
Posted 1 day ago by 1752148309
Negotiable
Outside
Remote
USA
Summary: The Azure Data Engineer role focuses on upgrading legacy systems and building new data solutions within the healthcare sector. Candidates must have experience with healthcare or patient data, particularly with organizations like United Healthcare or Cigna. The position involves supporting existing operations while also contributing to new builds, particularly in data ingestion and analysis using tools like DBT and Snowflake. This is a remote position requiring senior-level expertise and is classified as outside IR35.
Key Responsibilities:
- Support existing operational work and legacy systems.
- Contribute to the upgrade of legacy foundations and new builds.
- Perform data ingestion and analysis using Azure Data Factory and Snowflake.
- Troubleshoot issues, conduct root cause analysis, and propose solutions.
- Collaborate with teams to ensure integration of core data elements around providers and member populations.
Key Skills:
- Experience with DBT and Snowflake (data warehouse).
- Proficiency in data ingestion with Azure Data Factory.
- Strong data analysis and root cause analysis skills.
- Background in healthcare or patient data.
- Senior-level experience in data engineering.
Salary (Rate): undetermined
City: undetermined
Country: USA
Working Arrangements: remote
IR35 Status: outside IR35
Seniority Level: Senior
Industry: IT
Role: Azure Data Engineer
Location: Remote
Duration: 6+ Months
W2 role
need some kind of healthcare/patient data experience.
United healthcare, Blue cross, Cigna are all examples of this. Pharmacy companies, etc.
Overall initiative for all four openings:
- This is a legacy foundation upgrade and a new build.
- Background: Recently migrated data into snowflake that was run on prem and they need to solidify areas focused on core data elements around providers and member population and how that all integrates other systems.
- Current flow of the system is sending data into vendors (Milliman Insights) and into their instances of Epic. These two pathways are putting a strain on existing world, in addition to the remaining analytics they are putting on top of this. Thus, showing cracks in the systems.
- Solution: rebuild, start with a blank slate in some cases, while also keeping existing systems running. To do this, they have been shuffling some people around to make this work, so there will be backfills, and net new openings.
- Some of these roles will be supporting their legacy operations, and some of the roles will be working on the teams doing the net new builds
Project Scope (dig into details here):
- Will be supporting existing operational work
Why is req open?
- Backfill opening for legacy operations team
Must-Haves (Concepts & Tools):
- DBT
- Snowflake (data warehouse)
- Data ingestion with Azure Data factory
- Data analysis, root cause analysis
- Must be able to trouble shoot, identify issue, do the analysis and propose a solution.
- See and issue and do validation.
- Senior level
What Will Win (formerly known as Nice-to-Haves ):
- Payer/ population health- insurance experience (united health, cigna, blue cross)
- Operations background