"Why this firm?" How to answer without lying

It turns up in the application form, in the HireVue, and again in the final round, and it is the question people prepare last. Part of the reason it feels hard is that everybody knows the honest first draft: you applied because it is a good firm, the pay is good, and it was on the list. You cannot say that, so you say something else instead, and the something else is usually worse than saying nothing.

Here is the useful reframe. Nobody is asking you to prove affection for a company. Why this firm is a test of whether you did any work before you turned up, and that is a question you can answer completely honestly.

— the four answers they hear all day

The culture. "I met your team at an event and everyone was so friendly and down to earth."
The prestige. "Your reputation in the market speaks for itself."
The size. "A lean team means I'd get real responsibility early."
The training. "Your graduate programme is really well structured."

None of these is untrue. They are just interchangeable. Every one of those sentences works word for word for the firm across the road, and your interviewer knows it, because an hour ago they heard the identical sentence from someone who applied to both of you.

If your answer also works for their closest competitor, it is not an answer. It is a placeholder.

— the shape of an answer that works

Three parts, in this order, and the order matters:

one specific, checkable thing this firm does
how you came to know it, ideally because of something you did
what you want out of it

The middle part is the one everybody drops, and it is the only part that stops the answer being a press release read aloud. Anyone can find out that a firm is independent, or strong in a sector, or structured around coverage teams. The thing that lands is I know this because I spent three weeks on it.

— where the specific bit comes from

You need one. Not five. Places it reliably hides:

a deal, mandate, case or product launch from the last twelve months
how the firm is actually built: the coverage model, which sectors sit together, where the desk reports
something they published, whether that is a research note, the annual report, or an engineering blog
a person you actually spoke to, which is the strongest of all because the next candidate cannot google it
the honest difference between them and the obvious alternative

That last one is the fastest route if you are stuck. Pick their nearest rival and write down three real differences. Independent advisory against a balance sheet bank. Sector specialist against generalist. Partner owned against listed. Founder led against a fifteen year old product. Once you can name the difference, you can explain why you picked the side you picked, and that explanation is automatically not transferable.

— the same answer, twice

✏️ Weak vs specific

Weak: "I want to work here because of your outstanding reputation in M&A and your collaborative culture. I've always been passionate about finance and I know I'd learn a huge amount from your team." Specific: "You're one of the few advisers here with no balance sheet, so the advice isn't being sold next to the financing. I got interested tracking the [defence] last autumn for a valuation project, and the sell side arguments were the part I kept rereading. I want to learn somewhere the advice is the entire product."

The second one is not better because it is longer, because it is barely longer. It is better because it could only have been said by someone who chose this firm over a specific alternative, and it hands the interviewer something to ask about.

— which is also the trap

Whatever you claim, the next question is about that claim. Say you followed a deal and you will be asked what you made of it. Say you read their research and you will be asked which piece. Say you spoke to someone on the team and you had better be able to say what they told you.

So the rule is simple: only claim what you can defend for two more minutes. One thing you genuinely understand beats four you skimmed the night before, every single time, and the difference between the two is visible within one follow up question.

⚠️ Ways people get caught

Naming a deal you cannot describe. "What did you think of the price?" ends it. "I read your annual report." Which part. There is always a follow up. Citing a conversation that did not happen. The teams are small and they talk. Praising a team that got wound down last year. Check the date on everything. Quoting their own marketing back at them. They wrote it. They know.

— what if you do not have a strong reason

You are allowed to be early in your understanding of an industry. What you are not allowed to be is vague about it. "I don't have a ten year story about this firm. What I do have is this one thing I went and looked at" is a perfectly good answer, delivered without apology.

And if you genuinely cannot find a single specific thing to say about a firm after twenty minutes of looking, treat that as information rather than a writing problem. Either you have not looked properly, or this application is filler, and your time belongs to the ten firms you can actually answer for.

— how long it should be

Spoken, forty five to sixty seconds. Written, about 150 words. Longer than that and you sound like you are either stalling or reciting, and both readings cost you. The specific thing, how you know it, what you want. Then stop talking, which is harder than it sounds and does more work than another sentence would.

— the test before you walk in

Take your answer and cover up the firm's name. Read it back, and drop a competitor's name into the gap.

If it still holds together, you have not answered the question yet. It is the same test that separates a real cold email from a mail merge, and it fails for the same reason: nothing in it could only have been written about them.