EY India Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about EY India. You are hired to sit in front of clients, so they weight how you think and communicate at least as much as raw technical depth.

• A candidate who explains a database index clearly in two sentences and then asks a sharp question beats one who knows three more algorithms but mumbles.
• If you can only fix one thing before your loop, fix the way you talk about what you know.

2Getting the call (the part most guides skip)#

EY India fills Tech Consultant roles through four doors. The door you walk through decides how much of the loop is automated versus human.

• Campus placements: structured drives, often compressed into one or two days.
• Off-campus drives and referrals: your best odds of a human reading your resume.
• Job portals: the EY careers site, LinkedIn, Naukri.
• Aptitude test platforms: these gate many requisitions automatically.

Referrals matter more than people think. EY runs a formal employee referral program, and a referred resume is far more likely to be read than to die in an ATS queue.

• Ask anyone at EY, EY GDS, or a college alum now working there to refer you against a specific job ID, not a vague "pass my resume along."
• Give them the requisition number and a two-line note on why you fit, so they can paste it straight into the referral form.
• A referral does not skip the aptitude test. It gets you into the test pool, which for many postings is the hard part.

Resume rules. One page for freshers, two at most for experienced. Lead every bullet with impact and a number.

• Weak: "Worked on a web app using React."
• Strong: "Built a React dashboard that cut a 3-hour manual reporting task to under 10 minutes for a 12-person team."

The pattern: verb, what you built, the number it moved, who it helped. If a bullet has no number and no beneficiary, rewrite it or cut it. That second bullet signals business impact, which is exactly the consultant mindset EY screens for.

ATS keywords. EY uses applicant-tracking systems, so mirror the job description.

• Make the real skills appear verbatim: SQL, Python, Java, cloud (AWS/Azure/GCP), SAP, data analytics, Power BI/Tableau, REST APIs, Agile, plus the specific domain in the posting (cybersecurity, ERP, data engineering).
• The ATS matches exact strings, so write "Power BI" if the JD says "Power BI," not "data visualization."
• Do not keyword-stuff. List only what you can defend, because every line is a line the technical panel can question.

3The loop at a glance#

The four rounds, what each one measures, and roughly how long it runs:

A few wrinkles worth knowing before you walk in:

• Some drives merge the managerial and HR rounds.
• Experienced hires may get an extra panel with the practice lead or partner who owns the account you would join.
• Campus hiring can run all of this in a single long day, so stamina counts: your energy in the HR round at 5pm should match the technical round at 10am.

4The aptitude and technical test, patterns, not problems#

This is the gate. Treat it as the most important round, because it is the one most people fail. The test typically has five sections.

Quantitative aptitude. Standard placement-prep material, moderate difficulty. Speed matters more than cleverness.

• Topics: percentages, ratio and proportion, profit and loss, time-speed-distance, time and work, simple/compound interest, averages, number systems, permutations and combinations, basic probability.
• You get roughly a minute per question, so memorize the shortcuts: percentage-to-fraction conversions, the work-rate formula, the compound-interest multiplier.
• The people who clear this are not smarter. They are faster, because they stopped deriving from scratch.

Logical reasoning. The puzzle-style questions are the time sink; train for them specifically.

• Topics: series, coding-decoding, blood relations, directions, seating arrangements, syllogisms, data arrangement puzzles.
• A circular seating puzzle can swallow four minutes if you draw it wrong once.
• Sketch the diagram first and mark fixed positions before placing anyone.

Verbal ability. For a consulting firm, clean English is non-negotiable, so this section doubles as a communication filter.

• Topics: reading comprehension, sentence correction, fill-in-the-blanks, synonyms/antonyms, para-jumbles.
• Read the comprehension questions before the passage so you know what you are hunting for.
• Treat para-jumbles as logic: find the opening sentence and the clear pronoun links first.

Coding / pseudocode. Easy-to-medium, not a competitive-programming gauntlet.

• You may get pseudocode MCQs (predict the output, find the bug) or one to two actual coding problems.
• Common patterns: string manipulation, arrays, loops, basic recursion, simple sorting/searching, output-tracing.
• You rarely get hard dynamic-programming problems on a consulting track.
• For output-tracing, write the variable values in the margin at each loop iteration instead of tracking them in your head. That is where most people slip.

Domain / technical MCQs. Tied to the stack in the job posting.

• Topics: SQL queries, DBMS normalization, OOP concepts, basic OS, networking basics.
• Expect a few SQL questions that ask you to read a query and predict the result set.
• Practice reading JOIN and GROUP BY queries both ways: writing them and tracing what they return.

How to practice. Do timed, sectioned mock tests, not untimed problem-solving.

