I have an interview with Strategy& for their Deals Technology Strategy team? I am really confused about the kind of cases to expect? Would they be similar to general MBB style cases on M&A/ Growth or too tech inclined

Hi there,

Having experience across Big 4 strategy houses, cases for Strategy& Deals Technology Strategy typically sit between classic strategy and technology focused problem solving. You should expect M&A, carve out, or growth related cases, but with a clear technology lens rather than pure general strategy. For example, assessing the tech implications of an acquisition, IT integration risks, digital operating models, or how technology enables value creation post deal.

They are usually not deep technical or coding cases. Instead, interviewers look for structured thinking, comfort discussing technology at a conceptual level, and the ability to link tech decisions to business impact. Preparing with MBB style M&A and growth cases is very relevant, but it helps to also be familiar with tech due diligence and post merger integration topics at a high level.

Happy to help you prep if useful.

Best,
Evelina

Strategy& Deals Technology Strategy sits at the intersection of M&A and tech, so expect cases that blend both.

You'll likely get cases around tech due diligence, IT integration post-merger, or technology carve-outs. Think questions like: should this company acquire a tech startup? How do we integrate two different IT systems after a merger? What's the technology cost synergy potential in this deal?

It won't be pure MBB-style market entry or profitability cases. But it also won't be deeply technical like a software engineering interview. They want to see you can think through business problems with a technology lens.

A few things to keep in mind:

Understand basic M&A concepts like synergies, due diligence, integration planning, and deal rationale. You don't need to be an investment banker, but know the fundamentals.

Know how technology fits into deals. IT costs, systems integration, tech debt, digital capabilities, data migration. These come up a lot in deals technology work.

Be ready to talk about tech strategy. How do companies use technology to create value, reduce costs, or drive growth? If you have experience here, bring specific examples.

Practice cases with a tech or M&A angle. Look for ones involving acquisitions, post-merger integration, or technology transformation. That's closer to what you'll actually face.

And don't skip fit prep. Why Strategy&? Why deals? Why technology? Have clear answers that connect your background to this specific team.

Don't overthink it. Structure still matters. Clear thinking still matters. They just want to see you can apply it to their world.

Good luck.

That is a very common point of confusion. The case interview expectations change significantly once you interview for a specialized function like Deals Technology Strategy, especially within the PwC network structure. You are correct that they are neither pure generalist MBB nor entirely technical deep-dives.

The reality is that your case will be a hybrid. You are still being assessed for the core Strategy& competency—structured problem-solving and executive presence—which means the fundamental case frameworks (Market sizing, M&A logic, Synergies) still apply. However, the content and the risks you are asked to analyze will be centered entirely on IT assets. Expect cases to focus specifically on IT Due Diligence (ITDD) or Post-Merger Integration (PMI). They want to know if you can structure a standard M&A case, but then pivot to assess technology debt, evaluate the cost of security risks, or quantify the time needed to separate complex ERP systems.

Your preparation strategy needs to reflect this specialization. While you should be sharp on general market entry and profitability cases, spend the majority of your time practicing M&A cases where the core question revolves around the IT implications of the deal. Be ready to discuss the non-financial aspects—for instance, how you would structure the Transition Services Agreement (TSA) or identify integration risk during a carve-out. The interviewer is looking for comfort in using high-level tech jargon (cloud migration, core systems, technical debt) within a rigorous financial structure.

All the best with your interview!

hey there :)

Based on my experience, cases for Strategy& Deals Technology Strategy usually combine classic deal and growth logic with a strong focus on how technology supports or limits value creation. You can expect topics like acquisitions, separations or growth decisions, but discussed through questions around IT architecture, integration feasibility, digital capabilities or operational impact rather than pure high level strategy. The cases are not technical in an engineering sense, but they do test whether you can think clearly about technology as a business enabler and risk factor. Solid preparation with MBB style M&A cases works very well if you consciously add a tech perspective on top. Happy to help further if you want to go deeper.

best,
Alessa :)

Ask the recruiter. 

My expectation is that they will be primarily candidate led and primarily from within financial services / PE focused. 

You can find examples of such cases also on the PrepLounge library. Here's one of my cases that is relevant for your area:

https://www.preplounge.com/en/management-consulting-cases/interviewer-led/beginner/russell-university-fresh-attacker-on-the-online-education-market-mckinsey-1st-round-289

Best,
Cristian