Hello Everyone, 

Ever since I posted about my offer with Amazon, I have been asked a LOT about the interview process and how to prepare. So, I thought I could post a comprehensive guide for the process. Please be advised that I will not be covering the basics of leadership principles, STAR format and loop interview process in this post. This is a more in depth post about the actual process and some nuances that are not available online. 

1. HR Phone Screen: This is the first round of the interview process with an Amazon recruiter on call. The recruiter will mostly ask basic questions about your resume and experience and pass you on to the next round if they think you are a good fit. I had two different experiences in this round. For the position I got hired for, the recruiter said I don’t need to do the HR phone screen since she thought I was a good fit already. In another instance, I had the HR phone screen but the recruiter ghosted me. So it is hit or miss. On paper, Amazon has a 48-hour response time promise for this round. 

2. Technical Phone Screen: I got a little lucky in this round because the interviewer was informed late and she asked questions from the top of her head. Even then, it was really technical, asking about my workflows, thought processes and experience with various software. I have been told horror stories of intense technical grilling, especially by SDE roles. So I would highly suggest preparing well. I used ChatGPT for this purpose. Some of my prompts were:

   1. I am interviewing for <job posting link> with <interviewer linkedin link> on a technical phone screen. What kind of questions can I expect?

   2. I am interviewing for <job posting link> with <interviewer linkedin link> on a technical phone screen. <job description line> is a core responsibility. What kind of questions can I expect? On paper, Amazon has a 48-hour response time promise for this round.

3. Recruiter Counselling Call: If you pass the technical phone screen, the recruiter will schedule what I call as a counselling call with you. They will discuss the loop structure, STAR format and leadership principles (LPS). There is a good chance they might tell you what leadership principles (out of Amazon’s 14) and technical competencies (TCs) will be needed for this role. 

4. The Loop: Amazon loop interview is basically a panel 4-6 interviewers with each one given an hour to test you on LPs and TCs associated with the role. The hiring manager assigns LPs & TCs to each interviewer to test your abilities. Here is a typical amazon interview panel:

   1. Hiring Manager

   2. Bar Raiser: From a completely different team, has veto power to overturn the panel’s hiring decision

   3. Cross-Functional Stakeholder

   4. Teammates/Peers

   5. Management Personnel

This is how I would prepare for my loop if I were to do it all over again, assuming I am confident about the job description expectations. My prompts to ChatGPT were:I am interviewing for the role of <job posting link> with Amazon. <linkedin profile link> is a loop interviewer. What kind of questions can I expect?

I am interviewing for the role of <job posting link> with Amazon. The LPs & TCs associated are _____. What questions can I expect?

Get creative with prompts. Use multiple AI agents. It’s all worth it, the more the better. Amazon expects all answers in STAR format unless specifically said “scenario based question”. STAR is basically a Situation-Task-Action-Result format. The time I recommend for each answer is 6-10 minutes, with a 20-20-40-20 split. Amazon has a 5-day response time promise for this round and I heard back on day 4. 

Personal Advise:

1. Make at least 15-20 STAR format stories. Match LPs to stories, not the other way around. One story can be associated with multiple LPs. 

2. I recommend not repeating stories within the loop BUT I did repeat two stories twice and I was okay. 

3. Don’t be nervous, but at the same time don’t make small talk unless reciprocated. Interviewers are very formal and serious at Amazon. They are trained to do so. 

4. Carry a single page notes sheet with summary of all stories. 

5. Use as many numbers as possible. 

6. Ask ChatGPT to review, rate and polish all your STAR format answers. Repeat this for every answer until ChatGPT rates it 4.5 or above.

How many questions and what type of questions the hiring manager usually ask for the vendor manager role ?

Whats up everyone, I just accepted a non-tech role at Amazon and thought it’d be helpful to share my experience with the interview process. Hopefully this helps anyone currently preparing or thinking about applying.

⸻

Prepare, Prepare, Prepare

Your recruiter should give you guidance on which Leadership Principles (LPs) to focus on, and this is the foundation of your prep. Make sure you build out multiple stories for each LP, and format them using STAR (Situation, Task, Action, Result). This structure is huge because the interviewers are specifically trained to listen for it. I also recommend looking up the Amazon interview question banks online, you’ll find plenty of examples that mirror the types of questions you’ll get.

