Senior Data Engineer hos Doktor.se i Stockholm

What you'll do

Our data platform works, but it was built to solve yesterday's problems. We have data scattered across Postgres databases, Amplitude, S3 file dumps, and a tangle of Python jobs that move it around. The reports get built and the business runs on them. But trust is brittle, reconciliation is too manual, and the foundations need work before we can scale to where we're going.

We need someone who can help us rebuild this — not maintain what we have, but reshape it. If you want a place where the warehouse is clean and the pipelines just run, this isn't it. If you want to redesign a data platform from foundations up, with real ownership and the leverage to make it good, here's what you'd own:

• Reshape the data foundations — multi-tenancy, retention, and data contracts with backend services.
• Decide what the warehouse actually is: self-hosted Postgres + dbt, managed Snowflake or BigQuery, or something else. You'll shape this.
• Unify three data sources that don't currently talk to each other: our operational databases, Amplitude product analytics, and a long tail of S3-based partner integrations.
• Build observability into the platform — lineage, freshness, and alerting that actually means something.
• Own reporting that finance, operations, and the board rely on. Make those reports trustworthy by design, not by manual reconciliation.
• Work directly with backend, product, and finance teams. You're not a service desk — you're a peer who shapes how data gets produced upstream, not just consumed downstream.
• Use AI aggressively for pipeline boilerplate, schema generation, transformation logic, and exploratory analysis — the same discipline we hold ourselves to.

You'll be part of a small data engineering team. That's a lot of ownership and not a lot of cover. The right person sees that as opportunity.

What we're looking for

• You've designed and run data platforms in production — not just written DAGs. You've thought about what to build vs buy, where transformations belong, and how to keep schemas honest as products evolve.
• You're fluent in Python and SQL, with strong opinions about how Postgres should be used as a warehouse (and when it shouldn't).
• You've used dbt or equivalent in a real environment and understand data modelling — staging, marts, tests.
• You have working knowledge of one or more managed warehouses (Snowflake, BigQuery, Redshift) and can evaluate them honestly against self-hosted options.
• You're comfortable with orchestration tools — Airflow, Dagster, Prefect, whichever — and know what an orchestrator is for.
• You think about data contracts as a product problem, not just a pipeline problem, and can make that case to backend engineers.
• You use AI in your daily work and can talk about how. If your answer is "I haven't really tried it yet," this isn't the role.
• Healthcare data experience is a plus. GDPR fluency is expected. Patientdatalagen familiarity is a bonus.
• You have a relevant university degree or equivalent experience.

What we offer

• Real influence. The data platform is being rebuilt and you're at the centre of it.
• Small team, direct impact. 25 engineers — your work is visible, not lost in a machine.
• Autonomy. No micromanagement, no endless approval chains.
• Collective agreement, 30 days vacation, wellness allowance, personal development budget.