Academic snapshot
Marks: 7.0+ CGPA / 70% throughout (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads (~2 years)
Mahindra Placement Papers 2026
Mahindra & Mahindra is a major Indian automotive and farm equipment manufacturer with a growing portfolio of SUVs, tractors, and electric vehicles. Its engineering teams hire for mechanical, electronics, and software roles supporting vehicle design, connected car features, and EV platform development.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Mahindra fresher eligibility for campus drives
Mahindra campus hiring is entity-specific. A software/analyst letter from Mahindra Tech is not a Pune plant GET letter, and neither is a Tech Mahindra ASE offer. Read the notice before you memorise one CGPA story.
Who this hub is for
- For: Students targeting Software Engineer / Analyst roles on Group digital or Mahindra Tech tracks, and students targeting GET (Mechanical/Automobile/related) at plants.
- Not the same track: Tech Mahindra volume ASE (often ₹3.5-4.5 LPA, SuperCoder on some paths). Use that hub instead.
- Experienced hires: Mid-level loops add deeper design or domain ownership and different CTC.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, college CGPA list when printed | Coding/core bar, interview depth |
| Careers portal / referral | Resume screen volume | Still expect OA + interviews |
| GET off-campus | Aptitude paper may be shorter | You still defend a core project |
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. Selection still hinges on OA and interview narration. A 7.1 with a clear project beats a 9.0 that cannot explain a library-management sketch.
Branches: CS/IT/ECE/EE for software. Mechanical/Automobile/Electrical for many GET notices. Related streams show up when the JD lists them.
Gaps and backlogs: Active backlogs are a hard blocker on most drives. Gaps of 1-2 years are often acceptable with a skills story. Lying about CGPA is an instant HR fail.
What helps the resume screen: One project you can defend, any internship with ownership language, and (for software) basic DSA. See certifications only after fundamentals are solid.
Branch & skills
Software: CS / IT / ECE / EE
GET: Mechanical / Automobile / related
Languages: C, C++, Java, Python
Focus: Aptitude + technical + one defendable project
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ / ~70% across 10th, 12th, graduation | Verify every drive |
| Degree | B.Tech / B.E. / M.Tech / MCA | Related degrees on many posts |
| Branch | CS/IT/ECE/EE or Mechanical/Auto for GET | JD wins |
| Year | Final year + recent grads (~2 years) | Intern conversion also appears |
| Backlogs | No active backlogs | Clear them before paperwork |
| Coding languages | C, C++, Java, Python | Stick to one for software OA |
Mahindra CGPA criteria
The minimum CGPA required is commonly 7.0+ CGPA / 70% throughout. Treat it as a shortlisting filter when printed. OA and interviews still decide.
| Academic Level | Minimum (typical) | Notes |
|---|---|---|
| 10th | 7.0+ / 70% | Consistently applied on many drives |
| 12th | 7.0+ / 70% | Diploma holders evaluated similarly |
| Graduation | 7.0+ / 70% | No active backlogs at hiring |
| Backlogs | None active | Cleared backlogs generally accepted |
Mahindra placement papers - last few years
Download 2026 Mahindra placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Mahindra previous year papers actually train
Mahindra does not publish one permanent official paper set. Papers on this site are pattern trainers for the first filter and early technical rounds.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy: technical MCQs, aptitude, domain, coding when present |
| Technical 1 | Live coding or core viva + project |
| Technical 2 | Deeper design / domain / library or workflow sketch |
| HR | Why Mahindra, location, digital or plant story, integrity |
Themes that keep repeating (2024-2026)
- 2024 software campus: ~90-minute mixed OA, then two technicals (projects, a library-management style sketch, recursive vs iterative coding), then HR on digital initiatives and location. One note ended at about ₹10 LPA in ~2 weeks.
- 2024 GET mechanical (Pune, off-campus): 50 questions / 60 minutes (quant, reasoning, Carnot efficiency and similar), then ~30 min face-to-face on an Automated Gear Shifting project, second law, stress vs strain, 4-stroke cycle.
- 2025-2026 prep expectation: Keep aptitude speed and either one complete coding submit or a core-subject project warm. Domain MCQs still mention automotive technology and digital transformation. Treat PDF packs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: run a full ~90-minute mock (aptitude + technical + domain) in the language or discipline you will use.
- Untimed review: rewrite the cleaner coding solution or the cleaner thermo derivation.
- Map each miss to a theme and pull two cousins from coding questions or aptitude.
- Speak a 60-second project story and a 20-second “Why Mahindra.”
- Log one STAR teamwork story the session reminded you of.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Mahindra asks it |
|---|---|---|
| Percentages / ratio / TSD | Speed arithmetic | Volume aptitude |
| SQL / OOP / OS one-liners | Joins, inheritance, deadlock | Technical MCQs |
| Arrays / strings / recursion | Complete submit | Software tech round |
| Library or workflow sketch | Actors, APIs, bottlenecks | Tech 2 design lite |
| Thermo / manufacturing / machines | One worked numerical | GET viva |
Mahindra placement process, round by round
Mahindra hires freshers through campus cells, the careers portal, and referrals. After eligibility, software tracks look like mixed OA then two technicals then HR. GET tracks can compress the written paper and lean harder on a core viva.
Application methods
Campus recruitment
Through college placement cells. PPT, then OA and interviews on a batch timeline.
Online applications
Apply on mahindra.com careers. Follow the invite for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, 7.0+ / 70% throughout when printed, backlogs, and year of passing. This is a gate, not the hard filter.
2. Online Assessment (~90 min)
Candidate reports commonly describe a ~90-minute software assessment with about 30-50 questions. Exact splits vary; treat the table as a working map.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Technical | 15-25 | 45-60 min | Programming, DSA, DBMS, OS |
| Aptitude & reasoning | 10-15 | 20-30 min | Quant, logic, DI |
| Domain | 5-10 | 10-15 min | Automotive / digital / IT services lite |
Languages: C, C++, Java, Python when coding is present. No negative marking is often claimed; still do not random-fill if your mailer says otherwise. Roughly 30-40% of a large OA batch advancing is a common rumour, not a promise.
GET variant: One March 2024 Pune note described 50 questions in 60 minutes mixing quant, reasoning, and mechanical basics (Carnot efficiency). If your invite looks like that, do not panic-rewrite a 90-minute software plan.
Student tip: Bank easy quant first. Leave time for technical MCQs. If coding is present, finish one complete program.
Deeper OA notes: Mahindra online assessment.
3. Technical interview 1 (~60 min)
Virtual or face-to-face. Software: OOP, DBMS, one live easy-medium code, project deep dive. GET: discipline fundamentals plus the resume project.
Pass habit: “I wrote X, the bug was Y, the metric was Z.” “We used React” is not a project story. For GET: name the cycle, the assumption, and the result.
4. Technical interview 2 (~60 min)
Deeper projects, a small design sketch (library management, workflow, vehicle telemetry lite), or advanced core questions. Evaluation is approach plus communication, not contest rating.
5. HR (~30 min)
Why Mahindra, location (Mumbai, Pune, Bangalore, or plant city), joining date vs finals, integrity. Know the ₹8-14 LPA software/analyst band if that is your track so you do not invent a 25 LPA ask.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA | ~90 min (or ~60 GET) | Timed accuracy |
| 2 | Technical 1 | ~60 min | Code or core + project |
| 3 | Technical 2 | ~60 min | Depth / design lite |
| 4 | HR | ~30 min | Fit, location, logistics |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA → shortlist | A few days common | Same-day next rounds on some campuses |
| Technical + HR | ~1 week | Order can shuffle |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
How Mahindra differs from generic IT services
- You may be asked about SUVs, farm equipment, EV, or digital cockpits even on a software letter.
- CTC bands for Group software/analyst reports often sit above volume ASE letters.
- Two technicals are common; do not train only one 20-minute chat.
- Confirm you are not sitting the Tech Mahindra SuperCoder path by mistake.
Aptitude skip rules that save the 90-minute paper
- Percentages, ratio, average: do first.
- Time-work / TSD: one equation, not five tricks.
- One DI table: question first, then two cells.
- Seating / puzzle: 45 seconds then skip.
- Technical MCQs: eliminate two options; do not overthink pointer trivia.
- Domain (EV / farm / digital): one concrete fact beats a paragraph of slogans.
- Coding if present: read both prompts; finish the easier one fully.
Log every mock: which of the seven ate the clock. That log is the prep plan.
Weekend mock that matches a real drive
Saturday 10:00: 90-minute mixed OA (technical + aptitude + domain).
Saturday 12:00: review misses into an error log.
Saturday 16:00: one easy coding rewrite or one core numerical written by hand, plus 20 one-liners.
Sunday 11:00: 20-minute technical oral (OOP + SQL + project, or 4-stroke + project).
Sunday 12:00: HR including city and CTC band.
Two weekends of that beat twelve nights of random YouTube. If the PPT named Tech Mahindra, stop and switch hubs.
Documents pack
10th, 12th, all semesters, ID, photo if asked, resume one page. Throughout 70% means the 12th PDF matters. Name and percentages must match the college form.
Night-before checklist
- Charger, ID, resume print
- 10th/12th PDFs on phone and drive
- One language chosen for software coding, or one core topic sheet for GET
- 60-second intro recorded once more
- One light aptitude set already reviewed
- Sleep. A 9 a.m. OA after a 3 a.m. mock is how easy verbal items go wrong
What’s on the Mahindra test & where to practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How students actually prep for Mahindra
If a Mahindra invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Mahindra sits around ₹8-14 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported campus floor is often 7.0+ CGPA or 70% across 10th, 12th, and graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, EE or related fields for software tracks; final-year or recent grads (within about 2 years); no active backlogs; gaps often acceptable up to 1-2 years. Core GET notices may list Mechanical/Automobile. Always verify the drive notice.
What you are training for: Typical software/analyst loop: Online Assessment (~90 min, technical + aptitude + domain) → Technical 1 (~60 min) → Technical 2 (~60 min) → HR (~30 min). Core GET paths may run a shorter aptitude paper then a mechanical viva. Campus batches often finish in about 2-3 weeks.
Short version of the prep split: For software tracks, split time roughly 40% programming/DSA, 30% CS + automotive/digital domain lite, 20% timed aptitude, 10% project + Why Mahindra. Languages: C, C++, Java, Python. Core GET: discipline MCQs plus one project you can defend. Full week plan: /mahindra/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Mahindra previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Mahindra drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Mahindra usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Mahindra?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Mahindra-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Mahindra story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Mahindra PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Mahindra papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Mahindra papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Mahindra-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
What to practise this month for Mahindra
Week-by-week calendars live on the preparation guide. This section is the focus split so you do not study like you are sitting Tech Mahindra SuperCoder and a mechanical GET viva on the same night.
Time split that matches the filter
| Bucket | Share | What “done” looks like |
|---|---|---|
| Programming / DSA or core numericals | ~40% | One complete coding submit or one worked thermo/machines problem |
| CS or discipline MCQs | ~30% | OOP/SQL/OS or manufacturing/powertrain one-liners |
| Timed aptitude | ~20% | Full 60-90 minute mocks |
| Project + HR | ~10% | 60-second story + Why Mahindra + city answer |
If you already clear aptitude and fail coding, invert 40/20 for two weeks. If you code fine and fail domain MCQs, spend three evenings on EV / farm-equipment / digital one-pagers.
This week, not “someday”
- One full timed mock from aptitude questions plus online assessment.
- Two easy coding problems submitted end-to-end or two core numericals written by hand.
- Twenty SQL/OS or thermo/manufacturing one-liners on paper.
- Record “Why Mahindra” once with one real product line named. Cut fillers.
- Error log: three slow quant types, one coding or core miss, one HR blank.
What not to waste time on
- Treating Mahindra and Tech Mahindra as the same letter
- Memorising “last year exact paper” dumps
- Starting a second coding language the week of the drive
- Staff-level system design for a campus analyst cabin
- Quoting 25 LPA in HR on an ₹8-14 LPA software drive
Entity check before you mock
If the PPT says Tech Mahindra, switch hubs. If it says GET Mechanical, Pune plant, drill Carnot, 4-stroke, and your project. If it says Mahindra Tech / digital, keep the 90-minute mixed OA warm.
Software vs GET: two different months
Software / analyst: your week is mixed OA stamina. You need sectional speed, one complete program, and a 60-second project with a metric. Domain MCQs are a bonus, not a vehicle-dynamics exam.
GET mechanical: your week is aptitude plus one project you can defend at a whiteboard. Carnot, 4-stroke, stress vs strain, manufacturing defects. “I also did a bit of Python” is optional colour, not the offer.
Do not run both calendars at half effort. Pick the notice in front of you. If your college has both drives, stack software mocks on weekdays and one GET oral on Sunday. That is still two processes, not one “Mahindra prep.”
Why Mahindra without a slogan
Pick one real line: Scorpio/XUV, farm tractors, EV, or a digital cockpit story from the PPT. Say what the team builds and what you want to learn in year one. “Diversified conglomerate with excellent growth” is what everyone else says. Interviewers have heard it since 2018.
Offer-stage discipline
- Read location and entity (Mahindra Tech vs plant vs Tech Mahindra)
- 10th/12th/degree % must match
- Verbal classroom “selected” is not an offer PDF
- Do not resign another services offer until the letter names CTC and city
Mahindra fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on entity (software vs GET), location, hiring year, and written components.
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst | ₹8-14 LPA | Primary band for this hub |
| Campus note (2024) | ~₹10 LPA | One software path; not a guarantee |
| GET / plant (indicative) | Varies by notification | Confirm allowances on the letter |
| Senior / mid-level | Higher range | Not the fresher campus default |
Confirm base vs variable, joining location, and any service agreement on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Health insurance, PF/gratuity on the usual India pattern, learning after joining (manager-dependent), and relocation when the letter names Mumbai, Pune, Bangalore, or a plant city. Hybrid language varies. Ask HR; do not assume WFH.
How to talk CTC in HR
Know ₹8-14 LPA for software/analyst if that is your track. Ask how the package splits. One calm clarifying question beats aggressive negotiation with no market anchor.
Mumbai, Pune, and Bangalore show up most in software notes. Plant GET letters name the unit city. A higher blog midpoint that assumes Bangalore does not apply to a Nagpur or Chennai plant posting. Ask HR the city before you compare TCS Ninja numbers in a WhatsApp group.
Mahindra hiring updates for 2026
Entity names on letters
Mahindra Tech, plant GET, and Tech Mahindra still get mixed up in student groups. Read the employer line.
Mixed 90-minute OA
Software tracks still mix technical, aptitude, and domain. Coding is not always the whole paper.
Two technicals common
Project plus a small design or core viva. One 20-minute chat is not the whole loop.
EV and digital in HR
Electric vehicles, farm equipment, and digital transformation show up in PPTs. Day-one work is still a team and a stack or a shop floor.
Net for 2026: do not wait for Mahindra to become a coding-only product company. Double down on timed aptitude, one complete program or core story, and one product line you can name.
Common questions about Mahindra hiring
Papers & process
Can I download Mahindra placement papers PDF for free?
Yes. Free Mahindra placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What is the Mahindra placement process for freshers?
Typical software path: Online Assessment (~90 min) → Technical 1 (~60 min) → Technical 2 (~60 min) → HR (~30 min). GET paths may use a shorter aptitude paper then a core viva. Campus batches often finish in about 2-3 weeks.
How many interview rounds does Mahindra usually have?
Most fresher software loops report four stages. GET write-ups sometimes show three. Count the mailer for your entity.
What does the Mahindra Online Assessment look like?
Often ~90 minutes with ~30-50 technical, aptitude, and domain questions; coding on some invites. GET papers can be ~50 questions in 60 minutes. Details: online assessment.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly reported floor: 7.0+ CGPA / 70% across 10th, 12th, and graduation; listed degrees; no active backlogs; gaps often ≤ ~2 years. Your drive notice overrides this page.
What is Mahindra fresher salary in India?
Candidate-reported Software Engineer/Analyst CTC often lands around ₹8-14 LPA (as of August 2026). One campus note cited ~₹10 LPA. GET letters differ. The written offer is the only number that matters.
Is Mahindra the same as Tech Mahindra?
No. Tech Mahindra is the Group IT services company with its own ASE process. This hub is Mahindra Group / Mahindra Tech / plant GET style drives. Read the employer name.
Prep & Mahindra-specific
How should I prepare for Mahindra?
Software: ~40% DSA/programming, 30% CS + domain lite, 20% aptitude, 10% project/HR. GET: core subjects plus one project. Details: preparation guide.
Which programming languages are allowed?
C, C++, Java, and Python are the usual set for software. Confirm on the invite. Do not switch languages the week of the drive.
Do I need automotive knowledge for software roles?
A little helps in domain MCQs and HR. You do not need vehicle-dynamics expertise for a Java campus role. GET mechanical loops do expect core depth.
Mahindra vs TCS vs Infosys for freshers?
Mahindra software/analyst reports often sit around ₹8-14 LPA with automotive/digital stories. TCS/Infosys are volume IT services with different exam names. Share aptitude+coding; customise HR.
Any pro tip that actually changes outcomes?
Name the entity on your invite. Finish aptitude plus one complete coding or core story. Research one real product line so Why Mahindra is not a slogan.
Where can I read real interview experiences?
Start with Mahindra interview experience on this site, then cross-check recent campus notes for software vs GET variants.
Will I have to relocate?
Often yes. HR commonly asks about Mumbai, Pune, Bangalore, or the plant city. Answer honestly; state constraints early.
Does every Mahindra drive include coding?
Software/analyst OAs often mix MCQs with coding on some invites. GET mechanical papers can be aptitude plus core with no coding. Read the notice for your entity before you spend a month on only LeetCode.
Mahindra - recent candidate experiences
Software Engineer campus path (Nov 2024)
A campus path summarized on this site interview experience described a ~90-minute online assessment, two technical rounds (projects, library-management design sketch, recursive/iterative coding), and HR on digital initiatives and location. Offer in about 2 weeks at about ₹10 LPA.
Takeaway: two technicals are real. A tiny design sketch plus a project metric beat a CGPA-only story.
GET Mechanical, Pune, March 2024
Rajveer’s off-campus GET interview (published 2025 on Jobs Adda Freshers) opened with a 50-question / 60-minute online aptitude (quant, reasoning, mechanical basics like Carnot efficiency). Face-to-face tech (~30 min) covered an Automated Gear Shifting project, second law, stress vs strain, and 4-stroke cycle. Why Mahindra answer named engineering and manufacturing, not a generic IT slogan. Selected within a week.
Takeaway: GET is a different paper. Do not train only LeetCode if the notice says Mechanical.
Composite notes students repeated
What helped: full timed mocks; one passing coding submit or a core project with a metric; knowing the entity name; a short Why Mahindra with one product line.
What hurt: mixing Tech Mahindra ASE prep into a Group software drive; treating HR as a formality; quoting product-company CTC; freezing when asked “what would you change in your project?”
After you clear OA
- Re-solve every miss from your last two mocks cold.
- Speak two STAR stories without notes.
- Warm one array/string medium or one core numerical.
- Sketch the library/workflow or the 4-stroke story once more.
- Sleep and document scans.
What mass vs selective hiring means here
A Mahindra Tech campus can still take a batch. A plant GET drive can be smaller and slower. Either way, aptitude still deletes a chunk. Empty technical MCQs still delete a chunk. Easy coding still deletes people who never compile. Your job is to be easy to say yes to: complete written, one passing program or a core project sentence with a metric, documents ready.
Keep a backup process live until the offer PDF lands. If you also hold a TCS or Infosys letter, compare city, joining date, and entity name, not only the blog midpoint.
More fresher narratives: Mahindra interview experience.