⸻

Reusing Stories is Okay

One thing I want to clear up is the idea that you should never reuse stories. In my experience, that’s not true. I reused one of my stories three different times because it demonstrated three different LPs. As long as the story connects with the question being asked and aligns with the LP they’re evaluating, you’ll be fine. The only time it backfires is if the story doesn’t really fit the question or show the principle they’re looking for.

⸻

Know Your Story Inside and Out

When you answer, be prepared for follow-ups. Amazon interviewers are going to drill down into your story even if you’ve already given them a lot of detail. They want to see how you think and how you respond when pushed for more information. So, know your examples in and out, and be ready to explain them from multiple angles. A big part of this is being able to tie your answers back to the LPs in different ways, it shows depth and consistency.

⸻

Relax (Seriously)

I went into the process super nervous because of all the stories I had heard about how tough Amazon interviews are. Honestly, once I got through the first one, I realized the interviewers are just normal people. You can laugh, smile, and have a natural conversation with them. It’s not some robotic interrogation. That realization helped me relax and give more genuine answers, which I think made a big difference.

⸻

Overall Thoughts

The process was definitely long, but I actually found it kind of enjoyable. My recruiter and schedulers were very organized and kept me in the loop about what to expect and how to prepare. My interviewers all had different personalities and leadership styles, which gave me a really interesting perspective on the company.

Hope this helps anyone prepping right now,best of luck!

I applied for an Amazon position in Seattle and today got two emails, one asking me to schedule a phone interview and another asking me to schedule a call with a recruiter before scheduling a phone interview. Is this normal? What should I expect from the recruiter call? I’m not a strong interviewer but I want this job (over 200 applications since September and this is only my second interview request) so this has me super nervous, any advice is appreciated!

edit/update: The recruiter call was a LOT of info about the job, and some helpful tips about the interview, what they’re looking for. The first virtual interview included a LOT of questions about times I’d failed, assuming they wanted what I learned from it. I apparently succeeded, as I’ve now been invited to the final round which includes a call with a different recruiter and then a ‘virtual onsite’ with 3-4 interviews in one day

I am an SDE at Amazon and have done dozens of interviews, and it’s actually insane how few people ask enough clarifying questions about their coding problem.

I mean literally 1/20 candidates ask good enough questions at the start so that they don’t need to go back and change something later on.

Please ask more questions like:

• Does case sensitivity matter?

• What is the allowed list of characters?

• Will special characters affect input? Eg if working with strings is “cat, dog, frog” considered the same as “cat dog frog”

• etc etc

This small thing is actually costing some of you guys the job.

Also, please do not DM me asking for tips or resume feedback.

Hi All,

I have an upcoming interview at Amazon, and I've been researching the structure and expectations of the loop round. I understand it will primarily focus on Amazon's leadership principles.

I have a couple of questions:

1. What is the ideal length of time to structure an answer using the STAR format ?

2. Is it recommended that notes or memos be included for answers during the interview?

I would appreciate any insights or advice you could share.

Edit - The role is a Business analyst role (Non tech)

Long story short. Had an initial call for 1 hour, then 5, 1 hour interviews each on behavioural questions. Answered them to the best of my ability using their BS star method and then once the rejection call came in it’s just a few seconds. No feedback whatsoever. I’m so pissed they let it go this long rather than giving an initial response. Bunch of idiots!

ROUND 1 (30min LP + 30min coding + 2min questions)
The interviewer informed me that this round would consist of two parts: the first half would focus on Leadership Principles (LP), and the second half would be a coding challenge. The LP round went well, and soon, I moved on to the coding part. The problem was similar to detecting a cycle in a graph. I began by explaining my approach, thinking out loud. To my surprise, the interviewer asked me to code the entire solution first and review it later. This caught me off guard, and for a moment, I felt unsettled. When I finally started coding, my mind went blank. However, I decided to take small steps and began coding the parts I was confident about. Gradually, I managed to piece together an almost correct solution. Next, I started the dry run. After testing the code with basic cases, I was convinced it was correct. But then, the interviewer introduced a test case that was completely unexpected—and my solution failed.

