Strengths and Weaknesses: Answers That Don't Sound Rehearsed

Almost every Arabic and English article on this question prints the same three answers: perfectionism, working too hard, and caring too much about the work. Interviewers hear those several times a day. When they do, they do not learn about your weakness — they learn that you googled the question the night before.

This post gives you a method for picking a weakness that is real, safe and creditable, twelve worked examples across role families, and a short list of weaknesses that will genuinely end the process for certain Saudi roles. For the wider set of questions, see the Saudi interview guide.

Quick answer

• Strengths: name two, each with one piece of evidence and a number.
• Weaknesses: name one real gap that is adjacent to the job, not central to it.
• Every weakness answer needs three parts: the gap, the cost it caused once, and the correction you already started.
• Retire perfectionism, “I work too much”, and “I’m too detail-oriented”.
• Do not confess anything that is a core requirement of the role.

What is the interviewer actually scoring?

Not the weakness. The answer is scored on self-awareness and corrective behaviour — can this person see themselves accurately, and do they act on what they see?

That is why “I have no weaknesses” fails hard, and why “I’m a perfectionist” fails softly but still fails. Both give the interviewer nothing to score. Meanwhile a candidate who says “I was weak at pushing back on unrealistic deadlines, it cost us a rushed delivery last year, so now I put a written scope confirmation in before I accept a date” has just demonstrated three things: honesty, an understanding of consequence, and a system.

Definition worth holding onto: a disqualifying weakness is one that overlaps with a core requirement in the job description. A safe weakness is a real gap adjacent to the role — something that touches your work occasionally but is not what you were hired to do.

The selection method

Work through this in order. It takes about fifteen minutes and produces an answer you will not need to memorise, because it is true.

1. List three things you actually avoid at work. The tasks you postpone, the ones you hand to a colleague, the ones that make you close the laptop. Be honest with the page; nobody else reads it.
2. Check each against the job description. Cross out anything that appears in the core responsibilities. If the role is “financial reporting” and your weakness is spreadsheets, that one stays in the notebook.
3. Find the incident. Pick a specific time this gap cost something — a delay, a rework, an awkward meeting. One incident, small enough to describe in two sentences.
4. Name the correction and when you started it. A tool, a habit, a course, a check you now run. It must be something you already do, not something you plan to do.
5. Say it out loud in under 45 seconds. If it runs longer, you are over-explaining, which reads as defensive.

Weak: “My biggest weakness is that I’m a perfectionist. I keep working on things until they’re perfect, which sometimes takes extra time, but I think that’s good for quality.”

Strong: “I used to under-communicate while I was still working on something. On a report last year I went quiet for four days because it wasn’t finished, and my manager assumed it was stuck. Since then I send a two-line status on Sunday and Wednesday whether or not there’s progress. It has stopped that particular problem completely.”

Same length. The second one gives the interviewer something to write down.

Twelve worked examples by role family

Use these as patterns, not scripts — the incident must be yours.

Role family	Safe weakness	The correction that makes it work
Accounting / finance	Reluctant to chase other departments for missing documents	Now sends a fixed reminder schedule with a named deadline rather than waiting
Sales	Over-invested in large accounts and neglected the mid-tier pipeline	Blocks a fixed half-day weekly for pipeline below a set deal size
Engineering (site)	Slow to escalate a subcontractor problem, hoping it would resolve	Escalates anything that slips two days, in writing, with a proposed fix
Software	Went too deep on refactoring before shipping	Timeboxes cleanup and raises anything beyond the box as a separate ticket
HR	Avoided difficult conversations with hiring managers about unrealistic profiles	Opens every intake meeting with a market-reality slide before taking the brief
Marketing	Weak on the analytics side relative to the creative side	Finished a measurement certification and now writes the dashboard spec first
Customer service	Took escalations personally and it showed in tone	Uses a fixed de-escalation script and a two-minute reset between hard calls
Operations / logistics	Kept too much process knowledge in own head	Documented the three critical flows so cover is possible during leave
Project management	Under-estimated durations to keep stakeholders happy	Now presents ranges with named assumptions instead of a single optimistic date
Teaching / training	Struggled to cut material when a session ran long	Builds every session with a marked “drop first” third
Data / analysis	Presented the full analysis instead of the decision	Leads every deck with a one-slide recommendation and moves detail to an appendix
Fresh graduate	No experience of working under a real commercial deadline	Took a Tamheer placement / freelance work specifically to get that exposure

Two things to notice. Every weakness is adjacent, not central — the accountant’s weakness is interdepartmental chasing, not reconciliation. And every correction is a mechanism, not an intention: a schedule, a template, a timebox, a document. Mechanisms are credible; “I try to be more aware of it” is not.

Weaknesses that are genuinely disqualifying

Some honest answers should stay honest and stay unsaid. These are not the ones to volunteer, because they collide directly with a core requirement:

