Tell Me About a Time You Worked With Limited Resources: How to Answer

"Tell me about a time you worked with limited resources" is a common behavioral question at startups, nonprofits, consultancies, retailers and large companies alike. Almost every real job involves a budget that is smaller than ideal, a team that is stretched or tools that are not quite right. The interviewer is not trying to catch you out. They want to know what you do when the situation is not ideal: do you stall, complain, or find a practical path forward?

The question also reveals how you think about trade-offs. Doing more with less always means choosing what not to do, and the people who make those choices openly and sensibly are the people managers trust with bigger scopes. Candidates who describe heroic overwork instead of smart prioritization usually score lower, because overwork does not scale.

The table below shows what most interviewers score. Use it to test your story before the interview.

Because the question is so open, many candidates answer it with a vague story about "being busy." The next section gives you a structure that avoids that trap.

The STAR method (Situation, Task, Action, Result) works well here, but the Action portion needs more structure than usual, because that is where resourcefulness shows. The RESOURCE framework gives you six steps to describe in order. If you are new to STAR, read our guide to the STAR interview technique first.

How the framework maps onto STAR

Situation and Task cover the context: the project, the shortage and the goal. Sort priorities through Update stakeholders make up your Action and should fill about half of your answer. Review and evaluate is your Result, including a figure and one lesson you applied afterward. A good rule of thumb is roughly 20 percent context, 50 percent action and 30 percent result and reflection.

The framework also doubles as a self-check. If you cannot say what you cut, or whom you told, the story needs more detail. Add the missing step before the interview, not during it.

The best limited-resources story has three ingredients: a real, specific shortage, a decision that was yours to make, and an outcome you can describe in numbers. Before you pick, list four or five projects from the last two or three years and score each against the table below.

Early-career candidates often worry that they have no relevant story. You do. Student organizations, part-time jobs, internships, volunteering, group projects and even personal projects like a side business all involve scarce money, time and people. What matters is how you responded, not the size of the budget.

Match the story to the role

If you are applying for finance, consulting or analytics roles, favor a story with data and a quantified trade-off. For operations and retail, choose staffing or inventory shortages. For marketing and communications, a budget story with creative workarounds works well. For technology roles, tools, time and technical debt are common constraints. Read the job description for words like "lean," "scrappy," "fast-paced" or "ownership": they hint at which constraints the team deals with.

Prepare two stories if you can. The second one gives you a fresh example if the interviewer asks a follow-up such as "tell me about another time," and it protects you if the first story is already used by an earlier interviewer in a panel loop.

Use these as models for structure, not scripts to memorize. Swap in your own details and numbers, and keep the length to about two minutes when spoken.

Example 1: Student event on a small budget

Best for: students and recent graduates

Situation: As treasurer of a business society, I was asked to run our annual career night. Last year's event had cost about $6,000, but our funding this year was only $1,800.

Task: My goal was to keep attendance and speaker quality high while spending under the new limit.

Action: I first confirmed with our president that attendance and employer turnout mattered most. I then listed every cost, ranked them by impact and cut printed programs and catering from full meals to light snacks. I asked the university to waive the room fee in exchange for opening the event to all students, and I recruited eight members as volunteers instead of hiring an event assistant. I shared a one-page budget with the board so nobody was surprised.

Result: We hosted 140 attendees and seven employers, about 90 percent of last year's turnout, for $1,650. The board adopted my budget template for later events.

Example 2: Short-staffed retail shift

Best for: retail, hospitality and customer service roles

Situation: During the holiday season, two of our six team members left within a week, and head office would not approve hiring until January.

Task: As shift lead, I had to keep customer wait times acceptable and avoid burning out the remaining team.

Action: I tracked foot traffic for three days and found that 60 percent of customers arrived between noon and 3 p.m. I moved our stocking tasks to early mornings, cross-trained two cashiers on returns and asked my manager to approve short, targeted overtime instead of a full schedule extension. I told the team why we were changing the plan and checked in with each person weekly.

Result: Average checkout wait stayed under four minutes through December, our satisfaction score held at 4.6 out of 5, and nobody left during the period. My manager later used the schedule as a template for other stores.

Example 3: Analysis without the right data

Best for: analyst, consulting and finance roles

Situation: At my internship, a manager asked for a market-sizing estimate for a new product, but our team had no subscription to the usual research database and only two days.

Task: I needed to deliver a credible estimate with public information, and be clear about uncertainty.

Action: I split the problem into a top-down and a bottom-up estimate. For the top-down view I used government statistics and public company filings. For the bottom-up view I interviewed three sales colleagues about typical customer counts. I documented every assumption in a spreadsheet and gave the manager a low, base and high case rather than one number.

Result: The base case came within 12 percent of the figure the research firm later reported. My manager used my range in the leadership meeting and I learned to state assumptions clearly.

Example 4: Cross-team project with no formal authority

Best for: project, operations and technology roles

Situation: I led a website migration with one developer, a small budget and no dedicated designer. The launch date was fixed by a contract renewal.

Task: I had to decide which features were essential and persuade other teams to lend time.

Action: I ran a prioritization session where we ranked features as must-have, should-have and later. I moved 12 low-impact pages to a second phase and wrote that decision in the project plan. I asked the marketing team to lend a designer for four half-days in exchange for early access to the new analytics. I held a 15-minute weekly status call so every stakeholder saw progress and risks.

Result: We launched on schedule with 85 percent of planned pages, and phase two shipped six weeks later. Page load time improved by 35 percent and I now document scope trade-offs in every project.

Most weak answers to this question fall into a small number of patterns. Check your draft against the list below.

The "hero" trap

A common mistake is to present yourself as the only person who saved the project. Teams are not impressed by solo heroics, because they imply fragile processes and poor delegation. Mention the colleagues who helped, the people you consulted and the ones who approved your plan. Credit makes you look more senior, not less.

A second trap is describing a constraint that was trivial, such as "I had to share a printer." Choose a shortage that genuinely forced a decision. If the stakes were low, say so and explain why the decision still taught you something.

Interviewers phrase this question in several ways. The same story usually works for all of them, as long as you adjust the emphasis. Here are the most common variations and the angle each one expects.

Related stories also appear in questions about initiative, adaptability and problem solving. Our guides on initiative interview questions and problem-solving interview questions show how to adapt one strong story to several of them.

If your interview includes a case exercise or an online assessment, the same skill appears there too: SHL situational judgment tests often present a scenario with limited time or staff and ask you to choose the most effective response. Practicing both formats reinforces the same habits of prioritizing and communicating early.

A strong answer is the product of preparation, not improvisation. Use the five-step plan below in the days before your interview.

Delivery tips for the day

Open with the context in one or two sentences, then name the constraint with a number. Slow down at the decision point, because that is where the interviewer is scoring you. Use plain language and avoid jargon unless the role calls for it. Finish with the result and a one-sentence lesson, then stop. Silence after a good answer is fine; the interviewer will follow up if they want more.

If you blank out in the interview, buy yourself a few seconds by saying "Let me think of the best example." That is perfectly acceptable and sounds more thoughtful than starting with a weak story. For a broader preparation plan, read our guide to behavioral interview questions and the STAR method, and for the other common questions you may face in the same round, see common interview questions and answers.

Finally, remember that a limited-resources answer is a chance to show maturity. You are demonstrating that you can be given a constraint and a goal, and trusted to figure out the rest.