Back to jobs

Senior Product Data Engineer- Data Insights (remote, Europe)

Bratislava, Bratislava Region, Slovakia

Actively hiring, first seen by us 3 days ago
Pay
€100,000–130,000/year — pay source
Fully remote in Europe 🏠 Work from wherever you do your best work. Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is €100,000 to €130,000. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience. Flexible hours ⏱ We care about outcomes, not when you log on.
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
  • Build creator datapoints like brand collaborations, contacts, location, and related creators

  • Define and measure data quality checks per platform and catch regressions

  • Take projects from idea to production, including architecture, code, and release

  • Decide where LLMs beat rules or simpler models and estimate their cost at scale

From the employer’s posting
You'll turn raw posts, bios, and profile data into signals: brand collaborations, contact details, creator location, related creators
decide what good looks like for your datapoint, measure it per platform against real coverage numbers, and catch regressions before customers do
You'll shape the problem, scope the work, design the architecture, write the code, ship it, and learn from how it performs.
You'll decide where an LLM beats a rule or a simpler model, and work out what it costs across 200M+ profiles before it ships.

What you’ll bring

All qualifications

Core experience

  • You have solid experience as a data engineer and have worked with large, complex datasets in production.
  • Experience with Airflow or AWS Step Functions, and with services such as EMR, Glue, Athena, DynamoDB, S3, Kinesis, Lambda, or ECS, will help you get moving quickly.
Qualification wording
Built data systems at meaningful scale. You have solid experience as a data engineer and have worked with large, complex datasets in production.
Worked with orchestration and cloud infrastructure. Experience with Airflow or AWS Step Functions, and with services such as EMR, Glue, Athena, DynamoDB, S3, Kinesis, Lambda, or ECS, will help you get moving quickly.

Benefits in the posting

Full benefits wording
  • Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is €100,000 to €130,000. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience.
  • Unlimited paid vacation 🌴 Take the time you need to stay rested and do great work.

From the employer’s posting.

Apply at Modash

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 12, 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,770 similar postings that came down. Coming down is not always a hire.

Modash 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
  • Scala
  • SQL
  • AWS
  • Databricks
  • DynamoDB
  • Iceberg
  • PostgreSQL
  • S3
  • Spark
  • Airflow
  • PySpark
Where the posting names them
- Owned full features. You've taken a feature through planning, scoping, architecture, implementation, release, and iteration. - Written production Python and SQL. You care about code quality, system design, and maintainability. - Worked with orchestration and cloud infrastructure. Experience with Airflow or AWS Step Functions, and with services such as EMR, Glue, Athena, DynamoDB, S3, Kinesis, Lambda, or ECS, will help you get moving quickly.
- Built data systems at meaningful scale. You have solid experience as a data engineer and have worked with large, complex datasets in production. - Worked deeply with Spark. PySpark, Scala, or Databricks all count. We use PySpark, but strong Spark fundamentals matter more than the exact flavour. Here is the blog post that helps explain the kind of work we do. - Turned messy data into signals people rely on. Entity matching, classification, deduplication, or enrichment: you've built reliable output from data that started out incomplete, inconsistent, or wrong.
- Written production Python and SQL. You care about code quality, system design, and maintainability. - Worked with orchestration and cloud infrastructure. Experience with Airflow or AWS Step Functions, and with services such as EMR, Glue, Athena, DynamoDB, S3, Kinesis, Lambda, or ECS, will help you get moving quickly. - Worked using agentic development. You use coding agents like Cursor in your daily work, give them clear context, and review what they write as carefully as a teammate's PR.
Our stack - AWS, with Pulumi for infrastructure as code - Spark on EMR, mostly PySpark
- LLM models for data enrichment - DynamoDB, Kinesis, Lambda, and ECS - GitHub, Notion, Linear, Cursor
- Spark on EMR, mostly PySpark - Iceberg tables on S3, queried through Glue and Athena - PostgreSQL on Aurora
- Iceberg tables on S3, queried through Glue and Athena - PostgreSQL on Aurora - Airflow
- AWS, with Pulumi for infrastructure as code - Spark on EMR, mostly PySpark - Iceberg tables on S3, queried through Glue and Athena
- PostgreSQL on Aurora - Airflow - Great Expectations for data quality checks
- Monday. You spot-check your datapoint's output and find a quality problem. You write a short plan for fixing it and get feedback from another data engineer before you start. - Tuesday. You build the change in PySpark and test it. It's too slow on the full dataset, so you profile the job and fix it. - Wednesday. A pipeline failed overnight. You find the cause, ship a fix, and rerun it. In the afternoon you review a teammate's PR, then get back to your project.
- Intro chat - Two technical interviews: an agentic PySpark coding challenge and a system design session - Team fit and project presentation

