Engineering Manager interview
at Spotify.

Tell-me-about-a-time stories on ownership, conflict, and impact — scored against this company's real values.

1. 01 Tell me about a time you managed a conflict within your squad and how you resolved it while preserving psychological safety.
2. 02 Describe how you cultivate aligned autonomy, giving your engineers ownership of the how while keeping them aligned on the why.
3. 03 Walk me through how you handled an underperforming engineer through performance management and coaching.
4. 04 Give an example of how you balanced delivery pressure with a culture that treats occasional mistakes as an acceptable cost of speed.

The hard screen for the craft itself — talked through out loud, not whiteboarded in your head.

1. 01 Walk me through the architecture of a system you previously owned and the key tradeoffs you guided your team toward.
2. 02 How would you guide your team to design a scalable, highly available music streaming service?
3. 03 How do you ensure technical quality and reduce on-call burden across multiple autonomous squads?
4. 04 How would you evaluate the technical decision to migrate a core service to a new infrastructure without halting feature delivery?

Open-ended design of the systems this company actually runs, with the interviewer probing your tradeoffs.

1. 01 Design how you would structure squads, chapters, and guilds to own Spotify's recommendation platform at scale.
2. 02 Design the engineering roadmap and service architecture for launching offline playback in a new market.
3. 03 Design a system for tracking team-level reliability and delivery metrics across a tribe of squads.
4. 04 Design the cross-squad ownership and rollout plan for re-architecting the playlist service while keeping it live.