How to Answer "What Are Your Strengths?" in Banking

Introduction

"What are your strengths?" is the softest-sounding question in an investment banking interview, which is precisely why it eliminates people. It arrives early, it is phrased as an invitation, and it feels like the one moment where you can talk about yourself without hedging. Candidates who have rehearsed a DCF for six weeks answer this one off the cuff, produce three adjectives, and hand the interviewer nothing worth writing on the scorecard.

The interviewer is not curious about your personality. They are running a comparison against the job: what a first-year analyst has to do at 11pm on a Thursday when the VP sends twelve comments on a deck. "I'm a strong communicator and a hard worker" says nothing about that job. "I catch my own mistakes before someone else does, and here is the time I caught one" says almost everything.

This post covers what the question is really scoring, which strengths carry weight in banking and which are dead on arrival, a three-move answer framework, four sample answers for four different backgrounds, how the question pairs with weaknesses and with "what would your manager say about you", and the follow-ups that separate a rehearsed answer from a real one.

Banks do not ask this question to be nice to you. Fit interviews at every large firm run on some version of a scoring rubric, and the strengths question is one of the cheapest ways to populate it. In roughly ninety seconds the interviewer learns whether you understand the role, whether you can support an assertion with evidence, and whether you can talk about yourself without either shrinking or overselling.

Behavioral interview

The portion of a job interview that evaluates how you have actually worked in the past, on the theory that past behavior predicts future behavior. Questions typically begin with "tell me about a time" or ask you to characterize yourself, and the interviewer scores the specificity and relevance of your evidence rather than the adjectives you choose. In investment banking, the behavioral or fit round usually sits alongside a technical round and often carries equal weight in the final decision.

That scoring instinct is not a banking quirk. A 2022 re-analysis of decades of personnel selection research, published in the Journal of Applied Psychology, found that structured interviews rank at the very top of selection methods for predicting job performance, ahead of cognitive ability tests. Firms have internalized that finding. The more structured the interview, the more your answer is being graded against a written standard rather than against whether the interviewer likes you.

They are testing whether you know the job

The most revealing part of your answer is which strength you pick, before you say a word about proving it. Choosing precision on repetitive work signals that you know an analyst spends most of the first year producing materials that have to be right. Choosing strategic vision signals that you are describing a job that does not exist at your level. Interviewers read the selection itself as evidence of research, and this is where a surprising number of otherwise strong candidates give themselves away.

The same logic applies in reverse. When a candidate names a strength that is genuinely useful in the seat, the interviewer relaxes slightly, because it means the rest of the conversation can be about whether the evidence is real rather than about whether the candidate understands what they are applying for.

They are testing whether you can prove a claim

The second thing being scored is whether you treat your own claim as something requiring support. This is the same muscle the job uses constantly. An analyst who writes 12% revenue growth in a deck and cannot say where it came from is a liability. An analyst who says "I'm detail-oriented" and cannot produce a single instance of catching something is doing the same thing with themselves as the subject.

Underneath both of those, the question is a quiet test of self-perception. Candidates who claim five strengths sound unserious. Candidates who mumble one and immediately qualify it sound like they will fold the first time an associate pushes back on their numbers. The correct register is flat and factual: this is a thing I am good at, here is why I believe that, here is where it would be useful to you. Interviewers who have run a hundred of these conversations pick up the difference between confidence built on evidence and confidence built on volume within a sentence or two.

Not all true strengths are useful strengths. The filter is simple: does this trait change the quality of work a first-year analyst produces, and can it be demonstrated? Run every candidate strength through that filter before it goes anywhere near your answer.

The six that carry weight

Attention to detail is the one banks care about most and the one candidates prove least. It is not a personality trait, it is a habit: checking your own work before someone else has to, tying numbers across pages, noticing when a footnote and a table disagree. Work ethic and stamina matters because the job is genuinely long and the failure mode is degradation late at night rather than an inability to start. Coachability is the trait that determines whether your second month is better than your first, and it is why interviewers listen so carefully for how you talk about criticism.

Quantitative comfort is not the same as being a math genius. It means numbers do not intimidate you, you can sanity-check an output, and you notice when a result is implausible. Ownership is the difference between finishing the task you were given and finishing the task the team actually needed. Composure is what keeps the other five intact at 1am. These map closely to the traits the wider profile of an analyst demands, which our breakdown of what separates a top bucket analyst from an average one unpacks in more detail.

Top bucket

The highest performance tier in an investment bank's annual analyst or associate review, typically covering the strongest ten to fifteen percent of a class and driving the largest bonus, the best staffings, and the strongest support for exit opportunities. Rankings are usually built from written feedback across the deal teams you worked with during the year, which is why reliability and ownership tend to matter more to the outcome than raw technical brilliance.

Employer research outside finance points in the same direction. The National Association of Colleges and Employers reports that recruiters reviewing graduate resumes are looking for demonstrated evidence of teamwork, problem-solving and communication rather than assertions of those qualities. Banking narrows the list and raises the bar on precision, but the underlying expectation is identical: show it, do not claim it.

