60 Investment Banking Analyst interview questions to ask job applicants

The best investment banking analyst interview questions do two jobs at once: they test whether someone can actually build and defend a model, and they test whether that person stays accurate at 2am in week three of a live deal. Ask for the mechanics, then ask for the judgment. A candidate who can recite the WACC formula but cannot say which assumption they would attack first is not ready for a deal team.

This page gives you 60 distinct questions, grouped by what they measure, with a note under each on what a strong answer sounds like. It is written for the person running the interview, not the person preparing for one. If your panel only has 30 minutes, the scoring section further down tells you which questions to keep and which to cut.

TL;DR

• Technical fluency is the entry ticket, not the differentiator. Most shortlisted analyst candidates can walk you through a discounted cash flow model, so the separating question is which assumption they would stress first and why.
• Test accuracy under pressure directly. Deal work is long hours of detailed spreadsheet work, so ask about a mistake they caught and how they caught it, not whether they work hard.
• Use the same questions in the same order for every candidate, scored on the same scale. That is what makes two interviewers' notes comparable at all.
• Split your questions across four areas: technical skill, behavior under load, real deal exposure, and motivation. Weight them for the role you are actually filling.
• A 45-minute interview cannot measure modeling accuracy. A timed modeling or finance assessment before the interview can, which frees the panel to spend its time on judgment.
• Median pay for financial and investment analysts was 102,740 dollars in May 2025, so a slow, unstructured process loses candidates to faster banks.

What does an investment banking analyst do?

An investment banking analyst builds the financial analysis behind deals: three-statement models, valuation work, comparable company and precedent transaction analysis, and the pitch materials that go to clients. Day to day, the job is detailed spreadsheet and slide work under deadline, supporting associates and bankers on live mandates.

The formal occupation data is broader than the banking-specific title suggests. The U.S. Bureau of Labor Statistics groups this work under financial and investment analysts, reporting a median annual wage of 102,740 dollars in May 2025, employment growth of 7 percent from 2025 to 2035, and a bachelor's degree as the typical entry requirement. O*NET's task list for the same occupation code includes assessing companies as investments by examining company facilities and collaborating with investment bankers to attract new corporate clients.

Two things follow for hiring. First, the credential floor is low relative to the skill floor, so a degree screen tells you almost nothing. Second, the pay band is high enough that your process competes on speed as much as on brand. A strong candidate sitting in a three-week scheduling gap is a candidate someone else is closing.

What separates a strong analyst from an average one?

Four competencies predict analyst performance better than pedigree: modeling accuracy, valuation judgment, communication under scrutiny, and resilience across long deal cycles. Pedigree correlates with all of them, which is exactly why it is a poor filter. It tells you who had access, not who can do the work.

Testlify starts from the role rather than from a test. Map the role to competencies, each competency to evidence you can actually collect, and only then pick the method. Here is that map for an analyst hire.

Notice which rows the interview alone can serve. Valuation judgment, communication and resilience are interview work. Modeling accuracy and error rate are not, because a conversation cannot measure whether someone's circular reference breaks a model. That single split should drive how you design the loop.

What technical questions test modeling skill?

Technical questions establish whether a candidate has genuinely built models or has only read about them. Ask the mechanics first, then push one level past the textbook answer. The follow-up is where the signal is: anyone can define enterprise value, but explaining why a company's cash changes the picture separates practice from memorization.

