Candidatei-me por meio de uma faculdade ou universidade. O processo levou 2 semanas. Fui entrevistado pela Amazon (Austin, TX) em fev. de 2013
Entrevista
After I submitted my resume in university career fair. I got 2 round on campus interview. All techinical questions, actually not about the project experience too much. The first round is by AMS manager who seems pretty nice and interested in large scale computing. The interview went nice and I need to write code on a paper briefly about my solution. Second round is by 3 interviews together,45 min each with an engineer. The problems are like link list, priority queue, binary search tree and almost all has been mentioned somehow in career cup or so. Take a look at the interview preparation website is a great help. They seems like the free and open culture in Amazon and they have great passion about their job. Very nice.
Outras avaliações de entrevista de vagas de Software Engineer da empresa Amazon
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.
Candidatei-me por meio de uma faculdade ou universidade. Fiz uma entrevista na empresa Amazon (Dublin, Dublin).
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.
Perguntas de entrevista [1]
Pergunta 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.
Perguntas de entrevista [1]
Pergunta 1
Most coding questions were LeetCode Medium. Common themes: graphs, heaps, sliding window, hashmaps, and LRU/design., system design,