The ones that are true but useless

Some strengths are perfectly real and still cost you points, because they signal a misread of the job. "I'm a natural leader" invites the obvious response that you would be the most junior person on every team you join for two years. "I'm creative" runs into the reality that most of the first year is executing a defined process correctly rather than inventing a new one. "I'm passionate about markets" is not a strength at all, it is a baseline assumption; nobody applies to a banking analyst program while indifferent to finance.

Three moves, sixty to ninety seconds. The structure is deliberately boring because the content is doing the work.

Picking: start from the job, not from yourself

Most candidates build this answer by introspecting. Start from the other end. Write down what a first-year analyst on that desk actually does in a week: builds and updates models, produces and formats materials, pulls and checks data, turns comments, coordinates between people who are busier than you. Then ask which of your genuine strengths most directly improves one of those activities. That intersection is your answer.

Two strengths is the maximum, and one deeply proven strength beats two shallow ones nearly every time. If you name three, the interviewer hears a list rather than a claim, and none of the three gets enough evidence to survive a follow-up. Banks publish this advice themselves in slightly gentler language; Morgan Stanley's guidance for students preparing for interviews emphasizes understanding what people at your level actually do before you try to describe your fit for it.

Proving: one story, ending in a result

The proof is the answer. Everything else is scaffolding. Choose a story you can tell in about forty seconds, with three components: what the situation was, what you specifically did, and what happened as a result. If the story is about detail, the result should involve something that would otherwise have been wrong. If it is about ownership, the result should involve something that would otherwise not have happened.

Resist the temptation to reach for your most impressive experience. Reach for your most relevant one. A story about reconciling a messy dataset for a professor is better evidence of analytical care than a story about a leadership role in a club, even though the club role sounds grander. The mechanics of building these stories are the same ones behind a strong greatest accomplishment answer, and the same story bank serves both questions.

The final ten seconds of the answer, the connection, do the work most candidates skip. Say out loud what this strength means for the team that hires you. "That is the habit I would bring to checking a model before it goes to the client" is a sentence the interviewer can quote in the debrief. Without it, you have told a nice story and left the interviewer to work out the relevance, which is a job they will not always do on your behalf.

Naming a strength is easy; holding it up under three follow-up questions is where candidates stall: Work through behavioral prompts, brainteasers and technicals in one place, start practicing interview questions for free and find out which of your stories survive contact with a real question.

The framework is the same for everyone; the raw material is not. Here is how the same three moves look across very different profiles. Note that none of these opens the same way, and none of them uses the word "passionate."

The student with a finance internship

If you have already done a version of the job, lead with the strength that the internship most directly evidenced. You have the rare advantage of a proof point set in the actual working environment, so use it and resist the urge to also mention four other things.

Notice what that answer does not contain: no adjectives beyond the opening claim, no second strength competing for airtime, and no vague ending. It closes on the transfer.

The non-finance background

If you are a STEM major, a humanities major, or anything else outside a finance program, the mistake is apologizing for it. Your strength is usually more credible than a finance major's precisely because it was tested somewhere harder than a classroom.

A mechanical engineering major might open on the evidence rather than the label: "For two years I ran the fatigue-testing rig in a materials lab, which meant every result I logged went into a dataset three other people built conclusions on. Early on I found that our sample failure rate was inflated because we were not controlling for humidity between batches, so I rewrote the logging protocol and re-ran the affected set. The corrected data changed the conclusion of the section I was working on. What I would bring is that instinct to distrust a number until I know where it came from, which is most of what checking a model is."

That answer never uses the phrase "attention to detail," and it lands harder for it. The strength is inferred from behavior, which is exactly how the interviewer wants to receive it.

The career switcher

Switchers have the strongest raw material and use it worst, usually by framing their background as an obstacle to be excused. The correct framing is that the previous career trained something the analyst seat needs and a twenty-two-year-old will not have.

A civil engineer moving into banking through a master's program might lead with the seat's requirement: "Five years running construction packages taught me to own a deliverable that other people's schedules depend on. On one interchange rebuild I was responsible for a $60 million budget line and a change-order process that had been taking two weeks to clear. I rebuilt the approval sequence so that anything under a set threshold cleared in 48 hours, which took roughly three weeks out of the critical path. Nobody asked me to fix it; it was slowing my package down. That is what I mean by ownership, and it is the part of this job I am least worried about."

The technicals are the switcher's gap, and the work habits are the switcher's edge. Say so, briefly, and do not spend the answer defending the resume. The same reframing principle governs the why should we hire you answer, which is where a switcher's positioning usually gets its fullest airing.

The associate-level MBA candidate

At the associate level, the question shifts. The interviewer already assumes competence and is now screening for judgment, for the ability to manage down to analysts, and for whether you can be trusted in front of a client. The strengths that land are different.

The measurable result there is not the margin plan, it is that the analysts asked to work with him again. At the associate level, that kind of evidence is worth more than a deal size.

Get the complete guide: Download our comprehensive 160-page PDF, access the IB Interview Guide covering the full behavioral framework alongside every technical question set you will face.

