A Faster Path From Idea to Experiment
Spotify’s Platform Developer Experience (PDX) Tribe, part of the Technology Infrastructure Group, builds the CI/CD tools, web tools, and testing frameworks that let engineering teams ship features quickly. The goal is straightforward: turn an idea into a live A/B test within a single day — idea in the morning, experiment shipped during the day, data back by the evening.
The company operates on an “ops in squad” model: each team owns a feature end-to-end, handling both development and operations. That autonomy speeds up delivery but has also led to fragmentation across toolsets and practices. The PDX response has been to build abstractions that reduce low-variance work so engineers can focus on the creative and technical problems that matter.
Standardizing Project Setup With Golden Paths
Before PDX introduced its current toolchain, spinning up a new web campaign site was a manual ordeal. Developers had to create a GitHub repo, manually register it in the developer portal, set up a Google Cloud project and Jenkins CI pipeline by hand, and then wade through documentation — often ending with a plea for help on Slack. That process consumed roughly 14 days before any code could be written.
Golden Paths changed that. These are documented best practices presented as a wizard in Spotify’s developer portal, Backstage, guiding engineers through the setup of backend services, data pipelines, machine learning projects, and web apps. The wizard creates the skeleton automatically, reducing the number of decisions a developer needs to make. For a web project, the output includes a GCP project, a GitHub Enterprise repository, and CI/CD configuration, all ready for commits. What once took 14 days now takes under five minutes.
Automated Builds With Tingle
Once code is committed, the CI/CD system takes over. Tingle, built in 2017, serves as Spotify’s centralized CI/CD platform for backend, data, and web services. It automatically builds, tests, packages, and deploys changes within the standard GitHub workflow.
Build results appear directly in GitHub and Backstage; passing tests trigger deployment to production with no pipeline configuration required. Tingle has displaced more than 200 standalone Jenkins machines previously managed by individual feature teams and now processes tens of thousands of builds weekly.
This automation, combined with Golden Paths, reduced the time from project setup to first build and deployment from 14 days to 5 minutes — a critical improvement for a streaming service that depends on constant experimentation.
Quality Signals Through Test Certification
Infrastructure tools are only part of the equation. PDX also created a test-certification program for each engineering discipline to give teams visibility into code quality. Using a gamified approach, developers are encouraged to apply appropriate tests and are alerted when their suites contain flaky tests.
When a service meets certification requirements, it automatically displays a badge in the portal, signaling that it follows best practices for quality control. Teams also receive reports on build times, code coverage, and test suite reliability. Since 2018, teams that invested in test certification have seen a significant drop in blocking bugs and reactive work, enabling more confident continuous deployment.
Flexibility Within Standardization
Autonomy is core to Spotify’s engineering culture, and teams remain free to choose how they work. Recognizing that standardization must accommodate this, PDX offers three usage options for its services, allowing teams to adopt the tools and methods that fit their operating style. This flexibility keeps the golden path approach from becoming a constraint.
The combined effect is an infrastructure that lets autonomous teams operate at greater speed and scale. By reducing the number of decisions and the complexity of underlying integrations, PDX has shifted engineers further up the stack — toward collaboration and innovation rather than infrastructure plumbing.