Your next step

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

Applying through Workable

  • No account needed. You can import your resume to fill in the form, or skip that and fill it in yourself.

Already applied? Track this application

Job description

View original posting ↗

Hey, I'm Tadas. I'm hiring a Senior Product Data Engineer for Data Insights, the team that builds Modash's data products.

Modash helps brands find, understand, and work with creators on Instagram, TikTok, and YouTube. More than 2,700 companies, including Stanley 1913, Sennheiser, and NordVPN, use us to run and grow their creator partnerships.

Data Insights turns raw social media data into the datapoints customers buy: which brands a creator has worked with, how to contact them, where they're based, and which other creators are like them. Most of the work is taking messy public data across 200M+ profiles and making it accurate enough that a brand will act on it.

In this role you'll own datapoints end to end, from the raw signal to what the customer sees, and you'll be judged on their quality.

Why we're hiring

At Modash, the data is the product customers pay for. Brands use our collaboration, contact, and location data to decide which creators to work with, and our largest customers take it in regular bulk deliveries through our API.

We need a senior engineer who can take one of these datapoints from a rough idea to a production pipeline and keep improving it after launch. Right now that means building our own creator-location data, using LLMs to find and validate creator contact emails, and matching sponsored posts to the right brand and its parent company.

You'll join a team of four data engineers who work closely with four backend engineers. You'll make important technical decisions yourself, with strong teammates to back you up, and customers will see what you build.

For a feel of how we build software, read our Engineering Blog.

What you'll own

1. Build the datapoints customers pay for.

You'll turn raw posts, bios, and profile data into signals: brand collaborations, contact details, creator location, related creators, and links between one creator's accounts on different platforms.

2. Make data quality measurable.

Every datapoint we ship has automated quality checks. You'll decide what good looks like for your datapoint, measure it per platform against real coverage numbers, and catch regressions before customers do.

3. Take projects from idea to production.

You'll shape the problem, scope the work, design the architecture, write the code, ship it, and learn from how it performs. We expect senior engineers to own the outcome, even when the problem arrives half-defined.

4. Use LLMs where they pay off.

We run LLM enrichment at large scale. You'll decide where an LLM beats a rule or a simpler model, and work out what it costs across 200M+ profiles before it ships.

What the day-to-day looks like

Most weeks you're on one project for days at a time, with some of your time going to pipeline issues and code review. A typical week might look like this:

  • Monday. You spot-check your datapoint's output and find a quality problem. You write a short plan for fixing it and get feedback from another data engineer before you start.
  • Tuesday. You build the change in PySpark and test it. It's too slow on the full dataset, so you profile the job and fix it.
  • Wednesday. A pipeline failed overnight. You find the cause, ship a fix, and rerun it. In the afternoon you review a teammate's PR, then get back to your project.
  • Thursday. You compare results before and after the change on each platform. One number moves more than expected, and you dig in until you can explain it.
  • Friday. You merge, watch the first production run, and check the quality reports. You answer a question from a backend engineer about the data, then plan next week.

Every meeting needs a reason, and we protect time for focused work. You'll have a short standup, pair with people when it helps, and get long stretches to plan, build, and ship.

Requirements

