Intervu is in beta — feedback welcome at support@intervu.io

Spotify Program / Project Manager Interview Questions

30 real practice questions for the mid-level Program / Project Manager role at Spotify (Streaming / Technology), spanning behavioral, problem solving, role knowledge, situational, and stakeholder. Drive cross-functional programs end to end: stakeholder alignment, planning, risk management, and delivery. The first 3 questions below include what Spotify interviewers actually listen for, plus likely follow-ups.

Practice these questions with AI feedback
Questions
30
Categories
Behavioral (6), Problem Solving (6), Role Knowledge (6), Situational (6), Stakeholder (6)
Difficulty mix
10 easy · 10 medium · 10 hard
Avg. answer time
~4 min

Behavioral Questions (6)

  1. 1.Tell me about a time your squad had to make a significant project decision — a scope call, a priority shift, a build-vs-buy — without waiting for someone above you to sign off. How did you drive alignment and move forward?

    easy~3 min

    What interviewers look for

    • Candidate took clear ownership of the decision-making process rather than escalating or stalling, reflecting Spotify's Autonomous Squads model where teams own outcomes end-to-end.
    • Used a defined framework or structured approach (e.g., documented trade-offs, ran a decision doc, facilitated a team vote) to drive alignment without top-down authority.
    • Acknowledged the risk of moving without full information and described how they mitigated it — showing comfort with ambiguity at a mid-level scope.
    • Communicated the decision and rationale to stakeholders outside the squad proactively, keeping broader visibility without seeking permission.

    Likely follow-ups

    • Who pushed back on that decision, and how did you handle it?
    • If you had to make that same call today, what would you do differently?
    • How did you know when you had enough information to stop gathering input and just decide?

    Company context

    Spotify's Autonomous Squads model is central to how the company operates — small cross-functional teams own a domain end-to-end and are expected to move without waiting for top-down approval. For a mid-level PM or Program Manager, this means being comfortable making and socializing significant decisions at the squad level. This question tests whether a candidate has actually lived inside that operating model or whether they default to escalation and approval-seeking, which would slow Spotify's teams down.

  2. 2.Tell me about a time you noticed a teammate had the skills to take on more, but they weren't being given the opportunity. What did you do about it?

    easy~3 min

    What interviewers look for

    • Candidate spotted the gap proactively — not because they were asked to mentor or develop someone — showing the Servant Leadership instinct to elevate others without a formal directive.
    • Took a concrete action to create or advocate for the opportunity — not just encouragement, but something that changed the teammate's access to stretch work, visibility, or decision-making authority.
    • Balanced the teammate's development with program or project needs — didn't sacrifice delivery, but found a way to invest in both simultaneously.
    • Checked in after the opportunity was created to see how the teammate was doing and adjusted their support accordingly — showing sustained investment, not a one-time gesture.

    Likely follow-ups

    • Did the teammate know you were advocating for them, or did you work in the background? Why?
    • Was there any risk to you or the project from creating that opportunity — and how did you think about it?
    • How did that person's growth affect the rest of the team?

    Company context

    Spotify's Servant Leadership principle holds that a manager's — and by extension, a program leader's — primary job is to grow and unblock people, not to direct them. At Spotify, where squads are small and cross-functional, a Program Manager who spots and develops hidden capability in teammates directly strengthens the squad's ability to operate autonomously. This question tests whether the candidate's instinct is to hoard ownership or to multiply it — a signal that matters deeply in Spotify's collaborative, non-hierarchical culture.

  3. 3.Walk me through a project where a key contributor was blocked or underperforming. What specifically did you do to unblock them — and what did you deliberately not do?

    medium~4 min

    What interviewers look for

    • Candidate diagnosed the root cause of the block before acting — distinguishing between a skill gap, a process failure, a dependency issue, or a motivation problem — consistent with Spotify's Servant Leadership principle of coaching over directing.
    • Took concrete, specific actions to remove the obstacle (e.g., cleared a dependency, restructured the workstream, ran a 1:1 to surface unstated blockers) rather than reassigning the work or doing it themselves.
    • Articulated what they deliberately avoided — such as micromanaging, taking over the task, or publicly escalating — showing awareness of the difference between helping and undermining autonomy.
    • Reflected on how the contributor responded and what the candidate learned about their own coaching or facilitation style.

    Likely follow-ups

    • At what point would you have escalated instead of continuing to coach? What would have had to happen?
    • Did the contributor know you saw them as blocked, or did you work around it without naming it directly?
    • How did this change the way you set up projects to avoid that kind of block in the future?

    Company context

    Spotify's Servant Leadership principle defines a leader's primary job as removing obstacles, not directing work. For a mid-level Program Manager operating across squads at Spotify's scale, this is a daily reality — you won't have authority over most of the people your program depends on. This question probes whether the candidate leads by enabling others or defaults to control, workarounds, or escalation when someone on the critical path struggles.

  4. 4.Tell me about a time you saw something broken in how your team was working together — not a project problem, but a culture or process problem — and you fixed it without being asked to.

    medium~4 min

  5. 5.Describe a project decision you made where the data was pointing one way but your instinct or qualitative signal was pointing another. What did you do, and how did it turn out?

    hard~5 min

  6. 6.Tell me about a time you had to push a program forward when your squad had no clear mandate or ownership boundaries — overlapping responsibilities, unclear accountability, and pressure to deliver. How did you create structure without a top-down org chart to rely on?

    hard~5 min