At that point, I thought I had bombed the interview. Time was running out, and I was feeling the pressure. Suddenly, it struck me that removing a specific if condition would make my code handle the edge case the interviewer had mentioned.(I was considering undirected graph instead of directed graph). I quickly implemented the fix and explained my reasoning just as the time ran out. I left the interview feeling uncertain. I was able to code a working solution, but there was still a lingering doubt in my mind if I had done everything correctly. Overall the interviewer was good.

ROUND 2 (28min LP + 31min coding + 3min questions) (Probably Bar-Raiser)
This round followed immediately after the previous one, with the same format. However, this time the LP (Leadership Principles) questions were very challenging. The interviewer delved deeply into the details of each situation—so much so that, at one point, even I couldn’t remember what I had done! To prepare for the LP section, I had revisited stories from my past experiences. I didn’t want to risk creating fake stories, as I’m not good at that. The interviewer maintained a completely neutral expression throughout, which added to the stress. As if that wasn’t enough, the noise cancellation on my earbuds suddenly turned off, signalling that the battery was low. I quickly switched to speaker mode mid-conversation. At one point, the interviewer even mentioned that he couldn’t understand what I was trying to convey—another moment where I felt like I was bombing the interview.

Somehow, I managed to get through all the LP questions and finally moved on to the coding portion. By this time, I was already feeling a bit nervous. When the problem was presented, it was a bit different from any standard LeetCode problem I had seen. The question had two parts, and the interviewer instructed me to solve the first part first. I tackled it, did a dry run, and explained why it could be represented as a recursion problem.

With 10 minutes left on the clock, the interviewer asked me to solve the more complex part of the problem. It took me a few moments to come up with a solution. While thinking aloud, I explained my thought process to the interviewer. After some back-and-forth discussion, I finally arrived at the correct solution and performed a quick dry run—with just one minute to spare! The interviewer seemed satisfied with my solution.

At the end of the interview, I asked about their work. For the first time, I saw him smiling. I also asked a specific question about one of the AWS services, which led to good discussion for next 5 minutes. I think I nailed the technical part in this one. Overall, the interviewer seemed to be very experienced and he could put anyone in stress during interview.

ROUND 3 (18min LP + 40min Coding + 3min questions)
By this time, I was feeling nervous but still confident as last technical was good. Next interviewer was very friendly. He actually eased all the stress I had from the previous round. The LP (Leadership Principles) part was relatively straightforward and took about 18 minutes to complete. He seem to have like some of the experience I shared.

This was the Low-Level Design (LLD) round for the coding part, and the question I received was very similar to design a Hotel Management System or LRU cache with two specific methods to implement(add and remove). I asked few questions to get idea of how much complexity I need to handle. I started with a naive approach, using a list for the implementation. Then, I explained how adding a cache (using a hashmap) could reduce the remove operation's time complexity to O(1).

Gradually, I refined the solution to achieve O(1) complexity for both required features by incorporating a Doubly Linked List. At this stage, I had implemented only the necessary classes, planning to add methods as needed. I was writing code in python so for every class I would write pass keyword. Sometimes I add a class I would need but immediately decide to remove it. Basically, I was talking to myself out loud. I also justified my choice for eg why Doubly Linked List over a Singly Linked List.

While coding, I mentioned alternative approaches I might consider in the future. The interview initially told me to keep the design simple, but still seem to like that I am thinking it from reusability and scalability perspective. For instance, designing these classes in a way that they wouldn't depend on any specific data structure by applying strategy design pattern. Although I didn’t implement this during the interview, I thoroughly explained the idea.

When I finished, the interviewer remarked that my explanation and design choices was quite good. Finally, when asked if I had any questions, I inquired about the work he is doing at Amazon. Overall, the interview was very friendly. It felt like it was discussion rather than an interview.

