EY Interview Questions: 9 Real Q&A + Prep Tips (2026)
Curated EY (Ernst & Young GDS India) interview questions with model answers.
Industry: Consulting & Technology Services. Difficulty: Medium. Hiring for: Associate Analyst - Technology Consulting, Software Engineer - GDS, Data Analyst - GDS, Cyber Security Analyst. Average package: ₹5-6.5 LPA (Fresher Analyst), ₹7-9 LPA (Experienced Associate/Digital Consultant).
Selection process
- Online Assessment (Aptitude, Logical Reasoning, Technical MCQs)
- Group Discussion (for some consulting-focused roles)
- Technical Interview 1 (Coding, DSA, Core Concepts)
- Technical Interview 2 (System Design, Project Discussion, Managerial Fit)
- HR Interview
Real interview questions and answers
HR: Why EY GDS, and how do you see yourself contributing to our global delivery model?
EY GDS attracts me due to its unique blend of global exposure and cutting-edge technology solutions, specifically within a 'Big 4' framework. I understand GDS focuses on delivering scalable, high-quality services to clients worldwide. My skills in data analysis and problem-solving, coupled with my collaborative mindset, align well with a global delivery model where cross-cultural communication and efficient execution are paramount. I'm eager to contribute to projects that leverage technology to solve complex business challenges for diverse international clients, enhancing efficiency and innovation within the GDS framework.
Technical: Explain the difference between a clustered and non-clustered index in SQL, and when would you use each?
A clustered index determines the physical order of data rows in a table, meaning the data itself is sorted based on the index key. A table can have only one clustered index, typically on the primary key, as it physically reorders the data. A non-clustered index, on the other hand, does not affect the physical order of data. It creates a separate structure containing the index key and pointers to the actual data rows. You'd use a clustered index for columns frequently used in range queries or sorting, like an `OrderID`. Non-clustered indexes are ideal for columns used in frequent `WHERE` clauses or `JOIN` conditions, where the physical order is less critical, but quick lookups are needed.
Behavioral: Describe a time you had to learn a new technology or skill quickly for a project. How did you approach it?
During my final year project, we needed to integrate a real-time data streaming component using Apache Kafka, which none of us knew. My approach followed the STAR method: **S**ituation: Project deadline was tight. **T**ask: Implement Kafka for real-time sensor data. **A**ction: I started with official documentation and online tutorials, focusing on core concepts like producers, consumers, and topics. I then built small proof-of-concept applications, iteratively adding complexity. I also leveraged forums and our mentor for specific roadblocks. **R**esult: Within two weeks, I successfully integrated Kafka, ensuring smooth data flow and meeting the project's real-time requirements, significantly enhancing the system's robustness.
Technical: What are the principles of Object-Oriented Programming (OOP)? Provide an example for each.
The four core principles of OOP are Encapsulation, Abstraction, Inheritance, and Polymorphism. **Encapsulation** bundles data and methods that operate on the data within a single unit (e.g., a `Car` class encapsulating `speed` and `accelerate()` method). **Abstraction** hides complex implementation details, showing only essential features (e.g., a `Car` interface with `start()` and `stop()` without revealing engine mechanics). **Inheritance** allows a new class (subclass) to acquire properties and methods from an existing class (superclass) (e.g., `Sedan` inheriting from `Car`). **Polymorphism** allows objects of different classes to be treated as objects of a common superclass, enabling a single interface to represent different types (e.g., a `Vehicle` array holding `Car` and `Bike` objects, each responding differently to a `start()` method).
HR: Where do you see yourself in the next five years, especially within a global consulting and technology firm like EY GDS?
In the next five years, I envision myself evolving into a specialized consultant or lead engineer within EY GDS, actively contributing to complex client engagements. I aim to deepen my expertise in a specific domain, perhaps cloud solutions or data engineering, while also developing strong project management and client-facing skills. I'm particularly keen on leveraging the global opportunities at EY GDS to work with diverse teams and international clients, understanding different business landscapes. Ultimately, I want to be a trusted advisor, driving technological innovation and delivering tangible value that aligns with EY's commitment to building a better working world.
Behavioral: Tell me about a time you faced a significant challenge in a team project and how you overcame it.
During a college hackathon, our team faced a major challenge when a key API we relied on changed its specifications mid-project, rendering our existing code incompatible. **S**ituation: Critical API change during a hackathon. **T**ask: Adapt quickly to avoid project failure. **A**ction: I immediately called a team huddle to assess the impact. We divided tasks: two members researched the new API documentation, while I started refactoring the affected modules. We communicated constantly, sharing findings and testing incrementally. **R**esult: Through intense collaboration and focused effort, we successfully refactored the integration within a few hours, submitted our project on time, and still managed to secure a top-five finish.
Technical: What is the SDLC (Software Development Life Cycle) and why is it important in project delivery at a firm like EY GDS?
The SDLC (Software Development Life Cycle) is a structured process that outlines the stages involved in developing and maintaining software. Typically, it includes planning, analysis, design, implementation (coding), testing, deployment, and maintenance. In a firm like EY GDS, SDLC is crucial because it ensures systematic, efficient, and high-quality project delivery. It provides a clear roadmap, promotes collaboration among global teams, helps manage risks, and ensures that client requirements are met consistently. A well-defined SDLC minimizes errors, optimizes resource utilization, and ensures timely delivery of robust software solutions to diverse international clients, maintaining EY's service standards.
Technical: How would you handle a situation where a client's requirements are vague or constantly changing?
Handling vague or changing client requirements is a common challenge in consulting. My approach would involve proactive communication and structured methodologies. Firstly, I'd schedule frequent, detailed discussions with the client to understand their core business needs and desired outcomes, using techniques like use cases or user stories. I'd document everything meticulously and seek regular sign-offs. Secondly, I'd advocate for an agile development approach, allowing for iterative development, frequent feedback loops, and flexibility to incorporate changes without derailing the entire project. Prioritization of features with the client would also be key, ensuring critical functionalities are addressed first while managing scope creep effectively.
Behavioral: How do you prioritize tasks when you have multiple deadlines approaching simultaneously?
When facing multiple simultaneous deadlines, I employ a structured prioritization strategy. First, I list all tasks and their respective deadlines. Then, I assess each task's urgency and importance, often using a matrix like Eisenhower's (Urgent/Important). I also consider dependencies – which tasks need to be completed before others can start. If possible, I'll break down larger tasks into smaller, manageable chunks. I communicate proactively with my team or manager about potential conflicts or if I foresee any delays, seeking guidance on re-prioritization if necessary. This systematic approach ensures critical tasks are addressed first, minimizing stress and maximizing efficiency.
Preparation tips
- Brush up on core computer science fundamentals: DSA (arrays, linked lists, trees, sorting), OOP concepts, and SQL queries. Expect basic to intermediate coding challenges.
- Understand the 'Big 4' consulting model and EY GDS specifically. Research their service lines (e.g., Technology Consulting, Cyber, Data & Analytics) to align your skills.
- Practice behavioral questions using the STAR method. EY values communication, teamwork, and problem-solving, crucial for global delivery roles.
- Develop strong communication skills. You'll be interacting with diverse teams and potentially global clients. Articulate your thoughts clearly and concisely.
- Be aware of current technology trends relevant to enterprise solutions (e.g., Cloud computing basics, AI/ML concepts, Cybersecurity fundamentals). While not deep dives, awareness is key.
Common questions about EY interviews
What's the typical fresher package for tech roles at EY GDS India?
For freshers in tech roles like Associate Analyst or Software Engineer, the typical CTC (Cost to Company) at EY GDS India ranges from ₹5 LPA to ₹6.5 LPA, depending on the specific role and college tier. This includes base salary, allowances, and sometimes a joining bonus.
How difficult is the interview process for tech roles at EY GDS India?
The difficulty is generally 'Medium'. The online assessment screens candidates on aptitude and basic technical knowledge. Technical interviews focus on CS fundamentals, coding, and projects. While not as intense as product companies, a solid grasp of core concepts and good communication skills are essential.
Do only tier-1 college students get hired for tech roles at EY GDS?
No, EY GDS hires from a wide range of colleges, including Tier-2 and Tier-3 institutions across India. While Tier-1 colleges might have direct campus placements, strong performance in online assessments, technical skills, and communication abilities are key for all candidates, regardless of college tier.
How long does the hiring process usually take at EY GDS India?
The hiring process at EY GDS typically takes anywhere from 3 weeks to 2 months from the initial application to the final offer. This duration can vary based on the specific role, the number of applicants, and interview panel availability. Campus drives are often faster, completing within 2-3 weeks.