Spotify behavioral interview: Company values (The Bassline)
A dedicated values interview probes teamwork and judgment through past stories; candidates report STAR-style answers work well and that low collaboration can cost an offer.
| Progress | Principle | Your story |
|---|---|---|
| One TeamCollaboration and inclusion | Write a story | |
Sample answer: Describe a project that needed several teams. How did you get them aligned?Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other. Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me. Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part. Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs. Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences | ||
| Human JudgmentDiving deep · Ambiguity and judgment | Write a story | |
Sample answer: Tell me about a problem where the obvious cause was not the real oneWhether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Situation Our product catalogue service had short latency spikes roughly every ten minutes, where the slowest requests jumped from about 200 milliseconds to four seconds. The team had blamed the database for weeks and was planning to move to larger database servers. Task I was on call that week and wanted to be sure the expensive fix would actually work before we paid for it. Action First I lined up the spikes against database metrics, and the database was not busy during them; queries were slow because many arrived at once. So I looked at what sent them. Our service cached product data for exactly ten minutes. When we deployed, every instance filled its cache at the same moment, so the entries also expired at the same moment, and thousands of requests went to the database together. I confirmed it by reading the cache code and by reproducing the pattern on staging with a load test: same ten-minute spikes. The fix was small. I added a random spread of plus or minus two minutes to each entry's expiry and made sure only one request per key reloaded data while others waited for it. I tested it on staging, then rolled it out to one instance before the rest. Result The spikes disappeared; the slowest requests stayed under 300 milliseconds. We cancelled the database upgrade, which would have cost more than the rest of our yearly hosting for that service. I wrote a short note on synchronised cache expiry, and we added it to our design review checklist. Tip: Show you went to the data or the code to find the real root cause. Diving deep: weak answer, follow-ups and level differences | ||
| Make It HappenOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Spotify behavioral interview based on?
Company values (The Bassline): One Team, Human Judgment, Make It Happen. A dedicated values interview probes teamwork and judgment through past stories; candidates report STAR-style answers work well and that low collaboration can cost an offer.
How do I answer Spotify questions on "One Team"?
Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Show how you helped others succeed and made people feel they belonged. A typical question: Describe a project that needed several teams. How did you get them aligned?
How do I answer Spotify questions on "Human Judgment"?
Whether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Show you went to the data or the code to find the real root cause. A typical question: Tell me about a problem where the obvious cause was not the real one