Tell me about a time you were assigned a task and were unable to complete it.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests how you behave when execution breaks down: whether you recognize failure early, take ownership for the gap, and respond constructively rather than defensively. Interviewers are usually less interested in the fact that you couldn't complete something than in how you diagnosed the blocker, communicated about it, and adapted afterward. It is also a quiet test of honesty, judgment, and scope calibration.
Key Insights
- You do not need a dramatic disaster story. A strong answer is often a credible miss on something meaningful where you clearly show how you handled reality once success was no longer likely.
- Do not make the whole story about the blocker being external. Even if dependencies, timing, or changing priorities were real, interviewers want to hear what you owned: how you surfaced risk, what alternatives you explored, and how you reduced damage.
- You should make the ending explicit. Many candidates describe the miss but never close the learning loop by saying what changed in their behavior, planning, or communication afterward.
What interviewers probe atlevel
Top Priority
A strong junior answer ends with a simple, believable change in how you work next time.
Good examples
đ˘After that, I started writing down my assumptions before estimating and checking them with a more experienced engineer on similar tasks.
đ˘I changed my habit from struggling alone for too long to sharing a short status update when I'm blocked for more than a few hours.
Bad examples
đ´Since then, I just try harder and spend more time before asking for help.
đ´Now I'm more careful with deadlines in general.
Weak answers offer vague intention; strong answers describe a specific behavior change the interviewer can imagine repeating.
Valuable
Example answers atlevel
Great answers
In my first internship, I was assigned a small bug fix in our admin dashboard that I thought I could finish in a couple of days. After I started, I realized the issue touched an older part of the code that I didn't understand, and my first two fixes broke a related workflow in testing. I told my mentor before the deadline that I wasn't going to complete it as originally assigned, and I came with notes on what I'd tried and where I was confused. We decided to narrow the task to a safer fix for the main user path and leave the edge case for a follow-up. I finished that smaller piece, documented the remaining issue, and later used that experience to start checking my assumptions earlier and asking for help sooner when I'm stuck.
At my last job, I was helping our operations team prepare a monthly report for a client meeting, and I was given responsibility for pulling together data from two different spreadsheets and formatting it into our standard template. Halfway through, I realized one of the source files had missing entries and the numbers didnât line up cleanly, so I couldnât finish the report accurately on my own. I let my supervisor know the same day instead of waiting until the deadline, and I showed her exactly which rows were inconsistent and what I had already checked. She helped me get in touch with the person who owned the data, and we agreed to send a partial version with a note explaining what was still being confirmed. That taught me that being honest early matters more than trying to quietly force a finished result when the information isnât reliable.
Poor answers
I had a task once that I wasn't able to finish because the codebase was pretty messy and there were a lot of hidden issues. I kept working through it and tried several different fixes, but it just turned out to be bigger than expected. Eventually the sprint ended and we moved it out. Situations like that happen, especially when you're new, so I just stayed persistent and did what I could.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.