EY Software Engineer candidates report screens, technical discussions, and HR or manager conversations. Preparation should match the team’s stack while emphasizing project ownership, fundamentals, and practical problem solving.
$113K
Avg. Base Comp
$128K
Avg. Total Comp
2-4 rounds
Typical Rounds
2-4 weeks
Process Length
EY Software Engineer reports vary by team, but the clearest recurring preparation theme is be able to defend your resume in technical detail. Candidates describe introductory conversations about their background, previous work, motivation, and technologies they have used. Prepare a concise explanation of two or three projects, including your contribution, the tools involved, and the reasoning behind important implementation choices.
Technical coverage appears to depend on the position’s stack. One candidate completed live coding involving ArrayList and Arrays, answered Java questions, and discussed Python scope. Another report emphasized practical Python topics such as exception handling, JSON and file handling, validation, arrays, and string manipulation. Review the fundamentals of your primary language, then practice solving small problems while explaining your reasoning and checking edge cases aloud.
The reports also indicate that project scenarios, domain knowledge, communication, and delivery judgment can matter alongside coding. Candidates discussed prior technical work and how they handle pressure and deadlines. Some reports include HR or behavioral discussion, but the supplied evidence does not establish a single sequence for every EY engineering team. Ask the recruiter what stack and interview format apply to your opening, and tailor preparation to the experience shown on your resume.
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.
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 | |
| Resumable Fact Table Load | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Real-Time Hashtag Partitioning | |
| Duplicate Rows | |
| Skyscanner Partner ETL | |
| Mouse Search | |
| Pipeline Transformation Failures | |
| Marketing Workflow Optimization | |
| Azure Kubernetes Infrastructure | |
| Stakeholder Communication | |
| Relational Migration | |
| Why Do You Want to Work With Us | |
| Processing Large CSV | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Raining in Seattle | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Real-Time Transaction Streaming | |
| P-value to a Layman | |
| Normalize Grades |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an introductory HR or recruiter conversation that may cover work history, motivation, career goals, communication, and the technologies listed on a resume. Some accounts describe this as a brief screen before technical evaluation; the exact order and language can vary by team.
Candidates report technical checks that range from live coding with arrays, lists, strings, balanced parentheses, or medium-level problems to questions on core language concepts. Prepare the fundamentals for your stated stack and explain your reasoning, since several reports emphasize discussion of approach rather than only a final answer.
Technical interviews may probe projects, SQL work, APIs, framework choices, architecture, debugging, and practical tradeoffs. Reported examples differ by role—Java/Spring Boot, Python/FastAPI, Angular, cloud, automation, and operations tooling all appear—so use the job description and your own experience to prioritize topics.
Candidates report a final HR, manager, behavioral, or client-facing discussion in some processes. These conversations may ask about recent work, responsibilities, delivery pressure, collaboration, and why you want the role; prepare concise examples grounded in work you actually performed.
