Solicité el puesto a través de la escuela superior o la universidad. El proceso duró 5 semanas. Acudí a una entrevista en Amazon
Entrevista
Most of the details of the onsite interview are given once you are past the initial screening.
The interview process can differ from one batch of applicant to another.
In my case, I was asked to show up at around 10:30-11:00 AM. When I arrived, there was about 30 other candidates waiting to be interviewed. At around 11:30 AM, the recruiter came in and and lead us to a room where we can have lunch with the full-time engineers ; this was the time to ask them about their work, company culture, Seattle etc.
Afterwards, each candidate is led to a separate room were they would be interviewed individually. Overall, I had four 45min interviews over 3 hours. They were all technical.
Preguntas de entrevista [1]
Pregunta 1
Given a square matrix, implement a function to rotate the matrix 90 degrees.
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.
Solicité el puesto a través de la escuela superior o la universidad. Acudí a una entrevista en Amazon (Dublín, Dublín)
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Technical assessment so a basic leet code style question about reversing the orders of long numerical strings.
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.
Preguntas de entrevista [1]
Pregunta 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,