← Spotify
Something new at Spotify

Ship a next-title cue after chapter end without showing unplayable books

You’re the software engineer. Your team is in the room. Printed Oct 15, 2026.

A finished audiobook creates a discovery moment, but availability and language can break it.

Repeat listening depends on a useful next title, while every recommendation must respect market rights and listener expectations.

Who you’d be doing this for

“I finished the book on my commute, then spent ten minutes opening titles that wouldn’t play.”

Berit Makinen · Premium listener

A listener in a newly opened market who has completed an audiobook and wants another title to start immediately.

What is at stake

Finished audiobook listeners are leaving after search leads them to unavailable or unexpected-language titles. You must weigh a fast continuation cue against the trust cost of showing a title that cannot actually be played.

Why it isn’t already fixed

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

  • repeat listening vs. catalog correctness
  • personalized ranking vs. market availability
  • global reuse vs. local language expectations
  • fast learning vs. shared pipeline latency

Why Spotify

Audiobook expansion across more than 180 markets makes each completion moment a test of whether the catalog feels usable locally.

Written with these in mind

backend product engineerrecommendation platform engineerinternationalization-minded software engineer

Not your kind of problem? 14 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.