← Spotify
Complex day at Spotify

Hold the lineage cutover until 99.9% of records are verified

You’re the data engineer. Your team is in the room. Printed Oct 21, 2026.

The catalog must recover its lineage without turning uncertain availability into published fact.

Discovery needs titles back in listener surfaces while licensing needs territory evidence preserved for every published record.

Who you’d be doing this for

“I found the book twice today, and both times it told me I couldn’t play it.”

Raghav Verma · Premium listener

Uses search and recommendations to choose audiobooks in a newly opened market.

What is at stake

Audiobook records are reaching discovery without reliable market-availability lineage, sending listeners to titles they cannot play. You must weigh a faster catalog recovery against proof that every recovered record is safe to publish.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • catalog availability vs. territory accuracy
  • fast recovery vs. verifiable lineage
  • snapshot continuity vs. historical evidence
  • discovery coverage vs. listener trust

Why Spotify

Audiobook expansion across new markets depends on catalog records that keep availability evidence connected to discovery surfaces.

Written with these in mind

reliability-minded data engineerdata platform buildergoverned data systems specialist

Not your kind of problem? 18 more at Spotify, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.