HR interview questions
Common Mahindra HR questions, sample answer frames, and STAR tips.
Mahindra Interview Experiences
How Mahindra fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Mahindra placement process includes: 1. Online Assessment (90 minutes) - Coding/aptitude questions. 2. Technical Interview Round 1 (60 minutes) - Technical concepts. 3. Technical Interview Round 2 (60 minutes) - Advanced concepts and projects. 4. HR Interview (30 minutes) - Motivation and company fit. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA or 70%.
Fresher package ballpark (from student reports): Analyst: ₹8-14 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online / Written Test | 90-120 min | Aptitude + domain / basic coding |
| Technical Interview | 30-45 min | Core subjects or IT fundamentals |
| HR | 20-30 min | Location, shifts, motivation |
Real interview experiences
Section titled “Real interview experiences”First, disambiguate: Mahindra & Mahindra (the auto and farm-equipment company) is not Tech Mahindra. Both hire “Graduate Engineer Trainees” and candidate reports get filed under both names, but M&M’s GET interview is a core-engineering and automotive-domain conversation, while Tech Mahindra’s is an IT-services funnel. Check which name is on your placement email. The notes below describe the M&M GET pattern, drawn from aggregated public candidate reports.
Individual M&M write-ups are thinner than for IT companies - the funnel is short and there is no coding round for core roles - so this is presented as the commonly reported pattern rather than as one person’s story.
The commonly reported pattern - GET, on-campus
Section titled “The commonly reported pattern - GET, on-campus”Stage 1 - online aptitude + technical test
- Quantitative aptitude and logical reasoning, plus a branch-specific technical section. Reported examples: thermodynamics and strength of materials for mechanical, circuits and machines for electrical.
- There is no DSA component for core branches. Speed on standard aptitude plus second-year core subjects is what clears it.
Stage 2 - technical interview
- Built on your branch’s core subjects and your project, not on general programming.
- Reported question flavours are heavily automotive: the working principle of an engine, how IC engines are evolving, diesel vs petrol engines, what the cetane number of diesel fuel measures.
- Industry-awareness questions recur: recent trends in the automobile industry, who leads on vehicle safety. These are asked as ordinary technical questions, so treating them as small talk costs marks.
Stage 3 - HR / resume round
- How your skills apply to the automobile industry, what value you would add to Mahindra, why Mahindra over competitors, and where you see yourself in five years.
- Resume claims are checked. Reports consistently warn against listing anything you cannot defend.
What the aggregated numbers say
Section titled “What the aggregated numbers say”- GET candidates rate interview difficulty around 3.1 / 5, with roughly 76% describing the experience as positive - moderate and fair rather than adversarial.
- The reported average time from application to hire for the GET role is around 38 days, so expect a slow, administrative back half.
Prep advice that recurs across reports
Section titled “Prep advice that recurs across reports”- Pick two core subjects and go deep, rather than skimming the whole syllabus - you will largely be interviewed on what you nominate.
- Read up on Indian automobile-industry trends and on Mahindra’s own positioning and products before the interview. “Why Mahindra” is a real question with a real wrong answer.
- Be able to explain your project end to end, including why you made each choice.
Sources: Glassdoor - Mahindra Graduate Engineer Trainee · Glassdoor - Mahindra and Mahindra interviews · Mployee - M&M Graduate Engineer Trainee questions
These are public candidate reports and vary by campus, branch, business unit and year. If your placement email or the official job posting says something different, follow that.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Basic array / string coding. Usually expects clear logic
- OOPs or domain follow-ups. Usually expects fundamentals
- Explain a project end-to-end. Usually expects clarity and ownership
- Discussion on core + IT tracks and OOPs/SQL for IT, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this company / business unit?
- Location flexibility
- How your project or internship maps to the role
- Long-term plans
Practical tips for Mahindra
Section titled “Practical tips for Mahindra”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain core + IT tracks in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Mahindra 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, Mahindra 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.