FINAL THOUGHTS
I’m currently waiting for the results. In my opinion, the interview went well, apart from a few hiccups. I promise to share more about my background and how I prepared for the interview(I have did months of grinding). I won’t be sharing the exact questions due to their policy against doing so(I don't want to risk it, this is very few option I have). However, I can say that the questions were fairly standard. I feel lucky not to have any twisted questions in LP and for coding. 

My final advice: practice for interviews, especially for situations where you might be asked unexpected, out-of-the-blue questions. Even if the questions are simple, you could mess up due to pressure.

OPTIONAL TO READ
Being an international student makes this even more challenging. For me, Amazon is one of the very few options(I know outcomes of FAANG can be based a lot on luck and can lead to misery when you put so much grinding into it. But right now I am betting everything on "hope"). Many other companies rejected me because they were seeking candidates with 4+ years of experience for a new grad role.(This was reason for one of rejection I had after an amazing interview). The current job market is tough, I want to get free of this loop and actually work on some of the ideas I have in technology. I’ve learned so much from this community, which is why I decided to write this detailed post—to hopefully help at least one person who is in a situation similar to mine.

Edit 1 : Got the offer from Amazon and accepted it !!

Edit 2 : Detailed preparation
https://www.reddit.com/r/leetcode/comments/1h5d3bc/a_detailed_guide_on_how_i_prepared_for_an/

I have been preparing dsa for a while now and i am not sure what is the difficulty level going on now a days, leetcode’s company wise questions is only for premium which is really expensive for me. I can get referral and pretty sure that i can get an interview scheduled, i am just afraid that I ain’t prepared well enough.

Thank you all in advance.

How did you feel about your preparation? Were you highly confident?

Lots of companies are emulating the Amazon way of having leadership principles and every interview needs the interviewee to regurgitate leadership principles as though they have implemented these principles right from popping out of the womb.

Isn't an interview supposed to be where the prospect can be creative, authentic, discuss new ideas and bring fresh perspectives to a role or a company?

I don't understand why the interview process has become so mechanical, give an answer exactly what they want to hear, often needing to manufacture answers to game the system.

I'm so sick of these cookie cutter interview questions.

Did you guys ever land on an Amazon interview, What was it like?

I have heard that it's purely luck many a times.

Just completed my final loop interview today and was in for quite a surprise. Prior to the interview, of course I did my due diligence and researched all that I could about the loop and read about others experiences. I was quite surprised that many parts of my loop differed from the experiences and advice found online so I thought I’d share my experience in case it would help others:

1. I was told that each interviewer would be assigned two LPs And ask you a question or two for each LP. Because of this I prepared about two stories format for each LP. However, many of my interviewers asked me 3, 4, even 5 questions! I was nowhere near prepared with that many stories for each LP.

2. I also read on here that we were not supposed to reuse a story that was already shared in the previous phone screens however, this turned out to not be accurate either according to my recruiter. I explicitly asked him if that was OK and if anyone from the loop would have access or see my phone screen answers. He told me the loop interviewers do not look at notes from the phone screen, and that it would be fine to tell those stories again in the loop. Not sure if this was just my situation or if it changes depending on the interview.

3. Another thing I see here a lot is that people claim that you only get a call after the loop if there’s good news. Some people say that they don’t hear back until the fifth day and that’s when the recruiter sends a calendar invite for a phone call to touch base. However, this was also different for me. My recruiter told me in the very beginning what day they would be debriefing and making a decision. He also explained that he would call me immediately after.

Overall I felt that my recruiter was a little… all over the place and it threw me off a bit.

Anyway the loop was probably one of the hardest interviews I’ve ever done in my life. I hope this could help or provide another perspective to anyone that’s about to go through it. Good luck!

Hey guy, in 2 days is my interview at Amazon but I don’t speak English i mean i speak English but no very well like fluent and I need some advice to pass my interview like the questions, what they do in pre hire some like that , i write that without translate lol, I appreciate it yall

Hi All,

I have an upcoming interview loop for a technical role at Amazon. I have been reading through the principles as it seems to be the most important driving factor in the interview.

Here are my few doubts regarding answering them:

1. Does the answer to the leadership principle have to be related to the experience of my technical role before or it could be any story from my college, part time work etc?

2. I have written down a few stories which can tick multiple leadership principles and I can highlight if any questions arise from those areas. Will this work?

3. How to not run out of stories since these questions might be repeated across the rounds?

4. Does it always have to be a success story or achieving something great?

5. How do I identify which leadership principle is the question related to and what will happen if I answer to it which somehow relates to other principles apart from intended question?

Please help as I have an the interview loop next week and I'm going crazy over thinking the answers to these questions.

Update: They ghosted me after the interview loops