Amazon Leadership PrinciplesSignal: "I noticed" -> "scaled to multiple teams" -> "saved $X/week" -> "managed trade-offs"

Tell Me About a Time You Scaled a Solution Far Beyond Its Original Scope - Amazon LP Competency

Proactively scaled solutions beyond original scope with measurable impact

Choose your preparation mode3 modes available

Competency STAR Evaluate

📌

Definition

Think Big at Amazon means identifying opportunities to expand a solution’s impact far beyond its initial scope, often without explicit direction. The core test is whether the candidate proactively envisions and executes on a broader, scalable outcome that benefits multiple teams or customers.

⚡

Core Signal

Did the candidate independently identify and deliver a solution that scaled significantly beyond the original problem or team?

🏢

Company Framing

Amazon expects Think Big to manifest as owner-driven expansion of impact, fixing root causes and enabling future growth, not just patching symptoms or doing what was asked.

🚫

What It Is NOT

Completing assigned tasks well - that is execution, not Think Big
Incremental improvements limited to your immediate team or sprint
Waiting for permission or a ticket before acting
Focusing only on short-term fixes without considering long-term scale
Confusing volume of work done with strategic impact

✅

Candidate explicitly states they noticed a problem outside their team or sprint with no prior assignment.

"I noticed""wasn't on my sprint""nobody had flagged it"

Shows self-initiated awareness beyond immediate responsibilities, a prerequisite for Think Big.

Common Miss My manager mentioned it might be worth looking into

✅

Candidate describes expanding the solution to multiple teams or customers beyond the original scope.

"scaled to""rolled out across""impacted multiple teams"

Demonstrates the candidate’s ability to envision and execute broad impact, not just local fixes.

Common Miss We fixed it for our team only

✅

Candidate quantifies the impact in business terms, such as cost savings or customer experience improvements.

"saved $X per week""reduced latency by Y%""improved customer satisfaction"

Amazon values measurable outcomes that translate technical work into business impact.

Common Miss It made things better

✅

Candidate explains trade-offs and risks they managed when scaling the solution.

"I weighed the cost of delay""managed risk by""decided to prioritize"

Shows mature thinking about long-term consequences and decision-making under uncertainty.

Common Miss I just did it without thinking about trade-offs

✅

Candidate describes how they influenced others or collaborated cross-functionally to enable scaling.

"I convinced""partnered with""aligned stakeholders"

Scaling often requires influence beyond direct authority, a key Amazon leadership behavior.

Common Miss They helped me fix it

✅

Candidate uses first-person singular consistently to highlight their individual contribution.

"I designed""I implemented""I proposed"

Distinguishes personal ownership from team or manager-driven work.

Common Miss We did it

💡

Depth Tip

Action section = 70% of your answer. Situation+Task combined = 50 seconds max. Focus on 3+ sentences starting with 'I' describing your specific steps to scale the solution.

❌ Manager-Assigned Initiation

"My manager suggested I look into this since I had bandwidth"

Ownership is binary - self-initiated or not. Manager-assigned = execution. No excellent execution recovers an assigned story.

DetectionAsk: Would I have done this if my manager said nothing? If no, find a different story.

FixI noticed X while doing Y. Nobody had filed a ticket. I decided to act because...

❌ Team-Only Scope

"This was a bug only in my team's codebase and I fixed it quickly"

Think Big requires scaling beyond your immediate team. Single-team fixes show execution, not big thinking.

DetectionCheck if the impact or scope extends beyond your team or project.

FixI identified a root cause affecting multiple teams and proposed a cross-team solution.

❌ No Quantified Impact

"It made things better"

Without measurable impact, the story lacks evidence of meaningful scale or business value.

DetectionAsk: How much did this improve the system or business? What metrics changed?

FixI reduced error rates by 30%, saving $10K weekly in support costs.

❌ Passive Language / Team Credit

"We did it"

Obscures individual ownership and contribution, critical for Amazon evaluation.

DetectionListen for first-person singular actions versus collective pronouns.

FixI designed and implemented the core algorithm that enabled scaling.

❌ Short-Term Fix Only

"I patched the bug quickly to unblock the team"

Think Big requires long-term scalable solutions, not quick patches.

DetectionCheck if the candidate mentions root cause or future-proofing.

FixI redesigned the system component to prevent recurrence and enable future growth.

🚩 Passive Voice Throughout

"The problem was identified"

Candidate was spectator not actor. Passive strips agency from every action.

FixUse active voice: 'I identified the problem.'

