What EY-Parthenon is testing
Parthenon sits on the strategy side of EY. The case is usually a growth, market-entry, pricing, or diligence question. The interviewer wants a thesis, a structure that splits the value, and a recommendation a partner could put in front of a client. Technology shows up as a driver — a channel, a product, a cost line — not as the whole case.
An EY technology interview, by contrast, spends more of the hour on architecture defense and delivery: budget, sequencing, and who owns the system after launch. If you are interviewing for Parthenon, do not open with a cloud framework unless the prompt is actually a technology decision.
A structure that fits
Use three branches, not a memorized strategy stencil:
- Is the prize real? Size the revenue or the saving, and say what would make the number wrong.
- Can this client capture it? Share, capability, regulation, and the competitive response.
- What do we do next? The option you would pick, the one you would drop, and the risk you would watch.
Then do the math out loud. A direction without a number reads as a hunch. The case math guide is the drill for that close.
How this differs from a technology case
| | EY-Parthenon | EY technology | |---|---|---| | Decision | Enter, price, buy, or walk away | Build, buy, sequence, or stop | | Evidence | Market, margin, synergy | Architecture, cost, operating model | | Close | Commercial recommendation | Delivery recommendation with an owner |
Practice
The EY case library is written in EY's technology register, which is the right drill if your interview sits with EY's tech practice. Use it for structure and math even if your target is Parthenon, and keep the close commercial: what to do, what it is worth, and what you would not do.