Problem Solving Questions (6)

  1. 7.Spotify Premium has roughly 240 million paid subscribers globally. Estimate how many customer support tickets the Premium team handles per month, and what fraction you'd expect to be billing-related.

    easy~3 min

  2. 8.You're a PM on the Spotify for Artists team. A quarterly business review shows that the percentage of artists who log in more than once per month dropped from 45% to 38% over two quarters. How do you figure out what's driving it?

    easy~3 min

  3. 9.Spotify is considering adding a new 'mood-based playlist' feature to the Premium app. You need to estimate the engineering and design investment required to build an MVP. How do you scope it, and what's your process for getting to an estimate you'd actually put in front of leadership?

    medium~4 min

  4. 10.The Spotify Ad Studio team wants to grow self-serve ad revenue by 25% next year without adding headcount to the sales team. Walk me through how you'd structure a program to hit that target.

    medium~4 min

  5. 11.Spotify is launching a new podcast discovery feature globally across 180 markets simultaneously. Three weeks before launch, your data shows that feature adoption in your internal beta is significantly higher in English-language markets than in non-English markets — roughly 3x the engagement rate. How do you respond?

    hard~5 min

  6. 12.Spotify Wrapped drives enormous engagement every December, but the program involves 15+ squads, an immovable launch date, and a dependency chain that starts in August. Walk me through how you'd design the overall program structure from kickoff to launch.

    hard~5 min

Role Knowledge Questions (6)

  1. 13.Walk me through how you build and maintain a program roadmap when you're coordinating work across three or more squads with different release cadences.

    easy~3 min

  2. 14.You're running a program and you realize midway through that your original scope estimate was off by about 30%. How do you handle the conversation with your stakeholders?

    easy~3 min

  3. 15.How do you decide which risks in a program actually need a mitigation plan versus which ones you just monitor and accept?

    medium~4 min

  4. 16.A launch you're managing is two weeks out and a new compliance review requirement just appeared — legal says it could take four to six weeks. How do you manage the program from that moment?

    medium~4 min

  5. 17.You're asked to define the success metrics for a new internal tooling program — say, a rollout of Backstage to 200 engineers across five squads. What metrics do you put in place and how do you know when the program has actually succeeded?

    hard~5 min

  6. 18.You're managing a cross-functional program — think something like a Spotify Ad Studio feature launch involving product, engineering, sales, and legal — and two squads have directly conflicting priorities that are both on your critical path. How do you resolve it without escalating to a VP?

    hard~5 min

Situational Questions (6)

  1. 19.You're running a Spotify Wrapped delivery program and a dependency team tells you they'll be two days late — which pushes your final QA window into the weekend before the global launch. What do you do in the next four hours?

    easy~2 min

  2. 20.Midway through a program, you realize two squads are building overlapping functionality because no one clearly drew the boundary at kickoff. Both leads think they own it. How do you sort it out?

    easy~3 min

  3. 21.You're running a program to roll out a new feature in Spotify for Artists, and three weeks before launch, the engineering lead tells you the backend won't scale beyond 50,000 artists at launch — but you've already told the artist partnerships team to expect full rollout. What do you do?

    medium~4 min

  4. 22.You're coordinating a program with five squads and realize your weekly status update is becoming the only place where dependencies get surfaced — teams are waiting for that meeting to flag blockers instead of raising them in real time. How do you change this without adding process overhead?

    medium~4 min

  5. 23.You're PM on a program to deliver a new advertiser reporting feature for Spotify Ad Studio. Two weeks before the GA release date, your sales team tells you three enterprise advertisers — accounting for $4M in bookings — are threatening to pause spend unless the feature ships on time. Engineering just flagged a data accuracy issue that needs an extra week to fix. Do you ship on time or delay?

    hard~5 min

  6. 24.You're managing a cross-functional program that's been running for four months. A senior engineer on one of the squads tells you privately that the tech lead has been making architectural decisions that will create significant rework later — but the tech lead is well-respected and the squad lead doesn't see a problem. What do you do with that information?

    hard~5 min

Stakeholder Questions (6)

  1. 25.Think of a stakeholder — a marketing lead, a finance partner, whoever — who consistently went around you to get answers directly from your team. How did you handle it?

    easy~3 min

  2. 26.Tell me about a time you had to get alignment from a partner team — say sales, legal, or finance — on a deadline or scope call, and they pushed back hard. How did you move it forward?

    easy~3 min

  3. 27.Describe a time when two senior stakeholders gave you directly contradictory direction on a program you owned. What did you do?

    medium~4 min

  4. 28.You're three months into a program, and a key exec sponsor has gone quiet — skipping reviews, slow to respond, clearly less invested than at kickoff. How do you diagnose what's happening and what do you do about it?

    medium~4 min

  5. 29.Tell me about a time you had to convince a stakeholder to trust a data signal or a recommendation that directly contradicted what they believed based on their experience. How did you do it?

    hard~5 min

  6. 30.You're running a program where a senior sales leader keeps expanding the scope in stakeholder reviews — new requirements, new use cases — and the engineering lead is about to walk. How do you handle both relationships at once?

    hard~5 min

More Spotify interview questions