What you've done before

  • Built data systems at meaningful scale. You have solid experience as a data engineer and have worked with large, complex datasets in production.
  • Worked deeply with Spark. PySpark, Scala, or Databricks all count. We use PySpark, but strong Spark fundamentals matter more than the exact flavour. Here is the blog post that helps explain the kind of work we do.
  • Turned messy data into signals people rely on. Entity matching, classification, deduplication, or enrichment: you've built reliable output from data that started out incomplete, inconsistent, or wrong.
  • Treated data quality as part of the job. You've defined quality checks, tracked coverage and accuracy, and handled a quality drop like a bug.
  • Owned full features. You've taken a feature through planning, scoping, architecture, implementation, release, and iteration.
  • Written production Python and SQL. You care about code quality, system design, and maintainability.
  • Worked with orchestration and cloud infrastructure. Experience with Airflow or AWS Step Functions, and with services such as EMR, Glue, Athena, DynamoDB, S3, Kinesis, Lambda, or ECS, will help you get moving quickly.
  • Worked using agentic development. You use coding agents like Cursor in your daily work, give them clear context, and review what they write as carefully as a teammate's PR.
  • Worked autonomously without working alone. You make progress with incomplete information, say what you think, ask for feedback, and help teammates do better work.

Curiosity about the creator economy helps too, but we'll get you up to speed.

Our stack

  • AWS, with Pulumi for infrastructure as code
  • Spark on EMR, mostly PySpark
  • Iceberg tables on S3, queried through Glue and Athena
  • PostgreSQL on Aurora
  • Airflow
  • Great Expectations for data quality checks
  • LLM models for data enrichment
  • DynamoDB, Kinesis, Lambda, and ECS
  • GitHub, Notion, Linear, Cursor

The interview process

We move quickly and can finish the process in under a week:

  1. Intro chat
  2. Two technical interviews: an agentic PySpark coding challenge and a system design session
  3. Team fit and project presentation
  4. Culture and alignment conversation with our CEO, Avery Shrader

Benefits

What we offer

  • Fully remote in Europe 🏠 Work from wherever you do your best work.
  • Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is €100,000 to €130,000. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience.
  • Flexible hours ⏱ We care about outcomes, not when you log on.
  • Unlimited paid vacation 🌴 Take the time you need to stay rested and do great work.
  • Personal development support 🧠 Courses, books, and conferences are on us.
  • Real ownership 💡 Take meaningful customer problems from ambiguity to impact.
  • Regular offsites ✈️ We’re remote-first, but we make time to connect in person.

And a little more about us...

Founded in 2018 by a high-school dropout and a Canadian (yes, we’re also shocked it’s going so well), Modash is building a suite of tools that help brands scale partnerships with online content creators.

2,700+ companies like Stanley 1913, Sennheiser, and NordVPN already use Modash to manage and scale their influencer marketing work. And we're just getting started. Over the coming decade, brand investment in creators will continue to boom, and Modash will be at the centre of it all.

Modash is here to stay. We have 8-figures in ARR across two products, a $12M series A investment, and we are default alive. We are building a company that will still be here in 20 years; not rushing towards an exit.

We’re almost 100 people distributed across 20+ countries, operating with a fast, async-first culture. If you join Modash, you’ll be surrounded by people who truly want to be the greatest at their craft. People who make you better. Interesting people too, who have done everything from building solar cars, to hanging out with Metallica and Bon Jovi.

Come join us. Be great, do great things, create great memories, all while making a great impact. Do it.

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
Fully remote in Europe 🏠 Work from wherever you do your best work. Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is €100,000 to €130,000. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience. Flexible hours ⏱ We care about outcomes, not when you log on.
Location & working pattern

Bratislava, Bratislava Region, Slovakia

What we offer - Fully remote in Europe 🏠 Work from wherever you do your best work. - Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is €100,000 to €130,000. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience.
More source context
- Real ownership 💡 Take meaningful customer problems from ambiguity to impact. - Regular offsites ✈️ We’re remote-first, but we make time to connect in person. And a little more about us...
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.