Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

8 stories

Likes earn the author +10 XP for the first 3 likes each day

SpotifySoftware Engineer
Reported Jun 2026

Spotify Software Engineer interview with a 75-minute side-project and coding session

After speaking with a recruiter by phone, I moved into one focused interview with a senior software engineer. It lasted about 75 minutes. The format was structured: I introduced a side project, then answered technical questions based on what I'd shared, and finally did live coding in the style of classic LeetCode problems. The pacing felt fairly straightforward, but the interview was still techni…

Technical Screen0
SpotifySoftware Engineer
Reported May 2026

Spotify Software Engineer interview: DSA, system design, and behavioral loop

My process started with an HR screening, followed by a technical and behavioral screen with two engineers. That round used a HackerRank-style setup and included what felt like standard DSA questions. I then went through a full loop with several interview slots: two more DSA coding rounds, one system design round, and one behavioral interview. The format was methodical. Each interviewer seemed to…

HR Screen0
SpotifyFull Stack Engineer
Reported May 2026

Spotify Full Stack Engineer interview: Backend Tech Screen changed to Web Tech Screen

I had a phone screen followed by a technical interview with two senior software engineers. The interview invite initially said "Backend Tech Screen." The night before, the recruiter sent an updated invite that kept the same time. I noticed the change while checking the details, then apologized for sending too many messages. On the day of the interview, I got front-end questions instead. Only afte…

HR Screen0
SpotifySoftware Engineer
Reported May 2026

Spotify Software Engineer interview with a difficult technical panel

My first contact was a recruiter call covering the usual basics: my background and resume, why I was interested in Spotify, why the role suited me, current compensation and expectations, work authorization and visa status, and my availability. The later interviews were noticeably harder than the early stages. I reached a technical round with a hiring panel led by a senior-level engineer, and the…

HR Screen0
SpotifyData Scientist
Reported May 2026

Spotify Data Scientist interview: five-week wait for feedback

My process started with a recruiter screen, followed by a technical round with two MLEs. That part was focused and direct. The final step was a behavioral interview with the hiring manager. It took about five weeks to hear back. They still came back with feedback after making a decision, which made the wait feel less abrupt than I expected. Location: United States. Overall feedback: Positive. Off…

HR Screen0
SpotifyBackend Engineer
Reported May 2026

Spotify Backend Engineer interview with unexpected domain questions

I started with an initial screening, which led to a technical screen divided into three parts: a discussion of my project, domain questions, and LeetCode-style coding. I expected the domain questions to relate to the project I’d discussed, but the atmosphere felt cold. During the domain section, the interviewer seemed to jump around and choose questions on the spot. I got a lot of basic, exam-lik…

RejectedTechnical Screen0
SpotifyData Engineer
Reported May 2026

Spotify Data Engineer interview with a demanding coding round

After a conversation with a recruiter, I had a coding-focused round that I expected to be straightforward. It turned out to be difficult. The round was with two senior engineers, and the pace felt demanding. I remember feeling that I needed to be much more fluent with interview-style practice than I actually was, and that gap made the interview harder than it should have been. I didn't receive an…

HR Screen0
SpotifyData Engineer
Reported May 2026

Spotify Data Engineer interview: 12-minute phone screen

My process started with a recruiter chat about my background and visa status. The phone screen was pretty quick, and the scheduling felt a little chaotic. I realized the interviewer was in a rush, and the call, which was supposed to last about half an hour, ended after roughly 12 minutes. Even with the short, hurried conversation, I was selected to move on to the next round. I felt like there was…

0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP