Direct answer
To answer “What is your greatest weakness?”, name a real work habit, give a specific example of its effect, and explain what you are doing about it. Describe progress only as far as your evidence supports it. If you have just started improving, say that plainly. Keep the answer concise and avoid disguising a strength as a weakness.
A sample answer when improvement is not yet proven
Here is a fictional example for a junior analyst whose job involves routine team planning. It is an illustration to adapt, not a script or a claim about a real candidate.
“I sometimes wait too long to raise a question when I'm not sure I'm right. In a recent planning meeting, I noticed an unclear reporting requirement but didn't ask until after the meeting. The reporting task had already started, and we had to redo part of it. A teammate pointed out that an earlier question would have helped. I've started writing down one point I'm unsure about before planning meetings, and raising it while we are still discussing the work. I've done that once so far, so I can't yet say it's reduced rework. Next, I want to see whether I raise questions early enough to change the plan.”
The last two sentences matter. Starting a new habit is an action. Knowing that it works requires an observation. You can explain an action honestly without inventing a result.
How do you know your approach is working?
Before the second attempt, the candidate can answer: “I can't say it's reduced rework yet. I've tried the new approach once: I prepared a question and raised it during the planning meeting instead of waiting until afterwards. Next, I want to check whether I keep raising questions while decisions are still being made, and whether we clarify requirements before work starts.”
That answer names the action already taken, the limit of the evidence and the next observation to look for. It does not claim the action has already improved the work.
What changes when new evidence arrives?
After the original answer was prepared, imagine the candidate trying the new habit for a second time a few weeks later. In that second planning meeting, the candidate asked about a missing data field before work began, and the team clarified the requirement there.
The candidate can now replace the final part of the answer with:
“In a later planning meeting, I asked about a missing data field before we started, and we clarified the requirement there. That's one example of raising a question earlier. I'm continuing the same preparation habit and checking whether I do it consistently.”
The updated answer adds a concrete observation of the changed behaviour. It still does not establish a measured reduction in rework, prove that no mistakes will happen, or show that the habit is permanent.
“I've started preparing a question before planning meetings.”
Verdict: Keep if true. Reason: Describes an action you took.
“In a later meeting I asked about a missing field before work began, and we clarified it then.”
Verdict: Keep only after the later event. Reason: Names a particular observation.
“This has made the whole team more efficient.”
Verdict: Remove without supporting evidence. Reason: Goes beyond the packet.
“This is no longer a weakness.”
Verdict: Remove. Reason: A couple of events do not establish a lasting change.
You do not need a percentage to describe a genuine attempt. One real event can support an account of what you have started doing; it may not establish improvement.
The facts behind the sample answer
The following packet is fictional. It deliberately contains no impressive improvement result. Use the same check on your own answer: identify the fact behind each sentence, then remove any claim that goes beyond it.
The candidate recalls holding back questions in a few earlier meetings when unsure.
What that supports: A pattern the candidate has noticed, not a measured frequency.
The candidate noticed an unclear reporting requirement during a meeting and asked only after it ended.
What that supports: A specific example of the habit.
The team had started work before the question was resolved and revised it.
What that supports: A concrete cost in this example; no time or money total.
A teammate said an earlier question would have helped.
What that supports: Feedback, not proof of a permanent pattern in every meeting.
The candidate prepared a question and raised it during one later planning meeting.
What that supports: The candidate completed the new action once: preparing and raising a question during the meeting. The packet does not establish whether that question changed a decision or prevented rework.
No reduction in rework has been established yet.
What that supports: “I can't yet say it's reduced rework.”
These facts support saying that the candidate has started trying a different approach. They do not support “I've solved this”, “my team is more productive”, or “we now avoid rework”. Those claims would need more evidence.
Choose a weakness that reflects your work
Start with something you have actually noticed or received feedback about. Describe the situation and behaviour, rather than giving yourself a broad label such as “bad at communication”. Then read the job requirements: how much would this limitation affect the work you are applying to do?
The example above would need more scrutiny for a role whose main responsibility is leading discussions or raising urgent operational concerns. A polished answer cannot remove a missing essential skill. If asked directly about a requirement you cannot meet, explain your current ability and the support you would need.
Do not borrow a weakness because a list calls it “safe”. Public speaking, delegation and attention to detail matter differently in different jobs. You also do not need a dramatic personal story to discuss a work habit.
Other weaknesses that fit this method
These are habits to consider only if they reflect your actual work, not a list of safe answers.
Over-polishing low-risk drafts.
Consider how much precision the role requires; do not treat required checks as wasted effort. Trying a time limit once supports a claim about your action, not a claim that you now work faster without losing quality.
Accepting small requests before checking priorities.
Consider whether the role requires an immediate response. Asking your manager to clarify priorities is an action you can describe; it does not yet prove that you meet deadlines more reliably.
Giving overly detailed project updates.
Consider what detail the audience needs, especially in a handover. Starting with a shorter summary is a changed approach; do not claim it is clearer without an observation or feedback that supports that conclusion.
Prepare for the follow-up
“When did this last cause a problem?”
Give the reporting example directly. Explain what you did and the resulting revision, without blaming the unclear requirement or the team.
“How would you handle this weakness on our team?”
Describe your current preparation habit, then ask how this team raises uncertainties. Do not promise that another workplace uses the same process.
“Have you done anything about it yet?”
If you have not, do not invent a course, checklist or conversation. Say what you have noticed, distinguish your intended next step from an action already taken, and accept that your answer shows less change for now. You can begin a genuine improvement step before the interview, but do not turn one rehearsal into a claim of workplace success.
Make your own answer from four notes
Write four short notes: the habit; a specific example and its effect; the action you have actually taken; and the result you can currently support. If the last note is “not known yet”, keep that limit in your answer.
For each sentence, ask: What happened? How do I know? Am I describing an action, an observation or a hope? Can I answer the next question without adding a new fact I cannot support?
Say the answer out loud once, then answer “How do you know it helped?” without looking at your notes. Listen for any result you added just to make the ending sound stronger. Remove it or find the evidence for it.
Use the interview answer timer for an offline practice round. You can do the whole exercise with your own notes; an AI interview is not required. If you are preparing in another language, the English-interview guide offers simpler sentence frames. The sample report shows how feedback can be tied to particular words, with the limits explained on that page.
Time one honest answer, then rehearse the evidence follow-up.Sources and limits
Big Interview’s weakness-answer guide discusses choosing a genuine weakness, considering the role and explaining improvement. CoPrep’s guide also addresses bounded weaknesses, evidence and continuing progress. UNC’s weakness-answer guide includes an example of improvement just begun. Those general principles are not new.
The before-and-after example and sentence checks above are an original fictional practice exercise. They are not a customer case study, a validated assessment, or evidence that a particular answer increases the chance of an offer.