Spotify Interview Questions & Reviews

Updated Aug 10, 2014
Updated Aug 10, 2014
42 interviews

Interview Experience

Interview Experience

45%
16%
38%

Getting an Interview

Getting an Interview

44%
40%
7%

Interview Difficulty

3.1
Average

Interview Difficulty

Hard

Average

Easy

Candidate Interview Reviews

Sort: Popular Date Difficulty
  1. 1 person found this helpful  

    Software Engineer Interview

    Anonymous Employee  in  New York, NY
    Anonymous Employee in New York, NY
    Application Details

    I interviewed online. The process took 4+ weeks - interviewed at Spotify in October 2013.

    Interview Details

    Responded within 24 hours after I submitted the application. Really interesting job requirements. Went through two phone interviews, basic knowledge questions and not hard coding problems. Went on-site for interviews about two weeks after the last phone interview. Everything feels good, the company is clearly a more than awesome place to work in, though I myself is to blame to code some really dirty in one of the coding interviews. That can be the major reason I am rejected.

    Interview Questions
    • There is only one unpleasant experience, it is the system design interview. The interviewer kept prying the system architecture I designed in my last summer internship, where I did in a small startup. He asked every details and clearly impatient and displeased with the simple design I brought about. That made me uncomfortable, since his questions are based on some facts which already happened in the past and there is nothing I can change about. And clearly my design is also based on the practical need and some conventions already established in that company. Wouldn't it be more proper that questions are drawn like "what's your opinion over XXX situation? what's your ideal design if faced with XXX?" Instead, I am getting responses like "Oh so you guys make it this simple? Why?" with displeased expressions. I felt it so unfair since he was evaluating the company I interned in but not myself. Just hope these kind of interview questions can be better designed. nobody likes being put in the situation that either you lie about the things you did or you admitted some naive design you have applied, which is actually very reasonable under that certain practical circumstance.   Answer Question
    No Offer
    Positive Experience
    Average Interview
  2. 2 people found this helpful  

    Software Engineer Interview

    Anonymous Interview Candidate  in  San Francisco, CA
    Anonymous Interview Candidate in San Francisco, CA
    Application Details

    I interviewed through an employee referral. The process took 2 weeks - interviewed at Spotify.

    Interview Details

    The day after showing initial interest in working at Spotify, I was contacted by HR. A week later, I went in for lunch, an architectural interview with some members of the team, followed by informal coffee interview afterwards. I was also giving a take-home project to work on, and a week to complete it. A few days after going in to their office, I chatted on Skype with the director of engineering to answer any lingering questions I had. A couple days after submitting the take-home project, I received an offer.

    Interview Questions
    • Take home project was to create something (open-ended) with their Metadata API.   Answer Question
    • How would you implement a "like" button on a website?   Answer Question
    Negotiation Details
    Yes - I was given an initial offer, and asked for about 15% more. They counter-offered of about 1/2 that, plus a signing bonus. It was very friendly and quick (1 day turn-around).
    Accepted Offer
    Positive Experience
    Easy Interview
  3. 1 person found this helpful  

    EX Team Position Interview

    Anonymous Employee  in  New York, NY
    Anonymous Employee in New York, NY
    Application Details

    I interviewed online. The process took 4+ weeks - interviewed at Spotify in July 2013.

    Interview Details

    The interview process for me, was over a month long. It involved initially phone calls, multiple stages. Followed by skype interviews, multiple stages. And finally a flight to NYC, and a series of in person interviews. All of the interviews were technical in nature.

    There was as I mention below, an extensive take home coding exercise. I spent several hours writing it, and submitted it. I have no idea if it was ever even looked at by anyone. I received no feedback on my performance from spotify at all. In fact, their general lack of communication was something of a concern to me.

    Throughout the process there were delays in next step communications of weeks. I was told repeatedly that I was basically a sure thing torwards the end, and got on the plane home expecting an offer that never came. Having been told this after the more difficult technical interviews had passed, I was confused, and a bit angry when no offer was given.

    I really would love to know why that was the case. I received no feedback indicating to me in any way that there was some deficiency in my interview performance. At one point in the in person, a top engineer who had been silently tapping away at his keyboard asked his sole question of "what is your favorite color?" That was probably the strangest interview question I've ever been asked.

    Interview Questions
    • There was an extensive take home coding assignment. It tooke several hours to write.   View Answer
    No Offer
    Negative Experience
    Difficult Interview
  4. We want your feedback – Is this interview information helpful to you?  Yes | No
  5. 4 people found this helpful  

    Mobile Software Engineer Interview

    Anonymous Employee  in  New York, NY
    Anonymous Employee in New York, NY
    Application Details

    interviewed at Spotify in June 2013.

    Interview Details

    First I had to a phone screen where we discussed several questions about Objective C: memory management KVO, KVC, Core Data...

    If you pass this interview, they will bring you on site and you will have a series of interviews (4 for me). 3 of them were engineering related, with whiteboard coding problems.

    The current office is pretty crowded and everything looked a little messy, but they told me they are about to move to their new shiny office, so I expect that to change soon enough.

    Interview Questions
    • They asked typical BS questions, like LCS in a binary search tree and in a regular binary tree and other search related problems. Also expect some design/architect questions.   Answer Question
    Declined Offer
  6. 2 people found this helpful  

    Software Engineer Interview

    Anonymous Employee  in  San Francisco, CA
    Anonymous Employee in San Francisco, CA
    Application Details

    I interviewed through a recruiter. The process took 2 days - interviewed at Spotify in April 2013.

    Interview Details

    I had an initial phone screen with an HR person. It was a basic screen, but then she asked me some technical questions about objective c. That when OK and I had another phone screen with the hiring manager. The questions he asked were very text book and not really problem solving ones. So I didn't really know some of them because I hadn't cracked a cs text book in a while. So I was pretty unsure about the next step. But I waited for the recruiter to call me back and she never did.

    Interview Questions
    No Offer
    Negative Experience
    Average Interview
  7. 2 people found this helpful  

    Javascript Engineer Interview

    Anonymous Employee  in  New York, NY
    Anonymous Employee in New York, NY
    Application Details

    I interviewed through a recruiter. The process took 2 weeks - interviewed at Spotify in May 2013.

    Interview Details

    A Talent Acquisition rep reached out to me via LinkedIn, indicating that they wanted to talk to me about a Javascript Engineer position. I responded (via LinkedIn) that I was interested in the position. After not hearing back for over a week I contacted the rep directly (their email address was listed publicly).

    The rep responded within minutes to let me know that she didn't handle the Javascript Engineer position and that she would pass my resume off to the correct person. I was included on the hand-off / handshake email. The new rep responded almost immediately and requested that I re-send my resume (even though the hand-off email included all of my LinkedIn details and a copy of my resume).

    After some back-and-forth to confirm that the phone number listed on my resume (the same number that appeared in the signature of all of my emails) was the best number to reach me, we scheduled a phone call for later in the week. The phone call was simply to confirm that I was interested in the previously-discussed Javascript Engineer position and that I was capable of writing "non-jQuery" Javascript. With those points established we scheduled a second phone call with an engineer for the following week.

    When the engineer called, he hadn't seen my resume and knew nothing about me other than my name and that he was to quiz me on all things Javascript. The first few questions were straight-forward; "what's the difference between 'var x = 0' and 'x = 0'". Subsequent questions were vague and covered some broad topics, "describe closures", "describe a couple design patterns", etc.

    After the quiz we talked about the range of products & tools teams worked on as well as the way Spotify constructs its teams. Because the engineer knew nothing about me or which position I was interviewing for, he couldn't provide any detail about the team or product I'd be working on.

    Why was I contacted by someone about a position they had no control over? Why did I have to wait 3 days to have a 5 minute phone call just to verify that I was applying for the position they had contacted me about? Why hadn't the interviewing engineer been given a copy of my resume and been told which position I was interviewing for? While everyone I spoke to was friendly, there was a general air of disinterest. The entire process felt muddled and impersonal which is unfortunate, considering that the process was started when the company reached out to me.

    Interview Questions
    • In Javascript, how would you make a variable read-only?   View Answer
    No Offer
    Negative Experience
    Average Interview
  8. 3 people found this helpful  

    Software Engineer Interview

    Anonymous Interview Candidate  in  New York, NY
    Anonymous Interview Candidate in New York, NY
    Application Details

    I interviewed through other source. The process took 3 weeks - interviewed at Spotify in December 2012.

    Interview Details

    I initially had to create an HTML5/JS webapp using the Spotify Metadata Web API. Once this effort was deemed worthy I had a phone screen to go over my solution. The phone screen went well and I was invited to the office to interview for four hours in the following topics:
    1) Overall development pattern discussion (pub/sub, MVC, etc) with some basic JS problems
    2) Culture fit over 1:1 lunch
    3) System design (build an app, what technologies would you use, how would you setup your database schema, etc)
    4) Another review of my initial programming challenge with some algorithm-focused questions

    Interview Questions
    • This was for a JS-heavy role so if you don't know JS's nuances well you can easily get confused.

      I was asking in three different contexts what the value of a variable and 'this' would be equal to for specific snippets of code.
        Answer Question
    Accepted Offer
    Positive Experience
    Average Interview
  9. 1 person found this helpful  

    Operations Interview

    Anonymous Employee
    Anonymous Employee
    Interview Details

    its a good company with a big upside. Has been constantly growing. had a phone interview it was was just usual interview questions.

    Interview Questions
    No Offer
  10. 2 people found this helpful  

    Software Engineer Interview

    Anonymous Employee
    Anonymous Employee
    Application Details

    I interviewed through a recruiter. The process took 2+ weeks - interviewed at Spotify in January 2013.

    Interview Details

    Phone interview and onsite.

    1) 1 round phone interview covers all the basics of computer science i.e, OS, synchronization, networking, distributed systems, software engineering process. Then there were 2 simple coding questions on shared editor.

    After this they said there will be an onsite. Recruiter called me to check about my salary details. When I told my salary, bonus, equity per annum which is like 105k + 10k + 7k recruiter remained silent. He then said he will get back to me about the schedule for the onsite. Since they did not want to proceed because of salary they for formality arranged a 2nd phone round interview. Obviously it was not technical interview and they just said they won't proceed after that.

    Interview Questions
    • not difficult for a good engineer with decent experience in distributed systems.   Answer Question
    No Offer
    Easy Interview
  11. 2 people found this helpful  

    Business Development Analyst Interview

    Anonymous Interview Candidate  in  New York, NY
    Anonymous Interview Candidate in New York, NY
    Application Details

    I interviewed online. The process took 3 days - interviewed at Spotify in November 2011.

    Interview Details

    I applied online and very quickly (that day) got a call from the Head of BD. He asked me about my interest in the role, just a few quick questions and then called me in. It was an extended process. I first went into interview and fumbled pretty badly. I was asked a few different questions about partnerships, how to maximize ROI and cost structures. For my second interview that day I met with another guy and it was pure fit questions, which was much easier. I then met with the General Manager and he just went over my background. I knew I messed up the first piece, so I sent an email asking if I could put together a deck for them that would better represent myself. They agreed and I had 48 hours to answer a case question on market entry. I did that, handed it in and then met again with another recruiter and the head of finance. Those were fit as well.

    Interview Questions
    • What would be a better partnership, brand, hardware, or telecom and why.   Answer Question
    • How would you go about entering the Canadian market, who would you partner with and how much revenue would it bring?   Answer Question
    Negotiation Details
    Haggle a little bit.
    Accepted Offer
    Positive Experience
    Difficult Interview

See What Spotify Employees Are Saying

1 person found this helpful

 Current Anonymous Employee in Riverside, CA

Pros: “It was great Marketing experience” Full Review

Worked for Spotify? Contribute to the Community!

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.