What is your greatest weakness?
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to test self-awareness, honesty, and whether you can improve a real limitation without excessive hand-holding. They are usually less interested in the weakness itself than in whether you can name something credible, explain its impact clearly, and show a believable pattern of changed behavior. At higher levels, they also check whether the weakness is calibrated to your role and whether your mitigation approach matches your scope.
Key Insights
- You do not need to pick a catastrophic flaw, but it does need to be a real one. A polished non-weakness answer often reads as evasive, while an overly severe weakness raises judgment concerns.
- You should explain the mechanism of the weakness: what situations trigger it, how it affected your work, and how you noticed the pattern. That level of specificity is a strong signal that you actually understand yourself.
- The best answers show an ongoing improvement loop, not a one-time correction. Name what you changed, how you check yourself now, and what evidence tells you the weakness is being managed better.
What interviewers probe atlevel
Top Priority
Pick a real early-career weakness that could plausibly show up in your work, but not one that makes the interviewer doubt basic job readiness.
Good examples
🟢Early on I hesitated to ask for help soon enough when I was blocked, because I wanted to solve everything on my own first.
🟢A weakness I've been working on is turning ambiguous tasks into concrete next steps; I used to wait too long before clarifying assumptions.
Bad examples
🔴My biggest weakness is that I care too much about quality, so I sometimes spend extra time making things really polished.
🔴I would say public speaking, but it has not really affected my work because most of my job is heads-down coding.
Weak answers either dodge the premise or pick something too detached from day-to-day work. Strong answers name a genuine junior-level limitation that matters and can be improved.
Valuable
Example answers atlevel
Great answers
One weakness I've been working on is waiting too long to ask for help when I'm blocked. Early in my first internship, I felt like I was supposed to figure everything out myself, so I spent almost a full day chasing an issue that a more experienced engineer helped me resolve in fifteen minutes. After that, I started giving myself a time limit and writing down what I'd tried before reaching out, so my questions were more focused. That helped me get unstuck faster without just handing the problem away. On later tasks, my mentor actually told me my questions had become much sharper and that I was making faster progress.
One weakness I’ve been working on is being too careful before I send anything for review. In college projects and my first part-time dev role, I wanted my work to be very polished before anyone saw it, because I didn’t want to waste other people’s time with rough drafts. The downside was that I’d sometimes spend extra time on things that could have been corrected much faster if I’d shared them earlier. Now I try to send a smaller version sooner and ask for feedback at the right checkpoints, especially on small tasks. That has made me more efficient, and I’ve found that teammates actually appreciate getting something they can react to instead of waiting until the end.
Poor answers
My biggest weakness is probably that I care a lot about doing high-quality work, so sometimes I spend extra time polishing things. I do not really see that as a bad thing because it means I take my work seriously. In school and internships, people usually appreciated that I had a high bar. So I would say my weakness is mostly being too detail-oriented.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late March, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.