Academic snapshot
Marks: 6.5+ CGPA / 65% common
Degree: B.E. / B.Tech (M.Tech on some posts)
Backlogs: None active preferred
Year: Final-year and recent grads
Tata Motors builds passenger and commercial vehicles, including a growing electric vehicle portfolio. Founded in 1945, it is one of India’s largest automakers with hubs in Pune, Jamshedpur, Sanand, and Bengaluru. Tata Motors recruits graduate engineer trainees for manufacturing, R&D, and automotive software roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch written, GD often same day | Auto/mechanical bar |
| tatamotors.com/careers | Resume volume; role-specific JD | Same fundamentals interview |
| Referral | Visibility | You still sit the test |
Off-campus does not mean easier thermodynamics. It often means more applicants who only prepared CAT aptitude, or who prepared TAS games by mistake.
Is 6.5 CGPA enough? It matches the commonly reported preferred floor on many campus notices (or 65%). Selection still hinges on the technical paper, a GD that does not collapse, and a technical that can defend one engine, CV system, or EV sketch. A 6.6 who can explain a 4-stroke and a simple EV architecture beats an 8.4 who only memorised MCQ keys.
Branches: Mechanical, Automobile, Production, Electrical for many GET seats. ECE and CS/IT for EV and some software posts. Confirm the notice.
What helps the resume screen: A lab or internship with a measurement (cycle time, defect ppm, range/efficiency delta), a Baja/Supra/EV project you can draw. See certifications after core subjects, not as a substitute.
Academic snapshot
Marks: 6.5+ CGPA / 65% common
Degree: B.E. / B.Tech (M.Tech on some posts)
Backlogs: None active preferred
Year: Final-year and recent grads
Skills they actually filter
Plant GET: Engines, manufacturing, SOM, quality
EV / software: C/C++/Python + vehicle electronics
Soft filter: GD + Tata values + plant willingness
Exam filter: Tata Motors Online Test
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 6.5+ / 65% on many campus lists | Some EV/software notices sit higher |
| 10th / 12th | Listed on some “throughout” JDs | Keep marksheets |
| Branch | Mech/Auto/Elec vs ECE/CS by JD | EV GET ≠ plant GET paper |
| Backlogs | None active | Clear before joining |
| Not TAS | Different program, different test | Do not mix prep |
Tata Motors shortlists on academics when the JD prints a floor, then filters on the technical half of the written and a values-aware HR. Clearing CGPA only gets you into the funnel. Plant location is a real gate.
Good fit: You can sit a timed aptitude + auto MCQ paper, you have one shop-floor or EV-lab story with a number, and you are open to Pune, Jamshedpur, or Sanand for the GET period the letter describes. You can say Why Tata Motors without reciting a TAS brochure.
Harder path: You only practiced CAT; you freeze on “why this cycle?”; you refuse any plant and still ticked “any location”; you prepared TAS games for a GET mailer. A high CGPA with zero manufacturing vocabulary usually dies in technical.
Branch myth: Non-Mechanical students are not auto-rejected on EV/software JDs. They also are not waved through Jamshedpur plant GET.
Gap years and backlogs: zero active backlogs is the usual campus rule. Plan to clear everything before joining. Full-time degrees only for the GET path described here.
Download 2026 Tata Motors placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Tata Motors does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers for the GET written, GD themes, and domain interviews, not leaked live papers, and not TAS assessments.
| Round (typical) | What to practice |
|---|---|
| Online / written test | Aptitude, mechanical/auto/electrical MCQs |
| GD | Structured speech on auto, EV, CV, current affairs |
| Technical | 2-3 domains deep + project |
| HR | Why Tata Motors, site, values |
Think of papers as simulators for written stamina. Tata Motors reuses themes (Otto/Diesel, manufacturing, SOM, EV basics, aptitude speed) more than exact clones.
| Theme you saw in a set | What to drill next | Why Tata Motors asks it |
|---|---|---|
| Otto / Diesel | Efficiency, knocking | Passenger + CV engines |
| Manufacturing | Casting, welding, machining | Shop-floor GET |
| EV basics | Motor, battery, inverter one-liners | Growing EV portfolio |
| SOM / TOM | Stress, gears, balancing | Design + plant |
| C/Python (EV paper) | Pointers, loops, scripts | Software / electronics |
| Aptitude speed | Percentages, DI | Written filter |
2025 PDFs often drill a simple Otto-cycle numerical. Own why compression ratio matters, not memorising a one-line definition.
Tata Motors hires freshers through campus cells and tatamotors.com/careers. After resume screen, the shape is industrial: a written that mixes aptitude with auto/mechanical (or EV/software), often a GD, then a technical that can smell a memorised one-liner.
Campus recruitment
PPT, written, technical and/or GD, HR. Often compressed.
Online applications
tatamotors.com/careers for GET / early-career; follow the invite for test vendor.
Referrals
Help visibility. You still need the written and a plant-location answer.
Degree, branch, CGPA/percentage, 10th/12th if listed, backlogs. Put one quantified internship or SAE/EV project on the first page if you have it.
Campus/off-campus as notified. Automotive GET hiring uses aptitude + technical filters. Section-level splits vary; your placement email wins. EV/software papers add C/C++/Python flavour.
| Section (typical) | What shows up | Pass habit |
|---|---|---|
| Aptitude | Quant, logical, sometimes verbal | 45-second skip |
| Technical | Engines, mfg, SOM, auto, EV lite | This is the cut |
| C/Python (EV/software) | Output, loops, basics | Do not invent syntax |
Negative marking: confirm on the invite.
Deeper OA notes: Tata Motors Online Assessment.
Plant GET (illustrative): Otto vs Diesel, knocking, casting vs forging, a welding defect, a stress-strain one-liner, gear ratio, a quality/SPC idea, a commercial-vehicle braking or chassis one-liner.
EV / software (illustrative): battery pack vs cell, motor vs ICE torque curve intuition, a C pointer output, a Python loop, why a sensor needs calibration.
You will not memorise 400 items. Cover your core syllabus once, then timed sets.
Technical: 25-45 minutes, 2-3 domains deep, projects read line by line. GD (when present): EVs, CV safety, localisation. Structure a 40-second turn.
Worked mini-outline - why Tata Motors (not TAS):
Why Tata Motors, Pune / Jamshedpur / Sanand / Bengaluru, shifts, CTC around ₹7-13 LPA, Tata values as stories. Full HR banks: HR interview questions.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | Online test | Drive-specific | Aptitude + domain |
| 2 | Technical / GD | 25-45 min / 15 min | Depth + structure |
| 3 | HR | 15-25 min | Site, values, fit |
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week |
| Online test | 1 day | Written or portal |
| Tech / GD + HR | Same day or next | Campus compression |
| Offer / paperwork | Days | Written letter + site |
| End to end | ~2-6 weeks often | Campus can be 48 hours |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude | Skip rules | mock quiz |
| Auto / mechanical MCQs | Engines, mfg, SOM | 20 items/day |
| EV lite | Motor, battery, inverter | One sketch |
| C/Python (if JD) | Easy output | coding questions |
| GD / HR | Values + site | Two STAR + relocation |
| Minute | Move |
|---|---|
| 0-3 | Skim sections. Note negative marking. |
| 3-25 | Aptitude: skip after 45 seconds. |
| 25-55 | Technical: definition items first, then numericals. |
| 55-end | Flagged easy only. Guess only if no negative marking. |
Do not steal from technical to finish a puzzle. The domain MCQs are where GET shortlists die.
Write the mailer title at the top of your notes. If it says manufacturing GET in Jamshedpur, your bag is engines and shop-floor. If it says EV/software in Pune or Bengaluru, add C/Python and a pack/inverter sketch. Carrying both bags at 30% depth is how people fail both papers.
TAS campus is a Tata Group leadership program with a different assessment. Tata Motors GET is OEM engineering. If your seniors say “Tata games,” ask which logo and which JD. Preparing the wrong one wastes a month.
Leave the 400-page handbook in the bag. Seniors ask you to talk.
| Item | Tata Motors GET | TAS campus |
|---|---|---|
| Who hires | Tata Motors OEM | Tata Group leadership program |
| Test flavour | Aptitude + domain technical | Separate TAS assessment (often described as gamified / leadership) |
| Interview | Engines, EV, plant, values | Broader leadership / case |
| Site | Pune, Jamshedpur, Sanand, Bengaluru plants/offices | Different posting logic |
| Prep | This hub + preparation guide | Not this page |
If the PDF or email says TAS, stop using this hub as your paper trainer. If it says Tata Motors GET / graduate engineer, do not download TAS mocks.
Q1: Draw a 4-stroke. Mark valve events.
Q2: Why Diesel compression is higher; what knocking means on petrol.
Q3: One thing that changes on a commercial vehicle vs a hatchback (duty cycle, brakes, cooling). Stop before a 20-minute emissions lecture.
CV context is a Tata Motors differentiator versus a pure passenger-car OEM speech. You do not need to have designed a truck. You do need to not pretend a Nexon and a Prima are the same problem.
Do not recite a marketing brochure. An honest “I did a college EV workshop; here is the block diagram I can defend” beats a fake battery-chemist story.
Inventing a Sanand line story is worse than an honest college shop.
HR will not grade you on reciting integrity/excellence/responsibility. They will ask what you did when:
Prepare two STARs with a real ending. “Safety is our top priority” without a story is a fail.
Write four bullets. Speak one minute. Sit down.
| Week | Chapter focus | Output |
|---|---|---|
| 1 | IC engines + 4-stroke | 40 MCQs; Otto sketch from memory |
| 2 | Manufacturing + quality | 30 MCQs; one defect oral each |
| 3 | SOM/TOM lite + auto systems | 30 MCQs; one gear-ratio oral |
| 4 | EV lite if JD else CV systems | One block diagram; 20 MCQs |
| 5 | Aptitude speed + GD | 3 timed sets; 4 GD topics |
| 6 | Full written mocks + 2-domain orals | 2 mocks; error log closed |
ECE/CS on EV/software: swap weeks 1-3 toward C/Python and vehicle electronics. Do not carry both bags at 30%.
Plant page: Otto/Diesel; knocking; casting vs forging; takt; Cp/Cpk three bullets; one CV brake one-liner.
EV page: pack vs cell; inverter; motor torque sketch; C pointer vs array if the paper needs it.
Write it by hand. Recite it. Whiteboard reproduction is the point.
Write three columns: must have, can do two years, cannot do. Jamshedpur and Sanand are plant realities (shifts, township/hostel talk in some senior stories). Pune mixes plant and engineering. Bengaluru shows up more on EV/software chatter. If Jamshedpur is “cannot,” do not tick “any location.” HR will ask.
Bring water. If they ask a third domain you did not name, say so. Inventing a combustion lecture you cannot finish is worse. Have one metric and one thing you would redo on the internship.
Selected: accurate domain MCQs, one derived sketch, a values story that happened, honest site, not a TAS speech.
Almost-selected: CAT-only paper, “all of mechanical,” refusing the plant after “any location,” preparing TAS games.
The difference is oral practice plus reading the mailer logo.
Your invite wins. If there is a penalty, blank is better than a 1-in-4 thermo guess. Write the rule on the rough sheet.
Campus: 24-48 hours sometimes. Off-campus: weeks, and the JD may be EV-specific. Read the title. Prepping a generic “core company” speech for an EV software cell is a miss; prepping only Python for a Jamshedpur GET is a miss.
Keep a one-page error log: engine misses on the left, aptitude skips on the right. Night before: that page only. Sleep beats one more MCQ set.
Week-by-week calendars live on the preparation guide, not here.
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.
If a Tata Motors 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 Tata Motors sits around ₹7-13 LPA (candidate-reported - confirm the letter). Languages students mention most often: C++, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Tata Motors GET eligibility is drive-specific. Common India reports: B.E./B.Tech in Mechanical, Automobile, Electrical, Production, or related for plant/design GET; CS/ECE for some EV/software tracks; typically 6.5+ CGPA or 65%; no active backlogs. Always verify tatamotors.com/careers or your campus JD. This is not TAS.
What you are training for: Typical GET loop: Tata Motors Online Test (aptitude + domain technical) → Technical interview and/or GD → HR. End-to-end often 1-2 campus days or 2-6 weeks off-campus. Do not apply the TAS gamified leadership assessment to this engineering GET process.
Short version of the prep split: Split time roughly: 35% domain technical (engines, manufacturing, EV basics, or C/Python if software), 25% aptitude, 20% GD/technical oral, 10% Tata values/HR, 10% site/relocation. Do not prep TAS case games for a GET mailer.
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Tata Motors 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 Tata Motors 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 Tata Motors 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 Tata Motors?” 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.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Tata Motors-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.
Use this hub for the Tata Motors story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Tata Motors papers on three different days, then interview prep on the leftovers.
Figures are candidate-reported (as of August 2026). Tata Motors does not publish a single GET CTC PDF for every India intake.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| GET / many early-career engineering roles | ₹7-13 LPA | Primary band used on this hub |
| Some plant GET | Often toward the lower end | Site and role dependent |
| EV / software early-career | Inside the same band, sometimes higher | JD dependent |
| TAS / other Tata Group | Different process and bands | Do not mix |
Confirm base, bonus, and joining site on the written offer.
Know ₹7-13 LPA as the hub’s reported band and ask what this GET letter includes. Do not invent a number from AmbitionBox midpoints, and do not quote a TAS package.
Keep every email.
Maruti is passenger-car volume. Mahindra is SUV/tractor-heavy. Bosch is automotive-supplier plus industrial. Tata Motors adds commercial vehicles and a growing EV portfolio, plus Tata values in HR. Prep branch fundamentals for all; customise Why-company to CV + EV + the site you will actually join.
If the cell asks for marksheets, keep a thin file. Do not rummage in the cabin.
You do not need a certificate. You do need: do not defeat a guard, lock-out if the JD is plant, report a near-miss. A 40-second lab story beats “safety is our top priority.”
2024-style sets train aptitude plus engines/manufacturing.
2025-style sets keep those families and add more EV language in interview notes.
2026 pages are expected-pattern trainers. EV/software tracks need C/Python add-ons the older plant packs may not emphasise.
Three reviewed papers beat ten skimmed ones. When a year pack shows a manufacturing numerical, compute it once.
This is a cheap differentiator in a GET cabin full of people who only talked hatchbacks.
Net for 2026: pick plant vs EV/software now. A Mechanical student grinding only LeetCode will die on manufacturing MCQs. An ECE student grinding only IC engines will die on C. Process length matters for your calendar; it does not replace fundamentals.
Also expect more EV language in PPTs than 2018-era notes. The plant bar does not drop because the slide mentioned Nexon EV. Confirm GET vs TAS on the mailer, then spend the week on engines or C, not on arguing which Tata logo you applied to.
Typical GET path: Tata Motors Online Test → technical and/or GD → HR. Campus can finish in one or two days. Off-campus often 2-6 weeks. This is not the TAS leadership assessment.
Usually 3 (test, technical/GD, HR). Some campuses run both GD and technical. Count the mailer.
Yes. Free Tata Motors placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the paper archive.
Drive-specific. Recurring reports: aptitude + mechanical/auto/electrical technical. EV/software tracks add C/C++/Python. Confirm sections on your college email. Do not use a TAS pattern.
Commonly reported: 6.5+ CGPA or 65%; B.E./B.Tech in listed branches; no active backlogs. Your notice overrides this page.
Candidate-reported CTC often lands around ₹7-13 LPA as of August 2026. Some plant GET offers sit toward the lower end. The written letter is the only number that matters. Sites: Pune, Jamshedpur, Sanand, Bengaluru.
No. TAS is a separate Tata Group leadership campus program. Tata Motors GET is OEM engineering hiring. Mixing prep is a common unforced error.
Split time roughly 35% domain technical, 25% aptitude, 20% GD/oral, 10% values/HR, 10% site. Details: preparation guide.
Plant GET is mostly MCQ. EV/software commonly C, C++, or Python. Confirm the JD.
Yes. EV/software adds C/C++/Python and vehicle-electronics context. Plant GET stays engines, manufacturing, quality, CV systems. Read the JD.
Those are the India sites this hub emphasises. HR checks relocation. Be honest early.
Bank the written with skip rules. Rehearse one engine or EV sketch three questions deep. Decide plant yes or no. Confirm you are not preparing TAS by mistake.
Start with Tata Motors interview experience on this site. Public detailed write-ups are still thin; use campus blogs as maps, not formula sheets.
The aptitude half is familiar. The domain MCQs, the GD, and the plant-location HR are the difference. Treat it as GATE-lite plus values, not NQT with a logo swap.
All three run aptitude plus auto technicals and often a GD. Tata Motors adds CVs and EV product talk, and is not TAS. Customise Why-company and site answer.
Yes, as stories, not posters. Prepare two STARs (integrity, safety, a wrong number you fixed). Reciting the Code of Conduct without an example underperforms.
Helpful if you can defend your subsystem. Not a universal GET requirement. An honest workshop internship beats a fake team-captain story.
Detailed first-person write-ups are still thin. The pattern students and prep sites keep repeating for 2024-2026 GET drives is consistent enough to steal from: aptitude + domain written, a technical that goes into engines or EV basics, HR that checks site and Tata values, and a standing warning not to confuse this loop with TAS. More: interview experience.
Steal: written stamina; a 40-second GD; 2-3 domains deep; honest Jamshedpur/Sanand answer; TAS check.
Ignore: memorising a random PDF key; quoting EV CTC on a plant GET JD; preparing TAS games for a GET mailer.
If you only do three things: sit one timed written mock, pick two domains and speak them, and confirm the mailer says Tata Motors GET, not TAS.
Mechanical students on plant GET still face engines and manufacturing. ECE/CS students on EV/software still face C/Python and a bit of auto context. Mixing those prep lists is the most common unforced error after TAS confusion.
Helped: accurate technical MCQs; a derived sketch; a project metric; honest site; a values story that happened.
Hurt: guessed papers; shallow “all of mechanical”; refusing the plant after “any location”; a TAS speech in a GET cabin.
More narratives: Tata Motors interview experience.
Students who cleared describe banking aptitude, then spending the remaining minutes on engines and manufacturing they could derive. Students who failed often treated the paper as CAT and guessed thermo. Takeaway: domain MCQs are the cut.
The late-stage drop is rarely “they asked a hard gear problem.” It is location and values. People who ticked “any location” and then refused Jamshedpur, or who recited a TAS brochure, created avoidable rejects. Decide the city on paper. Tell one real story.
A friend on an EV software mailer will talk Python. That does not make Python your plant GET homework. Read the title. Mixing bags is the second most common unforced error after TAS confusion.
Maruti Suzuki · Mahindra · Bosch · L&T