Answer 'What Is Your Greatest Weakness' Honestly Without Clichés

Get a 60-90 second interview answer built on a real weakness, a step you are already taking, and proof of progress, plus a short version and likely follow-ups.

You getWeakness check, spoken answer and short version

Prompt

Prompt
Act as an interview coach who has sat on many hiring panels. Help me answer "What is your greatest weakness?" honestly and without clichés.

Before writing anything, ask me these questions in one message and wait for my answers:
1. What role and level are you interviewing for?
2. What is one real weakness a manager or colleague has pointed out, or that has cost you time or results?
3. What are you already doing about it, and since when?
4. Which skills are central to this role?

Rules:
- Ban fake weaknesses: perfectionism, working too hard, caring too much, being too detail-oriented.
- The weakness must be real and specific, and not a core requirement of the target role.
- Include one concrete step I am already taking, with a frequency or start date, plus one sign of progress. Use only facts I gave you; do not invent results.
- Keep the spoken answer to about 150-200 words, first person, plain language.

Output format:
1. Weakness check: one line on why this weakness is safe and believable for the role.
2. Spoken answer: the full answer.
3. Short version: 2-3 sentences.
4. Likely follow-ups: 2 questions, each with a one-line answer note.

End with one line flagging anything that could still sound rehearsed or risky.

Example output

At a glanceHow the weakness answer is builtBackend engineer example: underestimating task time
  1. Name the weaknessUnderestimating how long work will take
  2. Show the impactTwo-day tickets took four; sprint planning suffered
  3. Describe the fixSince MarchSpreadsheet of estimate vs actual, reviewed every Friday
  4. Give proof of progressLast six tickets within about 20 percent
  5. Prepare follow-upsMissed estimates and what the spreadsheet taught

Example for: a backend software engineer with 3 years' experience applying for a mid-level role; weakness is underestimating task time.

1. Weakness check

Estimation is a real, common gap for engineers at this level, it is not the core skill being hired for (building and maintaining services), and you have a tracked habit that shows it is improving.

2. Spoken answer

"My biggest weakness has been underestimating how long work will take. Early in my current job I'd say a ticket was two days, and it would take four, usually because I didn't account for testing, code review, or edge cases I found halfway through. My lead pointed out that it made sprint planning harder for the whole team, and she was right.

Since March, I've kept a simple spreadsheet: my estimate, the actual time, and the reason for any gap. Every Friday I spend ten minutes reviewing it. The pattern was clear: I was skipping review and testing time. So now I break each ticket into build, test and review before I give a number.

It's not solved, but it's better. On my last six tickets I was within about 20 percent, where before I was often off by double. I still flag uncertainty early when a task touches code I haven't worked in."

3. Short version

"I used to underestimate how long tasks would take, which made sprint planning harder for my team. Since March I've tracked estimates against actual time and now split work into build, test and review before estimating. My last six estimates were within about 20 percent."

4. Likely follow-ups
  • "How do you handle it when you realize you'll miss an estimate?" Say you tell your lead as soon as the gap is clear, with a new number and the reason.
  • "What did you learn from the spreadsheet?" Name the pattern: review and testing time was the missing piece, not coding speed.

Risk check: "it's not solved, but it's better" is honest and good to keep, but say the 20 percent figure only if you can show the spreadsheet if asked.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Banning perfectionism and similar dodges forces a weakness interviewers actually believe.
  • Requiring a step already in progress, with a date, turns the answer into evidence of self-awareness.
  • Checking the weakness against the role's core skills keeps the honest answer from costing you the job.

Use before any interview where this question is likely. Have one honest weakness and what you have done about it ready. Works in ChatGPT, Claude or Gemini; answer the four questions in one reply.

Common edits

  • Ask for a version under 45 seconds for phone screens.
  • Add a fifth question about a past interview where your weakness answer fell flat.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search