Tell Me About a Time You Overcame a Challenge

"Tell me about a time you overcame a challenge" tempts you to reach for the hardest thing that ever happened to you, as if a bigger hardship scores more points. It doesn't. This question grades your problem-solving approach, not how rough your story was. This guide gives you a selection rule for picking an external obstacle where your thinking is the story, an answer shape weighted on what you tried and adjusted, one full worked example from coursework or clubs, and the traps that sink an otherwise fine answer. One quick line to keep you out of the wrong lane: this is not the failure question. There, you own a mistake you caused. Here, you push through a barrier you did not.

What interviewers are really testing

The word "challenge" makes people think the test is about grit. It's really about three signals, and none of them is the size of the hardship.

You push through instead of stalling. When something blocks the path, do you keep working the problem, or do you freeze and wait for someone to rescue you? On their team, things will get stuck: a dataset will be a mess, a dependency will break, a stakeholder will go quiet. They want to see that you treat a blocker as a puzzle, not a full stop.

Your thinking is visible. They can't see inside your head, so the answer has to show your reasoning out loud: what you tried, why it didn't work, and what you did next. A story where the obstacle just "worked itself out" tells them nothing about you.

The obstacle came from outside you. This is what makes it a resilience question rather than a confession. The barrier should be something you did not create: a group that fell apart, a course that outran you, a tool that didn't exist. That keeps the spotlight on how you responded, not on a mess you made.

The size of the hardship is not scored. A cancelled venue and a broken data pipeline can both make excellent answers. A dramatic personal ordeal, told with no problem-solving inside it, makes a weak one.

The selection rule: an external obstacle where your approach is the story

Pick the story on one test: is the interesting part what I did, or what happened to me? If it's the second, keep looking.

It should be a barrier you didn't cause

This is the line that separates this question from the failure question, and getting it wrong is the most common mistake. If the honest version of your story starts with a bad decision of yours, that's a mistake you caused, and it belongs in the failure question instead. An overcoming-a-challenge story starts with something going wrong that wasn't your doing, and then leads with how you problem-solved through it. Teammate ghosts the group two weeks out: external. Course assumes a background you don't have: external. You procrastinated and blew your own timeline: that's a failure answer, tell it there.

It also isn't a "greatest accomplishment" answer. Your greatest accomplishment is a win you drove and can brag about from the first sentence. An obstacle story opens with something blocking you and earns the good ending. Same event can feed both, but you lead them differently: one leads with the trophy, this one leads with the wall.

One more neighbor to keep straight: this is close to, but not the same as, the adapt-to-change answer. That one is about a plan that flipped when it wasn't your call, where the move is re-planning calmly. This one leans on a first attempt that fell short and the fix you made after. If your story has no failed first try, it probably fits adapting better.

Where to find one with no work history

You have more of these than you think. Strong, safe sources for students:

• A group project that went sideways, like a member dropping the course halfway or a shared plan collapsing days before submission.
• A course or skill you had to claw through, where the class assumed knowledge you didn't have and you had to build the base yourself.
• A club problem nobody would touch, the broken process or dead event that everyone complained about and no one fixed.
• A resource or tool constraint you worked around, like no budget, no access to the software you needed, or data that arrived in an unusable shape.

Each of these is a barrier from outside you, with room to show a sequence of moves. Pick the one where you made the most decisions.

Skip the trauma dump

A heavy personal story is the trap this question sets, and most people walk into it. Leading with a serious personal hardship usually backfires here, not because your life isn't hard, but because it shifts the room from "how does this person solve problems" to "how do I respond to this news," and it can put the interviewer in an awkward spot they can't grade. Coursework, clubs, and projects are almost always the stronger, safer pick.

If a personal challenge genuinely is your best problem-solving story, you can use it, but keep the setup to a sentence and keep every other word on the approach: what you tried, what you changed, what you built to get through. The emotion is not the evidence. The plan is.

The answer shape: STAR weighted on what you tried and adjusted

Use the STAR method as the skeleton and reuse it across your story bank, but weight it differently than usual for this question. The obstacle gets one or two lines. The bulk of the answer goes on your actions, and inside the actions, one beat carries more than the rest: the adjustment.

Tell it in this order:

1. The obstacle, in one or two lines. What blocked you, and why it was genuinely hard. Resist narrating the whole backstory.
2. Your first attempt. What you tried initially, and, honestly, what didn't work about it. This is the setup that makes the rest land.
3. The adjustment (weighted heaviest). What you changed when the first attempt fell short, and why. This is the part interviewers are actually buying. A story where the first thing you tried worked perfectly shows less than one where you hit a wall, rethought, and course-corrected.
4. The result. How it turned out, with a concrete outcome, plus a line on what you'd carry forward.

