This is the first article of our guide to preparing for a Software Development Engineer (SDE) interview with Amazon.
- Prepare for Amazon behavioral interview questions
- 9 Amazon behavioral interview tips
- 10+ Amazon coding interview tips
- Amazon coding interview questions
Preparing for the Amazon behavioral interview questions may seem intimidating and overwhelming at first.
Behavioral questions, what does it even mean? Where should a candidate start? How to cover a variety of questions? In this article, we will go over a simple technic to facilitate the preparation for the behavioral questions.
When you are ready, you can request a mock interview led by one of our Software Engineers on mocki.co.
Amazon behavioral questions
A Googler I recently interviewed through mocki.co took offense at the Behavioral Questions I asked. Arguing that it wasn’t how he had been interviewed in the past. That it was too long and left too little time for the coding question itself.
The idea behind the success of behavioral questions is that a candidate’s past performance is a good indicator of his or her future performance. Amazonians don’t skim over those questions.
Amazon’s Leadership Principles
Amazon has **publicly*- published its Leadership Principles. It’s a very good opportunity for you as a candidate to get prepared for your interviews. Let’s understand how.
What are the Leadership Principles?
Leadership Principles (LP) are values or common traits that you can find in people working at Amazon (Amazonians). As a candidate, you have to demonstrate those Leadership Principles, LPs.
How to prepare for the Amazon behavioral questions?
Try to come up with a list of stories where you demonstrated those Leadership Principles. Then dress a list of possible follow-up questions an interviewer may ask. Be prepared to talk about a story in detail (technically or not).
Follow the STAR approach. The STAR approach helps you to structure your answer. It helps give the context (Situation) and clearly identify what was asked from you (Task), what you end up doing (Action) and what the outcome was (Result).
Organize everything in stories.
Assuming we are working on the following Leadership Principle: Customer Obsession.
Come up with a good story where you demonstrated that you were customer-obsessed? Where you went above and beyond for customers? What did you do? What was the result? Did you receive feedback from your customers? How?
Prepare 10-15 good stories total, across the Leadership Principles. You will be able to reuse some stories for multiple LPs.
Stories that can easily be reused for multiple Leadership Principles include:
- An interesting technical problem you solved.
- An interpersonal conflict you overcame.
- A time where you demonstrated leadership or ownership.
- A situation where you should have done differently in a past project.
- Do you fix things that aren’t quite right, even if you don’t have to?
- Be creative!
You can organize everything in rows and columns. The nugget is just a very brief description of the story.
Example of story
- Silverlight – reduced the size app of 35%.
- Situation / Task:
- Customers Worldwide
- Complaints app is slow to load.
- Datacenter in one single EU country only.
- No CDN.
- Up to 5 minutes to load (from India for instance).
- Build a script to remove duplicated dependencies from the final package. Integrated script into our pipeline for automation.
- POC to improve our dependency management and dependency graph.
- Reduced the size of the application by 35%.
- Better UX. Lighter and faster to load.
- Fewer complaints from customers.
- Customer Obsession, Think Big, Ownership, Invent and Simplify, Learn and Be Curious and Insist on the Highest Standards.
Not too many stories
A candidate I interviewed on mocki.co shared with me the stories he had prepared for Amazon’s behavioral questions. A long-winded document including several **distinct*- stories per Leadership Principle. While answering the behavior question during the mock interview, he struggled to remember the stories. This is because he had prepared **too many stories**.
As recommended in this best seller book, organize your stories with nuggets. As stated earlier, a nugget is just a very brief description of the story, easy to trigger through visual memory of your notes.
Also, check out this other article about Amazon Behavioral Questions tips.
If you want to have a dry-run at an Amazon behavioral interview, take a mock interview led by an SDE from Amazon at mocki.co.
Some elements of the methodology described in this article come from Cracking the Coding Interview.