The Spotify Model is a way of organizing product and tech teams, described in 2012 by Henrik Kniberg and Anders Ivarsson based on their experience at Spotify, built on autonomous teams grouped by domain and connected by communities of practice.
It is structured around four levels:
- squads, small cross-functional teams responsible for part of the product;
- tribes, which group several squads working on the same domain;
- chapters, which bring together people with the same skill across squads (for example all the back-end developers in a tribe);
- guilds, communities of interest open to everyone.
The model has been widely copied, often to the letter. Yet its authors presented it as a snapshot at a given moment, not a framework to replicate, and Spotify itself has changed its organization since. It remains a useful source of inspiration, not a ready-made method.
Why it matters when hiring
The model directly affects which roles to hire: who manages the developers (the chapter lead or the squad lead?), who sets priorities, who keeps technical consistency across teams. Before hiring an Engineering Manager into a "Spotify-style" organization, clarify these lines. On the candidate side, ask what did not work in their previous organization: the answer shows whether they have stepped back and reflected.