Merger Integration Interview Coaching

Reviewed by Fallon Han· Updated 2026-06-01 06:04:25.877

This conversation was generated using Cook'd AI's career assistant and reviewed by Fallon Han from our editorial team for accuracy.

I am a first-year MBA in Brazil interviewing for a corporate development role at a large industrial company in Sao Paulo. Can you walk me through how to think about the integration plan for a recent deal and which issues matter most? I want to focus on merger integration, especially synergy estimates, integration risks, and how to prioritize the first 100 days.

Absolutely. For your setting, I would frame the integration plan as a value capture story, not just an operations checklist. In a corporate development interview, the interviewer wants to see that you can translate the deal thesis into a realistic first 100 days plan. I would break it into three buckets: 1. Synergy capture 2. Integration risks 3. First 100 days priorities Start with synergy estimates. Be specific about where the value comes from. In an industrial deal, the main buckets are usually procurement, SG&A, manufacturing footprint, logistics, and maybe revenue synergies if there is channel overlap. For each synergy, I would ask: how big is it, how fast can we capture it, and what must happen operationally to realize it? Then assess risks. The biggest ones are usually disruption to operations, customer loss, talent attrition, and weak governance. In Brazil, you might also mention labor considerations, local supplier dependence, and regulatory approvals if relevant. For the first 100 days, the goal is to protect the core business and lock in the top synergies. That means: establish integration governance, assign owners, prioritize a clean synergy tracker, and set clear decision rights between the two legacy teams. If you want, I can walk through a simple sample case and show how to answer this in an interview.

Yes, please. Suppose the company acquired a smaller domestic industrial supplier in Brazil. How would you estimate the synergies without sounding too vague? I want to sound credible, but I do not have the deal model.

Good question. Without the full model, you can still sound credible by using a structured estimate and showing your assumptions. I would say something like: - Procurement synergies: combine raw material purchases and leverage higher volume with suppliers - SG&A synergies: eliminate duplicate finance, HR, and admin roles - Manufacturing and logistics synergies: optimize plant utilization, reduce freight, and improve network design Then give ranges instead of exact numbers. For example: - Procurement: low to moderate, perhaps 1 to 3 percent of combined COGS if categories overlap - SG&A: more visible and faster, maybe 3 to 5 percent of combined SG&A in overlapping functions - Logistics and footprint: medium-term, depends on plant overlap and route redesign The key is to explain the logic behind the estimate. For instance, if the acquired supplier is domestic and has similar inputs, procurement synergy is more likely. If both companies have separate back-office teams in Sao Paulo, SG&A synergies may be easier and faster. If plants are in different regions and serve different customers, footprint synergy is more limited. In an interview, I would avoid pretending to know the exact model. Instead, I would say: "I would size synergies by category, validate them against operational overlap, and then haircut them for execution risk." That shows discipline. If you want, I can help you build a strong answer for the risks side next.

Yes. What are the integration risks I should emphasize first, and how would I prioritize them for the first 100 days? I do not want to list ten random risks.

Great instinct. Do not list everything. Pick the few risks that can destroy value early. For a domestic industrial acquisition, I would prioritize these four: 1. Customer disruption If the integration distracts the sales or operations teams, service levels can slip. In industrial businesses, that can quickly lead to churn. 2. Talent retention You may lose key plant managers, sales leaders, or technical staff who know the business best. 3. Operational continuity Systems changes, procurement changes, or plant process changes can cause delays, stockouts, or quality issues. 4. Governance and decision speed If there is no clear integration leadership, teams spend too much time aligning instead of executing. How to prioritize them in the first 100 days: - Days 1 to 30: protect business continuity, set governance, and identify critical talent - Days 31 to 60: launch the highest-value synergies that do not create major disruption, like back-office consolidation or joint procurement planning - Days 61 to 100: begin more complex work such as footprint optimization or ERP integration planning A good interview answer would say that the first 100 days should focus on preserving the core business before chasing aggressive transformation. In other words, do not jeopardize revenue or operations just to chase headline synergies. If you want, I can help you craft a polished 60-second interview answer.

Please do. Also, how can I show judgment on trade-offs? For example, if a synergy is large but hard to implement, how should I explain whether to pursue it now or later?

Here is a concise interview answer you can adapt: "For the integration plan, I would focus first on protecting the core business and then capturing the most achievable synergies. In an industrial acquisition, I would size synergies across procurement, SG&A, and logistics, but I would prioritize the ones with clear ownership and low disruption, like back-office overlap or supplier consolidation. The main risks are customer disruption, talent attrition, and operational interruptions, so the first 100 days should establish governance, retain key people, and launch a clean synergy tracker. If a synergy is large but complex, I would not ignore it, but I would sequence it behind quick wins and use the first 100 days to do the analysis, design, and risk mitigation before execution." On trade-offs, the strongest answer is to show sequencing logic. A large but hard synergy, such as plant consolidation, may be worth pursuing if the payback is meaningful. But it should usually come later because it has higher execution risk. In contrast, smaller synergies like shared services or procurement standardization may have lower upside individually, but they are easier to deliver and build credibility early. So your framework is: - High value and low risk: do now - High value and high risk: prepare now, execute later - Low value and low risk: only do if it is easy and supports the larger plan - Low value and high risk: usually avoid That framework sounds thoughtful in interviews because it shows you can balance value and execution, not just chase a spreadsheet.

That helps. One last thing: if the interviewer asks how I would personally add value in that role, given I am an MBA student in Sao Paulo and not relocating, how should I connect that to the integration work?

You can connect your profile to local execution strength. A strong answer would be: "As someone based in Sao Paulo, I could add value by helping coordinate cross-functional work closely with local teams, especially where execution depends on day-to-day alignment with operations, finance, and commercial leaders. In an integration, speed and trust matter, so being local helps me stay close to the business, understand cultural dynamics, and keep decisions moving. I would also be useful in tracking synergy delivery, preparing management updates, and supporting the first 100-day integration cadence." Why this works: - It is specific to the role - It shows you understand integration is execution-heavy - It turns your local presence into a practical advantage - It avoids overclaiming technical experience you may not yet have If they push further, you can mention that in Brazil industrial deals, local context matters for labor, supplier relationships, and communication with plant and commercial teams. That is a credible way to show fit without sounding generic. If you want, I can turn all of this into a single polished mock answer you can memorize and adapt.