Candidates describe an EY Product Manager interview that opens with an HR or recruiter screen, then moves to manager and director conversations on project delivery, stakeholder influence and past work, with a partner call for some.
$182K
Avg. Base Comp
$235K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
EY Product Manager candidates describe a process that is more conversational and judgment-driven than technical. It typically starts with an HR or recruiter call and then moves into manager, director or partner conversations about what you have actually delivered. Reported outcomes are mixed, with offers, a declined offer and rejections.
The clearest theme is stakeholder influence. One candidate was asked how they would persuade a difficult stakeholder who saw no value in their work, and how they explain value to a business audience. Another was asked to walk through a project with conflicting stakeholders and to explain how they thought about it, and was also asked how they would handle a difficult client.
Project ownership comes up just as often. Candidates were asked how they would deliver a specific project and why, and to walk through a significant project end to end, including exactly what they owned. One senior manager pressed on a previous client relationship in detail. Technical content seems to depend on the team. One candidate reported a round on SAP cutover strategies and IT security frameworks, while others described no technical component at all.
The early stages deserve care too. One candidate's recruiter screen was about 30 minutes and focused on process. An automated rejection arrived that night, even though they had been told they would advance. Another candidate found the role description vague, and a third said the recruiting team was slow between rounds. Prepare a specific answer for why EY, two or three detailed project stories, and questions about scope.
Synthesized from 10 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ey process.
The strangest part of my EY process wasn’t the interview itself, it was everything around it. A recruiter reached out and then dropped a random time on my calendar without asking what worked for me, which already felt pretty off. The actual call was about 30 minutes and was mostly the recruiter walking me through the structure of the process, repeating herself a lot about what she would ask and why. Even with the awkward scheduling, the conversation itself felt positive enough that I expected to move on. She told me I’d be going to the next round with the hiring manager and that I’d hear back early the following week.
Instead, that same night at around 9:30 p.m., I got an automated rejection tied to my application. It was a pretty jarring way to find out, especially after having already spoken with someone directly and being told I was advancing. I reached out to the recruiter because I wasn’t sure if it was a mistake, but the whole thing left a bad impression. There wasn’t any technical case or product exercise in this first round, just a recruiter screen, and the main thing I took away was how impersonal the process felt. If you’re interviewing here, I’d be prepared for a very light initial screen, but also don’t assume a verbal move-forward means the process is actually moving forward.
Prep tip from this candidate
Expect the first round to be a recruiter screen focused on process and fit rather than product cases or technical depth. Don’t overread a verbal advance until you get a confirmed follow-up, since the communication can be inconsistent.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ey
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top 3 Users | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Longest Streak Users | |
| Forecasting New Year Revenue | |
| Hurdles In Data Projects | |
| Xgboost vs Random Forest | |
| Duplicate Rows | |
| Classification and Regression | |
| Overfit Avoidance | |
| Marketing Workflow Optimization | |
| Azure Kubernetes Infrastructure | |
| Stakeholder Communication | |
| Company Acquisition Choice | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences | |
| Simple Explanations | |
| Relational Migration | |
| Marketing Dollar Efficiency | |
| 1000 Sample Classifier | |
| Quantify Uncertainty | |
| Linear vs Logistic Regression | |
| Backpropagation Explanation | |
| Analyzing Multiple Data Sources | |
| Experiment Validity | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Reports describe an opening call with HR or a recruiter. Questions included tell me about yourself, why EY rather than another Big 4 firm, and why you want the role. One recruiter call ran about 30 minutes and mostly walked through the process, with no product case. That candidate was later rejected by an automated message despite being told they would advance.
One candidate had two competency-based interviews with Directors, who asked for the best way to deliver a specific project and why. Another had an hour-long hiring manager round about walking through a significant project end to end and what they personally owned. A Senior Manager also questioned one candidate closely on a previous client relationship.
Scenario and behavioral questions recur across reports. Examples include convincing a stakeholder who sees no value in your work, explaining value in business terms, handling a difficult client, and walking through a project with conflicting stakeholders. One candidate also described a fairly straightforward case study, a presentation of their own work, and questions on giving and receiving feedback.
One candidate described an hour-long technical round on SAP cutover strategies and a comparison of IT security frameworks, focused on trade-offs and reasoning rather than coding. Another had a final call with a Partner that felt conversational. One candidate was told a client round follows only for those who progress, so later stages likely vary.
