BEHAVIORAL · DOING MORE WITH LESS
Tell me about a time you achieved a lot with very few resources: sample answer
Whether constraints make you inventive rather than stuck: reusing what exists, cutting waste, and still delivering the result. They also check that you did not save money in a way that created hidden costs or risk.
Also asked as
- Tell me about a time you achieved a lot with very few resources.
The short version: Show a result you got with limited people, time or money.
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 Our team's cloud bill for logging had grown about 60 percent in a year, much faster than our traffic. Finance asked every team to cut costs, and there was no budget for a new logging tool or extra people.
Task I volunteered to bring our logging cost down by at least a third within a quarter, alongside my normal work, without losing the logs we needed for debugging and audits.
Action I started by finding where the money went. A one-day analysis showed that four services produced 70 percent of our log volume, and most of it was debug-level messages left on in production and the same error repeated thousands of times a minute during retries. I fixed the cheapest problems first: I turned debug logging off by default with a way to switch it on for one service for an hour, and added sampling so a repeated error was logged once with a count. Then I looked at storage. We kept every log in fast, searchable storage for 90 days, but almost nobody searched past two weeks. With the security team's agreement, I moved logs older than 14 days to cheaper archive storage that could still be restored for audits. Everything used features our existing tools already had.
Result Our logging bill fell by 48 percent in two months with no new tools. Search actually got faster because there was less noise, and during the next incident nobody missed a log. Two other teams used my one-day analysis script to find their own savings.
Weak answer vs strong answer
Weak
"I am very frugal. I always try to avoid unnecessary spending, and on one project I reduced costs by choosing a cheaper server type."
Why it scores low: There is no constraint, no analysis of where the cost came from, no thought about risk and no real result. Picking a cheaper server is a single decision, not resourcefulness.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show a result you got with limited people, time or money.
How the story changes with level
At SDE 1, building something useful by reusing an existing library or service instead of writing a new one, or cutting waste in your own service, is the right size.
At senior or staff level, show savings across several services or teams, a method others reused, and a careful judgment about which costs are worth keeping.
Follow-up questions interviewers ask
- How did you make sure you were not deleting logs you needed?Mention the security team, the restore path, and the next incident.
- Why not buy a better logging tool?Show the cheaper option met the need, and a new tool had its own cost.
- How did you find time alongside your normal work?Cheapest, biggest wins first; a day of analysis before any change.
- Tell me about a time saving money was the wrong call.Show you know when frugality creates risk, such as cutting backups.
Amazon Leadership Principles that test this
Frugality · Tell me about a time you delivered something with limited resources.
Achieve more with less; limits push you to be resourceful and self-reliant, and spending more or adding people earns no extra credit.
Situation We needed a load-testing environment before a big sale event, but a full copy of production would have cost more than our team's monthly budget, and there was no time to request more.
Task I had to give the team a realistic load test within two weeks using what we already had.
Action I looked at what we really needed to test: the checkout path and its three dependencies, not the whole system. I built a scaled-down environment at one quarter of production size, using spare capacity in our staging account during nights only, and turned it off automatically each morning. To make results meaningful, I tested at one quarter of the target load and checked that resource use scaled roughly in a straight line, then confirmed the biggest risk, the database connection limit, with a targeted test at full load on a single component.
Result The tests cost about five percent of a full copy. They found a connection-pool limit that would have failed at about 60 percent of the expected peak. We fixed it, and checkout ran without errors through the sale.
Tip: Show how you cut the problem down to what mattered and still got a trustworthy result.
Companies that test this
Prepare your own
Write your story in the story bank and tag it "Doing more with less"; it will show up against every company value that tests this theme.