I applied through college or university. The process took 3 weeks. I interviewed at Amazon (Hyderābād) in Jun 2026
Interview
There were 4 rounds of interview
1st round:
Asked 2 dsa question of medium-hard level. Topics were dp and graph. Then a littile bit project discussion
2nd round:
Asked 2 dsa question of easy-meduim level. Topics were dp and string. Then some behaviour questions
3rd round:
Asked 1 dsa question of easy level based on minimum sliding window.
I had given only 3 rounds and then was rejected.
Interview questions [1]
Question 1
They asked a minimum sliding window problem.
Given 2 strings s and t, find minimum length substring of s which contains all characters of t (including its frequency)
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.