I interviewed for an SDE II role, and the whole process felt pretty standard and transparent. Amazon told me upfront what the process would look like, so I did not feel like I was guessing what came next: first an online assessment, then three 40-minute interviews back to back on the same day. The technical questions were all very classic problems, and the biggest surprise was that my interviewers often started with coding first instead of spending the first part on behavioral. The behavioral side was still important, but the follow-ups went deep into the actual details of my work instead of stopping at a polished STAR answer. After the loop, my recruiter mostly asked about logistics like start date and work authorization, and then they sent me the offer letter.
I interviewed for an L4 entry-level SWE role, and the process was one 30 minute phone screen followed by a three-interview super day. The phone screen was quick and a bit rushed, with no real introduction, just one medium array problem and then Q&A. In the loop, the behavioral was only about 10 minutes, but it was done by a technical person who kept going deeper and deeper into whatever project I brought up, so it felt more technical than I expected. The coding round was classic DSA with a graph problem and then a heap problem because we had extra time, and the last round was a low-level OOP design around coupons and vouchers. Overall, I did not think the interview was that difficult, but I realized you really have to be ready to defend the details of your behavioral examples.
I interviewed in March 2025 for the Seattle SDE intern role. My whole process was just an online assessment and then one interview, with no recruiter screen or extra technical rounds in between. That last interview packed everything into one session, about 25 to 30 minutes of coding and 15 minutes of behavioral questions. It felt really streamlined because they put all the evaluation into that one final conversation.
I interviewed for SDE-1. The process was a recruiter screen first, then a live coding interview, then a couple of technical rounds with different team members, and the last round was with the hiring manager. It felt pretty straightforward from a structure standpoint. After that final conversation with the hiring manager, I got the offer.
The OA was much more difficult than others I have experienced in the past. I would say it landed on the hard side of Leetcode questions. I'd focus more on graphs and layering other algoritms on top like binary search.
- Delivery hub location optimization
Very heavy emphasis on behavioral, wasn't prepared as well as I should have been. Coding was easy if you've done Leetcode and basic system design and OOPS-oriented coding. For behavioral, make sure to have at least 6 distinct experiences to talk about with solid metrics, reusing stories looks bad.
The process seems to be getting more rigorous than the past, with multiple technical rounds. There is a large focus on the leadership principles.
In DSA it was focusing on Design DSA style problem, then i have HLD and LLD interviews.
Design DSA: Implement Trie for recent searches usecase
LLD: Bookmyshow style ticket booking system
HLD: Design Link preview feature, similar to what's found in Slack or Whatsapp
Prepared for DSA since its phone-screen. Although question was easy i bombed it. At the start of interview LP about project are aksed.
The process was more rigorous than anything I’d done at other big tech companies, but the recruiter was actually accurate and helpful on what to prepare, which is rare and I really appreciated that. A few things caught me off guard: one round had a heavy focus on low-level system design and concurrency, which wasn't explicitly mentioned in the initial prep guide.
What went well was the structure of the technical rounds they felt very practical and less like abstract LeetCode puzzles. The interviewers were engaged and gave good hints when I got stuck. What didn’t go well was my time management in the coding round; I spent too long optimizing a solution that was already passing the test cases, which left less time for the follow-up questions at the end.
- What is your strongest technical expertise?
- Why do you want to join Amazon?
- Given a tree with N nodes, each node has an integer value A[i] . We need to remove exactly one edge such that the tree is split into two connected components.
For every possible edge removal, calculate:
| sum(component1) - sum(component2) |
Return the 1-based index of the edge that produces the minimum possible difference.
Example
N = 7
Edges:
1 2
1 3
2 4
2 5
3 6
3 7
A:
3 6 5 3 2 3 5
The total sum is 27 .
If we remove edge 1 (1-2) :
Component 1 = {2,4,5} -> sum = 11
Component 2 = {1,3,6,7} -> sum = 16
Difference = 5
If we remove edge 2 (1-3) :
Component 1 = {3,6,7} -> sum = 13
Question was multi-stage coding challenge where each completed level unlocked the next set of requirements. Overall, the tasks were fairly straightforward. However, the exercise was quite time-consuming, and I ended up using the full allotted time without being able to complete every level. One challenge with the format was that the stages had to be completed sequentially, so there was no option to skip a level and move on to another problem. This made time management especially important.
The LLD Round and LP round where great. Both the interviewers where kind and patient.
LP (Leadership Principle) round started with the Behavioural questions and some past experience of mine. We had a great conversation.
In LLD round you need to make sure you provide proper list down of Requirements, Entities and Class Diagram. This is the basic minimum they expect of you. Rest you can explain it and write down the points.
The process was new as there was a repository question. This round was AI assisted so you need to use AI quite well.
It was well, interviewer was helpful and was asking mostly standard questions from leetcode. I prepared from Strivers A2Z sheet so it was enough. I could have explained my thinking better
OA was extremely rigourous and took about 3-4hrs at a stretch. 2 coding ques
1) DP Hard
2) Springboot framelwork 6 errors. had to solve using AI assisted bot through a repository
The difficulty level was medium, interviewer was very interested in understanding the different approaches rather then looking on a particular solution
After the online assessment, I got three rounds of interview back to back in one day. The technical question is a simplified version of a hard LeetCode question.
The interviewer did not ask me to optimize my answer to use tries, which I believe is the most efficient solution. Instead, I completed the brute force DFS / BFS solution only and the interviewer was satisfied.
I was asked to explain my code in depth though, talking through how recursion works and how iterative variations are usually more efficient since it does not include the function call stack overhead.
I was grilled hard in the behavioral interview, where I was asked multiple questions. From my experience, the interviewer expected each answer to hit multiple leadership principles.
- You're given an integer array, and your goal is to transform every element into k by performing a series of operations. Each operation allows you to pick a segment ending at the last element and either increase or decrease every number in that segment by 1. Your task is to determine the smallest number of operations needed to reduce all numbers in the array to k.
- A certain number transformation process follows a structured pattern. Starting with a sequence of digits, the process involves repeatedly summing adjacent pairs of numbers. After each sum, only the last digit (the least significant one) is kept. This operation is performed iteratively, reducing the sequence by one digit in each step, until only two digits remain. These final two digits represent the output of the transformation. Given an initial sequence of digits, apply this process to determine the final two-digit result. Your output should be a string representing these two digits.
- Leetcode 212 Word Search II
The process was pretty clear and straitforward. As long as coding skill is well prepared. You should be fine.
Overall, the interview process was well-structured and professional. The interviewers were knowledgeable, and I had a good opportunity to demonstrate my technical skills and discuss my experience. The technical questions were challenging but relevant to the role. One area that could have been better was having more clarity on the expectations and focus areas for each round. Overall, it was a valuable experience.
- Leetcode time to infom all employees
Overall experience was average, for last round interviewer was not friendly and he was not helping instead of I ask something they go deep into it
The overall process was structured and professional, with a mix of coding, technical discussion, and behavioral questions based on Amazon Leadership Principles. The interviewers were clear and gave me space to explain my reasoning. I felt strongest when discussing my past experience, system decisions, and behavioral examples. The main area I could have handled better was time management during coding.I spent too much time thinking through some details instead of communicating my approach and iterating quickly. Overall, it was a good learning experience and helped me identify where to improve for future interviews.
Overall, the process was pretty smooth: application, online assessment, then two virtual interviews. The OA and coding rounds went well because the questions were standard DSA and I was comfortable explaining my approach and complexity. The behavioral portions also felt solid once I got into my STAR examples. The hardest part was handling follow-up questions and changing constraints in real time, especially when I had to rethink an approach while still communicating clearly.
My interview panel was for a specific team and not a general hiring pipeline. 3 rounds technical + behavioral. First 20 mins behavioral then technical. Last round was bar raiser. Everything went good for me, few questions were new like "experience with gen ai", rest everything was traditional LC + LP based behavioral.
The OA is quite long and has multiple parts. Other than the technical coding questions, there are behavioral questions based on the LP and work style simulation (choosing between email replies)
- Amazon's development team is working on a feature for a new product, a smart array processor. In this smart processor, quite simply, given an array of numbers and instructions on which parts of the array to pick and combine into a new array, for each number in the original array, if it's included in the new array, its efficiency is O; otherwise, the efficiency is the count of smaller numbers in the new array. The goal is to add up the efficiencies for all numbers in the original array.
A user has provided an integer array called arr of sizen and a 2-dimensional array called pairs of size m x 2. Eachpair in the pairs array represents the starting and ending indices of a subarray within arr.
For each subarray of arr represented by the array pairs, the goal is to merge and concatenate them into a new array called efficient.
The efficiency of an element at index i in arris defined as follows: if the index i has not contributed to the formation of the array efficient, the efficiency is the count of integers in efficient that have a value strictly smaller than arlil. If the index i has contributed to the formation of the array efficient, its efficiency is o.
Find the sum of the efficiency of all the elements in the array arr.
Example
n = 6
arr = [1, 2, 3, 2, 4, 5]
m = 4
pairs = [[0, 1], [3, 4], [0, 0], [3, 4]]
On concatenating all the subarrays represented by pairs, we get efficient= [1, 2, 2, 4, 1, 2, 4]
The indices 2 and 5, don't contribute to the formation of the array efficient.
•For index 0, arr[0] = 1, the index has contributed to the formation of efficient, hence its efficiency is 0.
• For index 1, arr[1] = 2, the index has contributed to the formation of efficient, hence its efficiency is 0.
• For index 2, arr[2] = 3, the elements [1, 2, 2, 1, 2] are smaller than 3, having count = 5, hence its efficiency is 5.
•For index 3, arr[3] = 2, the index has contributed to the formation of efficient, hence its efficiency is 0.
• For index 4, arr[4] = 4, the index has contributed to the formation of efficient, hence its efficiency is 0.
• For index 5, arr[5] = 5, the elements [1, 2, 2, 4, 1, 2, 4] are smaller than 5, having
count = 7, hence its efficiency is 7.
The sum of the efficiencies of elements in arr = 0+0+5+0+0 + 7 = 12, hence the
answer is 12.
Both core rounds went okay-ish so far. The DSA round was strangely fixated on trees (weird) —the one topic I had not really prepared in-depth for Amazon—and was too focused on DP, strings, sliding window, LCS, and the type of stuff Amazon usually focuses on.
The tech interviewer requested a more technical answer. So i expanded on my existing experience. Complex systems are good to explain.
OA was easy, interview was 2, 1 hour rounds with 30m behavioral and 30m technical. Asking mostly about how you use AI and technicals were typical LC style questions with one being a bit more vague
It went well and answered all questions. and did both leetcode questions asked one in each interview
Preparation: I had a solid understanding of the role and prepared thoroughly with coding practice, system design concepts, and mock interviews.
Confidence in Communication: I introduced myself clearly, asked clarifying questions when needed, and explained my thought process step by step.
Problem-Solving Approach: Even when I didn’t immediately know the answer, I broke problems down logically, discussed possible approaches, and showed adaptability.
Technical Strengths: I performed well in areas I had practiced extensively, such as data structures, algorithms, and SQL queries.
- You are given an integer array nums and an integer x. In one operation, you can either remove the leftmost or the rightmost element from the array nums and subtract its value from x. Note that this modifies the array for future operations.
Return the minimum number of operations to reduce x to exactly 0 if it is possible, otherwise, return -1.
1. Recruiter reached me out on LinkedIn
2. OA
- you don't have to be perfect
3. Technical Screen (fail)
4. loop interview
I'm able to communicate while solving problem but unable to code the problem interviwers are very supportive and friendly they give hints when i stuck at last i was only able to provide pseudo code.
The OA was more challenging than I expected, the questions were more aligned with Competitive programming style. Recruiter was really supportive and informative. Still waiting on the next steps, which is the final round.
- Why do you want to join Amazon?
- Describe the most technically complex project you have worked on and explain why it was complex.
- The manager at the warehouse has decided to make changes to the inventory. Currently, the inventory has 'n' products, where the quality of the ith product after quality checks is represented by the array element quality[i].
The manager wants to create an optimal inventory, where the array of products quality follows the following property:
-All occurrences of each quality value must be contiguous.
In order to convert the inventory into an optimal inventory, the manager can do the following operation any number of times.
1. Choose two quality values x and y.
2. Replace every product with quality x to have quality y instead
3. This operation costs num_replacement units of money, where num_replacements is the number of products whose quality was changed.
Given 'n' products and array quality, find the minimum amount of money the manager has to spend to convert the inventory into an optimal inventory.
Note: the quality of a product can be negative indicating that the product is of poor quality.
Example:
Given n = 7, quality = [7,7,5,7,3,5,3]
One of the optimal ways to convert:
[7,7,5,7,3,5,3] spend 2 units of money-> [7,7,7,7,3,7,3] spends 2 units of money -> [7,7,7,7,7,7,7]
The Leetcode question had a couple of follow ups along with a question about time complexity. Also asked why Amazon?
The DSA question was not straightforward.The overall interview process was good. I suggest to take several mock interviews to get comfortable
Software Engineer
DSA
- Minimum Window Substring
- House Robber (Circular)
- Word Ladder
LLD
- Parking Lot
HLD (Hiring Manager)
- Design Amazon Lockers
Bar Raiser
- Strong focus on correctness, edge cases, and trade-offs
- Word Ladder coding problem
2 1 hour interview rounds after an online assessment. went well, standard questions. interviewer was conducted by one engineer, and one manager on the team that i was eventually hired for.
My overall interview process with Amazon was a positive experience. The process was well-structured, starting with an online assessment that tested problem-solving and coding skills, followed by technical and behavioral interviews. I appreciated that the interviewers were professional and gave me opportunities to explain my thought process, discuss my technical experience, and demonstrate my problem-solving approach. The technical questions were challenging but fair, and I enjoyed discussing my previous projects. One area that could have been improved was communication.
MY DSA was top notch so no issues there, leadership principle questions are predictable so I answered thoroughly.
Process was straightforward with quick feedback. Got a 3d dp and then easy second interview which was standard hashmap manipulation.
Software Engineer
1. Recruiter screen (30 min)
2. Online coding assessment (1 hr)
3. Onsite (4 hr): 3 coding, 1 system design
The overall process was quite slow and took longer than expected. The timeline seemed to depend largely on the interviewer, as the scheduling and progress varied based on their availability. There were also some delays between the different stages of the process, which made it feel less streamlined. Overall, the experience could have been more efficient if the communication and scheduling had been more consistent.
The process was fairly simple, online assessment with 2 coding questions and then multiple choice leadership principles questions (choose the right action for the given scenario). Then around a month later I received an interview invitation for 2 interviews, 1 hour each which consisted of about 40 mins of live coding and 20 mins of CV and competency questions, including AI usage, leadership, teamwork and project deep dives.
It went really well, they were trying to confirm whether I actually solved the assessment on my own and understood my solution.
- Rotate a 2D matrix.
- Dynamic Programming question
- Tell me about your past experiences at your internship
Software Engineer
The process was straightforward and detailed. All communications were done promptly and I was notified of every stage.
Very long process and dragged on for almost a month, more annoying considering the fact that I was still in the early stages of the process
My overall Amazon New Grad SDE interview process was rigorous and fairly challenging. I had three rounds covering coding, Leadership Principles, and low-level design. The coding questions were not just about getting to a solution, but also about understanding long problem statements, handling edge cases, and explaining my thought process clearly. What went well was that I was able to work through the problems, respond to hints, and connect my past experiences to Amazon’s Leadership Principles with specific examples. The LP discussions were also very detailed, with multiple follow-ups that pushed me to explain tradeoffs, ownership, business impact, and how I handled feedback. What did not go as smoothly was the scheduling and communication. All three interviews were initially planned for the same day, but the third round was rescheduled on the day itself and happened around 15 days later. I also was not introduced to the interviewers beforehand, and the process felt mostly automated, so it required a lot of independent preparation
Recruiter then oa then had an interview with hiring manager and then another with someone on the team both technical leetcodes
Smooth process overall but did take a while after the final to hear back about the offer (over a month) potentially due to headcount being still figured out at the time. Questions were easy - medium LC questions.
I interviewed for an Amazon Software Development Engineer internship in February 2025. The process was three rounds over about three weeks: a recruiter screen, a HackerRank assessment, and a final technical conversation that also included behavioral questions. The recruiter screen was straightforward and helpful for setting expectations. The HackerRank portion was the most time-sensitive part, so it rewarded being comfortable turning an approach into working code without spending too long on setup.
The final interviewer was genuinely nice and the conversation felt collaborative. The coding problem was to reverse a linked list. I started by explaining the iterative solution and the pointer changes before coding, then walked through edge cases such as an empty list and a single-node list. The behavioral questions were folded into the same conversation, so I tried to make my answers concise and connect them to how I approach problem-solving and teamwork. Overall, it felt like a fair intern process: not designed to be tricky, but it did require clear communication and clean implementation under time pressure.
A lot of focus spent in every round on LP questions. Make sure to have sufficient stories, sometimes they plan to ask two, but end up asking a third one.
Software Engineer
they give two hackerrank one medium and one hard question
There is not that much interaction with a recruiter. I was lucky in the coding question was not hard but they have a bank essentially similar to leetcode mediums. The bar raiser round you should prepare stories for each one
Too much bureaucratic process. Be prepared for ghosting. They expedite after onsites. Negotiation can take few rounds. Be patient, they do not throw away strong candidates.
Software Engineer
Software Engineer
The overall interview process was well-structured and engaging. The interviewers were professional, communicated expectations clearly, and gave me opportunities to demonstrate my technical and problem-solving skills. I particularly enjoyed the technical discussions and collaborative nature of the interviews. One area that could have been improved was having more clarity around the timeline and expectations between rounds.
All 3 rounds in loop were smooth, they are friendly and interviews went smoothly. I took entire loop in one go so it helped to be very much prepared.
Software Engineer
Overall, the interview process was well-structured and a positive experience. The interviewer was professional and approachable, and the questions provided a good opportunity to demonstrate my technical and problem-solving skills. I particularly appreciated the collaborative nature of the discussion.
One area for improvement would be allowing slightly more time for discussing alternative approaches and testing edge cases. Overall, I appreciated the experience and the opportunity to interview with the team.
The interview was really good
All rounds where proper
Coding round needs coder pad and really good
It was really good as they do seem to care about interview and i had a great time discussing with the interviewer.
My interview process started with a coding round focused on data structures and problem-solving, where I was able to understand the problem and write a working approach but struggled with optimizing the solution under time pressure. What went well was my ability to implement a correct baseline solution and explain my thought process, but I didn’t perform as well on edge cases and optimal complexity, which likely impacted the final outcome.
The interview was quite smooth. All of the interviewers asked their direct questions with no further small talk.
Software Engineer
Software Engineer
