HR interview questions
Common EY HR questions, sample answer frames, and STAR tips.
EY Interview Experiences
How EY fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
EY placement process includes: 1. Online Aptitude Test (60-90 minutes) - Quantitative aptitude, logical reasoning, verbal ability. 2. Group Discussion (20-30 minutes) - Current affairs and business topics. 3. Technical Interview (30-45 minutes) - Domain knowledge and problem-solving. 4. HR Interview (20-30 minutes) - Motivation, teamwork, and company fit. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 6.0 CGPA throughout (10th, 12th, graduation).
Fresher package ballpark (from student reports): Analyst/Associate: ₹6-10 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Aptitude Test | 60-90 min | Quant, logical, verbal |
| Group Discussion (if conducted) | 20-30 min | Current affairs / business topic |
| Technical Interview | 30-45 min | SQL, OOPs, projects, basics |
| HR Interview | 20-30 min | Communication, client readiness |
Real interview experiences
Section titled “Real interview experiences”Experience 1: Tech Consultant, EY GDS on-campus (2024)
Section titled “Experience 1: Tech Consultant, EY GDS on-campus (2024)”Source: GeeksforGeeks write-up - 22 selected out of 120 interviewed at that college
Online assessment
- Aptitude (logical reasoning, quantitative, verbal) followed by one easy coding problem in 45 minutes.
Verbal ability test
- A separate spoken-English stage assessing listening and speaking. EY runs this as its own gate, not as part of the interview.
Technical interview
- OOPs: the core principles plus real-life applications of each.
- Java-specific questions; database concepts including joins and normalisation.
- Two coding problems built around HashMap and HashSet.
HR interview
- Personal background, technology trends, the difference between a developer and a consultant, and one analytical puzzle.
Result: Selected as Consultant
What helped: foundations over breadth. The technical round stayed on OOPs, SQL and hashing rather than hard algorithms.
Experience 2: Tech Consultant, EY GDS on-campus (SHL assessment)
Section titled “Experience 2: Tech Consultant, EY GDS on-campus (SHL assessment)”Source: GeeksforGeeks write-up - about 30% cleared the online round
Online assessment (SHL), section by section
- English comprehension: 22 questions / 18 min. Logical ability: 14 / 14 min. Quantitative ability: 14 / 20 min.
- Two coding problems, 45 min total.
- A spoken-English module with seven sections, including sentence repetition, responding within a conversation, and speaking on a topic for 45 seconds.
Technical interview
- Career aspirations and behavioural questions first, technical content second.
- SQL dominated: types of joins, primary vs foreign key, writing queries.
- DSA: recursion and a Fibonacci implementation, linked lists, trees, binary search. Machine-learning questions off the resume.
HR interview
- Location preference, what you know about working at EY, hometown and family, and how your coursework will translate into contribution.
Result: Rejected after the HR round
Takeaway: HR is an elimination round at EY, not a formality. The write-up’s own advice is to move fast in the assessment, stay diplomatic on ambition questions, and avoid overclaiming technically. Note also that reported cycles differ: some run a group discussion, others a spoken-English test instead, and multiple accounts say the coding section carries the most weight in the shortlist.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Simple array or string warm-up. Usually expects two pointers / hashing
- SQL joins and aggregations. Usually expects GROUP BY, window functions
- OOPs design for a small system (ATM / library). Usually expects classes and relationships
- Discussion on SQL and Excel/logic, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why consulting?
- A client-facing or communication example
- Willingness to travel
- A time you influenced a decision
Practical tips for EY
Section titled “Practical tips for EY”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain SQL in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of EY panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, EY usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.