1. Walk me through the three financial statements and how they connect. What to listen for: net income flowing to the top of the cash flow statement and into retained earnings, depreciation added back, and the balance sheet actually balancing. Hesitation here ends the technical round.
2. If depreciation increases by 10 dollars, what happens across all three statements? What to listen for: a clean walk through the tax shield and the net cash increase. This is the single most reliable filter in a technical screen.
3. What is the difference between enterprise value and equity value? What to listen for: enterprise value as the value of the operating business regardless of capital structure, and a correct bridge through debt, cash and minority interests.
4. How do you build a discounted cash flow model? What to listen for: projecting unlevered free cash flow, discounting at WACC, a terminal value, and a sanity check against trading comparables.
5. Which DCF assumption would you attack first, and why? What to listen for: terminal value, since it often carries most of the valuation. A candidate who names it unprompted is thinking like an analyst, not a student.
6. How do you calculate WACC, and where do the inputs come from? What to listen for: cost of equity via CAPM, after-tax cost of debt, market-value weights, and awareness that the beta source is a judgment call.
7. Why do you unlever and relever beta? What to listen for: stripping out the capital structure of comparable companies so you can apply the target's own structure. Many candidates know the formula and not the reason.
8. Which valuation method usually produces the highest value, and why? What to listen for: precedent transactions, because of the control premium, with the caveat that it depends on market conditions at the time of those deals.
9. How do you pick a comparable company set? What to listen for: industry, size, growth, margin profile and geography, plus willingness to defend excluding a company that looks comparable on paper.
10. Walk me through a merger model and what drives accretion or dilution. What to listen for: the relationship between the acquirer's and target's P/E ratios, the cost of financing, and synergies as an assumption rather than a given.
11. What makes a good LBO candidate? What to listen for: stable cash flows, low existing debt, a credible exit, and assets that support borrowing. Bonus if they mention management quality.
12. How does working capital affect free cash flow? What to listen for: an increase in working capital consuming cash, and an understanding that a fast-growing company can be profitable and cash-hungry at once.
13. How would you value a company with negative earnings? What to listen for: revenue multiples, forward-year multiples once profitability arrives, or a DCF built on a path to margin. Reciting a single method is a weak answer.
14. What is a circular reference in a model, and how do you handle it? What to listen for: the interest-and-debt loop, and a practical fix such as a switch, iterative calculation, or averaging beginning and ending balances.
15. How do you check your own model before it goes to an associate? What to listen for: a real routine. Balance sheet checks, tying to source documents, sensitivity ranges that behave sensibly. Vague answers here predict real errors later.

Which behavioral questions reveal how they work?

Behavioral questions work when they ask for a specific past event rather than a general policy. Ask what happened, not what someone believes. Push for the detail that a rehearsed answer will not have: the date, the number, the name of the deliverable, what the associate said next.

1. Tell me about a time you found an error in your own work after it had been sent. What to listen for: they own it, they say how they flagged it, and they describe the control they added afterwards. Candidates who have never made an error have not done enough work.
2. Describe the longest stretch of sustained pressure you have worked through. What to listen for: specifics on duration and workload, and a realistic account of what it cost them. Answers that make it sound easy are usually not real.
3. Tell me about a deadline you missed. What to listen for: escalation timing. The useful signal is whether they raised the risk early or hoped it would resolve itself.
4. Describe a time you had to learn a new sector quickly. What to listen for: a concrete method, such as reading filings and broker notes before asking a senior banker a short list of targeted questions.
5. Tell me about a time you disagreed with someone more senior. What to listen for: they raised it privately, with evidence, and accepted the final call. Both silence and public escalation are poor answers.
6. Describe a piece of work you were genuinely proud of. What to listen for: they can explain their specific contribution rather than the team's. Analysts who cannot separate the two tend to overstate their experience.
7. Tell me about a time you had to deliver bad news to a colleague or client. What to listen for: directness, early timing, and a proposed option rather than only the problem.
8. Describe how you handled two urgent requests from two different seniors. What to listen for: they asked about relative priority instead of guessing. This exact situation happens in week one.
9. Tell me about feedback that was hard to hear. What to listen for: the specific change they made. Generic gratitude for feedback is not evidence of anything.
10. Describe a time you worked with someone difficult. What to listen for: a description of the behavior and their response, without character assassination.
11. Tell me about a time you spotted something everyone else missed. What to listen for: a real, checkable detail. This question surfaces genuine attention to detail better than asking whether they are detail-oriented.
12. Describe a project where the scope changed late. What to listen for: they reset expectations rather than silently absorbing the extra work.
13. Tell me about a time you asked for help. What to listen for: they tried first, then asked with a specific question. Both never asking and asking immediately are risks.
14. Describe how you keep track of your work across several live projects. What to listen for: an actual system they can describe in 20 seconds, not an aspiration to be organized.
15. Tell me about a time you had to say no. What to listen for: they protected quality or accuracy, and offered an alternative. Analysts who can never push back tend to break quietly.