Because the obstacle is the diagnostic part here, some people rearrange STAR into a variant called SOAR: Situation, Obstacle, Action, Result, which swaps the "Task" beat for the barrier itself (The Interview Guys). Same beats you already know, just renamed to keep the obstacle up front. Don't over-formalize it in the room. Nobody wants to hear you announce an acronym. Just make sure the wall is clear and your adjustment gets the most airtime.

A full worked example (from coursework or clubs)

Made-up material, an ordinary outcome, not a hero story. Copy the shape, not the words. Watch the weak version first, then the fix.

Setup: a four-person group project where one member dropped the course with three weeks left, and their half was the part everything else plugged into.

Weak version: "One of our group members dropped out partway through, which was really stressful and honestly kind of unfair to the rest of us. We were down a person right before the deadline and I was worried we'd fail. But we pulled together and somehow got it done, and it turned out fine in the end. It taught me a lot about teamwork and not giving up."

That answer is all weather and no decisions. The obstacle is external, which is good, but nothing inside it shows how the student thinks. "We pulled together and somehow got it done" is exactly the line interviewers can't grade. Now the fixed version:

"Three weeks before our group project was due, one of our four members dropped the course, and his section was the piece the other three depended on. obstacle, one or two lines My first move was just to split his work evenly across the three of us, which felt fair. Within a couple of days it was clearly failing: we each tried to learn his part cold, on top of our own, and all three sections started slipping at once. first attempt, what didn't work So I changed the approach. Instead of splitting by fairness, I split by what each of us already half-knew. I mapped his section into three chunks, gave each person the chunk closest to work they'd already done, and took the messiest integration piece myself since I had the clearest view of how it all connected. Then I moved our first combined check to that same week, so we'd catch breakage early instead of the night before. the adjustment, weighted heaviest We submitted on time, and the integration held together because we'd tested it days out rather than at the end. What I kept from it: match work to what people can already do before you split it evenly, because even distribution isn't the same as smart distribution. result plus takeaway"

Same dropped teammate. The difference is that the fixed version shows a first attempt failing and a specific, reasoned adjustment, which is the exact thing the question exists to find.

Three traps that sink a good answer

• Trauma-dumping. Opening with a heavy personal ordeal moves the room off your problem-solving and can leave the interviewer with nothing to score and no comfortable way to respond. If you must use a personal story, one line of setup, then all approach.
• An obstacle you caused. If the barrier traces back to your own mistake or procrastination, you've accidentally answered the failure question. Interviewers hear the missing ownership. Move a self-inflicted story to the failure prompt and pick a genuinely external barrier here.
• Drama with no action. A gripping setup that ends in "and then it worked out" gives them a story with a hole where you should be. No first attempt, no adjustment, no result you can point to. The wall is not the answer. What you did about it is.

Frequently asked questions

Can I use a personal challenge if I have no work experience?

Yes, but choose one where problem-solving is the point, and keep the setup brief. A personal hardship with a clear sequence of things you tried and adjusted can work. A personal hardship told for its emotional weight usually doesn't. Coursework, club, and project stories are generally stronger and safer, because the whole answer stays on your approach.

What's a good example of a challenge you overcame?

A concrete external barrier with room to show your moves: a group project that lost a member mid-way, a course that assumed a background you had to build from scratch, or a club event whose plan broke days before. Use the shape (obstacle, first try, adjustment, result), not a memorized script, so it stays yours under follow-up questions.

Should the challenge be work-related?

No. Academic and extracurricular examples work fine for an intern role, as long as your actions are visible and the story maps loosely to a skill the job needs. Interviewers screening interns expect no work history. Pick the barrier where your problem-solving is clearest, not the one with the most impressive setting.

How long should the answer be?

Roughly 90 seconds to two minutes. A line or two of setup, the bulk on what you tried and how you adjusted, then the result and a short takeaway. If you're spending more than a couple of sentences on the obstacle itself, you're front-loading the wrong part.

What if I can't think of a time I overcame a challenge?

You have one, you just haven't labeled it as such. Prompt yourself with the last group project that went off the rails, the hardest class you had to fight through, or the club task nobody wanted. The moment something blocked you and you kept working the problem, that's your story.

Right now, draft one external-obstacle story: a barrier you did not cause, the first thing you tried, the adjustment you made when it fell short, and the result. Time it aloud to about 90 seconds and check that most of the words land on what you adjusted, not on the obstacle. Then browse internships and book the rounds you're now ready for.