Strengths and Weaknesses for a Job Interview

Why interviewers ask this question

The question tests three things: whether you know how you come across, whether you can be honest without underselling yourself, and whether your self-view matches what the role needs. A candidate who has never thought about their impact on colleagues is a risk in any team.

It is also a consistency check. Interviewers compare your answer with what your references say and how you behave in the interview itself. If you claim listening as a strength but interrupt repeatedly, the answer works against you.

Treat it as a work conversation, not a trap. The interviewer wants to picture you in the role: what you will do well from day one, and where they would need to support you.

How to choose a strength

Pick a strength that matters for this job, not just one you are proud of. Read the job description and choose something the role actually uses: clear written communication for a coordination role, calm prioritisation for a support role, structured decision-making for a lead role.

Attach one example with an observable outcome. ‘I communicate well' is a claim. ‘When our project changed scope, I wrote a short decision summary and checked each team's understanding before the handover' is evidence. Keep it to two or three sentences.

Interpersonal strengths are welcome here. Employers consistently rank communication, teamwork and adaptability among the most valued qualities, yet candidates often default to technical skills. If colleagues regularly ask you to explain decisions or smooth a difficult handover, that is a strength worth naming.

How to choose a weakness

Choose something real, not a disguised compliment. ‘I work too hard' and ‘I'm a perfectionist' signal that you are avoiding the question. Choose a behaviour you have genuinely needed to work on: delaying difficult conversations, over-explaining before stating a recommendation, or taking on too much instead of delegating.

Keep it honest but proportionate. Do not name a weakness that is core to the role—‘I miss deadlines' in a project management interview—or something that raises a conduct concern. The right weakness is a behaviour, not a character flaw, and one you are already addressing.

Structure the answer as: behaviour → impact → what you are doing about it. For example: ‘I used to delay raising disagreements until decisions were nearly final, which meant concerns surfaced too late to be useful. I now raise questions at the planning stage, and I ask a colleague afterwards whether my challenge came across as constructive.'

Example answers to adapt

Strength example (communication): ‘My strength is making complex work easy to follow. On our last migration project, I wrote the weekly update as decisions, risks and requests, and the support team told me it was the first update they could act on without a follow-up call. I would bring the same approach to stakeholder updates here.'

Strength example (collaboration): ‘I am good at working across teams with different priorities. When engineering and sales disagreed about a launch date, I mapped each team's constraints and proposed a phased release. Both teams agreed to it. I enjoy finding the version of a plan that several teams can genuinely commit to.'

Weakness example (self-promotion): ‘I tend to assume good work speaks for itself, so I have under-communicated progress to stakeholders. Twice last year, a sponsor was surprised by a status they should have known earlier. I now send a short fortnightly summary and ask my manager whether it gives them what they need.'

Weakness example (delegation): ‘Early in my current role I redid work myself rather than coaching colleagues through it. It was faster in the moment but slowed the team down. I have been practising handing over the task with a clear definition of done, then reviewing the output instead of rewriting it.'

Check your answers against reality

The strongest interview answers come from evidence, and the best evidence is how other people experience working with you. Before an interview, ask two or three colleagues: ‘What do I do that makes your work easier, and what would you like me to do differently?' Their answers are usually more specific than your own guesses.

If your self-view and your colleagues' view differ, that gap is worth knowing before an interviewer finds it. You might rate your listening highly while colleagues experience you finishing their sentences. A strength you name should survive a reference check.

ERA Skills is built for exactly this: a free self-assessment across Communication, Collaboration, Influence, Leadership and Adaptability, which you can then compare with pooled feedback from at least three people who know your work. Individual rater answers stay private. It gives you interview-ready examples grounded in how others actually experience you.

Mistakes to avoid

Do not memorise a script. Interviewers hear the same internet answers every week, and a polished recital invites a probing follow-up you cannot sustain. Prepare the substance—one strength, one weakness, one example each—then say it in your own words.

Do not list several strengths or several weaknesses. One well-evidenced answer beats a rapid-fire list. And do not apologise for the weakness or oversell the recovery: state it, show what you are doing, and stop.

• One strength, one real example, relevant to the role.
• One genuine weakness as a behaviour, with what you are doing about it.
• No disguised compliments, no claims you cannot evidence.
• Check your self-view against colleague feedback before the interview.