Interview essentials

How to answer “What is your greatest weakness?”

By MockReps ·

A professional reflecting on interview practice notes at a desk.

“I'm a perfectionist” can sound like the safest answer in the room. It can also leave the interviewer knowing very little about how you work. What does perfectionism actually cause you to do? Miss a deadline? Keep polishing something that was already useful? Avoid asking for feedback?

To answer “What is your greatest weakness?”, choose a real work habit or skill you are improving. Explain where it causes difficulty, what you have changed and what progress you can honestly point to. You do not need to present yourself as a finished product.

Choose a specific weakness you can discuss

Start with something you have noticed in your own work, or feedback you have received more than once. A useful example has edges: “I sometimes put too much technical detail into updates for people outside engineering” is easier to discuss than “I'm bad at communication”.

Read the role requirements before choosing. If the job depends on a skill you are still developing, be accurate about your current ability. Do not disguise a missing essential qualification as a minor habit. Equally, you do not have to choose your most personal difficulty or disclose health, family or other private circumstances.

Try writing down one recent situation where the weakness affected your work. If you cannot describe what happened without inventing details, choose another example. Our guide to preparing from a job description can help you decide which parts of your experience matter to this role.

Give the answer a clear shape

Open with the weakness in plain language. Then explain its effect, the change you are making and any evidence that the change is helping. These are drafting prompts, not a script or an employer's marking scheme.

For instance, “I used to wait too long before asking for help” names a habit. “That left less time for someone else to review a blocked task” explains why it mattered. Agreeing a point to raise blockers with your manager is a concrete change. Simply promising to communicate better is much harder to assess.

Keep the evidence proportionate. If you have tried a new approach on two projects, say that. You do not need a dramatic percentage improvement, and you should not claim that a habit has disappeared because one attempt went well.

Example: giving overly detailed updates

This example is fictional. Use it to see the level of detail, then build an answer from your own experience.

“I sometimes give too much technical background before explaining what someone needs to know. In a project update, I went through the implementation before making clear that we needed a decision on scope. My manager pointed out that the decision had got lost. I now start updates with the decision or risk, then add the detail underneath. I've used that format in our recent planning meetings, and the questions have been more focused. I still catch myself over-explaining when someone asks about the technical work, so I check whether they want the short version or the detail.”

The answer describes a recognisable problem and an adjustment the candidate can explain. The last sentence gives an honest limit to the progress. It also invites a useful follow-up about how they adapt to different audiences.

Example: speaking up in group discussions

You can use a course, volunteering role or group project if that is where your relevant experience comes from. This second example is also fictional.

“In group projects, I sometimes wait until I've worked out a complete answer before contributing. That meant I kept a concern about our testing plan to myself until the group had already divided up the work. Since then, I've started preparing one question before each meeting and raising concerns while we can still change the plan. In our latest project, I asked how we would test cancellations before we assigned tasks, and we included that work from the start. I'm still practising speaking when my idea isn't fully formed.”

This is more useful than claiming to have “no professional weaknesses” because you have not had a full-time job. It shows a behaviour, a consequence and a change you have actually tried.

Watch for answers that dodge the question

“I work too hard” leaves the problem unexplained. “My colleagues don't meet my standards” moves the responsibility elsewhere. “I used to struggle, but now I'm excellent” closes the story without showing how you know.

You can still talk about high standards if the real difficulty is deciding when to stop. Name the trade-off: spending too long polishing an internal document, for example, reduced time available for a more urgent task. Explain how you now agree the required level of detail. The point is to describe your behaviour clearly.

A weakness is usually a pattern. If the interviewer asks for one occasion when something went wrong, use a specific incident instead. See how to discuss a mistake in an interview for that version of the question.

Try a five-minute rehearsal

  1. Write four notes: the weakness, its effect, your change and the evidence so far.
  2. Say the answer aloud without reading full sentences.
  3. Ask someone to follow up with “What still needs work?” or “Can you give me a recent example?”
  4. Remove any claim you cannot explain with a real experience.

If you need more structure for the example, use our STAR guide. Keep enough space in your preparation for the rest of the conversation, including a focused answer to “Tell me about yourself”.

Further reading: the National Careers Service recommends honesty about weaknesses and explaining how you are improving. The examples and rehearsal above are MockReps guidance.