• Aptitude is a speed game, and untimed practice trains the wrong muscle.
• Spend two to three weeks on a standard quant/reasoning prep set (the kind used for TCS/Accenture/Infosys-style placement tests works well here).
• Drill SQL and output-tracing separately in short daily blocks.

How to win the round. Manage the clock ruthlessly.

• Answer the questions you know fast, flag the slow puzzles, come back.
• Never leave easy quant points on the table because you got stuck on one seating-arrangement puzzle.
• Rough target: if a question has not resolved in about 90 seconds, mark it and move on.
• If the coding section allows, write clean code and dry-run it with one example before submitting. A function that passes the sample case and reads well usually clears the hidden cases too.

5CS fundamentals (the technical interview core)#

For a Tech Consultant role the technical interview is fundamentals plus your resume. You do not need competitive-programming wizardry. You need to explain core concepts clearly and connect them to real work.

DBMS and SQL. The heaviest-weighted area. If you prep nothing else for the technical round, prep this.

• Know joins (inner/left/right/full), GROUP BY and HAVING, subqueries, normalization (1NF/2NF/3NF), primary vs foreign keys, indexes and why they speed reads, and ACID properties.
• Be ready to write a SQL query live.

The classics that come up again and again:

-- Second-highest salary
SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

-- Count of orders per customer
SELECT customer_id, COUNT(*) AS order_count
FROM orders
GROUP BY customer_id;

OOP. The four pillars with a one-line real example each, plus overloading vs overriding and interface vs abstract class.

• Pillars: encapsulation, abstraction, inheritance, polymorphism.
• Have a concrete example ready: encapsulation is a bank account class that hides the balance field and only exposes deposit and withdraw, so no outside code can set a negative balance directly.

Operating systems. Mid-level, not kernel internals.

• Know: process vs thread, deadlock and its four conditions (mutual exclusion, hold and wait, no preemption, circular wait), scheduling basics, paging vs segmentation at a high level.
• Process vs thread is the one they almost always ask: a process has its own memory space; threads share the memory of their parent process, which is why threads are lighter but need locks.

Networking. Expect at least one of these.

• Know: the OSI/TCP-IP layers at a glance, TCP vs UDP, what happens when you type a URL and hit enter, HTTP vs HTTPS, DNS.
• For TCP vs UDP, lead with the trade-off: TCP guarantees ordered, reliable delivery with a handshake; UDP is fire-and-forget and faster, so TCP for a web page and UDP for a live video call.

Data structures and algorithms. Reason about complexity even if you are not grinding LeetCode hard problems.

• Know: arrays, linked lists, stacks, queues, hash maps, trees, and time complexity (Big-O).
• Know why a hash map lookup is O(1) average and when it degrades, and why searching a sorted array is O(log n) with binary search.

Your stack and projects. Whatever is on your resume is fair game.

• If you list cloud, SAP, Python, or a framework, expect depth questions.
• Rehearse a two-minute walkthrough of each project: the problem, your role, the tech, the measurable result.
• The fastest way to lose this round is to list "AWS" and then freeze when asked which services you actually used and why.

Definition, example, trade-off. Say it in that order every time and you sound like a consultant explaining to a client.

6Behavioral and culture fit#

EY's brand promise is "Building a better working world," and its people framework centers on qualities you should weave into your stories, not quote.

• The qualities: integrity, respect and teaming (inclusive teamwork), and the energy and courage to lead, all under a client-first, continuous-learning mindset.
• EY also talks heavily about LEAD performance behaviors and personal growth.
• You do not need to recite these. You need to demonstrate them through what you actually did.

Build your story bank first. Write 6-8 STAR stories (Situation, Task, Action, Result) before the interview and reuse them across questions.

• Cover: a conflict you resolved, a time you handled ambiguity, a deadline you saved, a time you learned something fast, a leadership moment, a failure you grew from.
• Always close with a result that has a number.
• A story without a measurable result reads as effort without impact, and impact is the whole point at a consulting firm.

Common prompts to prepare:

• "Tell me about yourself."
• "Why consulting, or why EY?"
• "Describe a time you worked in a team with a conflict."
• "Tell me about a tight deadline."
• "A time you had to learn a new technology quickly."
• "Where do you see yourself in five years?"

One full worked STAR example (for "Tell me about a time you handled an ambiguous problem"):

