Data Engineer

We are looking for the person who will own the data foundation of a best-in-class data platform for hospitals

Health DataCore (HDC) is a Copenhagen-based health-tech company building a data platform that enables better treatment and management of patients.

That means our platform must do two things at once: Provide easy access to harmonized data about patients across systems and stand up to the scrutiny that comes with handling patient data in a regulated environment – parts of the platform will be classified as medical device software. Both start with the data – which arrives in many formats, from many systems, with varying quality, and has to end up harmonized, validated, traceable and interoperable before anyone can safely use it.

We are now putting together the delivery team that will build our platform, and we're looking for a Data Engineer to own that foundation: the pipelines, the data models and storage design, and the quality of the data flowing through them.

Why this role is different

In many organisations, data engineering means maintaining pipelines someone else designed, feeding a data warehouse someone else modelled. This isn't one of them.

We've chosen a lean, role-based setup: a Product Manager owns what we build and why, a Solution Architect owns the overall architecture, and a small delivery team builds it, working with a Scrum Master who is also the team's people manager. Within the team, you own the data – how it gets in, how it's modelled and stored, and how we know it's correct.

You’ll work closely with the Solution Architect on how data fits into the overall architecture, and with our Backend Engineer on how the platform’s services use it. In a regulated health context, data quality isn’t a nice-to-have – it's part of what makes the product safe to use. You’ll be the person making sure we get it right.

What you’ll be working on

• Designing and building data ingestion pipelines from laboratory, blood bank and EHR systems, and from national MedCom messaging
• Data modelling and storage design for harmonized, structured patient data across source systems
• Building data quality checks, validation and enrichment into the pipelines – not as an afterthought
• Building and maintaining interoperability with health data standards and terminologies
• Choosing, setting up and running pipeline orchestration – containerised, so it runs the same way in a customer's cloud or on-premises environment
• Ensuring data lineage and traceability, so we can always show where data came from and what happened to it
• Handling sensitive health data securely and in line with GDPR and our regulatory requirements
• Contributing to the documentation our medical device and regulatory work depends on
• Working closely with the Solution Architect and the Backend Engineer on how data and services fit together

What we’re looking for

We care more about how you think about data than which tools you’ve used to move it.

We imagine you have around five years or more of professional data engineering experience and strong fundamentals: ETL/ELT pipeline design, data modelling, pipeline orchestration, and running data workloads reliably in production. We haven’t settled the stack yet, so this is deliberately tool‑agnostic. SQL will be the daily core of the job, though, and software development skills beyond pipelines are valuable early on – we need builders, and you may well contribute across the platform.

You understand health data standards and the requirements that come with health data – how clinical data is structured, why interoperability is hard, and why accuracy, traceability and privacy matter when the data is about patients.

You enjoy designing data models that hold up over time; building pipelines that fail loudly rather than silently; turning messy, inconsistent source data into something trustworthy; documenting what you build so others can understand and verify it; and working closely with engineers and architects to get the whole system right.

Validated, traceable, well‑modelled data isn’t a stretch goal here – it's a requirement, and we’ll expect you to hold that line.

Strong pluses: regulated data work, preferably in life science or health; expert SQL and relational databases (SQL Server, MySQL or PostgreSQL); JVM or Python data tooling; standards and terminologies such as HL7 FHIR, OMOP CDM, SNOMED CT, ICD-10 (SKS in Denmark), NPU or LOINC; Danish hospital data sources; an understanding of what the European Health Data Space (EHDS) will require; and running pipelines in containers, including on Azure.

What you’ll get

Ownership of the foundation. You’ll own the pipelines, data models, storage design and data quality that the rest of the platform is built on – within the architecture the Solution Architect sets.

A clear role in a lean setup. No layers of management between you and the decisions. You’ll work directly with the Solution Architect, Product Manager and the rest of the delivery team.

The chance to shape a team. You’ll be one of the first members of the delivery team and help set its standards, habits and culture.

Work that matters. Harmonized, trustworthy patient data can improve treatment and patient management. Getting it right is a genuinely hard data problem.

About HDC

HDC is an early-stage company, but not starting from nothing: the platform builds on clinical decision‑support systems developed at Rigshospitalet and in daily clinical use there for years. Our task is to turn proven clinical software into a product that can run safely in any hospital. The team is small, and the two engineers we’re hiring now will be in the room for the early decisions.

HDC exists to make health data easier to use – securely, compliantly and in a way that clinicians, researchers and patients can trust.

We’re building a platform where quality, traceability and regulatory compliance are part of the foundation, not something bolted on afterwards.

• Hybrid: 2-3 regular days a week on site.
• Full-time, permanent position. Start as soon as possible, by agreement.
• Working language is English. Danish is a plus, since the source systems and their documentation are in Danish.
• You must be eligible to work in Denmark.

Applications are reviewed continuously, and the role closes when it's filled.