To answer “tell me about a time you worked with limited resources”, describe one project where budget, people, tools or time were clearly short of what the goal needed, explain the specific choices you made to get around the gap (prioritizing, reusing, simplifying or borrowing help), and finish with a measurable result plus what you would keep doing. Interviewers want resourcefulness, not heroics. “We had half the budget, so I cut scope here and reused this, and we still hit the target” is the shape of a strong answer.
What is the interviewer really testing with this question?
Every team has constraints, and many companies say openly that they value people who work well within them. The interviewer is listening for:
- A clear read of the constraint. You can say exactly what was missing and how big the gap was.
- Prioritization. You focused the limited resources on what mattered most.
- Creativity. You found a cheaper, faster or simpler way instead of only asking for more.
- Judgment about quality. You knew what you could trim and what you could not compromise.
- A good attitude. You treated the constraint as a problem to solve, not a grievance.
Asking for more resources is not wrong. A strong answer can include a well-argued request, as long as you also show what you did with what you had.
How does this question map to Amazon’s Frugality principle?
If you are interviewing at Amazon, this question often maps to Frugality, one of the company’s 16 Leadership Principles (as of October 2026). Amazon’s own wording opens with “Accomplish more with less,” and goes on to say that constraints encourage resourcefulness and invention, and that growing headcount or budget earns no extra credit. A limited-resources story can also support Invent and Simplify, Bias for Action and Deliver Results, depending on how you tell it.
Other employers use their own language for the same idea, such as “scrappy,” “resourceful” or “owner mindset.” Read the company’s values page and use their wording once, naturally, when you describe your approach. For Amazon specifically, our Amazon Leadership Principles examples show how to map one story to more than one principle, and the Amazon behavioral interview guide covers the loop.
Types of limited resources, and what to show for each
| Constraint | Example situation | What a strong answer shows |
|---|---|---|
| Budget | A campaign, event or tool purchase with a fraction of the usual spend | What you cut, what you reused, and cost per result compared with before |
| People | A teammate left, a hiring freeze, or you were the only person in your function | How you narrowed scope, automated or borrowed help from another team |
| Time | A fixed date with half the usual runway | What you delivered first and what you deferred |
| Tools or data | No proper software, incomplete data, old equipment | The workaround you built and its limits |
| Expertise | No specialist available for a key part | How you learned enough, or found an outside source of advice |
How do you answer “tell me about a time you worked with limited resources”?
Use the STAR method:
- Situation: the goal and the constraint, with numbers.
- Task: what you were responsible for delivering despite the gap.
- Action: the trade-offs, the workaround, who you enlisted and what you refused to compromise on.
- Result: the outcome against the goal, plus any lasting change, such as a cheaper process the team kept.
Three example answers we wrote
These are example answers we wrote, one each for budget, people and time. Use your own numbers.
Example answer we wrote: budget, B2B product launch
Situation: I was the product marketing manager for a new reporting feature at a software company. Budget cuts left us with $15,000 for the launch, compared with $40,000 for the previous major launch.
Task: I owned the launch plan and needed to reach a target of 400 accounts trying the feature in the first month.
Action: I listed every channel from the last launch with its cost and the sign-ups it produced. Paid ads had been the most expensive per sign-up, so I cut them by 80%. I moved the money into one customer webinar and recorded it for reuse. Instead of hiring an agency for the launch video, I wrote a script and asked our support team, who demo the product daily, to record a short walkthrough. I also wrote in-app messages that cost nothing and targeted the accounts already using similar reports.
Result: We reached 460 accounts in the first month and spent about $13,500. Cost per activated account was less than half of the previous launch. The in-app messaging approach became a standard part of our launch checklist.
Example answer we wrote: people, one-person IT team
Situation: At a 120-person manufacturing company, our IT team of two became one when my colleague left during a hiring freeze. We had a backlog of about 90 open tickets and a laptop refresh due that quarter.
Task: I had to keep support running and finish the refresh for 40 employees, alone, for at least three months.
Action: I tagged the backlog and found that around a third were password resets and printer issues. I set up self-service password reset and wrote five one-page guides for the most common printer fixes. For the refresh, I built a standard laptop image so each setup took 30 minutes instead of two hours, and asked each department to nominate one person to help colleagues with data transfer. I told my manager which low-priority requests would wait and posted a simple status page so people could see the queue.
Result: The backlog fell from 90 to under 20 in six weeks, and all 40 laptops were replaced on schedule. Password tickets dropped by about 70%, which made the case for hiring a junior technician the next quarter.
Example answer we wrote: time, startup engineer
Situation: I was one of three engineers at an early-stage startup. A large prospect agreed to a pilot if we could deliver single sign-on in three weeks, work we had planned for a full quarter.
Task: I owned the build and could not pull my two colleagues off a customer release.
Action: I wrote a one-page scope that covered only what the pilot needed: one identity provider, no custom roles, admin setup by our team. I chose a well-maintained open-source library instead of building the protocol handling myself, and I paired for an hour with an engineer at a friendly company who had done the same integration. I did not cut security reviews; I asked our CTO to review the token handling before launch.
Result: We delivered SSO in 17 days and the pilot started on time. The prospect signed an annual contract three months later, and the scoped-down version handled our next four customers before we needed to extend it.
Weak vs strong answers
| Element | Weak answer | Strong answer |
|---|---|---|
| The constraint | “We were a bit short-staffed.” | The size of the gap, with numbers |
| The approach | “Everyone worked extra hours.” | Specific trade-offs, reuse and workarounds |
| Quality | Corners cut with no thought | A clear line on what you would not compromise |
| Attitude | Complaints about leadership or budget | The constraint treated as a design problem |
| Result | “We got through it.” | Outcome against the goal, plus a lasting improvement |
Follow-up questions to expect, and mistakes to avoid
- What did you decide not to do, and why?
- Did you ask for more resources? Why or why not?
- What was the risk in your workaround?
- Would you take the same approach with a normal budget?
- What did the constraint teach you about the work?
Mistakes that weaken the answer:
- Making overtime the whole story. Long hours show commitment, not resourcefulness.
- Complaining about the constraint. Describe it neutrally, then move to what you did.
- Cutting something you should not have. Skipping safety, security or legal steps is a red flag, even if it worked out.
- No comparison. Without the original budget, headcount or timeline, the result is hard to judge.
A limited-resources story often sits next to the competing priorities question, the process improvement question and the creativity question, so pick a different story for each. Our complete list of “tell me about a time” questions helps you plan a full story bank.
Practice it
Numbers and trade-offs are what make this answer work, and they are the first things people drop when nervous. Rehearse with a no-signup AI mock interview built from your résumé and the job description. CoPilot Interview reads the question aloud, scores your spoken answer out of 10 and tells you what to fix, such as a constraint you never quantified. It is free for 15 minutes a day, with no account. To draft the story first, use the free STAR builder.
Practice your doing-more-with-less story
Answer behavioral questions out loud, get a score out of 10 and specific fixes, and repeat until the constraint and the result come through clearly.
Try a free AI mock interviewFAQ
What is a good example of working with limited resources?
A project where budget, people, time or tools were clearly short of what the goal needed, and you closed the gap by prioritizing, reusing, simplifying or borrowing help. Examples include a launch on a reduced budget, covering a role alone during a hiring freeze or delivering a feature in a fraction of the planned time.
Which Amazon Leadership Principle does this question test?
It most often maps to Frugality, which Amazon describes as accomplishing more with less. Depending on your story, it can also support Invent and Simplify, Bias for Action and Deliver Results.
Is it okay to say I asked for more resources?
Yes, if you also show what you did with what you had. A well-argued request backed by data, made after you had already found efficiencies, shows good judgment.
Can I use a story about working long hours?
Mention it briefly if it is true, but do not make it the answer. Interviewers want to hear the smart trade-offs and workarounds, not just extra effort.
What if the constraint was caused by bad management?
Describe the constraint neutrally and focus on your response. Criticizing past leadership makes the answer about blame rather than resourcefulness.
How long should my answer be?
About two minutes. Quantify the constraint early, spend most of the answer on your trade-offs and workarounds, and finish with the result compared with the original goal.