Skip to content

EY Interview Experience 2026

EY Global Delivery Services (GDS) campus loops for Tech Consultant roles emphasize aptitude + easy coding, verbal screens, project/SQL fundamentals, and Consultant-role awareness. This page synthesizes 2023-2024 campus patterns into round tables, outcome notes, and prep traps.

Round-wise process at a glance

Round Typical format What clears you
Online assessment Aptitude (quant/logical/verbal) + 1 easy coding (~45 min) Clear aptitude cut; finish the coding problem
Verbal / communication Listening and speaking tasks Clarity and fluency
Technical interview OOP/Java, projects, SQL, light coding Project ownership + fundamentals
HR interview Fit, role understanding, puzzle Motivation + communication

Technical interview experience 1 - Tech Consultant, on-campus 2024

Technical interview experience 1

Candidate profile: B.Tech fresher; EY GDS Consultant role

Online assessment
  • Aptitude: logical, quantitative, verbal
  • Coding: single easy problem; ~45 minutes
  • Tip: Practise arrays/hashing easy problems until one full AC is automatic
Verbal ability
  • Listening / speaking communication screen
  • Tip: Quiet room; clear mic - same hygiene as Accenture-style verbal rounds
Technical interview
  • OOP principles and real-life applications; Java follow-ups if Java is preferred
  • Academic projects - implementation and challenges
  • DBMS: joins, normalisation, one SQL query
  • Coding: two questions on HashMap and HashSet
  • Result: Cleared → HR
  • Tip: Prefer language you can defend under “why” questions
HR interview
  • Family background; why this language
  • Upcoming technologies; Developer vs Consultant difference
  • Simple puzzle / analytical prompt
  • Final result: One campus report selected 22 of ~120 interviewed
  • Tip: Explain Consultant as client-delivery problem solving, not only ticket coding

Key takeaways: EY GDS wants fundamentals plus role awareness. Project clarity beats exotic algorithms.

Takeaways

  • What decided it: Easy OA coding plus verbal clarity, then OOP/SQL/HashMap answers and a crisp Developer vs Consultant distinction in HR
  • Common fail: Treating Consultant as “only coding”, or weak project challenge stories after clearing aptitude
  • How to practise: One easy array/hash AC under 45 min; join+normalisation SQL; rehearse Consultant as client-delivery problem solving

Technical interview experience 2 - Combined tech + project panels

Technical interview experience 2

Candidate profile: Campus GDS candidate; project-demo heavy panel

Project-first technical
  • Some panels listen to a unique project / chatbot demo and skip favourite-subject grilling
  • Ask about training period, tech stack, role - shows curiosity
  • Tip: Host a live demo if allowed; proves authenticity
DSA + OS/DBMS variant (Aug 2024 report)
  • Resume and project questions
  • DS: stacks, queues, deques, linked lists, heaps
  • Coding: reverse linked list, string manipulation, sliding window
  • OS and DBMS fundamentals
  • ~30 minute mixed interview in one account
  • Result: Advances when explanations are structured
  • Tip: Start with approach, then code; narrate complexity

Key takeaways: Panel style varies - prepare both “project theatre” and “whiteboard DSA” modes.

Takeaways

  • What decided it: Either a live project/chatbot demo that proved authenticity, or structured DSA (LL reverse, sliding window) with OS/DBMS narration
  • Common fail: Preparing only one mode (demo-only or LeetCode-only) for a panel that uses the other
  • How to practise: Keep a demo-ready project; also drill stacks/queues/heaps with complexity narration for ~30 min mixed panels

Pool campus experience - HR before technical (2024)

Pool campus HR-first variant

Candidate profile: Pool-campus 2024 batch; OA cleared with aptitude, technical MCQs, and two easy coding problems

Online assessment
  • Aptitude, technical MCQs, and two easy coding questions
  • Candidate tip: finish early - some drives rank by completion time, not only score
