JUPUS logo

Staff Data Engineer

JUPUSData Science

Job Description

We're seeking a Staff Data Engineer to join one of the fastest-growing AI legal tech companies in Europe. You'll take technical ownership of the data platform behind how we run the business: the pipelines, the warehouse, and the definitions behind the numbers our leadership team actually uses.

You'll report to our Head of Engineering and work alongside a colleague who owns the business-facing side of data, plus our infrastructure and application engineers. This is a senior individual contributor role with no line management in either direction, roughly 70% hands-on building, 30% defining, documenting and explaining.

Your Challenge and Opportunity in This Role

JUPUS supports hundreds of law firms across Europe, and our customer base is growing roughly 4x a year. Our data platform has grown with it (ClickHouse, dbt, Python extract-load pipelines into an S3 data lake, orchestration in GitHub Actions) and it has grown fast.

Your job is to make it trustworthy. That means modernising what already exists, making historical trends a record of what actually happened rather than a nightly re-derivation of it, and owning the definitions behind the metrics that reach our board. This is not a greenfield build, and it is not a maintenance seat. It is a real platform with real problems, and you would own it.

Tasks

  • Own the data platform end to end: ingestion and the raw layer, the ClickHouse warehouse, and the dbt project on top of it. You're the person who can say whether a number is wrong or the pipeline is.
  • Make our numbers trustworthy: reliability, correctness, and a history that holds up, so that a trend is a record of what actually happened rather than a re-derivation of it.
  • Own the metrics the company runs on, starting with our customer health score- the definition, the denominator, the eligibility rules and the known limitations, not just the SQL underneath them.
  • Turn business questions into durable metrics: work directly with Customer Success, Sales, Product and leadership to understand what they're actually trying to decide, then build something defensible enough to decide on.
  • Keep cost and complexity in check as we grow: warehouse architecture, query cost, and the surfaces that deliver data into BI and our CRM. All of it gets harder as the customer base multiplies.
  • Set the standard for how data work is done here: one authoritative written definition per leadership-visible number, and the conventions that inform our Data function as it grows with us.

Requirements

Technical Expertise

  • Substantial experience in data engineering or analytics engineering, with production ownership of a warehouse and a transformation layer. We care more about evidence of ownership than about years served.
  • ClickHouse in production

  • dbt at ownership level: incremental models, snapshots, tests, macros, CI/CD. Ideally you've inherited someone else's dbt project and left it better than you found it.
  • Python data engineering: EL tooling, S3, CI-based orchestration that you’ve owned end to end, with no platform team behind you.
  • Product event streams: PostHog, Amplitude, Segment, Mixpanel or similar. You understand how user-to-company identity and group association break, and what that does to every metric downstream.

Judgement and Ownership

  • You have defined a business KPI end to end and defended it to non-technical people. This is the differentiator for us. An excellent engineer who takes requirements as given is not the right fit for this role.
  • Analytical rigour: cohorts, correct denominators, sample size stated before findings. You'll say "we can't tell yet, and here's exactly why" rather than produce a confident chart.
  • You act without waiting for a ticket, and you can name something you chose to stop doing.
  • You're comfortable in front of senior stakeholders, including C-level, and can hold a technical line without losing the room.

Further Requirements

  • Located within CET +/-2.
  • Nice to have: BI tool administration (we use Metabase), CRM and billing systems as data sources, dlt specifically, GDPR-driven data deletion work, Grafana, German, or B2B SaaS and legal-tech domain experience.
  • Nice to have: you're used to non-technical colleagues querying data through AI tools, and you design for that.

Benefits

🎯 Metric Ownership – Own a business-critical metric end to end, definition included β€” not just the pipeline that feeds it.

πŸ› οΈ A Real Platform – ClickHouse and dbt already in production, with genuine problems worth solving. No greenfield theatre, no maintenance seat.

⚑ Direct Access – A flat structure and a direct line to our Head of Engineering, CTO and CEO. No committee between you and a decision.

πŸ“ˆ Growth Stage – Roughly 4x customer growth a year at one of Europe's fastest-growing AI legal tech companies.

🏑 Fully Remote – Enjoy the flexibility of working from anywhere

πŸ’» Top Equipment – State-of-the-art MacBook plus all the accessories you need

πŸ‹οΈ Wellbeing Perks – Urban Sports Club membership to support your healthy lifestyle

If you're excited about owning the numbers an AI startup runs on and delivering the data that guides us in our scaling journey, we'd love to hear from you.

Next step

Ready to apply?

JUPUS Β· Worldwide Β· applications close Nov 16, 2026

Apply Now

How to apply

The Apply button opens JUPUS's own application page in a new browser tab β€” applying is free, and this board never sits between you and the employer: no middleman, no form of ours to fill first.

This posting runs on Ashby, the applicant tracking system behind JUPUS's job board β€” the form you'll see lives at jobs.ashbyhq.com. It asks for the basics first: your name, email, and a rΓ©sumΓ©/CV upload. After that come the custom questions this employer wrote for the role β€” Ashby lets each team tailor its application, and some postings add a short questionnaire on top, so set aside a few quiet minutes rather than a thirty-second sprint. Because the questions change per role, re-read the requirements above before you start typing; answers that echo the exact skills the listing names are the ones that survive screening. Two practical notes: apply promptly while the posting is verified live, since teams close applications once a role fills, and use one email address for the application so your details stay under one identity.

Before you start

Tailor your rΓ©sumΓ© to the skills this listing names β€” employers screen for the requirements they wrote.
Have your work-authorization details ready β€” citizenship, visas, and right-to-work countries come up on remote applications.
Check the employer's page for a pay range before naming a number β€” if they publish one, anchor to it.

Quick answers

Is this job still open?
Yes. Listings on this board are re-verified 4 times a day and auto-expire 45 days after posting β€” if this page is visible, the role was open at the last check.
Where does the Apply button go?
Straight to JUPUS's own application page β€” never a middleman. Every listing here comes from the employer's own job board, so the Apply button simply opens their page in a new tab.
Does it require experience?
The employer tags this role as lead level β€” the requirements above spell out what that means in practice.
Is the salary listed?
No β€” this employer didn't publish a salary range for this role. Their own application page is the place to check for pay details.
JUPUS logo

JUPUS

View Company
7 active roles

About the job

Posted on Oct 1, 2026
Apply before Nov 16, 2026
full-time
Worldwide

Skills

PythonMachine Learning

More Data Science roles

View all