How to Answer 'What Are Your Weaknesses?' in Indian Interviews 2026

Understanding the intent behind the question helps you craft the right answer.

Interviewers are not looking for a confession of failure. They are testing three things: self-awareness (do you know what you are not yet good at?), honesty and maturity (can you discuss imperfections without deflecting?), and growth orientation (are you working on your weak areas?). A candidate who says 'I have no real weaknesses' signals poor self-awareness. A candidate who shares a real weakness with evidence of active improvement signals exactly what interviewers want to see.

Use this four-part structure for the 'weakness' answer.

(1) Name the weakness honestly: but pick one that is real and relevant, not one that is obviously fake. (2) Give a brief example of where it showed up in your work or studies. (3) Explain what you have done or are doing to address it. (4) Show recent evidence of improvement.

Example for a fresher: 'I tend to overthink design decisions before starting to code: I can spend too long planning before implementing. I noticed this during my final-year project where I spent two weeks designing the architecture before writing a line of code. Since then, I have started using a 'timebox' approach: I limit planning to a set time and then start building, adjusting as I go. In my last internship, I shipped my first feature 40% faster using this approach.'

These weaknesses are real, credible, and show development potential without raising red flags for the role.

For technical roles: 'I sometimes focus too much on code quality and take longer than needed on refactoring tasks.' 'I am not yet comfortable presenting technical decisions to non-technical stakeholders: I'm working on this by joining my team's business review presentations.' 'I tend to take on too much work rather than delegating, which I'm improving by checking in with my team's capacity before committing.' For non-technical roles: 'I used to struggle with saying no to requests, which led to overcommitment. I now use a structured prioritisation approach and communicate timelines upfront.' 'I can be impatient when projects move slowly: I'm learning to manage this by focusing on what I can control within each stage.'

These responses consistently backfire in Indian interviews.

Fake weakness disguised as a strength: 'I'm a perfectionist' or 'I work too hard': interviewers have heard these thousands of times and they signal inauthenticity. No weakness at all: 'I can't think of any real weakness': signals either low self-awareness or dishonesty. Fundamental job-related weakness: 'I struggle with programming' for a software engineering role, or 'I have difficulty with public speaking' for a sales role: raises direct concern about your ability to do the job. Personal trait, not professional: 'I get angry easily' or 'I am not a morning person': these suggest cultural fit issues.

Tailored answers for different career stages.

Fresher: 'In college, I found it difficult to ask for help when I was stuck: I would spend hours trying to solve a problem independently before reaching out. I realised this was slowing me down, so I started using the '30-minute rule': if I'm stuck for more than 30 minutes, I reach out. This made me much more effective during my internship, where I got unblocked faster and learned more from my seniors.'

2–5 years experience: 'Earlier in my career, I was not confident facilitating meetings with senior stakeholders, which made some of my cross-team initiatives move slowly. Over the last year, I've led three cross-functional project reviews and received explicit positive feedback from one of the PMs on how I managed the discussion. I'm still growing in this area but have made real progress.'