general

Amazon Think Big: Meaning, Examples and Interview Questions

Think Big is the Amazon leadership principle about ambition, and it is the one where candidates most often tell the wrong story. They describe the biggest project they were ever on. Interviewers are listening for something different: a moment when the obvious plan was too small, you saw a bigger one, and you did something about it.

It appears in loops at every level, with the bar rising with seniority. A junior engineer can show it by questioning the scope of a ticket. A director is expected to show it by changing the direction of an organization. Either way, the interviewer wants to see the bigger idea, the work of convincing others, and what actually happened.

This guide covers the official wording, what Think Big looks like in practice, examples across roles, the interview questions to prepare for, and a worked STAR answer.

The official wording from Amazon

Thinking small is a self-fulfilling prophecy.

That is the first line of the principle on Amazon's leadership principles page. The rest asks leaders to create and communicate a bold direction that inspires results, to think differently, and to look around corners for ways to serve customers. Three parts, then: a bold direction, communicated so that others follow it, and rooted in the customer rather than in ambition for its own sake. An interview answer that has only the first part is a wish, not Think Big.

What Think Big means in practice

You question the frame before you work inside it. When a ticket says "add a filter," you ask whether the customer problem is really that they cannot find anything.
You set targets that a safe plan cannot hit, and you can explain why the safe plan was the riskier choice.
You communicate the direction in a way people can repeat. If your team cannot say the goal in one sentence, you have not finished thinking big.
You look around corners. You spend some of your time on what the customer will need in two years, not only on this quarter's commitments.
You pair ambition with a first step. The bold direction comes with a cheap experiment that proves or kills it quickly.

Think Big examples at work

A backend engineer and the one-off script. Asked to write a script to backfill one customer's missing invoices, the engineer noticed the same gap would affect every customer on an older plan. He proposed a reconciliation job that ran for all accounts nightly, got two days of scope approved instead of two hours, and the support queue for billing fell by a third over the next quarter.

A product manager and the feature request. Sales wanted an export button so customers could move data into a spreadsheet. The PM interviewed six of the requesting customers and found they were building the same report by hand every Monday. She pitched a scheduled report feature instead, which became the most-used addition that year and closed two enterprise deals that an export button would not have.

A data engineer and the dashboard. A team wanted a dashboard for their own metrics. The data engineer saw that four teams were about to build the same thing on four copies of the same data, proposed a single modeled layer with team views on top, and got the three other leads to co-sponsor it. The shared layer became the company's reporting standard.

A customer service lead and the refund policy. Handling an escalation about a delayed refund, the lead pulled the data and found refunds were the top reason for repeat contacts across the whole site. She proposed an automatic refund for low-value orders under a set of conditions, modeled the fraud exposure with finance, and piloted it in one region before it was rolled out everywhere.

Think Big interview questions

Direct questions

Tell me about a time you took a big risk and it failed. What did you learn? What would you do differently?
Tell me about your proudest professional achievement.
Give me an example of a radical approach to a problem you proposed. What was the problem, why did it need a different way of thinking, and was your approach successful?
How do you drive adoption for your vision or ideas? How do you know how well an idea has been adopted by other teams? Give a specific example.
Tell me about a time you looked at a process that was working well and questioned whether it was still the right one. What assumptions were you questioning, and did you change it?
Describe a time you were working on a project and realized you had the chance to do something far broader than planned.
When was the last time you were dissatisfied because you had not thought big enough?
Tell me about a time one of your ideas had a significant influence beyond your team.

Questions that test it indirectly

What is the most ambitious goal you have set for yourself or your team? What happened?
Tell me about a time you convinced leadership to invest in something they had not asked for.
Describe a time you expanded the scope of a project. How did you decide it was worth it?
Tell me about a time you were told an idea was unrealistic. What did you do next?
Where do you think your current product or team should be in three years? What would it take?
Tell me about a time you chose the smaller plan. Why, and was it right?

A sample STAR answer

Question: describe a time you were working on a project and realized you had the chance to do something far broader than planned.

Situation. I was a software engineer on the notifications team at a subscription company. I was assigned a two-week project to let customers choose which emails they received, because unsubscribe rates were rising.

Task. The ticket was a preferences page. While reading the support tickets behind the request, I found that most complaints were not about which emails people got but about getting the same message by email, push and SMS within minutes of each other.

Action. I wrote a one-page proposal for a different goal: one message per event per customer, delivered on the channel they actually open, with the preferences page as a small part of it. I included numbers from the support data, a rough estimate of the reduction in total sends, and a first step that fit the original two weeks: a de-duplication rule across channels for the three highest-volume events. I took it to my manager and the product lead and asked for the two weeks to be spent on the first step instead of the page. They agreed, on the condition that I ship the preferences page the following sprint.

Result. The de-duplication rule alone cut total sends by roughly a quarter for those events, and unsubscribe rates on them dropped within a month. The broader project was funded for the next two quarters and became the team's main goal. I led the channel-selection piece, and the preferences page shipped on schedule as part of it.

Why this answer works

The bigger idea came from customer evidence, not from a wish to work on something grander.
It includes the convincing: a written proposal, numbers, and a first step that fit the existing budget.
It reports the outcome honestly, including the condition leadership attached and what was delivered.

What the interviewer probes next

Why was the small plan wrong? Be able to argue that shipping the preferences page alone would have left the real problem in place.
What did you give up? The bigger plan delayed the original deliverable by a sprint; say so.
Who disagreed, and how did you win them over? A Think Big story with no resistance usually means the idea was not that big.
What was your role versus the team's? Separate the proposal you wrote from the work others did.
What was the risk, and what was your signal to stop? Interviewers want ambition with a kill criterion, not ambition alone.
What would you do differently? For the example: involve the product lead before writing the proposal, not after.

Common mistakes

Describing the largest project you were on rather than a time you made a plan bigger.
Telling a vision story with no evidence. The customer data is what makes the bold direction credible.
Skipping the communication. If nobody else changed what they were doing, the idea stayed in your head.
Hiding the failure. A big idea that did not work, told honestly with what you learned, is a strong answer to the first question on the list.
Confusing Think Big with scope creep. The bigger plan should have a first step and a reason it serves the customer better, not just more features.
Forgetting the result. Ambition without delivery collides with Deliver Results, and the interviewer will ask.

Related leadership principles

Invent and Simplify is often the shape the bigger idea takes: a different approach, not a larger version of the same one.
Bias for Action supplies the first step: a cheap, reversible experiment that proves the direction.
Customer Obsession is the anchor: the bold direction has to be about the customer, or it is just ambition.

The full list, with questions for every principle, is in the Amazon leadership principles guide.

Pressure-test the proposal half of your story with a coach who has sat on an Amazon loop: get matched. Build it first with the STAR method guide and the story bank guide.