🚩 Overuse of 'We' or 'Team'

"We implemented the solution"

Obscures individual contribution, making it impossible to assess ownership.

FixReplace with 'I' statements describing your role.

🚩 Vague Impact Statements

"It improved performance"

Fails to demonstrate measurable business or technical impact.

FixQuantify impact: 'It improved performance by 25%, reducing latency by 100ms.'

🚩 No Clear Scaling Beyond Original Scope

"I fixed the bug in my module"

Shows execution, not Think Big. No evidence of broader impact.

FixDescribe how the fix was extended or generalized to multiple teams or products.

🚩 Story Too Short or Surface-Level

"I just did it quickly"

Lacks depth and detail needed to evaluate ownership and impact.

FixProvide detailed steps, decisions, and quantified results.

🎯

Direct Triggers

Tell me about a time you scaled a solution far beyond its original scope
Describe a situation where you thought big and expanded the impact of your work
Give an example of when you identified an opportunity to improve a process across teams
Have you ever taken a small idea and turned it into a large-scale solution?

🔍

Indirect Triggers

Tell me about a time you went beyond your job description
Describe a project where you influenced multiple teams
Give an example of when you proactively solved a problem no one asked you to
Have you ever improved a system or process that affected many customers?

👁

How to Recognize

Keywords: without being asked, beyond your role, proactively, scaled, multiple teams, broad impact, long-term solution, measurable results.

⚠️

Do Not Confuse With

OwnershipOwnership is about self-initiating and owning end-to-end; Think Big requires expanding impact beyond original scope.

Deliver ResultsDeliver Results focuses on meeting committed goals under pressure; Think Big is about envisioning and executing broader impact without explicit assignment.

Bias for ActionBias for Action emphasizes speed and decisiveness; Think Big emphasizes scope and scale of impact.

❓

How did you identify that this problem could be scaled beyond your team?

Probes: Candidate’s ability to recognize broader opportunities and think strategically.

❌ Weak

I just realized it was a bigger problem after talking to my manager.

Shows reactive behavior and manager-driven insight, not proactive big thinking.

✅ Strong

While fixing the issue in my team, I analyzed logs and found similar errors in other teams’ services, so I proposed a cross-team solution.

""I proactively analyzed data beyond my team to identify a larger opportunity.""

❓

What trade-offs did you consider when scaling this solution?

Probes: Candidate’s judgment and risk management in expanding scope.

❌ Weak

I didn’t think much about trade-offs; I just wanted to fix it fast.

Lack of thoughtful decision-making undermines credibility for Think Big.

✅ Strong

I balanced the cost of delaying other sprint items against the long-term savings from scaling, deciding the upfront investment was justified.

""I explicitly weighed cost of delay against long-term impact before acting.""

❓

How did you get buy-in from other teams or stakeholders?

Probes: Candidate’s influence and collaboration skills critical for scaling solutions.

❌ Weak

I told them about the problem and they agreed to help.

Passive handoff, no evidence of active persuasion or leadership.

✅ Strong

I prepared a data-driven presentation showing impact and risks, then worked closely with tech leads to align priorities and integrate the solution.

""I led cross-team alignment by presenting clear data and collaborating closely.""

❓

What was the measurable impact of scaling this solution?

Probes: Candidate’s ability to quantify and translate technical work into business value.

❌ Weak

It improved things and made the system more stable.

Vague impact fails to convince interviewer of meaningful scale.

✅ Strong

The solution reduced error rates by 40%, saving $15K weekly in support costs and improving customer satisfaction scores by 10%.

""I delivered a 40% error reduction translating to $15K weekly savings.""

Amazon

Think Big

Amazon looks for long-term thinking - fix root cause not just symptom. Candidates must show owner mindset expanding impact across teams and time.

Signal: I also proposed adding X to prevent this class of problem in future services.

Example QTell me about a time you scaled a solution far beyond its original scope.

What Elevates

Name the trade-off explicitly: I pushed sprint item back 2 days. Cost of inaction ($8K/week) exceeded cost of delay. Amazon credits candidates who articulate the trade-off explicitly and show ownership of long-term impact.

Google

Think Big

Google values moonshot thinking and technical innovation that can impact billions. Emphasize novel approaches and technical depth in scaling.

Signal: I designed a new algorithm that reduced complexity from O(n^2) to O(n log n), enabling global scale.

Example QDescribe a project where you scaled a system to handle massive user growth.

What Elevates

Highlight technical innovation and scalability, showing how your solution enabled exponential growth and improved user experience at scale.