I applied online and the process took 5 days - interviewed at Netflix in June 2013.
Interview Details – The initial interview with the HR was great. The process was explained and the next interview was scheduled soon after the HR interview. The Engineer who interviewed me called late (this happens in many companies). It was a skype interview and the interviewer kept yawning throughout the interview. Overall the experience was ok. The questions asked were not to hard.
Interview Question – Questions relate to linked list, hash table and Algorithmic complexity. Answer Question
I applied through a recruiter and the process took 2 weeks - interviewed at Netflix in October 2012.
Interview Details – Recruiter contacted me and upon sending them my resume they scheduled 30 minutes call where they explained about Nexflix and its culture. After that they scheduled a 45 minutes phone interview. After the phone interview they asked me for an In-Person interview which was scheduled with 4 people. A hiring manager, 2 senior developers and one QA engineer.
Interview Question – Not any specific. They were checking more on scripting and SQL skills. Answer Question
I applied online and the process took a day - interviewed at Netflix in September 2010.
Interview Details – they are very responsive. Great team with a unique culture. The interview was scheduled with 5 mini interviews with 5 different employees
Interview Question – What is the difference between normalization and de-normalization? What are the pros and cons of each strategy? Answer Question
I applied through a recruiter and the process took 2 weeks - interviewed at Netflix.
Interview Details –
t's been about 5 months since my interview. i purposefully wanted to sit on for a while to find out how i really felt.
i was contacted by a direct recruiter over linkedin. a phone screen with the recruiter, then with the director of the group, then scheduled for an onsite. i was warned it would unorthodox and that they were trying something new.
when i arrived, i had a short chat with the director, then it was explained i would be given a laptop, and a problem to solve in about 2 hours. without going into details, the problem went like this,
"the netflix mobile app doesn't have feature XXX. we came across an open source app that has feature XXX, but it doesn't compile or otherwise run. can you get it to work?"
i was told that no one had ever got the app to work, so just do as much as you can in the allotted time. without going into too many details, i got the app almost 100% working. there were many problems: outdated libraries, broken project setup, and some very, very obscure code bugs related to authentication.
i was pretty happy that i succeeded, and the director seemed surprised and impressed as well. we had another short chat about what i had accomplished, then talked about next steps which was presented to me as a done-deal at the time. a few hours later, i get a call from the recruiter. they were passing. no reason given (as is typical of course).
now, this could have been completely legit. despite having succeeded technically, i may have rubbed them the wrong way. that seems unlikely though as 95% of the interview was be alone in a room coding. maybe they weren’t truthful about no one ever successfully getting the app to work, and i actually did much more poorly than the average candidate.
another possibility is that they brought me in to get some free work done. every one of my colleagues that i discuss this with suggests this. honestly, this seems a little crazy. is it worth the effort to get a few hours of free work when they have an entire staff of highly trained engineers with domain specific knowledge?
i’ll never know, but i must say, the entire thing felt strange, and still does. to add to that, i was later referred on linkedin to another employer out of the blue, by the same director.
Interview Question – see above. Answer Question
The process took a day - interviewed at Netflix in March 2012.
Interview Details – The interviewer was nice. He asked about a question that can utilize merge sort algorithm.
Interview Question – Question related to the usage of merge sort algorithm. Answer Question
I applied through a recruiter and the process took 5 days - interviewed at Netflix in January 2012.
Interview Details – Recruiter Contacted me over Linkedin. Then we dicussed about my experience both past and current. She asked about the future role that I am looking forward for. Then due to time constraints, she explained a little bit about the company and asked me to check their 2 presentation online on Careers website about Netflix culture.
Very Easy Interview
The process took 2 days - interviewed at Netflix in November 2011.
Interview Details –
Bizarre. I submitted my app online and they called me a few days later, showering me with praise. And the whole "We work hard / play hard" mantra was repeated over and over. The interview was OK, but the interviewer was clueless about the job. Every question I asked "I don't really know about that ha ha ha...".
They were really pushy to set up a follow up interview with the hiring manager for the next day. I had a previously scheduled commitment (wisdom teeth out) and they basically insisted that I speak to them right after my appointment. Yeah, not gonna happen. So, I re-shuffled my day and the time for our call came and went. No call. No email. No apology. Finally, I emailed them to remove myself from the whole process and they actually had the audacity to ask me if I would refer any of my friends for the position.
Interview Question – Why do you want to work here? Answer Question
Very Easy Interview
The process took a day - interviewed at Netflix in August 2011.
Interview Details – Contacted me for a job. I agreed to be interviewed and sent them a resume. After that, they just disappeared out of existence. Flakey and a waste of time - avoid.
Interview Question – What is a good time to call? Can you send a resume? Answer Question
I applied online and the process took 1+ week - interviewed at Netflix in September 2010.
Interview Details – The interviewer asked too many difficult questions irrelevant to the job description and was rushing throughout the interview which made it look as if the actual candidate may have already been hired.
Interview Question – Socket programming with respect to TCP/UDP Answer Question
Fast-moving. Few bureaucratic distractions. Willing to make big, disruptive changes quickly. The move to original content was smart and will propel growth well into the future.
If you function well in a meritocracy, then you will likely be… – Full Review
Your feedback has been sent to the team and we'll look into it.
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.
No thanks –