EY Data Analyst interviews typically pair a behavioral screen with SQL and Power BI/DAX technical rounds, sometimes adding an online assessment, case study, or guesstimates before senior-manager or director fit conversations, though structure varies by team.
$80K
Avg. Base Comp
$118K
Avg. Total Comp
3-5 rounds
Typical Rounds
3-4 weeks
Process Length
EY's Data Analyst interview process typically opens with a recruiter or HR screening. It covers your background, motivation for joining EY, and classic behavioral prompts like strengths, weaknesses, and a five-year plan. Some candidates also report an online assessment. In different accounts it covered multiple-choice SQL, Python, and company-policy questions, or focused on verbal reasoning, and one included a one-take recorded video question about why you want the role.
From there, candidates report a technical round built around core SQL fundamentals: joins, GROUP BY, ORDER BY, and window functions. It sometimes comes alongside basic DBMS questions or an Excel test. A second technical stage can go deep on Power BI and DAX, including:
One candidate described a 45-minute Power BI round stretching close to two hours, so expect this stage to run long when it appears.
Some loops add a case study or guesstimates, and one candidate faced deeper questions on ETL, data-pipeline design, and Spark or Hadoop. Later conversations with a senior manager or director mix fit questions like why EY and why the service line with a review of past project impact. Reported round counts and pacing vary by team and seniority, so treat this as the common shape rather than a fixed script. Come ready to walk through a real analytics project end to end in both SQL and Power BI.
Synthesized from 22 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.
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 | |
| Longest Streak Users | |
| Size of Joins | |
| Sort Strings | |
| Xgboost vs Random Forest | |
| Hurdles In Data Projects | |
| Forecasting New Year Revenue | |
| Duplicate Rows | |
| Classification and Regression | |
| Overfit Avoidance | |
| Pipeline Transformation Failures | |
| Company Acquisition Choice | |
| Marketing Workflow Optimization | |
| Stakeholder Communication | |
| Simple Explanations | |
| Relational Migration | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences | |
| Marketing Dollar Efficiency | |
| Linear vs Logistic Regression | |
| Backpropagation Explanation | |
| Analyzing Multiple Data Sources | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Experiment Validity | |
| Raining in Seattle | |
| Maximum Profit | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates start with a recruiter or HR phone screening focused on background, motivation for joining EY, and standard behavioral prompts such as strengths, weaknesses, and a five-year plan. Some report this paired with an online assessment covering multiple-choice SQL, Python, and company-policy questions, a verbal-reasoning test, or a one-take recorded video question about why you want the role, so early-stage prep is worth taking seriously.
A technical interviewer, often a senior developer or manager, typically tests core SQL skills including joins, GROUP BY, ORDER BY, and window functions, along with basic DBMS concepts. Some candidates also mention an Excel test. Clear explanation of query logic appears to matter as much as getting the right answer.
Candidates report a demanding Power BI round covering Power Query transformations, import versus direct query, star versus snowflake schema, measures versus calculated columns, relationships, row-level security, and optimizing reports for large datasets. One candidate described a 45-minute session that stretched close to two hours with pointed follow-up questions, so expect this stage to go deep.
Some loops include a case study or guesstimates alongside questions about the value you delivered in previous projects. One candidate also faced deeper questions on ETL, data-pipeline design, query optimization, and distributed tools like Spark or Hadoop. Interviewers appear to focus on reasoning and practical design decisions rather than memorized definitions.
The process generally closes with one or more conversations involving a senior manager or director. These blend fit questions like why EY and why this service line with a deeper review of past project impact, goals, and how you handle pressure. The exact structure appears to vary by team and seniority.
