finished an EY PM loop in early 2026, targeting their technology consulting practice. background: i've done PM loops at series B/C companies and one FAANG-adjacent company. EY is genuinely different and most PM interview prep materials won't tell you how.
First: the role. EY's PM-titled roles often look more like product owner or delivery lead on a client engagement than a traditional PM building an internal product roadmap. The interview surfaces this.
What they actually asked: Walk me through a product you've owned end-to-end. Standard, but they immediately pivoted to: how did you communicate progress to executive stakeholders who weren't embedded in the work? The client-communication angle came up fast. How would you prioritize a backlog when stakeholder requirements conflict? Classic product question, but framed around multiple stakeholder types (client sponsor, end users, the internal delivery team). Not a simple RICE framework question. Tell me about a time a product decision didn't go the way you planned. What happened and what did you change? Strong emphasis on the 'what did you change' part. Case-style question: client is a mid-size financial services firm, wants to digitize their document review process. What would you need to understand before you recommended a solution? This is consulting-flavored product thinking. They're not asking you to pitch an MVP. They're asking how you scope a problem. A values question: tell me about a time you had to maintain transparency with a client or stakeholder when the news was bad. EY's integrity value in disguise.
What they're not asking (that pure tech PM interviews often ask): metrics design, monetization strategy, specific product metrics to grow DAUs, deep PRD walkthroughs.
prep framing that worked for me: think of yourself as a PM whose primary product is a consulting engagement, and whose end user includes the client's leadership team. adjust every STAR story to include that layer.