Back to jobs

Data Engineer

Pay
€5,500–7,000/month — pay source
Our data stack includes Python, Dagster, Ray, Polars, Postgres, Vespa, Kubernetes and GCP. You don't need to know all of it, or anything about patents: we're much more interested in your judgment and ability to learn. The salary range for the role is €5,500–7,000/month, with equity on top. Ideally you're based in Helsinki, but elsewhere in Europe can work for the right person.
Read the full posting
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: FULL_TIME
From the employer’s posting

What you’ll work on

Full posting
  • Model patent, research paper and company data so their relationships are represented correctly

  • Build harnesses and evaluations that let agents fix data problems and judge when results are good enough

  • Build and run pipelines from data sources into the stores and APIs the product reads

  • Work with product and ML teams on data needs and machine learning in processing steps

  • Explore new data sources, including direct patent office data, and diagnose when sources fall short

From the employer’s posting
model it so that it reflects how patents, research papers and the companies behind them relate to each other
You'll build the harness and evaluations that let agents fix data problems on their own, and judge when their results are good enough.
You'll build and run the pipelines that take data from our sources into the stores and APIs the product reads from.
You'll work with the product teams on what data they need and in what form, and with the ML team on how we use machine learning in our processing steps.
You'll explore what new sources could give us, including data straight from patent offices, and help decide what's worth adding.
Apply at IPRally

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026
Employer says posted
Oct 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Early. Similar jobs usually come down between day 6 and day 56.

From 14,771 similar postings that came down. Coming down is not always a hire.

IPRally is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • GCP
  • Kubernetes
  • Dagster
  • Polars
  • PostgreSQL
Where the posting names them
You'll build the harness and evaluations that let agents fix data problems on their own, and judge when their results are good enough. You'll build and run the pipelines that take data from our sources into the stores and APIs the product reads from. They're written in Python, run with Dagster, and monitored with data quality checks that show when something has gone wrong. You'll work with the product teams on what data they need and in what form, and with the ML team on how we use machine learning in our processing steps.
AI agents are already a normal part of how we build at IPRally, and we're still working out what they change in data work. You'll have considerable room to experiment and help shape how the data team works with agents. Our data stack includes Python, Dagster, Ray, Polars, Postgres, Vespa, Kubernetes and GCP. You don't need to know all of it, or anything about patents: we're much more interested in your judgment and ability to learn. The salary range for the role is €5,500–7,000/month, with equity on top.

Your next step

Complete your application on iprally.teamtailor.com. The employer’s form will show what is required.

Applying through Teamtailor

  • No account needed.

Already applied? Track this application

Job description

View original posting ↗

We're looking for one data engineer who loves getting under the skin of data, and who is excited about what agents now make possible.

Agents have made data-driven development possible where it wasn't before. Messy real-world data needs ground truth and evaluations, and building them used to be very expensive. Now evaluation harnesses, with agents developing against them in a loop, can take the processing of such data to a precision and recall that wasn't possible before. What this needs is someone who understands what the data means, models it properly, and builds the harnesses that tell agents what right looks like.

IPRally is building a new generation of AI powered tools for understanding patents and technical knowledge, and everything our product does depends on patent data. Offices around the world publish it, each in its own format and language, and some of it exists only as scans of paper. Today it reaches us through data providers, and we expect to get more of it straight from the source.

Our users should see the right data in the right way. Your part of that is getting the data right and delivering it into the stores and APIs our product is built on. From there, product engineers, designers and product managers turn it into what users see. Doing your part well takes taste, and a feel for how the whole system fits together, from the sources to the product.

You'll join our data engineering team of three engineers and work closely with the other engineering teams and the rest of IPRally.

What you'll do

You'll learn what our data means, find where it falls short, and model it so that it reflects how patents, research papers and the companies behind them relate to each other.

You'll build the harness and evaluations that let agents fix data problems on their own, and judge when their results are good enough.

You'll build and run the pipelines that take data from our sources into the stores and APIs the product reads from. They're written in Python, run with Dagster, and monitored with data quality checks that show when something has gone wrong.

You'll work with the product teams on what data they need and in what form, and with the ML team on how we use machine learning in our processing steps.

You'll explore what new sources could give us, including data straight from patent offices, and help decide what's worth adding. With agents, we can try out a new source quickly before committing to it.

When a source stops delivering or falls short, you'll find out why and help work out what other sources could fill the gap.

What we're looking for

This role could be a strong fit if you:

  • Have built and run production pipelines on large, noisy real-world data, or worked with such data in statistics or ML.

  • Are comfortable deciding what to build when there's no fixed definition of correct and every tool is imperfect, and build statistical evaluations and measurable targets into your work from the start.

  • Build agent harnesses that develop our data processing systems on the same basis, so that we can be confident in the quality of both the data and the code.

  • Are curious about the real world behind the data: how it came to be, what it means, and how to represent it in the systems that process it.

  • Can work out what right data looks like when everything around it is imperfect, from who uses it, what they use it for.

  • Like working directly with the people who use the data, inside and outside engineering, to decide what's worth doing.

Experience with patent or other document data, distributed processing such as Ray, or running ML models over large datasets is an advantage, but isn't required.

How we build

Our engineers aren't measured by how much code they personally type. We're much more interested in whether you can understand the data and what people need from it, make good decisions, and use the tools available to turn those decisions into reliable pipelines.

AI agents are already a normal part of how we build at IPRally, and we're still working out what they change in data work. You'll have considerable room to experiment and help shape how the data team works with agents.

Our data stack includes Python, Dagster, Ray, Polars, Postgres, Vespa, Kubernetes and GCP. You don't need to know all of it, or anything about patents: we're much more interested in your judgment and ability to learn.

The salary range for the role is €5,500–7,000/month, with equity on top.

Ideally you're based in Helsinki, but elsewhere in Europe can work for the right person.

Along with your CV, write half a page answering this question: What's the most interesting dataset you've worked with, and what did it take before you could trust it? There's no right answer. We want to see how you think.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay
Our data stack includes Python, Dagster, Ray, Polars, Postgres, Vespa, Kubernetes and GCP. You don't need to know all of it, or anything about patents: we're much more interested in your judgment and ability to learn. The salary range for the role is €5,500–7,000/month, with equity on top. Ideally you're based in Helsinki, but elsewhere in Europe can work for the right person.
Location & working pattern

Helsinki, Finland, FI

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.