EY Software Engineer interview typically runs 2-5 rounds: HR screen, technical round, manager round, and sometimes an online assessment or client interview. The process usually takes about 1-3 weeks and is practical, resume-driven, and role-dependent.
$99K
Avg. Base Comp
$161K
Avg. Total Comp
3-5
Typical Rounds
2-4 weeks
Process Length
We've seen EY evaluate software engineers less like a pure coding shop and more like a team that wants to verify whether your claimed experience holds up under pressure. A recurring theme across candidate reports is that the interview stays tightly anchored to the resume: projects, tools, and the exact stack you say you’ve used. Multiple candidates mentioned being pushed to explain their most recent work in detail, whether that meant Java and Spring Boot, SQL-heavy project work, or Angular and cloud topics. The signal here is practical ownership, not polished theory.
Another pattern we keep seeing is that EY cares a lot about whether you can operate in real enterprise environments. Candidates were asked about incident/problem/change management, monitoring tools like Kibana and Dynatrace, ticketing systems, batch schedulers, AWS services, and troubleshooting scenarios such as memory fill-ups or SQL performance issues. That tells us the bar is often about production judgment: can you diagnose, explain tradeoffs, and connect the dots across systems? Even when coding appears, it tends to be short and grounded in fundamentals, like arrays, lists, or balanced parentheses, rather than elaborate algorithm puzzles.
The non-obvious make-or-break factor is how well you can stay specific without drifting into generic answers. Our candidates report that interviewers quickly probe past surface-level familiarity, especially when a project or tool appears on the resume. If you can clearly defend the choices you made, the stack you used, and the operational issues you handled, you tend to fit what EY is screening for. If not, the process exposes that gap fast.
Synthetized from 8 candidates 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 | |
|---|---|
| Hurdles In Data Projects | |
| Sort Strings | |
| Stakeholder Communication | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| Raining in Seattle | |
| Cyclic Detection | |
| Find Duplicate Numbers in a List | |
| Slow SQL Query | |
| Swap Variables | |
| Subway Machine Learning Model | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| Creating Companies Table | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| String Shift | |
| Employee Salaries | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Weighted Keys | |
| Prime to N | |
| Largest Salary by Department |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with an introductory call focused on your background, work experience, and motivation for joining EY. In some cases this is also used to gauge language ability and confirm basic fit for the role.
Some candidates first complete a short coding test with two medium-level LeetCode-style problems under time pressure. This stage is used as an initial filter before moving into deeper interviews.
The main technical round is usually centered on your resume, projects, and core stack knowledge rather than abstract theory. Depending on the team, this can include live coding, Java or Python fundamentals, SQL, Spring Boot, microservices, Angular, .NET, or practical troubleshooting questions.
A manager-led conversation typically follows, with a stronger emphasis on past experience, ownership, and how you handled previous work. Candidates reported questions about their last project, framework choices, and how they would approach real production or support scenarios.
The final stage is often an HR or behavioral discussion about communication, responsibilities, and fit. This round may also cover career goals, pressure handling, and general expectations before the final decision.