J'ai passé un entretien chez Amazon (Ciudad de Mexico)
Entretien
Primer filtro: Una prueba en HackerRank que duró como 90 minutos. Te dan 2-3 problemas de programación para resolver, básicamente algoritmos y estructuras de datos. Nada del otro mundo pero tienes que ser rápido porque el tiempo vuela.
Segundo filtro: Entrevista por video de soft skills y behavioral questions. Aquí ya te preguntan las típicas de Amazon sobre sus principios de liderazgo. "Cuéntame de una vez que...", "Describe una situación donde...", ese rollo. Dura como 45 minutos y tienes que tener ejemplos preparados.
Tercer filtro: Phone interview de live coding. Esta fue la más pesada. Te comparten pantalla en un editor de código online y tienes que resolver problemas mientras explicas tu proceso de pensamiento
Questions d'entretien [1]
Question 1
Me tocó resolver el clásico problema de contar islas en una matriz. Te dan una grid de 0s y 1s donde:
0 = agua
1 = tierra
Una isla es cualquier grupo de 1s que estén conectados horizontalmente o verticalmente (no en diagonal). Tienes que contar cuántas islas hay en total.
Por ejemplo si tienes:
1 1 0 0
1 0 0 1
0 0 1 1
Aquí hay 3 islas. La primera son los 1s de arriba a la izquierda que están conectados. El 1 solo de la derecha es otra isla. Y los dos 1s de abajo a la derecha forman la tercera isla.
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.
