Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Amazon (Seattle, WA) en ene 2014
Entrevista
For college students, an on-site group interview is likely, without any phone interviews.
I was contacted a few days after submitting an online application and resume, for an on-site interview later that month. All the interviewees were college students, both undergraduate and graduate.
Due to non-disclosure I cannot discuss questions, but it is already known that these group interviews split candidates into groups of 3, and allow them to each work on a portion of a problem. You are given a laptop, and a choice of languages, and several hours (roughly from 9:30am to 4:30pm) to provide the code for the solution.
During that time there were several interviewers who took us aside to ask us how we were solving the problem, first as a group, then as individuals. This part was closer to a standard interview: discuss the problem, things you fix, things you fail to fix, further work.
There was a tour in the morning, and a Q&A with employees at the end of the day.
Received an offer a few days later. Had 2 weeks to decide. Was given a choice of groups within the company to join.
Preguntas de entrevista [1]
Pregunta 1
Non-disclosure Agreement covers these questions.
Recommendation: fully outline your plan in comments before writing code. If you do not finish, or your code does not work correctly, there will be a record of what you intended.
Standard review of algorithms and data structures is good, but also practice writing, running, and testing code.
Recruiter reaches out after applying through Amazon careers, no referral. Had an initial OA, then after a month had four rounds in two days - three coding one system design. Each round had 30 min behavioral and 30 min coding.
Preguntas de entrevista [1]
Pregunta 1
Questions were mainly hashmap, sliding window and interval related.
The phone screen went longer than expected, focusing heavily on implementation details. The interviewer really grilled me on my approach to a Least Recently Used (LRU) cache, asking how I'd combine a hashmap with a doubly linked list. I felt well-prepared since I had gone through system design examples on PracHub, which made me comfortable discussing eviction policies. The later rounds included more technical questions and behavioral interviews, but in the end, I received an offer, though I ultimately decided to decline. Overall, I’d say the process was average, with solid questions.
Preguntas de entrevista [1]
Pregunta 1
Design and implement a Least Recently Used (LRU) cache supporting get(key) and put(key, value) in O(1) average time. Walk through combining a hashmap with a doubly linked list, eviction policy when capacity is exceeded, and how you'd extend it to handle thread-safe concurrent access.
Interview by recuriter, Phone interview over Chime with one easy Leet code problem and 2 behavioral questions. Although the interviewer was very casual at the start of the conversation, it quickly changed into behavioral questions at the start.
Preguntas de entrevista [1]
Pregunta 1
Encoding optimization algorithm and talk about a project you did recently.