Responded within 24 hours after I submitted the application. The job requirements were really interesting.
I went through two phone interviews. These involved basic knowledge questions, not hard coding problems.
I went on-site for interviews about two weeks after the last phone interview.
Everything felt good. The company is clearly a more than awesome place to work, though I myself am to blame for coding some really poorly in one of the coding interviews. That might be the major reason I was rejected.
There is only one unpleasant experience: the system design interview. The interviewer kept prying into the system architecture I designed during my last summer internship at a small startup. He asked for every detail and was clearly impatient and displeased with the simple design I presented. This made me uncomfortable, as his questions were based on past events that I couldn't change. Clearly, my design was also based on practical needs and conventions already established at that company.
Wouldn't it be more appropriate for questions to be framed like, "What's your opinion on X situation? What would be your ideal design if faced with X?" Instead, I received responses like, "Oh, so you guys made it this simple? Why?" with displeased expressions.
I felt it was unfair because he was evaluating the company I interned in, not me. I just hope these kinds of interview questions can be better designed. Nobody likes being put in a situation where they either have to lie about what they did or admit to a naive design, which was actually very reasonable under those specific practical circumstances.
The following metrics were computed from 26 interview experiences for the Spotify Software Engineer role in New York, New York.
Spotify's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Spotify's Software Engineer interview process in New York, New York.