I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon in Aug 2025
Interview
Te contactan por LinkedIn donde te comparten un link para iniciar el proceso de entrevista. Primero se llenan datos personales y de currículum, luego hay que iniciar una prueba técnica (llamada "assessment"), son dos problemas de programación (usualmente sobre estructura de datos) y te dan 1 hora para responder ambos, puedes dejar un problema en pausa si te causa conflicto y seguir con el 2do problema, lo que si es que ambos deben estar terminados, completando todos los casos de usos correctamente, y después una prueba sobre prácticas laborales que es más rápido y sencillo. Todo este proceso es en línea, si te escogen hay más pasos como una entrevista técnica en vivo y una entrevista con el gerente del área de la posición.
Interview questions [1]
Question 1
Preguntan específicamente sobre casos de uso de estructura de datos para programación. Es recomendable practicar antes en el sitio web que ellos mismos te dan para llegar con práctica a la prueba real. No son problemas de alto grado de dificultad pero el tiempo límite si hace que haya más presión de la usual resolviendo problemas.
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.
I applied through college or university. I interviewed at Amazon (Dublin, Dublin)
Interview
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.
Interview questions [1]
Question 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.
Interview questions [1]
Question 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
