Ho presentato la mia candidatura online. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso Spotify nel mese di ott 2022
Colloquio
All in all, I thought the Spotify interview process was fairly standard for the industry. I had pretty good communication throughout the process with the recruiter and the interviewers all seemed technically able and excited to answer questions about the company. I've outlined a more in-depth timeline below, but overall the process took just under 2 months from online application to offer. Detailed timeline: - I applied to a few different roles online, and heard back from the recruiter about 3 weeks later (for the first role I applied to, didn't hear back about the others) - Had a short chat with the recruiter about the role, interview process, and next steps in which they would submit my resume to a few different teams under the org the role was for. - Heard back from the recruiter about a week later that I would be moving on to the second round, which was a technical-based screening interview. I scheduled this for about 2 weeks later. - The technical screening itself was 75 minutes that had a technical background discussion where I was told to be able to discuss a recent project in technical depth and learnings. After the project overview I was asked a few java/backend domain questions which were fairly straightforward given you have industry experience. We ended with a leetcode style coding question. - Heard back from the recruiter that I passed the technical screen 2 days after. At this point we had a final round prep session and I scheduled the virtual onsite round for a week and a half later. - The onsite round itself had 4 1-hour long interviews, each with a different topic (programming/DSA, system design, values/behavioral, case study). All of the interviewers were engaged and friendly, and seemed more interested in my process/approach than quickly solving the questions. The case study round was the most interesting as it was made to simulate an oncall issue response. The system design stayed fairly high level and the programming interview was more object oriented than leetcode based. - 2 days after my onsite the recruiter reached out to me to set up a few HM calls (ultimately only one of them ended up happening) for the following week. I received an offer for the HM's team I chatted with 2 days afterward. - The offer deadline was 1 week and I accepted! My start date was set to be a week and half after my signing date.
Domande di colloquio [1]
Domanda 1
Behavioral questions were fairly standard, the domain questions were spread across language specificities and approach to certain aspects of a backend engineer (i.e. how do you handle an oncall issue?) The programming questions were standard LC/object oriented q's.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Spotify (New York, NY) nel mese di mag 2026
Colloquio
Spoke with a recruiter, was ghosted after the interview. He asked all the standard questions - why Spotify, expected level, salary expectation, what are the priorities, why left previous company, etc.
Domande di colloquio [1]
Domanda 1
What was the most complicated project you were working on in your previous company?
Initial HR Call and screening, then arround two weeks later leet code task, followed by on-site architectural/design test and the final culture fit check with HR/Managers. Overall the process was 3-4 weeks.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Spotify nel mese di dic 2025
Colloquio
The interview process was long and drawn out. It took 2.5 months with multiple delays and rearrangements from Spotify side. I can’t fault the actual interviewers, they were very nice and considerate, but the organisation of the process was very messy and disorganised. At the end I received a rejection with no feedback on Christmas Eve.
Domande di colloquio [1]
Domanda 1
Debug a production system with logs and Linux commands