This Tuesday in Atlanta · Talks & Ideas

Building a 4,000-Component Monorepo: How Spotify Uses AI to Scale Backend Development

Name: Building a 4,000-Component Monorepo: How Spotify Uses AI to Scale Backend Development
Start: 2026-10-20T22:30:00.000Z
End: 2026-10-21T01:00:00.000Z
Location: Perimeter Center

Tue, Oct 20 · 6:30 p.m.EDT

Perimeter Center · Atlanta

**We use the Luma site to host our events. [SIGN UP HERE](https://luma.com/mnrheuj2)** Spotify's backend monorepo consolidates over 4,000 services, libraries, and components into a single repository…

Building a 4,000-Component Monorepo: How Spotify Uses AI to Scale Backend Development

photo: Luma

When

Tue, Oct 20 · 6:30 p.m.Ends 9:00 p.m.EDT

Where

Perimeter CenterRoam Dunwoody, 1155 Mount Vernon Hwy NE #800, Atlanta, GA 30338, USA

Free

Add to calendar

Google Calendar Apple / Outlook (.ics)

When and where

Date and time: Tue, Oct 20 · 6:30 p.m.Ends 9:00 p.m.EDT — local Atlanta time
Location: Perimeter CenterRoam Dunwoody, 1155 Mount Vernon Hwy NE #800, Atlanta, GA 30338, USAAtlanta

About this event

**We use the Luma site to host our events. [SIGN UP HERE](https://luma.com/mnrheuj2)**

Spotify's backend monorepo consolidates over 4,000 services, libraries, and components into a single repository built with Bazel, deployed to Kubernetes, and supported by 131 custom developer tools. This talk explains why Spotify chose a monorepo for its backend infrastructure, the tooling ecosystem that makes it practical — from the CLI wrapper and Build

Buddy remote execution to Declarative Infrastructure and automated monitoring — and how AI skills and agents have become essential to operating at this scale.

I will discuss the over 90 Claude Code skills that encode institutional knowledge into repeatable workflows, with a deep dive into /import-repo: a skill that has migrated thousands of polyrepos into the monorepo, evolved through 206 commits over 8 months, and taught us hard lessons about AI agent autonomy, context window limits, and the value of encoding failure patterns as guardrails.

**W