EY's Interview Process (2026)

Blog / EY's Interview Process (2026)
EY Interview Process
The EY software engineer interview process generally runs 3 to 5 rounds and is notably more practical than what you'd find at a typical FAANG company. Most candidates report a focus on real production experience and resume-specific technical depth rather than abstract algorithmic puzzles.
  • Application and Automated Screening: You apply through the EY careers portal, where your resume is typically processed to check for relevant tech stacks like Java, Spring Boot, or React before a human ever sees it.
  • Online Assessment (Role-Dependent): Some candidates receive a short technical assessment, often around 30 minutes on a platform like HackerRank, covering fundamentals rather than complex competitive programming. This stage is not universal and depends on the specific role.
  • Recruiter Screen: A brief call, usually 15 to 30 minutes, to verify your experience, discuss salary expectations, and get a quick read on cultural fit.
  • Technical Interview(s): Typically one to two live video rounds with senior engineers or architects, each around 45 to 60 minutes. Expect to walk through your actual project work and explain specific technical decisions you made.
  • Manager or Partner Round: A final discussion, usually 30 to 60 minutes, combining high-level technical questions with strengths-based behavioral questions. For campus hires, this may be part of a back-to-back Super Day format.
  • Client Interview (Specific Roles Only): For certain consulting or staff augmentation roles, a final round with an EY client may be required before an offer is extended.
EY's technical rounds cover a fairly distinct set of topics compared to typical Big Tech interviews. Focus your preparation across these key areas:
  • Data Structures & Algorithms (DSA): Practical coding problems focused on arrays, strings, and core data structures rather than complex algorithmic puzzles.
  • Low-Level Design (LLD): Object-oriented design and common design patterns applied to realistic service-level problems.
  • SQL and Databases: Resume-anchored SQL questions with a strong emphasis on performance tuning, indexing, and query optimization.
  • Frontend and React: Framework-specific questions on React Hooks, Web Vitals, and practical component behavior.
  • Behavioral and Strengths-Based: EY uses a strengths-based methodology to assess whether you're naturally suited to the type of work they do, not just whether you can recall a past failure.
  • Production and DevOps: A company-specific focus on monitoring, incident response, and cloud tooling in enterprise environments.
1. Data Structures & Algorithms (DSA)EY's coding questions are intentionally grounded. You're unlikely to see graph theory or dynamic programming at most levels. Instead, expect problems built around arrays, strings, and basic data structures, such as Remove Duplicates in a String or Valid Parentheses.Other common patterns include reversing or manipulating words, like Reverse Words in a String III, and set operations. These questions test whether you can write clean, working code under mild pressure rather than whether you've memorized obscure algorithms.For a solid baseline, work through our top 100 DSA questions and make sure you're comfortable with arrays and stacks, as those surface most frequently in reported EY rounds.
2. Low-Level Design (LLD)Mid-to-senior candidates should expect at least one LLD-style question. EY interviewers often ask you to design a specific service, such as a Notification Service or an Email OTP Service, and want to see how you structure your classes and apply design patterns.Common patterns that come up include Singleton, Factory, and Observer. The goal isn't to whiteboard a massive system but to show you understand object-oriented principles and can apply them to a realistic, bounded problem.Practice these scenarios on our Low-Level Design practice page to get comfortable walking through design decisions out loud.
3. SQL and DatabasesIf SQL is on your resume, be prepared to go beyond basic joins. EY interviewers commonly ask about query performance, indexing strategies, and how you'd approach a slow-running query in production.Expect questions like Employees Earning More Than Managers or Second Highest Salary, which test both SQL fluency and your instinct for writing efficient queries. Brush up on execution plans and index types as well.For a solid theoretical foundation alongside practice problems, review our SQL theory materials.
4. Frontend and ReactFor roles that list frontend experience, EY digs into specific React behavior rather than broad JavaScript trivia. Interviewers have been known to ask about Hooks like useEffect and useMemo, and how they affect rendering and performance.Web Vitals and basic performance optimization are also in scope, so understanding concepts like lazy loading and how the browser handles re-renders is worth your time.Our React fundamentals page covers the core concepts that come up most often in these rounds.
5. Behavioral and Strengths-BasedEY uses a strengths-based interview methodology, which feels different from a standard behavioral round. Instead of only asking about past failures or conflicts, they ask questions designed to surface what kind of work energizes you naturally, for example, 'What kind of tasks make you lose track of time?'That said, you'll still need to tell structured stories about your past experience. Using the STAR format to frame your answers keeps them focused and easy to follow.You'll also want a genuine answer to 'Why EY?' since they're a professional services firm, not a product company, and they value candidates who understand that difference. The Behavioral Playbook has frameworks for questions exactly like these.
6. Production and DevOpsThis is one of the most distinctive parts of EY's technical process. Interviewers frequently ask how you'd handle real production scenarios, such as what you'd do if a server's memory was filling up or how you'd investigate a slow SQL query in a live environment.Tools like Kibana and Dynatrace come up regularly, as do questions about cloud services on AWS or Azure. They want to see that you can operate in a high-pressure enterprise setting, not just write code in isolation.Familiarizing yourself with caching fundamentals and system design core concepts will give you a strong foundation for these scenario-based questions.
ConclusionEY rewards candidates who can speak specifically and honestly about their real production experience, so the best preparation is a mix of targeted practice and honest reflection on your own past projects. Start with the areas most relevant to your resume, sharpen your fundamentals, and make sure you can tell concrete stories about the work you've actually done. Follow the EY Interview Roadmap for a structured, stage-by-stage preparation plan built around exactly what EY looks for.

About TechPrep

Never walk into a technical interview unprepared again. TechPrep empowers software engineers to stop guessing and start getting offers. We provide the exact questions asked by tech companies across Data Structures & Algorithms, System Design, Low-Level Design & Practical coding rounds. Don't leave your career up to chance. Join thousands of engineers who have successfully navigated the tech hiring maze and landed roles at top tech companies.