J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Amazon en mai 2011
Entretien
Java Int
Guy called me - started with the plan of interview..first 20 mts this...20 mts that
then
whats final finalize finally
hashmap implementation and tree -which one is good
what happens if there is collision in bucket - [hashmap] [all correct]
=================================
Gave me a requirement - he wanted me to impl it.
req-
process1 upgrade
do this 1[lets say a job - write to file]
do this 2
process 2
do that 3
call process 1 upgrade
end process 2 upgrade
existing process 2 do this[so upgrade stops here.]
design/ code in java - where i want to upgrade processes.
I mean even if we get the question, you will have to apply your thinking and coding/design ability to come up with the result.
ALSO - ask questions - cos he hardly mentioned anything.
[did not complete-tried to be too cool]
=====================================
last - write fibonacci series in java.[done in a min]
=======================================
i did fumble on design thing cos - i went with a very generic approach anf the time just ran out. he gave 15 mts i guess...
====================================
well i did ok, but i think im out.
prepare for int by learning few algos and trying to apply them in real time.
Autres retours d’entretien d’embauche pour un poste comme Software Developer chez Amazon
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.
Questions d'entretien [1]
Question 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.
Questions d'entretien [1]
Question 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.
Questions d'entretien [1]
Question 1
Encoding optimization algorithm and talk about a project you did recently.