Taro Logo

Software Engineer Interview Experience - United States

October 1, 2022
Positive ExperienceGot Offer

Process

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; I 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 and 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 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 on-call 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 a half after my signing date.

Questions

Behavioral questions were fairly standard.

The domain questions were spread across language specificities and approaches to certain aspects of a backend engineer (e.g., how do you handle an on-call issue?).

The programming questions were standard LeetCode/object-oriented questions.

Was this helpful?

Interview Statistics

The following metrics were computed from 43 interview experiences for the Spotify Software Engineer role in United States.

Success Rate

19%
Pass Rate

Spotify's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive47%
Neutral21%
Negative33%

Candidates reported having good feelings for Spotify's Software Engineer interview process in United States.

Spotify Work Experiences