Time since we first saw it
Day 120
Up longer than most. 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.
Paris · Paris, Île-de-France, France
Open 4 months, first seen by us 120 days agoAt Vibe, we want you to build something, own something, and grow fast. Here's how we back that up: The pay range for this role is €93,000–€142,000. We will support relocation to Paris for great candidates. Equity — Employee Stock Ownership Plan. You're building this; you should own part of it.Read the full posting
Location type: HybridFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Engineering & ProductFrom the employer’s posting
Vibe ingests more than 500,000 messages a second and stores several petabytes.
You get production ownership from week one, direct access to the engineers who built the infrastructure underneath you, and problems that don't have a Stack Overflow answer.
Ship schema changes across petabyte-scale tables without breaking downstream reporting
Make reporting queries faster and cheaper on ClickHouse and Cube
Turn new product features into production data models from Kafka and Iceberg
Trace data discrepancies to the source system and fix the root cause
Catch scaling and data-quality problems before they cause incidents
Vibe ingests more than 500,000 messages a second and stores several petabytes. Every advertiser who opens their dashboard expects their campaign numbers to be right, and current. You own the layer that makes that true. The platform side of the team builds the storage and compute. You run production on top of it: schema changes, data transformations, the reporting pipeline that feeds the client-facing UI. At this volume that is not maintenance work. A schema change is a distributed systems problem. A slow query is a customer-facing incident. We are already past what off-the-shelf systems handle, which is why this is a senior seat and not a junior one.
You get production ownership from week one, direct access to the engineers who built the infrastructure underneath you, and problems that don't have a Stack Overflow answer.
Ship schema changes across petabyte-scale tables without breaking downstream consumers or advertiser reporting
Make the reporting stack faster and cheaper. ClickHouse and Cube serve the client UI
Turn new product features into production data models, from raw Kafka and Iceberg through to what the advertiser sees
Trace discrepancies back through the stack to the source system, then fix the cause instead of the symptom
Catch scaling and data-quality problems before they page someone at 2am
5+ years in production data engineering. You have owned pipelines real users depended on, with on-call attached
Strong SQL and schema design at a volume where the design choice actually mattered
- 5+ years in production data engineering. You have owned pipelines real users depended on, with on-call attached - Strong SQL and schema design at a volume where the design choice actually mattered - Production experience with an orchestrator (Dagster, Airflow, Prefect) plus dbt or an equivalent transformation framework
Nice to Haves - ClickHouse in production, or another column store at serious scale (Druid, Pinot, BigQuery) with real war stories about partitioning, materialized views, or merge behaviour - Kafka or another streaming system feeding a serving layer, not just nightly batch
- Ship schema changes across petabyte-scale tables without breaking downstream consumers or advertiser reporting - Make the reporting stack faster and cheaper. ClickHouse and Cube serve the client UI, so query latency and compute spend are yours to defend - Turn new product features into production data models, from raw Kafka and Iceberg through to what the advertiser sees
- Strong SQL and schema design at a volume where the design choice actually mattered - Production experience with an orchestrator (Dagster, Airflow, Prefect) plus dbt or an equivalent transformation framework - One optimization win you can walk us through end to end: what was slow or expensive, what you changed, what the number went from and to, and why it worked
- Make the reporting stack faster and cheaper. ClickHouse and Cube serve the client UI, so query latency and compute spend are yours to defend - Turn new product features into production data models, from raw Kafka and Iceberg through to what the advertiser sees - Trace discrepancies back through the stack to the source system, then fix the cause instead of the symptom
- ClickHouse in production, or another column store at serious scale (Druid, Pinot, BigQuery) with real war stories about partitioning, materialized views, or merge behaviour - Kafka or another streaming system feeding a serving layer, not just nightly batch - AdTech or programmatic background
From the employer’s posting.
Open 4 monthsWe first saw this posting 120 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 120
Up longer than most. 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.
3 open jobs
Check the employer’s posting for the current role and application details.
Already applied? Track this application
Streaming TV is no longer just a brand awareness channel. It’s becoming a core part of the performance marketing mix, alongside search and social. Vibe.co is building the platform that makes TV work like the rest of the acquisition stack: targeted, measurable, and optimized for results.
Vibe.co is an Audience First Streaming TV Advertising platform that gives marketers the tools to reach the right audiences, optimize campaigns in real time, and understand what’s actually driving business outcomes. With hyper-targeted segmentation, AI-powered recommendations, real-time optimization, and incrementality measurement, Vibe brings the precision and accountability of digital advertising to the biggest screen in the house.
Today, more than 12,000 brands use Vibe.co to reach 120 million+ households. And in August 2026, Vibe.co became a Walmart company, opening up a new chapter for the business and the industry. With Walmart’s first-party data and purchase signals now part of the Vibe platform, advertisers can connect TV advertising to real-world transactions and measure the impact of CTV with a level of precision previously associated with platforms like Google and Meta.
This is a unique moment to join Vibe. With Walmart’s scale, data, and reach behind us, we’re building the next generation of TV advertising and creating a more measurable, performance-driven future for the channel.
Vibe ingests more than 500,000 messages a second and stores several petabytes. Every advertiser who opens their dashboard expects their campaign numbers to be right, and current. You own the layer that makes that true. The platform side of the team builds the storage and compute. You run production on top of it: schema changes, data transformations, the reporting pipeline that feeds the client-facing UI. At this volume that is not maintenance work. A schema change is a distributed systems problem. A slow query is a customer-facing incident. We are already past what off-the-shelf systems handle, which is why this is a senior seat and not a junior one.
You get production ownership from week one, direct access to the engineers who built the infrastructure underneath you, and problems that don't have a Stack Overflow answer.
Ship schema changes across petabyte-scale tables without breaking downstream consumers or advertiser reporting
Make the reporting stack faster and cheaper. ClickHouse and Cube serve the client UI, so query latency and compute spend are yours to defend
Turn new product features into production data models, from raw Kafka and Iceberg through to what the advertiser sees
Trace discrepancies back through the stack to the source system, then fix the cause instead of the symptom
Catch scaling and data-quality problems before they page someone at 2am
Push back when a request costs more than it's worth. "Not yet" and "not this way" are answers we expect to hear from you
5+ years in production data engineering. You have owned pipelines real users depended on, with on-call attached
Strong SQL and schema design at a volume where the design choice actually mattered
Production experience with an orchestrator (Dagster, Airflow, Prefect) plus dbt or an equivalent transformation framework
One optimization win you can walk us through end to end: what was slow or expensive, what you changed, what the number went from and to, and why it worked
Systems-level depth. Our technical round is the team drilling into how things work underneath, not a puzzle screen
The judgment to turn a vague request into a concrete plan, and the comfort to do it fast
ClickHouse in production, or another column store at serious scale (Druid, Pinot, BigQuery) with real war stories about partitioning, materialized views, or merge behaviour
Kafka or another streaming system feeding a serving layer, not just nightly batch
AdTech or programmatic background
At Vibe, we run on three values: Impact, Ambition, and Urgency. We tie every goal to a real business outcome, think 10x rather than settling for good enough, and move daily rather than waiting for perfect conditions.
You'll thrive here if you own outcomes without needing direction, default to action, and hold yourself to results, not effort.
This is a high-performance environment with high-performance rewards: you'll work alongside people who push you, with real ownership over hard problems in a market that's moving fast.
If that sounds like the best version of your career, we want to meet you.
At Vibe, we want you to build something, own something, and grow fast. Here's how we back that up:
The pay range for this role is €93,000–€142,000. We will support relocation to Paris for great candidates.
Equity — Employee Stock Ownership Plan. You're building this; you should own part of it.
Variable pay — based on objectives you hit. No arbitrary targets.
Hybrid flexibility — We're in the Heart of Paris and our team is in 3x a week!
Health insurance — Full coverage via Alan.
Meal vouchers — Via Swile.
Annual offsite — The whole team, once a year, somewhere worth the trip.
Tech Syncs — Engineering and Product meet in person at least quarterly, worldwide.
We respect your time. Here's exactly what to expect, no surprises, no ghosting.
Recruiter screen — 30 min with a recruiter. We'll share context; you'll share yours.
Manager interview — 45 min with the hiring manager. Experience deep-dive and judgment, not a technical grilling.
Technical interview — 90 min with the engineering team. No LeetCode, no from-scratch coding. Expect a hands-on, practical exercise, with the exact format tailored to your background.
Bar raiser — 30 min with our CTO and Cofounder. A final read on how you think and why Vibe.
Offer — Fast. We don't let good decisions sit.
Vibe is an equal opportunity employer. We evaluate all applicants without regard to race, color, religion, national origin, gender, gender identity or expression, sexual orientation, age, disability, veteran status, or any other characteristic protected by law.
We believe the best ideas come from teams with different backgrounds, perspectives, and experiences. If you need a reasonable accommodation during the application or interview process, please let us know.
Being referred? Ask your contact to submit your application directly on your behalf.
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
At Vibe, we want you to build something, own something, and grow fast. Here's how we back that up: The pay range for this role is €93,000–€142,000. We will support relocation to Paris for great candidates. Equity — Employee Stock Ownership Plan. You're building this; you should own part of it.
Paris, Île-de-France, France
- Variable pay — based on objectives you hit. No arbitrary targets. - Hybrid flexibility — We're in the Heart of Paris and our team is in 3x a week! - Health insurance — Full coverage via Alan.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting