How to Answer "What's Your Greatest Weakness?" in an IB Interview

"What's your greatest weakness?" is the question most candidates dread, and it's easy to see why. It feels like a trap. Admit something real and you worry you've just talked yourself out of the offer. Dodge it with a polished non-answer like "I just care too much" or "I work too hard," and the interviewer has heard the same line a dozen times before lunch. Either way, it seems like you lose.

Here's the reframe that gets you out of the trap. The interviewer doesn't actually care that much about the weakness itself. What they're testing is whether you can see yourself clearly, whether you can own a flaw without falling apart, and whether you do something about it. Name something real, take responsibility for it, and show you're actively closing the gap, and you've demonstrated self-awareness, maturity, and a growth mindset, all of which matter more than the weakness itself. Get that right and the specific weakness you pick barely registers.

This article walks through the whole thing: what the question is really probing, how to choose a weakness that's honest without being disqualifying, the simple structure that works every time, four worked examples broken down line by line, and the pitfalls that sink otherwise strong candidates.

What this question is actually testing

The weakness question belongs to a family interviewers think of as "simple" behavioral questions. They're short and direct, and your answer should run somewhere between 20 and 70 seconds. Don't let the word "simple" trick you into treating it as low-stakes. The goal of every question in this bucket is to figure out whether you're a genuine fit for the desk and, bluntly, whether you're someone they'd want to sit next to at 2 a.m. and not find weird.

The weakness question does one specific job inside that goal: it's the cleanest read they get on your self-awareness. Think about what your answer gives away. If you claim you don't really have weaknesses, you've shown you can't see yourself clearly, which is a real problem in a job built on taking feedback and revising your work ten times before it's right. If you confess something that would wreck your ability to do the work, you've shown poor judgment about what the role even demands. But if you name something true, own it, and walk them through how you're fixing it, you've shown exactly the trait that makes a junior worth training.

That's why the question trips so many people up. They treat it as a confession to survive rather than a chance to show how they think. The candidates who do well aren't the ones with the most flattering flaw. They're the ones who prove they can spot a weakness in themselves and systematically work on it, because that is precisely the quality a bank is buying when it hires an analyst.

How to choose the right weakness

The instinct most people have is to pick a "safe" weakness that won't scare the interviewer. The instinct is correct. The execution is usually where it goes wrong. Start from the core rule:

Choose a real weakness, but not one that would hurt your job performance. Don't say "attention to detail" or "work ethic." Pick something credible yet non-critical, like trouble delegating or getting too caught in the details.

Two things have to be true at the same time. The weakness has to be real, because a fake one is easy to smell and defeats the entire purpose of the question. And it has to be non-critical, meaning it won't make the interviewer doubt you can actually do the job. A first-year analyst's whole product is precise, accurate work delivered on a tight deadline. So the off-limits answers are the ones that strike directly at that. Telling an interviewer your weakness is "attention to detail" or "work ethic" is telling them you can't be trusted with the fundamentals of the role.

The "attention to detail" trap

This is the spot where people get tangled, because detail shows up on both the banned list and, in a different form, the safe list. The distinction is the whole game, so be precise about it.

Newton's 3rd Law: pick the opposite force

Here's a mental model that makes the choice almost automatic. Newton's 3rd Law says that for every action there's an equal and opposite reaction. The best weaknesses for an IB interview behave the same way: they're the equal and opposite "force" to a classic banker strength. A great analyst is driven, so the opposite force is impatience, or overloading yourself with work. A great analyst is precise, so the opposite force is getting too caught in the details. Pick a weakness that rides on the back of a real strength and you've named something believable that still signals you carry the underlying trait the job needs.

That logic gives you a reliable shortlist. Any of these work well:

• Impatience
• Difficulty dealing with ambiguity
• Hesitant to ask for help
• Frequently overload yourself with work
• Too detail-oriented
• High-intensity person

Notice what they have in common. Every one is the shadow side of something a bank wants. Impatience is drive with the brakes off. Overloading yourself is commitment that hasn't yet learned to say no. Being hesitant to ask for help is self-reliance taken a step too far. None of them makes an interviewer question whether you can do the work. Each makes you sound like someone who already has the raw material and is sanding down the rough edges.

Don't disguise a strength

One warning, because the opposite-force logic gets misread constantly. "Pick the flip side of a strength" is not the same as "pick a strength and pretend it's a weakness." There's a world of difference between "I overload myself, and here's the time it blew up in my face" and "my weakness is that I just work too hard." The first is a real weakness with a real cost. The second is a humble-brag the interviewer has heard a hundred times, and it reads as exactly what it is: a candidate dodging the question.

This is also why your weakness answer and your strengths answer need to stay in their own lanes. The greatest-strengths question is its own subject with its own approach, and it deserves separate preparation. Don't recycle one as the other.

How to structure the answer: state, example, fix

Once you've chosen your weakness, the structure is simple, and it never changes:

1. State the weakness. Name it plainly, with no hedging.
2. Give a quick example. One concrete moment where it actually cost you something.
3. Spend most of your answer on the fix. More than 40% of your airtime should be on how you're actively improving.

That last point is the one most candidates get backwards. They burn the bulk of the answer explaining and justifying the flaw, then tack on a hurried "but I'm working on it" at the end. Flip it. The weakness and the example are setup. The fix is the payload. The interviewer wants to watch you in growth mode, not confession mode, so give them more of the part that shows growth. If less than half your answer is about what you're doing to improve, you're telling the wrong story.

Worked examples, annotated

The four answers below are modeled on real answers from students who sat in the same chair you're about to. Read them for the structure and the moves, not the exact words. The goal is not to memorize someone else's story; it's to see the framework in action so you can build your own version on top of it. An answer in your own voice, with your own example, will always beat a borrowed script you're reciting from memory.

A single weakness: getting lost in the nitty-gritty

I would say my greatest weakness is getting lost in the nitty gritty. One example would be a take-home overnight stock pitch, with a number of moving parts, the investment thesis, valuation, risk and catalysts, I spent almost the entire night being as exact as I could with the valuation and did not dedicate much time on the investment thesis / catalyst, which are arguably integral to any pitch. After not sleeping that night and putting out a subpar pitch in my opinion the next day, I took some time to think on what I could've done better in those situations and how I can look back at the bigger picture frequently. Since then, in case competitions, pitches, assignments, I always think about, who is the end user of this product and what matters to them. And I think for the context of the stock pitch it would be why we want to invest in this company and how the market has mispriced it. So taking frequent steps back and remembering what my end goal is and what I am doing has helped me bridge that gap and achieve a fine balance between being detail oriented and looking at the big picture.

Watch the shape. The weakness is stated in the first sentence, no throat-clearing. The example is a single vivid moment, the overnight pitch, and it carries a real cost: no sleep and, in the candidate's own words, a "subpar pitch." That admission is what keeps "I'm too detail-oriented" from sounding like a brag. Then look at the back half. The majority of the answer is the fix, a concrete habit ("who is the end user of this product and what matters to them") that the candidate now applies across case competitions, pitches, and assignments. By the end you're convinced this is a person who found a flaw and built a system to manage it.

A single weakness: trouble delegating

One weakness I've worked on is delegation. During a past private equity internship, I was tasked with leading a project among six interns. Not knowing their strengths, I held back from assigning meaningful tasks and ended up doing most of the work myself — which led to late nights, a rushed deliverable, and a missed deadline. I realized the issue wasn't just lack of trust, but also not taking the time to understand my teammates. Since then, I've made a point to build that trust early, understand people's strengths, and delegate more effectively — something that's really paid off in my current internship, where the group work has been stronger because of it.

This is the tightest version of the framework. State the weakness, delegation. One example with an unmistakable cost: "late nights, a rushed deliverable, and a missed deadline." A missed deadline is a serious admission, and that's exactly why the answer lands; the candidate isn't hiding behind a costless flaw. The fix is specific and shows learning beyond the surface ("the issue wasn't just lack of trust, but also not taking the time to understand my teammates"), and it closes with evidence the change worked. Short, honest, complete.

When they ask for more than one

Sometimes the interviewer asks for two or three weaknesses. The move is to give each one its own mini-version of the structure, name, quick example, fix, while still spending most of your time improving rather than confessing. Here's the model:

I'd say my greatest weaknesses are – focusing too much on the details, not voicing my opinion often enough, and my hesitancy to delegate…

For example, when I was working on my investment fund, I sometimes spent too much time perfecting the formatting of a pitch deck after just the first draft, even though I could've added more meaningful insights instead. Taking a step back this year as a portfolio manager helped me better understand the broader purpose of each deliverable, and I've become much more intentional about how I manage my time and prioritize impact over polish.

In terms of voicing my opinion, going into NBIM (Government Pension Fund of Norway), I wasn't sure if I should be sharing my perspective on deals especially as I was working directly with seniors and MDs.

However as I started working on leaner 4-5 person deal teams, I realized how as an intern I'm often closest to the actual numbers and data, so it's really important to also share my key takeaways with the team which is something I often tried to do where I saw appropriate.

Lastly, I've realized my hesitancy to delegate often ends up hurting team efficiency, especially when I'm in a leadership position.

As I became a portfolio manager on my school's investment fund and at first I really struggled to let go of the slide creation as I felt there were small details I would want to fix and ended up taking on a much heavier workload.

However, I actually saw that this was resulting in poor exposure for the juniors I really tried to lead with more patience and built trust in my team where I could allow them to have a longer runway which I think is super important.

Three weaknesses, and not one of them is a disguised strength. Each gets the same treatment in miniature: a clear name, a concrete situation, and a specific change. The detail strand pays off ("prioritize impact over polish"). The speaking-up strand resolves into a reason and a habit. The delegation strand names a real cost, poor exposure for the juniors, and a fix, leading with more patience and a longer runway for the team. Even stacked three deep, the weight still sits on the improvement, not the flaw. That's what keeps a multi-weakness answer from turning into a pile-on of negatives.

Another register: hesitating to speak up

One weakness I've been working on is hesitating to speak up early in group settings to clarify my approach before starting a task. In my last internship, I'd often jump straight into the work without confirming my initial plan — and while the effort was there, it sometimes created inefficiencies or avoidable rework. I've since realized that a quick check-in upfront, especially for complex or unfamiliar tasks, can save time and give the team more confidence in the process. I've been applying this in group projects and in my role as a student club exec, making a habit of voicing my thinking early and aligning before diving in — and I've noticed a real difference in both my efficiency and team communication.

This shares some DNA with the "voicing my opinion" thread above, but it's a distinct register worth having in your back pocket: hesitating to confirm a plan before diving into the work. The cost here is "inefficiencies or avoidable rework," which is exactly the kind of thing that frustrates a deal team. The fix is admirably concrete: a quick check-in upfront on complex or unfamiliar tasks. It reads as someone who diagnosed a specific behavior and replaced it with a specific habit, which is the whole point.

Common pitfalls to avoid

The costless humble-brag. This is the single most common failure. The candidate names a "safe" weakness ("I'm a perfectionist," "I work too hard") and never attaches a real consequence. With no cost, the answer is just a strength wearing a disguise, and interviewers discount it instantly. The fix is the cost. If you can't point to a specific moment your weakness actually hurt an outcome, you've picked the wrong weakness or you're hiding from the question.

Dwelling on the flaw, rushing the fix. Plenty of candidates choose a fine weakness and then spend 80% of their airtime explaining and excusing it, with the improvement crammed into a final sentence. That inverts the whole point. The interviewer wants to see growth, so most of the answer has to be growth. More than 40% on the fix is the floor, not the target.

Naming a disqualifying weakness. Honesty is good, but not when it tells the interviewer you can't do the job. A weakness in accuracy, reliability, or work ethic isn't "self-aware," it's a reason not to hire you. Stay on the opposite-force shortlist, where the weakness is the back side of a strength the bank actually wants.

Reciting it like a script. Because these examples are modeled on real answers, it's tempting to memorize one and deliver it verbatim. Don't. A memorized answer sounds memorized, and it collapses the moment an interviewer asks a follow-up. Internalize the structure, plug in your own real weakness and your own real example, and the answer will hold up under any question because you actually lived it.

Related questions worth preparing

The weakness question doesn't sit in isolation. Two of its closest cousins deserve preparation right alongside it.

The first is the greatest-strengths question. It's the mirror image, and the two are tightly linked, which is exactly why people blur them. Keep them separate: strengths has its own approach and its own examples, and the surest way to fumble both is to treat the weakness answer as an upside-down strengths answer.

The second is "Why is your GPA so low?" Treat that one almost exactly like a weakness question. The same improvement-story arc powers it: own it without excuses, explain the root issue briefly, then spend most of your time on what you changed and the tangible results that followed. If you can nail the weakness structure, you're most of the way to nailing the GPA question too.