Corporate Development Interview Questions

The difference that shapes every question

A bank advises on a transaction and moves on. A corporate development team lives with what it bought, reports on the synergies it promised, and is still there when the integration goes badly. That single structural fact drives most of the difference between the two interviews.

It is why "what would you do the day after close" is a standard question, and why an answer that stops at signing is a weak one.

Strategic rationale before valuation

The first question about any deal is not what it is worth. It is why this company, and why buying rather than building or partnering. Build-versus-buy is the framework corp dev genuinely uses, and it comes up because it is the actual first conversation with a board.

A strong answer weighs time to market against cost and risk, and names the case for not doing the deal. Corp dev teams reject far more than they pursue, so a candidate who cannot argue the negative case has only seen half the job.

• What capability are we buying, and how long would building it take
• What does the acquisition cost relative to the internal alternative, including the failure rate of building
• What breaks if a competitor buys it instead

Synergies you would have to defend

In banking a synergy number supports a valuation. In corp dev it becomes a commitment somebody is measured against, which changes how it should be constructed and how you should talk about it.

Separate cost from revenue and treat them differently: cost synergies are more credible, arrive sooner and are easier to evidence; revenue synergies are routinely overstated and frequently never materialise. Say so. Naming the difference unprompted signals you understand what happens after close.

• Cost: overlap in functions, facilities, procurement — quantifiable and usually deliverable
• Revenue: cross-sell, pricing, distribution — slower, softer, and the ones that go unmet
• The cost to achieve, which is real cash and gets left out of the number that gets quoted

Accretion, dilution and the in-house version

The mechanics are the same as banking and will be tested. The framing is not: an acquirer with one balance sheet cares about leverage capacity and rating impact in a way an adviser running a screen does not, and questions often go straight to funding.

Be ready to say what the deal does to leverage, whether it is affordable in cash, and how the answer changes if it is funded with stock instead.

Integration, which is where the job actually happens

Interviews probe this because it is what separates people who want deals from people who want this job. Who owns the plan, what the first hundred days look like, which employees you cannot afford to lose, and how you know six months later whether it worked.

A candidate who has thought about retention of key people, systems integration and the reporting that tracks the promised numbers is describing the role. A candidate who lights up only about signing is describing banking.

Why you are leaving banking

This question is asked in every corp dev interview and answered badly in most. "Better hours" is heard constantly, is often true, and does nothing to suggest you want this particular job rather than any job that is not banking.

The stronger answer is about ownership: wanting to see whether the thesis was right, being in one industry deeply rather than many shallowly, and being accountable for the outcome rather than the advice. That is a reason to choose corp dev over the alternatives, which is what is being asked.