• Situation: During a college capstone, our client (a small retailer) could not say what report they wanted, only that "sales data was a mess."
• Task: As the data lead, I had to turn a vague complaint into something we could actually build in six weeks.
• Action: I ran two short interviews with the owner to find the real pain, then proposed a single dashboard scoped to three questions: top products, slow-moving stock, and weekly trend. I cleaned the data in Python and built the dashboard in Power BI, checking in weekly so we never drifted.
• Result: The owner cut the time spent on weekly stock decisions from about 2 hours to 15 minutes, and adopted the dashboard permanently. I learned that clarifying the question is half the consulting job.

Why that answer lands:

• It quietly shows integrity (honest scoping), teaming, initiative, and learning: the exact qualities EY screens for.
• It never names a single value out loud. You show the trait through the action, you do not announce it.

7Your prep plan#

Pick the plan that matches your runway. Every version front-loads aptitude on purpose.

4-week plan

• Week 1: Daily timed aptitude, quant and reasoning sections, one mock every other day. Start a SQL refresher.
• Week 2: Finish aptitude drills, add verbal practice. Deep-dive DBMS and OOP. Write first 4 STAR stories.
• Week 3: Networking + OS + DS/Algo fundamentals. Rehearse project walkthroughs out loud. Full mock aptitude test under timed conditions.
• Week 4: Mock interviews (technical + HR), polish all STAR stories, research EY's service lines and recent work, prepare your questions for the interviewer.

2-week plan

• Days 1-5: Timed aptitude every day (quant, reasoning, verbal) + nightly SQL and output-tracing drills.
• Days 6-9: DBMS, OOP, OS, networking fundamentals; one project walkthrough rehearsal daily.
• Days 10-12: Write and rehearse 6 STAR stories; two mock interviews.
• Days 13-14: Full mock aptitude test, review weak spots, prep "why EY" and your questions.

2-day crash plan

• Day 1: Two timed aptitude mocks. Drill SQL joins, normalization, OOP pillars, TCP vs UDP, process vs thread. Write 4 STAR stories.
• Day 2: One more aptitude mock focused on your weakest section. Rehearse "tell me about yourself," "why EY," and project walkthroughs out loud. Prepare 3 questions to ask. Sleep early.

8Why people get rejected at EY India#

Six failure modes, in rough order of how often they bite:

1. Aptitude score below cutoff. The number one reason, and it happens before any human sees you. The usual culprit: weak time management, burning eight minutes on two puzzles and running out of clock on fifteen easy questions you would have aced.
2. Shallow fundamentals. Reciting definitions but unable to write a basic SQL query or explain a concept with a real example. The panel tests depth by asking "why," so a memorized definition collapses on the second follow-up.
3. Weak communication. Consulting is a talking job. Mumbling, rambling, or poor English in the verbal and interview rounds is disqualifying even when the technical answer is correct.
4. Resume overclaim. Listing skills you cannot defend. If "AWS" is on your resume, you will be asked about it, and "I only used it a little" after claiming it reads as dishonest, the worst signal to send a firm built on integrity.
5. No curiosity or questions. Candidates who ask the interviewer nothing read as uninterested. EY wants people hungry to learn, so showing up with no questions is an active negative, not a neutral.
6. Poor fit on flexibility. Hesitation about shifts, relocation, or client travel can sink an otherwise strong candidate, especially for GDS and client-facing roles. Decide your real boundaries before the HR round so you answer with calm clarity instead of visible doubt.

9The offer, comp and negotiation#

The bands first, then how to move them:

• Freshers and analysts: total package roughly ₹6-9 LPA (EY GDS roles often land ₹5.5-8 LPA), structured as fixed base plus a modest variable/bonus component.
• Experienced Consultants (2-5 years): typically ₹10-18 LPA, with premiums for in-demand skills like cloud, SAP, cybersecurity, and data engineering.
• Numbers vary by location, service line, and your current CTC. Treat these as bands, not promises.

Negotiation tips for EY's context:

1. Anchor on skill scarcity, not need. If you bring a hot skill (certified cloud, SAP module expertise, strong data engineering), name it and ask for the top of the band. Specialized skills genuinely move the number, because those roles are the ones EY struggles to fill from the general pool.
2. Negotiate the whole package. Fixed vs variable split, joining bonus, and level/title matter as much as the headline figure. A higher band or level affects every future raise, so pushing for the next level up can be worth more over three years than a one-time bump to the base.
3. Be professional and have a real reason. "A competing offer at ₹X" or "my current fixed is ₹Y" is far more persuasive than a round number pulled from the air. EY HR respects data-backed asks and remembers candidates who stay polite, and you may well work with these people, so do not burn the relationship over the last 5 percent.

10Follow-ups#

Want this turned into a personalized, dated study schedule that counts down to your exact interview date? Tell me your timeline and current strengths, and I will build the day-by-day plan for you.