How to Answer "What Are Your Weaknesses" as a Fresher: Safe Weaknesses, Samples, Mistakes

"What are your weaknesses?" is the HR-round question freshers prepare for by memorising a trick, usually "I am a perfectionist". Interviewers have heard that answer thousands of times, and it tells them only that you were coached. The question is a self-awareness test, not a trap. Answered honestly and briefly, it can be one of the strongest moments in your round, because it is the one place where you get to show that you know yourself and can improve. This guide gives you a three-part formula, a list of safe weaknesses for freshers, the ones to avoid, sample answers for a fresher, a teacher and an IT professional, and the follow-up questions that usually come next.

Why interviewers ask about weaknesses

The interviewer is not collecting reasons to reject you. Three things are being checked:

• Self-awareness. Do you know where you fall short? People who do are easier to train and manage.
• Honesty under pressure. A candidate who dodges this question will probably dodge harder questions later, on a project or in a client call.
• Coachability. The best answers show a weakness plus a fix already in progress. That is exactly the behaviour a fresher's first manager wants to see.

For campus hiring, the question also separates candidates who have thought about themselves from candidates who have only rehearsed a script. It usually arrives after "tell me about yourself" and "what are your strengths", so the interviewer already has a picture of you and is checking whether it is honest.

The three-part formula: weakness, evidence, fix

Keep the answer to thirty or forty-five seconds and build it in this order:

Four rules:

1. Make it real. A weakness that is really a strength in disguise ("I care too much about quality") is heard as a dodge.
2. Keep it away from the core of the job. A developer should not say "I find debugging frustrating". A sales candidate should not say "I dislike talking to strangers".
3. Spend most of the time on the fix. The weakness takes one sentence. The fix takes two or three.
4. Stop after one. If the interviewer wants a second weakness, they will ask.

Safe weaknesses for freshers

These are honest, common among freshers, and not fatal for most roles. Each one comes with a way to phrase it and the fix you can mention.

Choose one that is actually true for you. The example in the "evidence" part will be easy to tell if it really happened.

Weaknesses to avoid

Some answers hurt you no matter how well they are delivered:

• Fake strengths. "I'm a perfectionist", "I work too hard", "I'm too honest". These are read as evasion.
• Core-skill weaknesses. "I'm not good at coding" for a developer role; "I struggle with numbers" for an accounts role; "I'm not patient with children" for a teaching job.
• Character flaws. "I get angry easily", "I lie sometimes", "I'm lazy in the mornings". These are disqualifying, not endearing.
• "I have no weaknesses." It signals either a lack of self-awareness or something hidden.
• Attendance and punctuality. "I'm often late" is not a weakness a company will train you out of.
• Anything about the company or the interviewer. "My weakness is that I don't like working late" is a complaint, not an answer.
• Weaknesses that are already visible. If your resume shows a backlog or a year gap, the interviewer will ask about it directly; do not volunteer it as your weakness.

Sample answer 1: fresher, IT or computer science

For a B.Tech or MCA candidate applying to a services company or startup developer role.

"My main weakness is that I try to solve a problem alone for too long before asking for help. During my internship I spent almost a full day stuck on a configuration issue in a Spring Boot service because I didn't want to look like I couldn't handle it; my mentor solved it in ten minutes once I finally asked. Since then I've set myself a rule: if I'm stuck for more than thirty minutes, I write down what I've tried and ask. In my final-year project that meant our team lost far less time, and my guide commented that our progress updates were the clearest in the batch. I still prefer to try first, but I've learned that asking early is part of the job, not a failure."

Why it works: the weakness is real and common, the evidence is specific and slightly embarrassing, the fix is a concrete rule with a visible result, and the whole thing stays clear of the core skill of programming.

Sample answer 2: teacher interview

For a B.Ed or subject-teacher candidate at a school, or a lecturer at a college. The weakness must not touch classroom control, subject knowledge or patience.

"A weakness I'm working on is that I tend to over-prepare my lessons and then try to cover everything in one period. In my teaching practice last year, I planned a forty-minute class on photosynthesis with far too much content, and the slower students were lost by the halfway mark. My supervising teacher pointed it out. Since then I plan every lesson around one objective, keep the extra material as an optional handout, and check understanding with two quick questions before moving on. By the end of the practice term my classes were running to time and my supervisor's feedback specifically noted the improvement in pacing."

Why it works: it shows care for students, names a real classroom problem that is not disqualifying, and describes a professional fix that any principal would want to hear.

Sample answer 3: IT professional, three years of experience

For an experienced developer or tester interviewing at a product company. The weakness should be about working style, not competence.

"My weakness has been delegation. When I became the owner of two services at Infosys, I kept taking the difficult tickets myself because it felt faster than explaining them to the two trainees on my team. It worked for a while, until a release month when I became the bottleneck and we slipped a date by three days. After that I started doing a weekly pairing session with each trainee, and I hand over one hard ticket a sprint with a written brief. Six months later both of them handle production issues without me, and I've had time to work on the batch-job rewrite that I'm proudest of. I still catch myself wanting to just do it, but now I notice it."

Why it works: the weakness is a common one for people moving into ownership, the cost is stated honestly, the fix has a system behind it, and the result is measurable.

Company variants: TCS, Infosys, Wipro and Accenture

The formula does not change by company. What changes is the follow-up:

• TCS: HR often follows with "how would that affect you in a client-facing project?". Have one sentence ready that connects your fix to client work.
• Infosys: expect "what did you learn from it?" Keep the answer to the fix and the result.
• Wipro: the Wipro interview questions bank shows HR often pairs this with "what are your strengths"; keep the two answers balanced in length.
• Accenture: behavioural probing is common, so the "evidence" part of your answer may become a full STAR question. Prepare it as one; the behavioural questions for freshers page shows the format.

Mistakes that weaken the answer

• Two sentences on the weakness, none on the fix. The fix is the answer.
• A weakness with no example. "I'm not good at time management" without a story sounds invented.
• Over-apologising. "I'm really sorry, this is a big problem for me..." Say it plainly and move to the fix.
• Choosing a weakness that contradicts your strengths. If you said "communication" was your strength five minutes ago, do not name "public speaking" as your weakness.
• Reading it off. This answer more than any other should sound like you, not like a script.

Follow-up questions to expect

• "How has this weakness affected your work or studies?"
• "What are you doing about it right now?"
• "Give me another weakness." Have a second one from the safe list ready.
• "What would your friends or teammates say is your weakness?" Same formula; the answer should not contradict the first.
• "What are your strengths?" if it has not been asked yet.
• "Why should we hire you?"

The complete set of surrounding questions is in the HR interview questions for freshers bank.

How to practise it

Write down three weaknesses that are actually true for you, then cross out any that are core to the job. For the one that remains, write one sentence of evidence and two of fix. Say it aloud and time it; anything past forty-five seconds is too long.

The hard part is the follow-up, because a rehearsed weakness collapses when someone asks "tell me more about that day". In a MockMate Practice session, the interviewer persona asks about your weakness and then presses on the example: what exactly happened, what you did, what changed. The report at the end lists each answer with response timing, the coaching evidence behind every note, and the weaknesses that recur across sessions, which is useful for this question in particular because it tells you what an interviewer might actually notice. Eligible accounts get three free Practice starts of up to ten minutes each.

MockMate's Live assistance on Windows is a separate mode: use it only where the organisation or interviewer permits assistance and you have disclosed it, and choose Practice whenever permission is unclear.

The Hindi version of this guide explains the same formula, the safe list and the samples in Hinglish.