The strengths question rarely travels alone. Interviewers use it as one leg of a triangle, and the answers are compared against each other for consistency. Preparing it in isolation is how candidates end up contradicting themselves twenty minutes apart.

Strengths and weaknesses are one answer in two parts

The most common pairing is the obvious one, and the trap is that people prepare them separately. If your strength is precision and your weakness is that you sometimes miss things when you rush, you have contradicted yourself. If your strength is precision and your weakness is that you used to over-polish work that did not need it, the two answers now reinforce each other: same underlying trait, honestly described from both sides.

Build them together. Pick the strength first, then choose a weakness from a different domain or from the same trait's known cost. The full logic for choosing a weakness that is real without being disqualifying is covered in our guide to answering the weaknesses question, and it is worth reading alongside this one rather than after it.

Strengths-based interview

An interview format that asks what you naturally do well and enjoy, rather than asking you to recount past situations. Questions sound like "what are you best at?" or "what kind of work energizes you?" and the interviewer is listening for genuine enthusiasm and consistency rather than for a rehearsed structure. Some graduate programs use it deliberately because it is harder to over-prepare than a standard behavioral interview, so answers that sound scripted stand out for the wrong reasons.

What would your manager say about you

This variant is the same question routed through a third party, and it is more revealing than the direct version because it forces you to cite external validation. The right answer quotes something real: a line from a review, a piece of feedback an associate actually gave you, the reason you were asked to do something again.

"My manager would say I was the person she stopped double-checking by August" is a far stronger sentence than any self-assessment, because it is attributable. If you have genuinely never received specific feedback, that is a preparation gap worth closing before the interview; our post on describing your role and the feedback you received walks through how to mine an internship for exactly this material.

A prepared answer that collapses under the first probe is worse than no preparation, because it demonstrates that the polish was memorized. Assume the interviewer will push once and plan for it.

"Give me an example"

If you get this follow-up, your original answer failed to include one. Take it as information rather than as an attack, and give the story you should have led with. Then, critically, keep a second example in reserve, because a persistent interviewer will sometimes ask for another instance to test whether the trait is a pattern or a one-off.

The second example should come from a different context than the first. Two stories from the same internship look like one story told twice. One from work and one from a substantial academic or extracurricular project reads as a genuine habit.

"How has that shown up under pressure?"

This is the most common serious probe, and it is a good one, because most strengths are easy in calm conditions. The interviewer wants to know whether your precision survives a 2am deadline or whether it is a fair-weather trait.

Answer with the worst version of the situation you have available: the night something went wrong, the deadline that moved, the deliverable that had to be rebuilt. Do not sanitize it. The story is more credible when it includes the part where it was genuinely difficult, and the resolution matters more than whether the situation was your fault. If you want a fuller treatment of building that particular story, our post on times you worked under pressure covers the structure in depth.

The variants worth preparing separately

"What are your three biggest strengths" is not an invitation to list three adjectives faster. Give one strength with a real proof point, then name the other two in a sentence each without stories. The interviewer asked for three; they did not ask for three equal-length answers, and depth on the first one is what they will remember.

"What makes you a good analyst?" is the same question narrowed to the job, which means the answer should skip anything not directly about producing accurate work under deadline. "What sets you apart?" is the same question widened to the competitive set, and it is really asking what the person after you cannot say. If your answer to it could be copied verbatim by the next candidate, it is the wrong answer.

The failure modes are consistent, and most of them are avoidable in an evening of preparation:

Content decides the score, but delivery decides whether the content lands. Say the strength in a flat, declarative sentence. Not "I guess one thing I'd maybe say is that I can be pretty detail-oriented," which contains four hedges before the claim arrives. Just: "I catch my own errors." The confidence should sit in the plainness of the statement, not in the volume.

Keep the whole answer between sixty and ninety seconds:

Practice it out loud rather than in your head, because the two are not the same exercise and the gap only shows up when someone is watching you. Vary the wording between practice runs; an answer that comes out identical every time has been over-rehearsed and will sound it.

Finally, watch your tense and your attribution. "I was responsible for" is stronger than "we were responsible for" when the point is what you specifically did, and interviewers do notice candidates who hide behind the team pronoun for the whole story and then claim personal credit for the result.

The strengths question is one of the few in a banking interview that you can prepare almost completely in advance, and one of the few that most candidates do not prepare at all. That asymmetry is the opportunity. While the person before you is producing three adjectives and a smile, you can produce a specific claim, a story with a number in it, and a sentence explaining what it means for the team. The interviewer will remember the second one because it is the only version they can actually write down.

Do the work in the right order. Start from what the job requires rather than from what you like about yourself. Pick one strength, or at most two. Find the story that proves it, and make sure the story ends in something that happened rather than something you felt. Then say the transfer out loud, so the relevance is not left to chance.

Prepare it alongside your weaknesses answer, not separately, and stress-test both against the follow-up you are least looking forward to. Done properly, this question stops being an awkward invitation to praise yourself and becomes what it actually is: a ninety-second window to show the interviewer that you understand the job, and that you have already been doing a version of it.