EY AI Engineer interview typically runs 3 rounds: HR screen, manager interview, technical interview. It usually takes 2-4 weeks and is conversational, with a strong focus on fit and experience.
$114K
Avg. Base Comp
$208K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that EY is looking for people who can connect AI concepts to real client work, not just recite frameworks. The strongest signal across experiences is clear, grounded explanation of your own background: one interviewer spent most of the conversation walking through the CV in detail, while another focused on how the candidate had handled software architecture and agentic AI in customer-facing settings. That tells us EY is checking for fit against the role spec as much as technical fluency, especially for more senior AI positions.
A recurring theme is the emphasis on applied AI tradeoffs. One candidate described a technical discussion centered on AI, cloud, and especially RAG, including comparisons between simpler and more complex implementations and the reasoning behind each choice. Even the lighter technical probing included fundamentals like singleton patterns, which suggests EY wants candidates who can move comfortably between modern AI systems and basic engineering concepts. The process feels less adversarial than many consulting interviews; multiple candidates noted that interviewers helped them reason through answers rather than trying to trap them.
We also see a very EY-specific pattern: the interview can feel straightforward, but the real surprise may come outside the technical conversation. One candidate said the compensation discussion was dramatically below expectations for the level, so it’s worth aligning on scope and pay early. In practice, EY seems to value candidates who are credible, client-ready, and technically solid — especially those who can explain why a solution is the right one, not just how to build it.
Synthetized from 2 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.
Sono passato prima da un colloquio con HR abbastanza lineare, in cui parlava quasi solo la recruiter e io dovevo raccontare in modo sintetico cosa faccio e come mi presento. Dopo quello c’è stato un colloquio con un manager che mi ha fatto un quiz di logica; la cosa positiva è che non era impostato in modo aggressivo, anzi mi ha aiutato a ragionare passo passo fino alla soluzione. L’ultimo round è stato quello più tecnico, con un altro manager, e lì si è parlato soprattutto di AI e di cloud, con un focus molto concreto su RAG: mi hanno chiesto di confrontare RAG semplice e RAG più complessa e di discutere i tradeoff tra diverse tecniche. In mezzo sono uscite anche domande un po’ più specifiche, tipo che cosa sia un singleton, quindi non era solo teoria alta ma anche concetti di base da saper spiegare bene. Nel complesso l’ho trovato un processo completo ma tranquillo, più orientato a capire come ragioni e come ti muovi su temi AI che a metterti in difficoltà con domande puramente algoritmiche. Alla fine ho ricevuto l’offerta, quindi direi che la parte più importante è arrivare preparati sia sul proprio CV sia su RAG, LLM e concetti fondamentali di programmazione.
Prep tip from this candidate
Ripassa bene i tradeoff tra RAG semplice e RAG più complessa, perché è stato il centro del colloquio tecnico. Preparati anche a spiegare il tuo CV in modo molto sintetico e a rispondere a domande di base come singleton, oltre a un breve quiz di logica con ragionamento guidato.
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 | |
| Classification and Regression | |
| Mouse Search | |
| Overfit Avoidance | |
| Azure Kubernetes Infrastructure | |
| Stakeholder Communication | |
| Simple Explanations | |
| Why Do You Want to Work With Us | |
| Xgboost vs Random Forest | |
| Your Strengths and Weaknesses | |
| 1000 Sample Classifier | |
| Quantify Uncertainty | |
| Linear vs Logistic Regression | |
| Backpropagation Explanation | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Size of Joins | |
| Raining in Seattle | |
| Longest Streak Users | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Fair Coin | |
| Using R Squared | |
| Cyclic Detection | |
| Assumptions of Linear Regression | |
| Precision and Recall | |
| Missing Housing Data |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with HR or a recruiter focused on introductions, your background, and basic fit for the role. In one experience, the recruiter led most of the discussion while the candidate gave a concise overview of their experience; in another, HR later handled salary and compensation expectations.
A deeper interview with a manager or senior manager that reviews your CV and past projects in detail. The discussion centers on your software, AI, and client-facing experience, and whether your background matches the job requirements.
A more technical round with a manager that covers AI and cloud topics, with a strong focus on RAG. Candidates were asked to compare simple versus more complex RAG approaches, discuss tradeoffs between techniques, and explain foundational programming concepts such as singleton.
If you progress to the final stage, HR may discuss salary and compensation details before an offer is finalized. One candidate noted that this conversation was the point where expectations needed to be clarified early, as the compensation discussed was significantly lower than expected.