Daily Listening Minutes

Audible: Report daily listening for the first two weeks of June, and say whether listening is falling.

Assignment

The content team has been told that listening dropped over the first half of June and wants to know whether that is true before it reaches the next planning review. They have shared two exports pulled on the morning of 15 June: the listening events recorded for the period, and a table of the titles.

Deliverables

• Daily listening minutes across 1 to 14 June.
• Whether listening actually fell over the period, with the reasoning behind your answer.
• A short closing report for the content team, covering what the daily figures should be based on and how long they should wait before treating a day's number as final.

Data Description

listening_events.csv is the listening the platform recorded for the period:

• event_id
• user_id
• title_id
• played_at - when the listening happened on the device
• received_at - when the platform received the record
• minutes_played
• source - how the title was being listened to

titles.csv has one row per title:

• title_id
• title_name
• runtime_minutes - how long the title runs

Practicalities

You can solve this in Python, SQL, or a mix of both — StrataScratch notebooks support both languages in the same notebook.

Assume this data comes directly from the listening platform and hasn't been cleaned, so review it carefully before relying on the numbers. When something looks off, work out what it is and decide how to handle it; when a definition or a final decision is genuinely ambiguous, choose a reasonable option and explain why. There's often more than one valid way to compute a result, so explain the approach you take and the reasoning behind your choices.

What's assessed: your results, and how clearly you explain what you see in the data and justify the choices you make.