TL;DR
- Choose a real, specific working behaviour you are actively improving.
- Explain the effect it had, the change you made and the evidence of progress.
- Avoid disguising a strength as a weakness or borrowing an experience that is not yours.
- Keep the answer relevant to work and be honest about any remaining limitation.
Treat the question as a request for self-awareness
“What are your weaknesses?” can feel like an invitation to undermine your application. A more useful preparation exercise is to identify a behaviour you have noticed, understand its effect and explain what you are doing differently.
Harvard's interviewing guidance recommends truthful answers that take responsibility and focus on behaviours and improvement. That is a better starting point than memorising “I work too hard” or selecting a supposedly harmless weakness from a list.
The interviewer may ask follow-up questions. If the answer is based on real experience, you can explain the context. If it is chosen only because it sounds safe, the follow-up can become difficult very quickly.
Build the answer in four parts
Name the behaviour, explain one consequence, describe the action you took and show what you have observed since. Keep the scope narrow enough to discuss concretely.
For example, “I sometimes delay asking for clarification when a task is ambiguous” is more specific than “I am bad at communication.” It points to a situation you can recognise and change. The consequence might be rework. The corrective action might be writing down assumptions before starting. The evidence might be catching a misunderstanding before it became a full day's work.
You do not need to claim the issue has disappeared. Explaining how you monitor it now can be more credible than declaring yourself permanently fixed.
Example: asking for clarification earlier
Here is a fictional answer you can use to understand the structure:
“Earlier in my current role, I sometimes waited too long to clarify an unclear request because I wanted to solve it independently. On one reporting task, I prepared a breakdown at the wrong level of detail and had to redo it. I now send a short summary of the intended output and any assumptions before starting unfamiliar work. That helped me catch a mismatch on a recent request before I built the report. I still work on recognising when a question will save time rather than slow things down.”
The answer identifies a genuine effect and a practical change. It does not blame the requester. Replace it with your own example rather than presenting this scenario as something you did.
Other starting points to examine honestly
| Behaviour to consider | A possible improvement habit | Evidence to look for |
|---|---|---|
| Giving too much detail in updates | Start with the decision or requested action | Fewer clarification questions |
| Underestimating unfamiliar tasks | Break work into smaller estimates | Earlier detection of schedule risks |
| Avoiding presentations | Volunteer for short team updates | Clearer delivery and specific feedback |
| Holding on to delegated work | Agree checkpoints and ownership | Teammates completing work independently |
These are prompts for reflection, not a menu of universally good answers. A behaviour that is a manageable development area in one role may be central to another. Read the job description and be accurate about your readiness for its essential responsibilities.
Avoid three common traps
First, do not turn the answer into a disguised compliment. “My standards are too high for everyone else” gives little evidence of learning and may sound dismissive of colleagues. If quality control really caused delays, explain how you now choose the appropriate standard for the task.
Second, avoid a long confession disconnected from work. You can discuss a professional behaviour without sharing private details. Keep the answer focused on the responsibility the employer is assessing.
Third, do not invent measurements. You can say your manager found the revised updates easier to act on if that feedback actually happened. You cannot turn that into a claimed productivity percentage without evidence.
Prepare for a follow-up
Ask a practice partner to challenge the answer: When did this last happen? How do you know the change helped? What do you do when the old habit returns? These questions help distinguish a repeatable improvement from a one-time intention.
You can also practise a shorter version. A clear initial answer gives the interviewer room to explore the example. A long explanation may bury the actual weakness and make it harder to understand what changed.
Use preparation to improve the behaviour itself
The most useful outcome is more than a polished answer. Choose one improvement habit you can apply this week and record what happens. That creates better evidence for future interviews and a better working process now.
Our STAR guide can help organise the example. When using PhantomCodeAI or another preparation tool, ask for clarity feedback and follow-up questions while keeping the underlying experience truthful.