Level

JUPUS

Staff Data Engineer

AI in this role

Own and modernize the end-to-end data platform, pipelines, warehouse, and metrics definitions for a fast-growing AI legal tech company.

clickhousedbtpythonaws-s3github-actions
data-engineeringdata-warehousingetlmetricssql

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.

How we rate this

Staff Data Engineer at JUPUS rates 65 out of 100 for how much of the daily work is AI. That makes it Works on AI (AI Level 3 of 4). The level is about AI in the job, not seniority.

Classification

Works on AI. The daily work is on AI products, without building the model.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Open the description and count.

Prepare for this job

A free preview built only from this posting: what it asks for, what you could be asked in an interview, and how to adjust your resume.

Skills and AI tools this role asks for

Data EngineeringData WarehousingETLMetricsSQLClickhouseDbtPython

Questions you could be asked

  1. Tell me about a project where data engineering was part of your work. What did you do?
  2. Tell me about a project where data warehousing was part of your work. What did you do?
  3. Tell me about a project where etl was part of your work. What did you do?
  4. Tell me about a project where metrics was part of your work. What did you do?
  5. Tell me about a project where sql was part of your work. What did you do?

Adapt your resume

  • List these exact terms on your resume: Data Engineering, Data Warehousing, ETL, Metrics, and SQL. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them — a tool named with nothing behind it rarely survives a human read.
  • Show where AI is part of your daily process, not a one-off project — this role expects it to be a running habit.

Want an expert to read your CV for this job?

Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.

Get a free CV review

Get new remote data engineer jobs (Works on AI ●●●○ or higher) by email

One email a week with the new remote data engineer jobs (Works on AI ●●●○ or higher), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free. One email a week. Unsubscribe in one click.

Similar roles

Data roles that work on AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at JUPUS

More data engineer jobs

Related searches

Same AI level