HR before technical (unusual order)
  • ~10-minute virtual HR after OA: introduction, then five-minute extempore (example topic: Manufacturing Sector of India)
  • Short closing - “Do you have questions for me?”
  • Result: Advanced to technical; final outcome not selected after technical
  • Tip: Treat HR as scored even when it runs before tech; keep extempore structure (intro → two points → conclusion)
Later technical round
  • Final-year project and side projects; SQL joins; technologies learning now
  • Tip: Most questions traced to projects and trending tech - depth beats breadth

Key takeaways: Round order is not fixed across EY pool drives - read the invite mail literally.

GDS on-campus 2023 - cybersecurity-heavy technical

GDS 2023 selected candidate

Candidate profile: B.Tech; EY GDS on-campus 2023; selected and joined GDS

Online stages
  • Aptitude (~30 English and reasoning questions) plus two easy coding problems
  • Technical ~25 min; HR ~15 min after selection from technical list
Technical highlights
  • Introduction led to conversational HR-style warm-up (hometown)
  • Swap two numbers without a temp variable (arithmetic and pointer approaches)
  • Cybersecurity: SQL injection, industry breaches, prevention - not only CS101
  • Result: Cleared → HR → offer after ~two weeks
HR highlights
  • Project challenges and how you coped; interest in technologies (e.g. data science side projects)
  • Higher studies plans; location preferences
  • Tip: HR is elimination on many GDS drives - align answers with technical stories

Key takeaways: Security-aware project narratives help even for general GDS roles.

HR interview experience

HR interview experience

Candidate profile: Candidate cleared technical

HR prompts
  • Tell me about yourself / family
  • Why EY GDS? Why Consultant over Developer?
  • Strengths; relocation; higher studies plans
  • Technology trends you follow
  • Light puzzle
  • Online vs offline HR sometimes offered on campus day
  • Final result: Same-day or short-wait results depending on drive

Key takeaways: Role clarity matters. “I only want to code” without client-delivery framing can clash with Consultant hiring.

Sample answers for high-frequency questions

Use these as frames, not scripts.

Technical

Q. OOP pillars with a real-life example?
A. Encapsulation (ATM hides ledger details), Abstraction (payment interface), Inheritance (SavingsAccount extends Account), Polymorphism (pay() differs by payment type). Tie to your project entities.

Q. HashMap vs HashSet - when each?
A. HashMap: key→value lookups. HashSet: unique elements, membership tests. Discuss hashing, collision ideas at a high level if probed.

Q. Developer vs Consultant?
A. Developer focuses on building software artefacts. Consultant (GDS framing) pairs technical delivery with client problem framing, documentation and stakeholder communication. Show you can do both.

HR

Q. Why EY?
A. Global client exposure via GDS + learning across technologies + a fact from the PPT. Avoid only Big4 prestige.

Common questions checklist

OA

  • Quant, logical, verbal
  • One easy coding problem

Technical

  • OOP/Java; projects; SQL joins/NF
  • HashMap/HashSet or linked-list/string coding
  • OS/DBMS basics on some panels

HR

  • Background; role understanding; trends; puzzle

Tips from successful candidates

Assessment tips

  • Finish the single coding problem fully
  • Revise aptitude timed sections
  • Treat verbal as scored communication

Interview tips

  • Project demo ready
  • Java/OOP with examples
  • One SQL join query practised on paper

HR tips

  • Know Consultant vs Developer
  • Prepare a short technology-trends take
  • Ask about training stack

Sources

These links are research inputs used to map EY GDS OA, verbal, and Consultant panels - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.

Verify round order against the drive mail (some pools run HR before technical).

Similar companies

Deloitte · PwC · Accenture · Capgemini

Ready to prepare? Clear the easy OA coding, own your project, and explain Consultant work without sounding anti-coding.

Pro tip: Shared funnels still filter hard before HR. Fundamentals plus role awareness decide offers.