J'ai postulé via un recruteur. J'ai passé un entretien chez Amazon (Berlin)
Entretien
The first part was the Amazon Leadership Principles question. Then, there was a Leetcode Medium question. First, I solved the question in suboptimal way and we discussed the time and space complexity. The interviewer was helpful and kept giving hints to solve the issue optimally.
Questions d'entretien [2]
Question 1
The LP question was something like: tell about the situation, when you had to deal with very time-constraint project/task.
Design a data structure that tracks visitors in a queue with the following requirements:
- Possibility to return the last person in the queue, who visited only once
- All operations must be O(1) time complexity
visit("Alice") -> Queue: [Alice]
visit("Bob") -> Queue: [Alice, Bob]
visit("Charlie") -> Queue: [Alice, Bob, Charlie]
visit("Bob") -> Queue: [Alice, Charlie] (Bob removed because second visit)
get_last_unique() -> Returns "Charlie"
visit("David") -> Queue: [Alice, Charlie, David]
visit("Charlie") -> Queue: [Alice, David] (Charlie removed because second visit)
get_last_unique() -> Returns "David"
Loop — 4 rounds, all on the same day
Round 1 — Coding (DSA)
Interviewer was a senior SDE, very friendly.
Warm-up + behavioral: "Tell me about a time you took ownership of something outside your responsibilities."
Main question: Given a list of meeting intervals, find the minimum number of conference rooms required. I used a heap. He then asked a follow-up: what if meetings could be reassigned to minimize total idle time? We discussed approaches but didn't fully code it.
He cared a lot about how I talked through edge cases out loud.
Round 2 — Coding + Problem Solving
LP question: "Describe a situation where you disagreed with a teammate."
Coding: LRU Cache implementation from scratch. I used a hashmap + doubly linked list. He pushed on thread-safety and what happens at capacity 0.
Round 3 — Behavioral (Bar Raiser)
This was the toughest round — no coding, all Leadership Principles, very deep STAR-format probing.
Questions I got:
"Tell me about a time you failed and what you learned."
"A time you had to deliver something with a tight deadline and limited information."
The bar raiser kept drilling: "What was your specific contribution?" "What would you do differently?" "What data did you use?" Have 6–8 strong stories ready with metrics.
Round 4 — Low-Level Design
Design: Design a parking lot system (classes, vehicle types, spot allocation, pricing). Then he asked me to code the findSpot() and releaseSpot() methods.
Questions d'entretien [1]
Question 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
Great interview process with three rounds, including a technical assessment and a technical interview. The interviewers were professional and supportive throughout the process. The questions mainly focused on DSA, problem-solving, and core technical concepts. The discussions were engaging and provided a good opportunity to demonstrate technical skills. Overall, the process was well-structured, smooth, transparent, and a very positive experience.
J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Amazon (Dublin, Dublin)
Entretien
Online techincal assessment. Had to screen share and complete basic coding tasks similar to Leet Code. Could choose a language of your choice. Overall a very fair system and judged based on merit.
Questions d'entretien [1]
Question 1
Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.