Arca
Explore the Finance interviews hub and the finance careers guide.
Ask 2 or 3 questions at the end of an interview, and bring 5 so you still have some left if they cover a few along the way. Make each one about the seat: the work, the team, and what good looks like by month 3. Then ask about next steps. This page is part of the finance interviews guide.
The end of the interview is the only part you steer.
MIT's career office says you're "expected to have several questions to ask your interviewer(s) when they give you the opportunity, usually towards the end of the interview."
How many questions should you ask at the end of an interview?
Ask 2 or 3, and prepare 5. Interviewers often answer one or two while they talk, and the extras mean you never say you have none. The University of Houston career centre says many employers "automatically reject candidates who don't have questions because they don't seem sufficiently interested in the role."
Binghamton University's career centre sets the same number: "Aim to have at least 5 questions prepared!"
Put them in the order you'd cut them.
Save one for the end. The Houston career centre suggests two wrap-up questions: "What are the next steps? What is your timeline for making a decision?"
What does the interviewer learn from your questions?
Three things. Whether you've thought about the seat or only the company. Whether you already think like someone doing the job. And whether you can hear something awkward about yourself without getting defensive. A question that does none of those is filling time, and they can tell.
A lot of finance work is asking the question nobody in the room has thought about yet. When the business says it's hiring more salespeople, my first question is whether there's enough pipeline coverage for them.
Point that same habit at the interviewer, and they get to see how you'd think on a Tuesday in month 2.
The best question gets the hiring manager explaining their philosophy. A posting is written wide to catch good candidates. The hiring manager wants someone specific, with traits they can't put on paper but can hear in ten minutes.
In one final round, the hiring manager asked how I'd approach my first 30, 60 and 90 days. What landed wasn't the plan itself. It was that my philosophy matched hers: "that's pretty much how I would do it."
So flip it. Instead of asking whether the role is a backfill, ask: "What's something new you're looking for from the next person to fill this role?" Senior people like to talk about how they see things. Let them. It's also how you learn the company, which generic questions never get you.
One hiring manager answered with "we need this person to figure out what to do." They never said ambiguity, but that's what it meant. I spent the rest of the interview showing I could take a goal and work out the steps, as long as we agreed on the goal.
What should you ask about the work itself?
Ask where the numbers go, when the calendar gets tight, and what finance is still trying to fix.
Questions about the work
| Ask | What the answer tells you |
|---|---|
| What does the close or planning calendar look like in a hard month? | How much of the job is deadlines, and whether the calendar is realistic. |
| Where does the forecast usually break? | Which assumptions nobody owns yet. |
| Which reports does leadership actually read? | Whether your work gets used or filed. |
| What problem is finance still trying to fix here? | Most of your first year, in one answer. |
| What changed in the last forecast, and why? | How decisions get made, and how often they move. |
There's always a fundamental problem in finance that the company is still trying to fix, and that's my answer to why FP&A.
Turn it into a question, because whatever they name is probably what you'd be hired to work on.
Ask about the close even for an FP&A seat. Before a close, I want everything I need to finish it in hand.
So ask what the team usually waits on, because that's where the late nights come from.
Ask about the last forecast, not only this one. The reason a number moved tells you as much as the number.
Skip "what does a typical day look like?" It gets a rehearsed answer. Ask what a hard week looks like, and you'll hear about the real work.
Switching industries? Finance is finance, so ask about what you're actually doing the finance on.
What should you ask about the team and the manager?
Ask how the team is measured, who it serves, and how the manager develops people. The answers also tell you whether the manager has thought about growth, or only about filling a gap.
- How is this team measured, and who decides that?
- Who does this seat work with most outside finance?
- How and when would my performance be evaluated? That one comes straight from MIT's sample list.
- What do the people who've done well here have in common?
Then ask how stretch work gets handed out.
Not every analyst wants it, and a team needs the people who don't. We also need worker bees.
If you want the harder work, say so near the end, because spotting who wants more is hard from the hiring side.
Which questions show you could do the job?
Ask the questions you'd ask in your first month. What should this seat have changed by day 90? Where does the data come from, and who fixes it when it's wrong? What's already been tried? Questions like these make the interviewer picture you in the seat, which is the point of the whole round.
Have a 30-60-90 day plan sketched before you ask about the first 90 days. If they turn it around and ask what you'd do, you want an answer ready.
That same first-move line is how a strong answer to why they should hire you ends.
"What's already been tried?" does more work than it looks. The best analysts I've hired asked about the nuances of a problem before they went near a fix. Asking about the history shows that instinct on day zero.
What is the best closing question to ask?
Ask: "Is there anything about my background that gives you pause?" It gives the interviewer permission to say what's worrying them while you're still in the room. The worry exists either way. If you don't ask, it goes into the debrief without your side of it, and nobody will call you to hear it.
It can feel awkward. Three things help.
- Ask it last, after your real questions, so it doesn't sound like fishing for a compliment.
- Say it plainly. "Before we finish, is there anything in my background that gives you pause for this role?"
- Answer once, then stop. Give the fact and one example, then let them respond. Don't argue with the concern.
If they say no, thank them and move to next steps.
If they say yes, that's the most useful minute of the interview.
Which interview questions should you ask each interviewer?
Match the question to what each person actually knows. A recruiter knows the process. The hiring manager knows the gap. A peer knows the real week. A senior leader knows where the business is going. Asking a recruiter how the forecast model is built wastes both of your time.
Who you're talking to
| Interviewer | Ask them |
|---|---|
| Recruiter | What the rounds are, who's on each one, the timeline for a decision, and the pay range. |
| Hiring manager | What this seat has to change in its first year, and what finance is still trying to fix. |
| Peer on the team | What a hard week looks like, and what everyone waits on at close. |
| Senior leader | Where the business is going next year, and what they need from finance to get there. |
Panels are harder, because two people may want different things.
Don't try to please both of them at the same time with your answers, and let them decide on your true answer.
Your questions work the same way: ask each person something only they can answer.
Do the questions change by role?
Yes. The frame stays the same, but the work you ask about changes. Analysts ask about data and reporting, FP&A asks about the planning cycle, controllers ask about the close and controls, and managers ask about people and ownership. Pick the hardest recurring moment in the role and ask about that.
- Financial analyst: where does the data come from, and how much of the week is building versus explaining? More in the financial analyst guide.
- FP&A: when does the plan get set, and who owns the forecast after that? The FP&A interview questions page has more.
- Controller or accounting: how many days does the close take today, and what do the auditors keep coming back to? See controller interview questions.
- Finance manager: which decisions does this seat make alone, and which go up a level? See finance manager interview questions.
What should you not ask at the end of an interview?
With the hiring manager and the panel, skip pay, time off and perks before they raise them or an offer is close. The recruiter screen is the place to confirm the pay range, so a deal-breaker doesn't wait for the offer. Also skip anything their website already answers, and questions that end in yes or no. Each sends a signal you didn't mean: wrong priorities, no homework, or no curiosity about the work.
One question, two ways
Do you use Excel here?
Which models does this team rebuild every cycle, and which ones does it trust?
Don't ask how you did, either. Ask what happens next.
What if they already answered all your questions?
Say so, and show you were listening. "You covered most of what I had, especially the close calendar. One thing I'd still like to know is..." Then follow up on something they said in the room, which proves you heard them in a way no prepared list can.
This is why 5 beats 3.
Sometimes the room hands you a better question. In one final round, the CFO mentioned he was five weeks into the job, brought in through an acquisition from a smaller company. I scrapped most of my questions. I asked how it was dealing with two bosses, what was different from running finance at a smaller company, and what problems he saw that needed fixing. None of it was about the role. All of it got him talking.
Practising without a timer helped me understand my whole thought process, and an answer I don't talk through naturally never feels like my own.
What should you prepare before the interview?
Write 5 questions, note what each answer would tell you, and put them in the order you'd cut them. Add the pause question and a next-steps question. Afterwards, log what you learned and the next step in your job application tracker.
Your end-of-interview questions
- One question about the work: the close, the plan or the forecast.
- One about the team and how it's measured.
- One that puts you in the seat at day 90.
- The pause question, asked last.
- Next steps and the timeline for a decision.
In a final round, keep the same list but lean toward the future: what the first year should deliver, and what would make the hiring manager glad they picked you a year from now.
The last ten minutes are yours. Use them.
