Why a blog
Podscribe measures podcast advertising. Behind the dashboards sit pipelines that ingest download logs, attribution models that match impressions to outcomes, a transcription service that turns audio into searchable text, and an AI assistant that answers questions over all of it. Most of that work never leaves the team. This blog is where we write it down.
What we will publish
Each post covers one engineering problem we actually had: what made it hard, which options we weighed, what we shipped, and what we would do differently. Expect code, diagrams and numbers rather than announcements.
The first two posts are already in progress:
- How we built the Podscribe AI chat bot on top of our reporting data.
- How our transcription pipeline handles thousands of hours of audio a day.
We aim for one post a month.
Who writes here
The engineer who did the work writes the post. Editing help comes from the rest of the team, but the technical detail stays first-hand.
Follow along
Subscribe with the RSS feed to get each post as it lands.