• “I’m not good with numbers” in any finance, procurement, audit or analyst role.
• “I don’t like dealing with people” in sales, HR, customer-facing, or teaching roles.
• “I struggle with English” for any role where the job description lists English as a requirement — and where the interview is being partly conducted in it.
• “I’m not punctual” or anything touching attendance, for shift, site, clinical or operations roles.
• “I don’t handle pressure” for anything with a delivery deadline, which is most jobs.
• “I can’t take criticism” in any role that sits inside a review cycle, which is all of them.
• “I have trouble with confidentiality” or anything adjacent to it, in HR, legal, finance and healthcare. This is not a weakness, it is a disqualification.

If one of these is genuinely your biggest gap and it is central to the job you are applying for, the answer is not a better script. It is either a different target role or a real plan to close the gap before you apply. That is a strategy question, not an interview question — changing direction deliberately is a more useful frame than trying to phrase it away.

How to answer the strengths half

The strengths question is easier and people still waste it, usually by listing adjectives. Two rules:

Pick strengths that appear in the job description. Read the posting and find the two capabilities it repeats. If it says “coordinate with multiple stakeholders” three times, coordination is one of your strengths that day.

Attach evidence, not adjectives. Every strength needs a fact behind it.

Weak: “I’m a strong communicator, I’m organised, I’m a fast learner and I work well under pressure.”

Strong: “Two things. First, coordination across teams — in my last role I ran the weekly interface meeting between engineering, procurement and the client, and that’s where most of our schedule risk got caught early. Second, I pick up systems fast; when we moved to a new ERP I was the one training the rest of the team within about six weeks.”

Two strengths, both evidenced, roughly 40 seconds. If the interviewer wants more they will ask, and then you switch into a STAR-structured story about one of them.

One warning: your strengths answer should not contradict your opening. If you told them in your opening answer that your edge is process design, do not name three unrelated strengths ten minutes later. The interviewer is building one picture of you across the whole session.

Delivery details that change the score

• Do not smile through the weakness. Nervous laughter while admitting a gap makes it sound like a joke answer. Say it flatly, like a fact.
• Do not stack three weaknesses. One is the answer. Volunteering a second signals anxiety.
• Do not end on the weakness. End on the correction, then stop. The last sentence is the one that stays.
• Do not use the word “but” to cancel it. “I’m disorganised, but actually that helps me be creative” reads as spin. The pattern is gap → cost → correction, no reversal.
• Prepare the Arabic version natively. Translated self-criticism sounds harsher in Arabic than it does in English. “كنت أتأخر في التصعيد” is calm; a literal translation of “I have a serious problem with” is not what you meant.

If you are asked a variation — “what would your manager say you need to improve?” — the same answer works, but attribute it: “In my last review, the point that came up was…” That framing is often easier to deliver and sounds more credible, because it implies a real conversation happened. The other high-frequency questions in the same set are covered in common Saudi interview questions.

The hardest part of this question is not phrasing — it is remembering the incident under pressure. Rehearsing out loud against something that pushes back is what fixes that. In TrueSira the AI interview practice runs these questions against your own Master Profile, so the follow-ups are about your actual history rather than a generic script, and you hear yourself answer before it counts. Get started free.

FAQ

What is a good weakness to say in an interview?

A real gap that is not central to the job, paired with the correction you have already started. The correction is the part being scored: a weakness with no visible action behind it reads as an admission, and a weakness with nothing real behind it reads as a script. Adjacent, specific, corrected — that is the whole formula.

Can I say perfectionism is my weakness?

No. Perfectionism, “I work too hard” and “I care too much” are the three most repeated answers in interviewing, and most interviewers now treat them as evidence that the candidate did not prepare or is avoiding the question. Even if perfectionism genuinely is your issue, describe the behaviour instead — for example, over-polishing drafts past the point of usefulness — and what you changed.

How many strengths should I mention?

Two, three at most, each with one short piece of evidence attached. A list of five adjectives with no proof scores lower than a single strength backed by a specific result you can describe in thirty seconds. Choose strengths that appear in the job description rather than the ones you like best about yourself.

Should my weakness relate to the job?

It should be adjacent to the job, not central to it. A weakness in something you will never do sounds like a dodge and the interviewer will ask again. A weakness in the core requirement of the role is a legitimate reason to reject you. The safe zone is a real gap that touches your work occasionally without being what you were hired to do.

What if I genuinely cannot think of a weakness?

You have one; you have just not named it. Look at your last performance review, the tasks you keep postponing, and the ones you quietly hand to a colleague. Anything you avoid is a real answer waiting to be phrased. Saying “I don’t really have one” is the single worst available answer, because it fails the self-awareness test outright.

Is it a red flag to admit a weakness honestly?

Not if it is adjacent to the role and paired with action you have already taken. Interviewers use the question to test self-awareness, not to find a reason to reject you. What actually raises a flag is refusing to name a weakness, or naming an obviously fake one, because both suggest the person cannot be given feedback later.