Strengths and weaknesses in an interview: examples and answers

The mistake is picking adjectives. "Hard-working", "organised", "a team player" — these describe about ninety per cent of applicants and evidence none of them.

Pick capabilities the role requires, then attach evidence.

How to choose:

1. 1List the five or six things the job advert says the role needs.
2. 2Mark the ones you are genuinely strong at — not competent, strong.
3. 3For each of those, find one occasion that proves it.
4. 4Take the three with the best evidence.

How to say it. Name the strength, give the occasion in two sentences, state the result. Fifteen to thirty seconds each.

Weak: "I would say one of my strengths is that I'm very organised and good with deadlines."

Strong: "Recovering projects that have slipped. On the Jubail fit-out we were five weeks behind at the halfway point. I rebuilt the sequence around the two trades that were actually blocking, moved the rest to follow them, and we handed over eight days late instead of five weeks. That's the work I'm most useful at."

The second one names a specific capability, proves it, and uses a number. It also tells the interviewer something they can use, which the first does not.

Do not claim a strength you cannot evidence. The follow-up question is always "can you give me an example?", and a strength with no example becomes a weakness in the interviewer's notes.

A usable weakness answer clears all three. Most answers clear none.

1. It is real. Something that has actually cost you or your team something. If it costs nothing, it is not a weakness and everyone in the room knows it.

2. It is not fatal for this role. Do not name the central requirement of the job. If the role is client-facing, your weakness is not "I find client conversations difficult."

3. You have done something about it. This is the part that converts the answer. The weakness is the setup; what you changed is the answer.

Structure: the weakness, one concrete instance of it costing something, what you changed, and where you are now — including any part that is still work in progress.

That last clause matters. "And I've completely fixed it" is a second dodge. "It is better and I still catch myself doing it under time pressure" is credible.

Weaknesses that work

Delegating too late. "I hold on to work longer than I should. On the ERP migration I kept the data-validation workstream myself until week six, and the result was that I was the bottleneck on three other things. What I changed was to name the owner for each workstream before kickoff rather than during. It has held on the last two projects, though I still find myself stepping back in on the parts I know best."

Over-preparing for low-stakes decisions. "I spend more time than a decision deserves when the reversal cost is low. It showed up in a supplier shortlist where I built a full scoring model for a SAR 60,000 purchase. Now I set the depth of analysis before I start, based on what it would cost to be wrong. It is a rule rather than an instinct, so I have to apply it deliberately."

Written communication in English. "My written English is slower and more formal than my spoken English. I noticed it in board papers, where my drafts needed heavy editing. I started writing short first, then expanding, and I ask a colleague to read anything that goes above my manager. It is much better than a year ago and still the thing I spend the most time on."

That third one is worth noticing: naming a genuine language limitation, with a system in place, reads as far stronger than pretending it is not there — particularly in a bilingual workplace where it will be obvious within a month anyway.

Weaknesses that fail

Fill it, say it out loud, and time it. Each strength should take under thirty seconds; the weakness under sixty.

13–16: ready. 8–12: usually criteria 2 and 7 — the examples and the action. Both are additions, not rewrites. Below 8: the material is not there. Do the worksheet before rehearsing anything.

"What would your manager say you need to work on?" Harder, because it invites a real answer. Use the same structure, and if you have had that feedback, say what it was — it is more credible than a self-selected weakness.

"What is your biggest weakness?" Same answer. Do not escalate to something worse because they said "biggest".

"Where do you want to develop?" Softer framing, and it lets you use a genuine growth area rather than a flaw. Still needs a concrete action.

"Tell me about a time you failed." A different question — that one needs a full story with a result, and the STAR structure applies.

Asked on a scoring form in a structured interview. Common in public-sector and government-linked processes. The assessor is marking against defined indicators, so the specific occasion and the action matter more than fluency.

Modesty is a real tension here. Listing your own strengths can feel uncomfortable, and candidates often under-claim. The way through is not to boast — it is to describe the work rather than yourself. "We handed over eight days late instead of five weeks" is a fact about a project; the interviewer draws the conclusion about you.

The weakness answer is where under-claiming becomes risky in the other direction. Deflecting entirely reads as evasive to an interviewer trained on structured assessment, and the assessor may have a box that requires them to record something.

If the interview switches language, prepare both versions. The weakness answer in particular is easy to make worse by translating — the hedges that sound appropriately modest in Arabic can read as evasive in English, and the directness that works in English can read as blunt in Arabic. Prepare each one in the language you will say it in.

How many strengths should I give?

Three if asked for strengths, one if asked for "your greatest strength". Do not list five; it dilutes the good ones.

Can I use the same weakness at every interview?

Yes, as long as it passes test 2 for that specific role. The one thing to check each time is whether it is the core requirement of the job in front of you.

Should I mention a weakness they will discover anyway?

If it is visible on the CV — a gap, a short tenure, a missing qualification — do not use it as your weakness answer. Address it where it belongs, as a factual explanation, not as self-criticism.

Is it safe to name a technical gap?

Usually yes, if it is not the central requirement and you have a plan. "I have not used Oracle, I have used SAP for six years, and I have started the Oracle fundamentals course" is a complete answer.

What if the weakness I choose leads to bad follow-ups?

Then it was the wrong weakness. Test it by asking yourself the two most obvious follow-ups before the interview — if either one has no good answer, pick another.

Do the worksheet, then rehearse against the rubric. The strengths take twenty minutes; the weakness takes longer because choosing well is most of the work.

For the rest of the interview, the question hub covers the five question types, and the STAR structure covers the behavioural answers. If your instinct is to deflect the weakness question and you cannot tell whether your answer lands, that is exactly what a mock interview is for — or work through it in the self-paced interview preparation course.