EY Technology Consultant Interview Guide
About EY
EY is one of the Big Four professional services firms, and in India much of its fresher technology hiring happens through EY Global Delivery Services (GDS). GDS is EY's delivery network. Teams in India work on engagements led by EY member firms in other countries, which is why communication is assessed so seriously. The Technology Consultant track, often called Tech Consultant on campus, is a common entry point for engineering graduates.
Two details in candidate reports stand out. First, candidates describe a separate spoken-English assessment between the aptitude test and the interviews, so a candidate can be screened out before anyone asks a technical question. Second, service-line allocation can vary by campus drive. In one reported EY GDS Tech Consultant drive, students who cleared the assessment were sorted into lines such as BPM, FS IT Control, GRC Technology, Non-FS Risk Transformation, Oracle or Enterprise Applications, Cyber, and Technology Risk, and the candidate said the sorting criteria were not explained.
Interview Process Overview
Candidates report four common stages for the on-campus Tech Consultant role: an online assessment, a spoken-English or verbal-communication assessment, a technical interview, and an HR interview. Some drives add a group discussion or case exercise, which is more common for consulting-leaning roles, and some run the assessment and spoken-English test on different days. Results between stages can take around a week.
Selection is competitive. One candidate reported that 22 of the 120 students interviewed from their college were selected, while another reported that roughly 30% cleared the online assessment. Process details vary by campus, year, and service line, so confirm the format with your placement cell.
Stage 1: Online Assessment
Format: An online, proctored test on a platform such as SHL. Candidates report being required to sit alone on camera with no phone visible. Sections are individually timed, and you may not be able to move between sections or return to previous questions.
What they test: Speed and accuracy under time pressure, plus basic programming ability.
Typical questions reported by candidates:
- English comprehension — one candidate reported 22 questions in 18 minutes.
- Logical ability — reported as 14 questions in 14 minutes.
- Quantitative ability — reported as 14 questions in 20 minutes.
- Coding — one or two easy problems in about 45 minutes. Candidates describe examples such as summing the digits of a number or summing only the prime digits, where you write the function only.
- Candidates describe the difficulty as time pressure rather than hard questions, so practise timed sets.
Stage 2: Spoken-English Assessment
Format: A separate online assessment of listening and speaking. One candidate described it as SVAR, a conversational-English test with several task types. Others describe it as a verbal-ability test focused on listening and speaking.
What they test: Clarity, pronunciation, listening accuracy, and fluency, because GDS consultants work with teams and clients in other countries.
Typical task types reported by candidates:
- Listen to a sentence and repeat it exactly.
- Listen to a sentence with a missing word, then repeat it with the word filled in.
- Listen to a short conversation and answer questions about it aloud.
- Hear a sentence that contains errors and repeat it correctly.
- Receive a topic, prepare for 30 seconds, and then speak about it for 45 seconds.
Stage 3: Technical Interview
Format: A one-to-one interview, conducted in person on campus or virtually, with a manager or senior consultant. Candidates describe it as conversational and report that questions followed their preferred programming language and the projects on their CV.
What they test: Core computer-science fundamentals, SQL, how well you understand your own projects, and how you think under light pressure.
Typical questions reported by candidates:
- "Tell me about yourself," followed by a deep dive into the real-world application of your project.
- "What are joins in SQL?", followed by inner versus outer joins, left versus right joins, and two or three easy SQL queries using joins.
- Primary key versus foreign key, and normalization.
- OOP principles and their real-life applications, with language-specific follow-ups such as Java, plus coding questions on
HashMapandHashSet. - "What is recursion?", followed by writing Fibonacci recursively and explaining the base case. Other reported topics include singly versus doubly linked lists, binary search, the name of the last node in a tree, and, if machine learning is on your CV, "What is regression?"
Candidates also report a puzzle in this round or in HR. Treat it as a chance to reason aloud in a structured way. Review the EY Technology Consultant and Developer interview questions to practise the technical topics before the interview.
Stage 4: HR Interview
Format: A short, conversational interview, usually conducted in person. Candidates describe it as relatively easy, but it is still a selection round. At least one candidate reported being rejected after it.
What they test: Fit with EY's culture, clarity of motivation, location flexibility, and whether you understand what a consultant actually does.
Typical questions reported by candidates:
- "Tell me about yourself."
- "What is the difference between a developer's work and a consultant's work?"
- "What do you know about EY's work culture?"
- Preferred job location, hometown, and family background.
- "What did you learn in your B.Tech and how will it help you at EY?" and "Where do you see yourself in five years?"
What Interviewers Look For
- Clear spoken communication. GDS work is delivered for teams abroad, and the separate speaking assessment shows how much weight EY places on it.
- Solid fundamentals over advanced tricks. Joins, keys, OOP, recursion, and basic data structures come up far more often in candidate reports than hard algorithm problems.
- Ownership of your projects. Expect to explain why you built something, how it works, and what went wrong.
- A consultant mindset. The job is about solving a client's problem, not only writing code.
- Composure. When you do not know an answer, a calm "I'm not sure, but here's how I'd approach it" shows structured thinking.
How to Stand Out
- Practise speaking, not only coding. Rehearse repeating sentences accurately and speaking for 45 seconds on a random topic with only 30 seconds to prepare. Record yourself and listen back.
- Know SQL joins cold. Be able to explain inner, left, right, and full outer joins with a simple two-table example and write the query on paper.
- Prepare a two-minute walkthrough of each project. Cover the problem, your role, the technology choices, one challenge, and what you would change.
- Have a crisp answer to "developer versus consultant." A developer builds to a specification. A consultant helps the client decide what should be built and why, then makes sure it delivers value.
- Bring two printed copies of your resume for an in-person round.
Use InterviewBee's EY Consultant mock interview to rehearse your project explanation, SQL fundamentals, consulting motivation, and spoken answers under realistic follow-up questioning.
Common Mistakes to Avoid
- Spending all your preparation time on hard DSA problems and none on communication. Candidate reports emphasize easy coding alongside a demanding speaking assessment.
- Running out of time in the online assessment. Sections are timed separately and you may not be able to return to previous questions, so pace yourself.
- Listing projects or skills on your CV that you cannot explain in depth. Interviewers follow your CV and preferred language.
- Treating HR as a formality. It is a selection round, and vague answers about location or motivation can cost you the offer.
- Answering too quickly. Let the interviewer finish, pause, and answer with structure rather than speed.