0 day streak

BEHAVIORAL · BIG IMPACT AND LONG-TERM THINKING

Tell me about the most ambitious project you have proposed: sample answer

Whether you can see past the next sprint, propose something with a larger or longer payoff, and make a convincing case for it while still delivering value along the way. Big ideas without a plan or results score poorly.

Also asked as

  • Tell me about a time you made a decision that hurt in the short term but helped in the long term.
  • Describe an idea of yours that the team adopted.
  • Describe a project that needed several teams. How did you get them aligned?
  • Tell me about the most ambitious project you have proposed.
  • Describe a time you considered the wider effect of your work on users or society.

The short version: Show you thought beyond the next sprint and made a bet with a long payoff.

Sample STAR answer

An invented example from typical software engineering work, about 250 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation Every team in our organisation sent analytics events in its own format. Each new report needed an engineer to write custom parsing code, and data analysts spent about a day a week cleaning events before they could use them.

Task I was asked to fix the parsing for one new report. I thought the real fix was a shared event format for the whole organisation, which no single team owned.

Action I did the one report as asked, then wrote a two-page proposal for a shared event schema with a small registry: teams would describe each event once, and invalid events would be flagged as they arrived. I estimated the cost honestly at two quarters of part-time work across teams, and showed the payoff using the analysts' own time logs. To make it less of a leap, I proposed starting with the three teams that sent the most events and keeping the old formats working in parallel. I got agreement from the analytics lead and two engineering managers, then built the registry and validation with one other engineer. I paired with each of the first three teams for their migration and wrote a guide so later teams could move on their own.

Result After two quarters, nine of twelve teams had moved over. New reports went from about a week of engineering work to a day, and analysts got back most of the day a week they spent cleaning data. Invalid events were caught in minutes instead of being found weeks later in reports.

Weak answer vs strong answer

Weak

"I always think big. I proposed rebuilding our whole data platform using the latest technology, which would make everything much better in the future."

Why it scores low: Big for its own sake, with no problem, no cost, no plan to reduce risk and no result. Interviewers want ambition backed by a case and delivery, not a wish list.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show you thought beyond the next sprint and made a bet with a long payoff.

How the story changes with level

SDE 1

At SDE 1, "big" can mean improving something beyond your ticket, like a reusable library instead of a one-off fix. Show you saw the larger pattern.

Senior and staff

At senior or staff level, the idea should span teams or quarters, and you should show the proposal, the people you convinced, the staged plan and the measured payoff.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. How did you convince people to invest two quarters?Use their own numbers and offer a small first step.
  2. What did you deliver before the big payoff?Show value early: the first three teams and the original report.
  3. What would have made you stop?Name a signal you agreed in advance, such as adoption after the first quarter.
  4. How did you handle teams that did not want to change?Keep old formats working and let results make the case.

Amazon Leadership Principles that test this

Think Big · Tell me about a time you turned a small task into something much bigger.

Set a bold direction that inspires results, think differently, and look around corners for ways to serve customers.

Situation I built a small tool for my team that replayed a sample of real production requests against a test environment, so we could catch performance problems before release.

Task Other teams kept asking to borrow it. I saw a chance to turn a one-team script into a shared service that could protect every release in our organisation.

Action I wrote a short proposal describing the bigger version: any team could register their service, and every release would automatically be replayed against real traffic patterns with a clear pass or fail. I kept it grounded by listing the three incidents from the past year it would have caught. To prove it, I onboarded two more teams myself over a month while keeping my normal work, and measured what it found. With those results I asked for one more engineer for a quarter, and we built self-service sign-up, privacy filtering of request data and automatic reports.

Result Within two quarters, 22 services used it, and it caught 9 performance problems before they reached users. It became a standard step in our release process.

Tip: Show the bold idea, the proof you gathered before asking for more, and how many people it reached.

Success and Scale Bring Broad Responsibility · Tell me about a time you considered the wider impact of something you built.

Remember that size brings influence; think about the wider effects of your decisions on users, communities and the world, and try to leave things better.

Situation I was building a feature that showed delivery drivers' live location to customers waiting for an order. The first design stored every location update permanently, because it might be useful for analytics later.

Task I was the engineer building the storage. I was uncomfortable keeping a detailed record of where every driver had been, long after it was needed.

Action I raised it with my product manager and our privacy team, framed around the drivers who had not been asked. I asked what the analytics team actually needed. They needed average delivery times by area, not exact routes. I proposed keeping exact locations only while an order was active, plus 24 hours for support questions, then storing only rounded, aggregated data. I also made sure customers stopped seeing a driver's location as soon as the delivery was complete. I wrote the deletion job, a test that proved old data was gone, and a short note explaining the decision for future engineers.

Result We launched with about 95 percent less stored location data, analytics still got everything it needed, and storage costs were lower. The retention rule was later reused for two other location features.

Tip: Show you thought about people affected beyond the immediate user, and turned that into a concrete design choice.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

  • AmazonThink Big · Strive to be Earth's Best Employer · Success and Scale Bring Broad Responsibility
  • MetaFocus on Long-Term Impact · Live in the Future
  • UberDesign & Architecture
  • AirbnbChampion the Mission
  • SnowflakeThink Big
  • CoinbaseMission first
  • ShopifyBuilt around a mission, not a headquarters
  • SalesforceSustainability
  • AdobeCreate the future
  • JPMorgan ChaseA commitment to integrity, fairness and responsibility
  • IBMTrust and personal responsibility in all relationships
  • DeloitteCollaborate for measurable impact
  • Deutsche BankAct responsibly to inspire trust · Think commercially for sustainable outcomes · Work collaboratively for the greatest impact
  • SwiggyThink Big
  • Meesho90% Impact, 50% Time
  • TCSResponsibility
  • WiproBe global and responsible
  • GrowwImpact you can see
  • FreshworksWe are empowered to make an impact
  • OlaBuilding for India scale
  • NykaaSustainability in every action
  • InMobiThink Big

Prepare your own

Write your story in the story bank and tag it "Big impact and long-term thinking"; it will show up against every company value that tests this theme.

Related: Ownership · Invention and simplification · Collaboration and inclusion · Integrity and trust

All behavioral themes · How the behavioral round is scored