We use our Leadership Principles every day. They are crucial to discussing ideas for new projects and to deciding the best ways to solve problems. They're just one of the things that makes us peculiar. All candidates are evaluated based on these principles. The best way to prepare for your interview is to consider how you’ve applied them in your past.

Leadership Principles

Our interviews are rooted in behavioral-based questions. We'll ask about past situations or challenges you’ve faced, using our principles to guide our discussion. We avoid brain teasers (for example, “How many windows are in Manhattan?”). We've found this approach is unreliable when it comes to predicting success.

Here are examples of questions:

• Tell me about a time when you were faced with a problem that had a number of possible solutions. What was the problem and how did you decide what to do? What was the outcome?
• When did you take a risk, make a mistake, or fail? How did you respond? How did you grow from it?
• Describe a time you took the lead on a project.
• What did you do when you needed to motivate a group or promote collaboration on a project?
• How have you used data to develop a strategy?

Keep in mind that we are data-driven. Ensure your answers are well-structured. Provide examples using metrics or data if applicable. Reference recent situations when possible.

The STAR method is a structured manner of responding to a behavioral-based interview question. Here’s what it looks like:

SITUATION

Describe the situation you were in, or the task you needed to do. Give enough detail for the interviewer to understand the complexities of the situation. This example can be from a previous job, school project, volunteer activity, or other relevant event.

TASK

Describe your goal.

ACTION

Describe the actions you took. Use an appropriate amount of detail. What steps did you take? What was your contribution? Let us know what you did, not what your team or group did. Use the word ‘I,’ not ‘we.’

RESULT

Describe the outcome of your actions. Don’t be shy about taking credit for what you did. What happened? How did it end? What did you accomplish? What did you learn? Provide examples using metrics or data if applicable.

Consider your successes and failures in relation to the Leadership Principles. Use examples that showcase your expertise and how you’ve taken risks, succeeded, failed, and grown. Keep in mind that some of our most successful programs have risen from the ashes of failed projects. Failure is a necessary part of innovation. We believe in failing early and persevering until we get it right.

• Practice using the STAR method. Frame your examples in relation to the Leadership Principles.

• Ensure each answer has a beginning, middle, and end. Describe the situation or problem, the actions you took, and the outcome.

• Prepare short descriptions of a handful of situations. Be ready to answer follow-up questions in greater detail. Select examples that highlight your unique skills.

• Have examples that showcase your experience and how you’ve taken risks, succeeded, failed, and grown.

• Specifics are key. Avoid generalizations. Give a detailed account of one situation for each question you answer. Use data or metrics to support your example.

• Be forthcoming. Don't embellish or omit parts of the story.

   

• Interview prep for tech roles (for example, software development and machine learning) can be found here.
• Unsure if you're interviewing for a technical role? Ask your recruiting point of contact.

• Be prepared to explain what interests you about the role and the team (or teams) you’ll be meeting with.
• Be concise but detailed in your answers. We know it’s hard to gauge how much info is too much versus not enough. A good test is to pause after your answer to ask if you’ve given enough detail or if the interviewer would like you to go into more depth.
• If you’re asked a question but aren't given enough info to provide a solid answer, don’t be shy about asking for clarification. If additional context isn't available, focus on how you'd attempt to solve the problem based on limited information.
• For some roles, we may ask you to provide a writing sample. Why? We don’t make slide-oriented presentations. Instead, we write narrative memos. We silently read them at the beginning of some meetings. These papers range from one to six pages and explain a project goal, steps, and outcomes. Given this aspect of our culture, and the impact these papers have on our decisions, it’s important to be able to express your thoughts in writing.
• We try to leave a few minutes at the end of each interview to answer your questions. If we don’t get to all of them, don’t hesitate to ask your point of contact.

• Check in: Arrive 15 minutes early and check in for your interview. Have your government-issued photo ID ready (for example, your driver’s license or passport).
• Location: You'll receive instructions via email. Some of our offices are dog-friendly. Let us know if you need an accommodation or have allergies.
• Dress code: Comfortable and casual. While some roles in our fulfillment centers may require certain clothing for safety reasons (such as closed-toed shoes), in most of our offices people wear everyday clothes. We're interested in what you have to say, not what you’re wearing.
• What to expect: Interviews will be a mixture of questions and discussions about your experience. Be ready with detailed examples. Concise, structured answers are best.
• Interviewers: Depending on the role, you'll meet with two to seven people. They'll likely be managers, team members, stakeholders from related teams, and a Bar Raiser (usually a person from another team). All interviewers will assess your potential for growth beyond the position you’re interviewing for. They'll evaluate how well your background and skills meet core competencies, along with how they relate to our Leadership Principles. We recommend approaching each interviewer the same way, rather than tailoring answers to their role. Interviewers will often take notes on their laptops. It’s important that they have precise notes from their time with you to share with one another.
• Resume or CV: Interviewers will have a copy, but feel free to bring one as well.
• Duration: Each session usually lasts between 45 minutes and an hour.
• Lunch: We’ll provide lunch if your interview is scheduled during the lunch hour. Let your point of contact or your lunch buddy know if you have dietary preferences.
• Technical roles: If you're interviewing for a technical role, be prepared to white board.
• Remote interviews: If you've been asked to do a remote interview, you'll likely need to download Amazon Chime, our tool for video conferencing (step-by-step guide here). If you're presenting, you'll need to download Chime to your desktop. The meeting ID will be emailed to you by your recruiting point of contact. For the best sound quality, use a headset with a microphone.

• Some teams use role-specific exercises or online assessments as part of the interview. You’ll be told if the job you’re interviewing for requires one of these.
• Confirm or book arrangements if your interview requires travel. We’ll set up your travel or put you in touch with our travel agency to help you coordinate details.
• Submit your expense reports after your visit. We’ll provide details on where and how to do this. Fill in your form clearly and ensure scanned receipts are legible. This will help prevent reimbursement delays.
• If you need an accommodation, or have questions or concerns, please get in touch. We ensure reasonable accommodations for everyone.
• After your interview, you should expect a brief survey via email. It’s important for us to know how we did so we can improve.
• Expect to hear back from us within five business days of your interview. If you don't, feel free to give us a nudge.