Preguntas de entrevista de Spotify | Glassdoor.es

Preguntas de entrevista de Spotify

Entrevistas en Spotify

389 Opiniones sobre entrevistas

Experiencia

Experiencia
40%
14%
46%

Entrevista conseguida

Entrevista conseguida
64%
19%
10%
2
2
2
1

Dificultad

2,9
Normal

Dificultad

Difícil
Normal
Fácil
  1. Útil (2)  

    Entrevista para Paralegal

    Candidato de entrevista anónimo en New York, NY (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista normal

    Solicitud

    Envié una solicitud electrónica. El proceso duró Más de 2 meses. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)) en mayo de 2018.

    Entrevista

    The interview process took 10 weeks from start to finish and included 3 in person meetings and several phone calls. This is an insane amount of time and interviews for a mid level paralegal position. They went for weeks without updating me on the interview process and I had to send a few requests for an update before they finally told me that I would not be receiving an offer. Overall the interview process was pretty negative, drawn out and unprofessional (the recruiter I was working with quit and the new one had no idea where I was in the interview process). I am grateful for not getting this job, as I am in a much better position somewhere else, with better benefits and pay. So it all worked out I suppose.

    Preguntas de entrevista

    • I was asked about contract management and my knowledge of software licensing contracts.   1 respuesta

  2. Útil (15)  

    Entrevista para Javascript Engineer

    Candidato de entrevista anónimo en New York, NY (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista normal

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)) en mayo de 2013.

    Entrevista

    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.

    Preguntas de entrevista

    • In Javascript, how would you make a variable read-only?   6 respuestas
  3. Útil (16)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en New York, NY (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista fácil

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró Más de 2 meses. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)) en septiembre de 2011.

    Entrevista

    Very disorganized. I interviewed for a software engineer position in 2011, meeting with a bunch of people, half of whom thought I was going for a data scientist position. Everyone at this stage was very friendly. This was followed by a Skype meeting with one of the VPs from Stockholm - at this point the Spotify recruiter said I should expect an offer within the next couple of days.

    Despite attempts to follow-up, two weeks go by and no response. Just as I was about to give up on the position, they get back to me and tell me that the VP flew into the US and wants to meet with me in person. We arrange that. 15 minutes before the scheduled time, after I had driven an hour to NYC and while I was waiting outside their office, I get an email that says the position has been filled and the interview has been cancelled. Maybe it was an honest mistake, but I came out of it with a pretty poor impression of the company's hiring process.

    Preguntas de entrevista


  4. Útil (6)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en San Francisco, CA (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista normal

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró 2 días. Acudí a una entrevista en Spotify (San Francisco, CA (Estados Unidos)) en abril de 2013.

    Entrevista

    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.

    Preguntas de entrevista


  5. Útil (19)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en New York, NY (Estados Unidos)
    Sin oferta
    Experiencia positiva
    Entrevista normal

    Solicitud

    Envié una solicitud electrónica. El proceso duró Más de 4 semanas. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)) en octubre de 2013.

    Entrevista

    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.

    Preguntas de entrevista

    • 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.   Respuesta Pregunta

  6. Útil (30)  

    Entrevista para Software Engineer

    Empleado anónimo en San Francisco, CA (Estados Unidos)
    Oferta aceptada
    Experiencia positiva
    Entrevista fácil

    Solicitud

    Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 semanas. Acudí a una entrevista en Spotify (San Francisco, CA (Estados Unidos)).

    Entrevista

    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.

    Preguntas de entrevista

    • Take home project was to create something (open-ended) with their Metadata API.   1 respuesta
    • How would you implement a "like" button on a website?   3 respuestas

    Negociación

    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).


  7. Útil (13)  

    Entrevista para Software Engineer

    Empleado anónimo en New York, NY (Estados Unidos)
    Oferta aceptada
    Experiencia positiva
    Entrevista normal

    Solicitud

    Solicité el puesto por otro medio. El proceso duró 3 semanas. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)) en diciembre de 2012.

    Entrevista

    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

    Preguntas de entrevista

    • 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.   1 respuesta
  8. Útil (6)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Entrevista fácil

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró Más de 2 semanas. Acudí a una entrevista en Spotify en enero de 2013.

    Entrevista

    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.

    Preguntas de entrevista

    • not difficult for a good engineer with decent experience in distributed systems.   1 respuesta

  9. Útil (10)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo en New York, NY (Estados Unidos)
    Sin oferta
    Experiencia negativa
    Entrevista normal

    Solicitud

    Solicité el puesto a través de un captador. El proceso duró 6 semanas. Acudí a una entrevista en Spotify (New York, NY (Estados Unidos)).

    Entrevista

    I was contacted by Spotify about potential opportunities. There was an initial recruiter phone screen followed by a 60 minute Round1 interview conducted over Google Hangout with shared documents.

    From the start the scheduling of phone screen was problematic. I would suggest a couple days+times later in the week and would get no response until the following week, asking for new times. I'd reply and then once again not hear back. This back and forth and long delays went on for 1 month. When it happened, the phone screen was routine and non-technical, just standard goals, request for current salary, etc. I generally don't like salary sharing this early but they claim they want to be sure we're in the same ballpark, which is fair-- so I gave a wider range.

    The Google Hangout technical interview was scheduled and the first time I was never contacted at the date+time by the interviewer. We rescheduled with the recruiter for a couple days later, and it happened on time. The interview was a technical discussion of CS fundamentals and common knowledge questions about the discipline I focus on. There was a couple routine programming questions on the shared document, mostly along the lines of: write a function that does ___. It wasn't all that hard. It concluded that they would be in touch in a few days with feedback.

    After this I never heard back from them, and was so worn out by the process I didn't bother to follow up. It took over 6 weeks to reach that point and still fell apart.

    Interesting company but poor communication in the recruitment pipeline, and didn't get the sense of any urgency in hiring or value of individual candidates. Perhaps they have a big pipeline and let people fall through the cracks since they can.

    Preguntas de entrevista


  10. Útil (7)  

    Entrevista para Software Engineer

    Candidato de entrevista anónimo
    Sin oferta
    Experiencia negativa
    Entrevista normal

    Solicitud

    Envié una solicitud electrónica. El proceso duró Más de 4 semanas. Acudí a una entrevista en Spotify en marzo de 2016.

    Entrevista

    An awkward experience.

    Everything started as usual, short phone interview with hr which I actually enjoyed because the guy was really friendly. Than he scheduled a phone interview with their engineer shortly. On phone tech interview we had a nice talk with a little bit of coding at the end, nothing special. Than I was contacted by my hr and he told me that I've passed and asked about the dates when I can fly to NY.

    Now the awkward part, shortly after that I've been contacted by another hr who said that she discussed me with my initial hr. She asked for another phone interview, on which I thought we would be discussing onsite travel and availability dates, but instead she started to go through the same questions I've been asked on the very first call and at the end she proposed to schedule another tech phone interview.

    After the second phone interview I got rejection letter, bottom line, don't be happy too early.

    Preguntas de entrevista

    • What is the alternative ways to refactor DNS ?   1 respuesta

No pierdas la oportunidad de conseguir tu empleo ideal
Carga un currículum para solicitar empleos desde cualquier lugar. ¡Es muy fácil!