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.
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.
Interview questions [1]
Question 1
Encoding optimization algorithm and talk about a project you did recently.
First round is just leet code coding which screens through AI before going into live coding. Pretty simple and straighforward. Not too tough. Recruiter walks through it pretty nicely. Not sure how many rounds there are exactly
After submitting my application for the Software Engineer position, I received an invitation to complete an automated Online Assessment (OA). The assessment consisted of standard coding challenges, primarily focusing on algorithmic and data structure problems. Unfortunately, a few days after submitting my solutions for the assessment, I received an email informing me that I would not be moving forward in the interview process and was rejected.