Why should we hire you? How to answer (finance examples)

Explore the Finance interviews hub and the finance careers guide.

Answer "why should we hire you?" in three parts: what the seat needs, one piece of proof for each need, and what you'd do first. Keep it to 30 to 60 seconds. Take the needs from the job posting and from anything the interviewer said earlier. It's one spoke of our guide to finance interviews.

The question sounds like it's about you. It's really about their problem.

Harvard Business Review puts it simply: "instead of starting with your hopes and expectations, you're leading with theirs."

What is the best answer to "why should we hire you"?

The best answer names two or three things the role needs, proves each one with something you've done, and ends on what you'd do first. It runs 30 to 60 seconds. It uses their words, not yours, and it doesn't repeat your resume in order.

If they want more, they'll ask. A follow-up usually means a proof landed.

What is the interviewer actually checking?

Three things. Whether you understood what the seat is for. Whether you have proof, not adjectives. And whether you listened for the last half hour. A strong answer uses something the interviewer said earlier, which shows you heard it and already know where it fits.

Most candidates answer as if the question were "why do you want this?" That gives the interviewer nothing to decide with.

HBR's advice is to flip it: "this isn't about what benefits you so much as what benefits them."

From the hiring side, it was less of a specific answer and more of an attitude. When I'm the one deciding, the yes goes to someone who expects fires and pushback and has the skills to deal with them.

A strong answer can't carry a seat that doesn't fit. One of my interviews went very well, but they wanted someone more technical, with a coding background, and I didn't get it. Good interview skills won't get you the job on their own. They're weighing whether you can do it and whether you're what the team is looking for, and sometimes that isn't your fault.

If the interviewer mentioned a messy forecast twenty minutes ago, the best answer picks that up by name. It proves you heard the problem before trying to solve it, which is what the best analysts I've hired did first.

How do you build your answer from the job posting?

Read the posting and pull out the three needs it repeats most. Write one proof next to each: a thing you did, with a number or a result. Then check that every need has a proof and every proof answers a need. Anything left over gets cut.

The Seattle Central College career centre starts the same exercise by "looking at the job description or posting."

In a model, I want every number to tie back to the source. In this answer, each claim ties back to their posting or to something they said in the room. A claim that ties to nothing is a plug, and interviewers spot plugs about as fast as reviewers do.

If a need has no proof, swap it, or own it as the part you'd learn first.

It's the same match as when you tailor your resume to a posting.

Your proofs are probably already in your story bank for behavioral questions. One sentence each is plenty.

What should you say you'd do first?

Say one thing you'd do in your first month, and make it a learning move: sit through a close, meet the people who read your numbers, find where the last forecast missed. One sentence. It shows you can picture the seat without pretending you already know how it works.

Don't turn the last beat into a full plan. Save the 30-60-90 day plan for when they ask, and give them its first line here.

I once pitched a CFO a 90-day plan they hadn't asked for, because that role was exactly the work I wanted. That pitch is where my 30-60-90 framework came from.

A first move that fixes something on day one is a warning sign, because you don't know the history yet. A first move that learns something is a promise you can keep.

Sample answers for finance roles

Each sample below follows the same build: their need, your proof, your first move. Swap in your own proof and the words from your posting. If it runs past 60 seconds, cut a clause, not a need.

A hiring manager hears a checking habit, which beats speed. The Bureau of Labor Statistics names detail oriented as a core analyst quality: "Financial analysts thoroughly examine relevant data and research to identify possible errors or risks." A candidate who can say how they'd handle a wrong number that got out is easy to trust.

FP&A proof is the story of a change. Explaining how a number moved from the last version, and why is most of the job. Pick a proof that shows it.

Controllers hire for control first and speed second. A reconciliation you own lands harder than a close you shortened.

At manager level the proof has two halves: the numbers and the people. Half an answer sounds like a senior analyst asking for a title.

Name what carries over, then what's new and what you've done about it. It's the same move as the "why this industry" answer, pointed at their needs instead of yours.

With little experience, proof can come from school, a co-op or a project, as long as it matches a need in the posting and shows how the work was checked.

How do you answer "what are your 3 strengths"?

Pick the three strengths the posting asks for most, not the three you like best. Give each one a one-line proof. Then stop. It's the same build as "why should we hire you" with the first move left off, so you can reuse the same notes.

A sample for an FP&A seat:

"Forecasting, because I've owned a quarterly reforecast and explained every change to the business. Excel and modelling, because my models tie back to the source and someone else can rebuild them. And partnering, because I sit with the operations lead every month on the budget."

A strength with no proof isn't one of your three for this interview.

Which answers won't work?

Answers about your needs, lists of traits and a recital of your resume. They all miss the question, which is about what they get. The Seattle Central guide lists "Because I need a job." as an answer that won't work, and calls "I am a hard worker." "a really trite answer."

A few more to drop:

• The resume in order. They have it. Pick the two lines that answer their need.
• The promise that nothing will go wrong. It sounds confident and reads as naive.

How is it different from "tell me about yourself"?

"Tell me about yourself" asks for your story, from where you've been to this seat. "Why do you want to work here" asks what you want from them. "Why should we hire you" asks what they get from you. Same facts, different order, different ending.

I've never actually been asked it. I get in front of it: my answer to tell me about yourself ends on why I'm good for this role and why I want it, so by the time I'm done both are answered. The pitch I use is on the finance manager page.

If they've asked the first two already, point back to one thing from earlier and spend the time on the proof.

What if they ask it first, or last?

Asked first, keep it short and general to the posting, because you haven't heard their problem yet. Asked last, use what you've learned in the interview, and name one thing they told you. The last version is usually the stronger one, so listen for material the whole way through.

When it comes early, lean on the posting and hold the first move loosely ("from what I've read, I'd start by...").

Don't memorize the samples above. Knowing the points isn't enough for me. Until I've talked it through naturally, untimed, it doesn't sound like my answer.

At the end, ask the questions that show you'd do the job. They finish the case this answer started.

Tick all five and the answer is ready before they ask.