What situational questions expose deal experience?

Situational questions separate candidates who have sat on a live deal from those who have studied one. The tell is usually texture: what the data room was missing, how the client reacted, which version of the model went out. Ask these of candidates with internship or lateral experience, and use judgment-style hypotheticals for those without.

1. Walk me through a deal you worked on from start to finish. What to listen for: their specific role, the timeline, and what went wrong. Flawless deal stories are usually secondhand.
2. What was the hardest assumption to defend in that deal? What to listen for: they can name one and explain the challenge to it. This is the highest-signal follow-up in the whole list.
3. Tell me about a deal you followed in the news and what you would have advised. What to listen for: a point of view with reasoning, for candidates with no live deal experience.
4. A client wants a valuation that is 20 percent above what your analysis supports. What do you do? What to listen for: they show the range and the drivers rather than quietly changing an assumption.
5. You find an error in a model an hour before the client meeting. What happens next? What to listen for: immediate escalation with a quantified impact. Any answer that involves fixing it silently is a fail.
6. The data room is missing three years of segment detail. How do you proceed? What to listen for: a request list, a documented assumption, and flagging the gap rather than hiding it.
7. How would you sanity-check a valuation someone else built? What to listen for: comparing against comps, checking the terminal value share, and testing whether the sensitivity table behaves logically.
8. How do you decide what belongs in a pitch book versus the appendix? What to listen for: the client's decision drives the main section. Everything defensive goes behind it.
9. A senior banker asks for a number you do not have. What do you say? What to listen for: an honest position with a time estimate, not a guessed figure.
10. How would you explain a DCF to a client who is not a finance person? What to listen for: plain language and an analogy that survives scrutiny. This is the communication test in the matrix above.
11. Two comparable sets give very different valuations. How do you present that? What to listen for: showing both with the reason for the divergence, rather than picking the flattering one.
12. How do you handle a model you inherited that you do not trust? What to listen for: rebuilding the critical sections and tying to source, instead of either blind trust or a full rebuild nobody asked for.
13. What would make you recommend against a transaction? What to listen for: they are willing to have a negative view and can say what evidence would drive it.
14. How do you prepare for a management presentation? What to listen for: anticipating the three hardest questions and having the backup slide ready.
15. What is the first thing you do when handed a new company to analyze? What to listen for: reading the filings and the revenue model before opening a spreadsheet. Candidates who start in Excel often model the wrong business.

Which questions reveal motivation and fit?

Motivation questions predict retention, which matters more than most panels admit. Analyst attrition is expensive precisely because the first six months are mostly investment. Look for specificity about your bank and your group. Generic enthusiasm for finance is the answer everyone gives.

1. Why investment banking rather than another finance path? What to listen for: a real comparison against a considered alternative, not a rehearsed script about learning quickly.
2. Why this bank, and why this group? What to listen for: specifics. A recent mandate, a sector focus, a person they spoke to. Vagueness here correlates strongly with early attrition.
3. What do you expect the first six months to be like? What to listen for: a realistic picture including the hours. Candidates with a rosy view leave when it arrives.
4. What part of the job do you expect to dislike? What to listen for: an honest answer. Claiming to enjoy everything is not credible and usually means they have not thought about it.
5. Where do you want to be in three years? What to listen for: honesty about their path. A candidate open about eventual buy-side ambitions is more trustworthy than one pretending otherwise.
6. What are you reading or following in the market right now? What to listen for: genuine interest with a specific example. This is hard to fake and easy to check.
7. How do you handle work that feels repetitive? What to listen for: acceptance that much of the job is careful repetition, plus a way to stay accurate through it.
8. What questions do you have about the group? What to listen for: questions about deal flow, staffing and the team, not only about compensation and exit opportunities.
9. Tell me about a time your motivation dropped. What did you do? What to listen for: self-awareness and a practical response.
10. What does a good manager look like to you? What to listen for: a description that matches how your associates actually work. Mismatch here causes friction in month two.
11. How do you recover after a long stretch of late nights? What to listen for: something real and sustainable. Nothing is a warning sign, not a strength.
12. What would make you turn down an offer from us? What to listen for: candor. The answer tells you what to address before you make the offer.
13. Which other processes are you in? What to listen for: an honest read of their timeline, which tells you how fast you need to move.
14. What have you done to prepare for this interview? What to listen for: effort proportional to the role. Preparation is the cheapest available signal of interest.
15. What should we have asked you that we did not? What to listen for: they surface a genuine strength or address a gap in their profile directly. Strong candidates use this well.

