Spotify Engineering Manager Interview Questions

1.Describe a situation where one of your engineers was struggling with performance or blockers. How did you help them succeed?

2.Tell me about a time when you developed someone on your team by giving them ownership of something they hadn't done before. How did you support them?

3.Tell me about a time your team had to make a significant technical or product decision without clear direction from leadership. What was the decision and how did you approach it?

4.Describe a time when you had to coordinate work across multiple teams or squads without formal authority over them. What was the challenge and how did you approach it?

5.Tell me about a time you noticed something about your team's culture that wasn't working well and you took action to change it. What did you do and what happened?

6.Walk me through a product or technical decision where you had strong data pointing one way but your gut told you something different. How did you resolve it?

7.Code review: This function processes real-time Kafka events for user listening sessions. What issues do you see and how would you guide a junior engineer to fix them?

8.Your team maintains a GraphQL API that serves mobile app data for playlist features. You discover that 80% of queries are requesting fields that require expensive joins, but only 20% of users actually view those fields in the UI. What's your approach?

9.Your squad owns the recommendation engine that serves 'Discover Weekly' playlists. The ML team wants to deploy a new model that improves engagement by 15% but increases P99 latency from 50ms to 150ms. How do you approach this decision?

10.You're leading the engineering side of migrating Spotify's artist analytics from a monolithic service to microservices. Three months in, two other squads depend on your APIs but your team is behind schedule. How do you handle this?

11.Walk me through how you'd design the architecture for Spotify Wrapped when we have 600M+ users who all want to access their data in the first few hours after launch.

12.Your squad is tasked with building a new feature that lets artists schedule social media posts across platforms when their music releases. The PM wants to ship in 6 weeks, but you identify that reliable social platform integrations typically take 12+ weeks. How do you navigate this?

13.Design the real-time notification system that powers Spotify's 'Friend Activity' feed. How would you handle when a popular artist with 50M followers releases a new song and all those users need to be notified within seconds?

14.Walk me through how you'd design the data pipeline that powers Spotify for Artists analytics, processing listening events from 600M+ users to give artists near real-time insights about their music performance.

15.Design the content delivery system for Spotify's podcast platform that needs to handle both live streaming podcasts and on-demand content for creators with audiences ranging from 100 to 100M listeners.

16.How would you architect the personalization engine that needs to generate 600M+ unique Daily Mix playlists every day, considering both real-time listening behavior and long-term user preferences?

17.Design the infrastructure for Spotify Ad Studio that needs to serve programmatic audio ads to hundreds of millions of users while providing real-time campaign performance data to advertisers.

18.Walk me through designing the backend systems for Spotify Wrapped that need to process a year's worth of listening data for 600M+ users and generate personalized experiences that can handle the traffic spike when it launches globally.

19.Tell me about a time when you had to make a decision that affected multiple squads but didn't have formal authority over those teams. How did you get alignment?

20.Tell me about a time when you had to advocate upward for something your team needed - resources, technology choices, or organizational changes - that leadership wasn't initially supportive of.

21.Describe a time when your team was experimenting with a new approach or technology and it wasn't working out as expected. How did you handle the pivot?

22.Walk me through a situation where you had to balance your squad's technical roadmap with an urgent business need that would require significant technical debt or shortcuts.

23.Tell me about the most difficult conversation you've had to have with an engineering lead or architect from another team about technical decisions that affected your squad's work.

24.Describe a time when you noticed that your team's ways of working weren't scaling with their growth or complexity of problems. What changes did you make?

25.Spotify's daily active users in Sweden dropped 3% over the past week, but we haven't shipped any major changes. Walk me through how you'd investigate this and what you'd prioritize checking first.

26.Estimate how many podcast episodes Spotify ingests per day globally. Walk me through your reasoning and key assumptions.

27.Your analytics team tells you that playlist creation on mobile is down 8% month-over-month, but desktop playlist creation is flat. The mobile team says nothing changed in their UI. How would you structure your investigation?

28.Estimate the storage cost impact if Spotify started storing 30 seconds of high-quality audio preview for every track in our 100+ million song catalog. What factors would drive your recommendation?

29.Spotify for Artists dashboard is showing 50% higher than normal traffic, but artist complaint tickets about missing analytics are up 300%. The monitoring shows all systems green. How do you debug this paradox?

30.A major label wants Spotify to guarantee their new album release reaches 10 million unique listeners in the first 48 hours through our recommendation systems. They're threatening to pull their entire catalog if we can't commit. How do you approach this request?