Pressure

Tell me about a time you achieved a goal with limited resources.

Why interviewers ask this

Interviewers ask this to see how you operate when you cannot just throw headcount or budget at a problem. They are listening for creativity, prioritization, and whether you protected quality on the parts that mattered most. Stories where the constraint was not actually limiting do not land.

STAR tip

Pick a goal where the gap between resources and ambition was real. Show what you cut, what you got creative about, and what the result was relative to the original target.

Sample answers

Marketing Manager

I had a fifteen-thousand dollar budget to launch a new feature, and our usual playbook for that kind of launch had been about ninety thousand. Paid was off the table at that scale. I built the launch around three earned moves instead. I lined up a guest post on a partner blog that drove our customer profile, recorded a forty-minute walkthrough with our founder for a podcast we had a relationship with, and built a one-page interactive demo our sales team could send instead of a deck. I spent the budget on a freelance designer for the demo and a small giveaway for the podcast audience. The launch generated about thirteen hundred trial signups in three weeks, which was close to seventy percent of what the old ninety-thousand-dollar playbook had hit on a previous launch. The interactive demo became the top-performing sales asset for the next two quarters. The constraint forced me to pick channels with longer tails.

Backend Engineer

My team was asked to add full-text search across a hundred-million-row table. The product manager wanted Elasticsearch. We had no infra budget for the quarter and no spare engineer to operate it. I spent two days reading our query patterns and found that ninety percent of searches were prefix matches on three columns. I proposed using Postgres trigram indexes on those columns instead, with a clear note on what we would lose — fuzzy ranking and stemming. I shipped a prototype in a week. P95 latency was about a hundred and sixty milliseconds, which was good enough for the use case. We launched without new infra. Six months later we were still on Postgres and the team had not had to learn Elasticsearch. The lesson was that constraints push you to look at your actual usage instead of the architecture you would build with infinite budget.

Common mistakes

  • Picking a goal where the constraint was nominal and easy to work around
  • Saying you just worked longer hours to make up the gap
  • No mention of what you cut or traded off
  • Generic outcome with no comparison to the original target
  • Ending without saying what the constraint forced you to learn

Score your own answer free

Paste your answer to "Tell me about a time you achieved a goal with limited resources.". Odin scores it on STAR coverage and rebuilds it line-by-line. No signup. 5 free scores per hour.

Free, no signup. 5 scores per hour without an account.

Practice this with real AI feedback

Odin runs voice-first mock interviews tailored to your resume and the job posting. You get STAR-method scoring and concrete suggestions on every answer.

Related questions

Tell me about a time you delivered under a tight deadline.
Pressure
Tell me about a time you found a creative solution.
Achievement
Tell me about a time you improved a process.
Leadership