When should you use skills assessments?

Use an assessment before the interview when the competency you care about is measurable in output rather than conversation, which for analyst hiring means modeling accuracy, finance fundamentals and error rate. A timed finance or modeling assessment scored on the answer, not the explanation, gives the panel something the interview cannot produce.

The sequencing argument is the practical one. If modeling accuracy is settled before the interview, the panel's 45 minutes go to judgment, communication and motivation, which are exactly the things a test cannot read. Run it the other way and you spend the interview asking a candidate to describe a spreadsheet.

Testlify's test library covers this role directly, including an investment analyst test, a business analyst investment banking test, and an investment banking associate test for the level above. Tests can be combined into one assessment, weighted by section, and scored with benchmarks so a shortlist arrives ranked rather than alphabetical. The same approach applies to adjacent finance roles, which is why the financial analyst interview questions follow the same competency-first structure.

On sequencing, most teams already run an applicant tracking system, and the assessment sits alongside it rather than in place of it. Candidates are invited after the initial screen, results land against the record your recruiters already work from, and the shortlist arrives ranked instead of alphabetical. For teams that run no tracking system at all, Testlify ships a basic one covering requisitions, an application form and an applied-to-shortlisted pipeline.

Two honest limits. An assessment measures a slice of the job under artificial conditions, so it belongs before the interview as a filter, not after it as a tiebreaker. And a test that takes 90 minutes will cost you candidates in a market where median pay sits above 100,000 dollars and strong people hold several processes at once. Keep it proportionate to the role.

Hire analysts on evidence, not on gut feel

Set up a role-based assessment for your analyst pipeline, then run the 60 questions above against a shortlist that has already cleared the technical bar. You can book a demo to see how the assessment and scoring side fits your existing process, including the applicant tracking system your team already runs.

Key takeaways

• Technical questions filter, judgment questions decide. Most candidates who reach a final round can walk through a DCF, so the mechanics only tell you who to reject. The separating signal is whether a candidate can name the assumption they would attack first and defend that choice, which is why the follow-up matters more than the question.
• A conversation cannot measure modeling accuracy. Interviews measure how someone describes their work. If error rate in client-facing documents matters to you, that evidence has to come from a work sample or a timed assessment, and no amount of interview time substitutes for it.
• Structure is what makes two interviewers comparable. Same questions, same order, same rating scale with written anchors defined in advance. Without it, a hiring debate is really a debate about which questions each interviewer happened to ask.
• Weight the rubric to the level you are hiring. Deal exposure should count for little in a first-year analyst hire, because the role is what provides it. Using a lateral rubric on a junior candidate rejects people for missing exactly what you were going to teach them.
• Motivation questions are retention questions. Specificity about your bank and your group predicts whether someone stays past the first bonus cycle. Generic enthusiasm is the answer every candidate gives, so it carries no information.
• Speed is part of the offer. With median pay for financial and investment analysts at 102,740 dollars in May 2025 and 7 percent projected growth through 2035, strong candidates run several processes at once. A three-week scheduling gap loses people that no interview quality can win back.

Frequently asked questions (FAQs)