I applied through a recruiter. The process took 1+ week. I interviewed at Amazon (Guadalajara, Jalisco) in Oct 2024
Interview
I had 4 interviews face to face, two were good but the other two were not
At the end of one, the guy told me to wait while he took some notes, we had a shared text editor and he did not realize that he was typing there, it was just random text, like "fdsfasdf", and he kept staring at his phone thoughout the interview
When I was applying the position was remote, but then they changed it to fully onsite
Interview questions [1]
Question 1
I had three coding sessions: Problem Solving, Data Structures and Algorithms, Logical and Maintainable, and the last session was a System Design problem
Interviewed for silicon team. Have only been asked about the domain specific knowledge in 1st round and system design in 2nd round and C coding in 3rd round.
The interviews were 50 mins each.
First round with hr screening - 2 leetcode questions then hr manager screening then the loop which consists of 4 interviews each an hour long. The 4 interview questions they asked where three medium leetcode questions. And one system design interview question about how to shadow deploy a test software to millions of users.
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.
Interview questions [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.