Me postulé a través de un reclutador. El proceso tomó más de 1 semana. Acudí a una entrevista en Amazon (Seattle, WA) en sep 2012
Entrevista
Was contacted by a recruiter based on my Linkedin profile. Procedure was pretty standard 2 phone interviews and then a day of onsite interviews
Phone round 1:
1) Reverse a linked list in place
2) Design a OO model for a parking lot
Phone round 2:
1) Given to BSTs write a function that says if the trees are the same or not.
2) Design a OO model for an online share trading system.
After these two went well I was asked to fly out to seattle for a day of interview
Round 1:
1) Given an large set of numbers, find the top 100. Write code on whiteboard.
Round 2:
1) How would you implement a anagrams functionality for kindle.
2) If you come in one day and you see that suddenly the traffic to your website is down 10% how would you go about troubleshooting this.
Round 3: (Lunch interview)
1) General stuff about what I was working on in the current company.
2) One question (some code on a paper) about threading and deadlocks.
Round 4:
1) Given a sorted array of numbers and then the numbers are rotated, how would you implement a search in less then O(n)
2) Given two string, check if one is a result of rotation of the other
Round 5:
1) Some question about single linked list (donot remember but was pretty easy)
2) How would you design a system to maintain a zoo (OO 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.
Me postulé a través de una facultad o 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,