Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Netflix (Los Angeles, CA) en oct 2021
Entrevista
Recruiter phone call, team lead video chat, then tech screen video chat.
All friendly and professional conversations.
Do emphasize what you're looking for, not what you're running from. (They headhunted me so I didn't have a vision prepared of what I hoped to find at Netflix.)
Tech screen was a sort of stream-of-consciousness Q and A through my CV to probe for technical depth. Interviewer interrupted a lot, which is understandable to keep things moving toward the goals, but twice it seemed premature enough to me that I redirected back to what I was saying so I could finish my thought.
As others here have said, coding interview portion can be take-home instead of on-the-spot, if you request it.
Preguntas de entrevista [1]
Pregunta 1
Have you worked with X? How would you solve Y problem?
Seeing the URL shortening service design question caught me off guard at first, but it turned out to be a lucky moment. Just a few days prior, I had practiced a similar architecture problem on PracHub, so I felt somewhat prepared to tackle scalability and data consistency aspects. The process included a recruiter screen, followed by a technical interview focused on system design. Overall, the questions were manageable, but I didn't end up receiving an offer, which was disappointing. The experience taught me a lot, though.
Preguntas de entrevista [1]
Pregunta 1
Design a URL shortening service (similar to bit.ly). What components would you include in your architecture, and how would you handle scalability and data consistency?
The Netflix interview loop is intense and lives up to its reputation. The recruiters are great, but the technical bar is absolute top tier. After a technical phone screen, the virtual onsite consisted of two deep system design rounds, a practical coding round, and very heavy behavioral rounds focused purely on their Culture Memo. They do not care about how many LeetCode hards you have memorized. They care about how you reason through scale, failure, and ambiguity.
Recruiter screen high level discussion.
Tech phone screen live programming exercise.
Virtual onsite, 3 tech rounds two culture/behavioral.
For mine it was like an out-of-body experience, except when I turned to look it wasn't a body at all; it was a plane. Watched it take off, seemed like maybe the pilot hit the throttle a little hard trying to reach cruising altitude and then.. dunno, maybe he dropped his cigarette under the seat or there was a bee in the cockpit or something because next thing you know he's flailing around while I watch the plane tumbling, helplessly aghast as a wing shears off from the stresses he's inducing. No survivors.
But seriously, good interview process. Very helpful recruiter team that will spend time detailing the process and expectations. Exercises are very realistic applied engineering stuff, not brain teasers or obscure algorithms or stuff you haven't done since college. Interview process may be different across the org so YMMV. I interviewed with the Content and Business Products side of the house (i.e., tools for studio, production, not streaming to end users) and the coding, sys design, and data modeling rounds all reflected that.
My advice to you: study the OSS software they publish, know your stuff and *stay calm*.
Preguntas de entrevista [1]
Pregunta 1
Describe a time when you had conflict with someone outside your group