Academic snapshot
Marks: 7.0+ CGPA / 70% common; some 60% throughout
Degree: B.E. / B.Tech (M.Tech on some posts)
Backlogs: None active preferred
Year: Final-year and recent grads
ABB Placement Papers 2026
ABB is a global engineering company focused on electrification, automation, and robotics for utilities and industry. In India, ABB is a steady recruiter for electrical, mechanical, and software engineers across Bengaluru, Nashik, and Vadodara. Teams work on power grids, factory automation, and industrial digital platforms.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to ABB in 2026?
Who this hub is for
- For: Students targeting Graduate Engineer Trainee (GET) and early-career software / digital automation roles at ABB India.
- Not the same track: Experienced robotics-architect loops, sales-only, or “fully remote 0 YOE” spam. This hub is the campus 110-minute test + domain interview.
- Two tracks: Core (EEE/ECE/Mech/EIE - machines, power, control) vs software (CSE/IT - C++/Python, DBMS, some DSA). Do not mix prep blindly.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch online test, possible GD same day or next | Branch technical bar |
| abb.com/careers | Resume volume; business-unit JD | Same fundamentals interview |
| Referral | Visibility | You still sit the test |
Off-campus does not mean easier machines questions. It often means more applicants who only prepared CAT aptitude.
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported preferred floor on many campus notices. Some drives print 60% throughout 10th, 12th, and degree. Selection still hinges on the technical paper and a 45-75 minute domain interview. A 7.1 who can derive torque-speed of an induction motor (or explain a PLC scan cycle) beats an 8.8 who only memorised MCQ keys.
Branches: EEE, ECE, EIE, Mechanical, Instrumentation for many GET seats. CSE/IT for software-adjacent posts. Confirm the notice.
What helps the resume screen: A lab or internship with a measurement (efficiency, cycle time, defect rate), a project you can draw. See certifications after core subjects, not as a substitute. A random PLC certificate without a project story is thin.
Skills they actually filter
Core: Machines, power, control, electronics
Software track: C/C++/Python, DBMS, light DSA
Automation: PLC/IEC awareness on some JDs
Exam filter: ABB Online Test
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 7.0+ / 70% on many campus lists | Some drives 60% throughout |
| 10th / 12th | 60%+ when “throughout” is printed | Keep marksheets |
| Branch | EEE/ECE/EIE/Mech vs CSE/IT by JD | Software GET ≠ core GET paper |
| Backlogs | None active | Clear before joining |
| Languages | C, C++, Python; IEC on automation | Match the JD |
ABB shortlists on academics when the JD prints a floor, then filters on the technical half of the online test. Clearing CGPA only gets you into the funnel. Interviews are long and senior-led - treat them as the real offer gate.
ABB previous year papers & PDFs
Download 2026 ABB placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What ABB previous year papers actually train
ABB does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers for the 110-minute test and domain interviews - not leaked live papers.
| Round (typical) | What to practice |
|---|---|
| Online test | Verbal, analytical, attention-to-detail, branch MCQs |
| GD (if any) | Structured speech on industry/ethics/sustainability |
| Technical | 2-3 domains deep + project |
| HR | Why ABB, site, safety mindset |
Think of papers as simulators for 110-minute stamina. ABB reuses themes (star-delta, induction motor, control stability, C++/DBMS on software papers) more than exact clones.
Themes that keep repeating (2024-2026)
- Written: ~50 aptitude in 50 min + ~60 technical in 60 min (110/110 total) in widely circulated campus notes. Verbal (RC, correction, para-jumbles), analytical (quant, DI, arrangements), attention to detail, then branch-split technical.
- Interviews: 45-75 minutes with senior engineers. Candidates asked to name 2-3 preferred domains and then go three questions deep. Software tracks add C++/OS/DBMS and light coding.
- GD: Not every campus. When present: industry trends, ethics, sustainability - 5-minute prep.
- 2026 prep expectation: Pick domains now. A CSE student grinding only CAT quant will die on DBMS/C++. An EEE student grinding only LeetCode will die on machines.
How to use one paper set in a single sitting
- Timed: 50 minutes aptitude-style + 60 minutes branch MCQs (or a 110-minute combined mock).
- Untimed review: rewrite the 8 technical items you guessed; derive one formula from first principles.
- Map misses to a domain (machines, power, control, or DBMS) and drill 10 cousins.
- Speak 5 minutes on one project as if a senior asked “show me the circuit / the scan cycle.”
- Log one STAR story (lab failure, internship safety catch).
Related problems to practice
| Theme you saw in a set | What to drill next | Why ABB asks it |
|---|---|---|
| Induction motor / torque-speed | Starting methods, slip | Electrification GET |
| Star-delta / transformers | Phasors, regulation | Same |
| Control systems | Stability, PID intuition | Automation |
| Power electronics | Converters at fresher depth | Drives |
| C++ / DBMS (CSE paper) | Pointers, joins, indexing | Software track |
| Attention to detail | Visual / copy-compare | The 50-min aptitude half |
2025 PDFs often drill circuit breakers. Own why we interrupt current, not memorising a one-line definition.
ABB placement process, round by round
ABB India hires freshers through campus cells and abb.com/careers. After resume screen, the shape is industrial: a long MCQ test, sometimes a GD, then a serious technical with senior engineers.
Application methods
Campus recruitment
PPT, online test, optional GD, technical, HR - often compressed.
Online applications
abb.com/careers for GET / early-career; follow the invite for test vendor and duration.
Referrals
Help visibility. You still need the technical paper and a domain conversation.
1. Resume / eligibility
Degree, branch, CGPA/percentage, 10th/12th if listed, backlogs. Gate only.
2. Online test - ~110 q / 110 min
| Section (typical) | Questions / time | What shows up | Pass habit |
|---|---|---|---|
| Verbal | Part of ~50 / 50 min | RC, correction, para-jumbles | Do not over-parse |
| Analytical | Same block | Quant, DI, arrangements | 45-second skip |
| Attention to detail | Same block | Visual / copy errors | Slow is fine |
| Technical | ~60 / 60 min | Branch paper | This is the cut |
Negative marking: confirm on the invite. If none, do not leave easy technical blank. If yes, do not wild-guess machines.
Software track: C++, DBMS, OS, networking, light DSA MCQs instead of machines.
Deeper OA notes: ABB Online Assessment.
Technical mcq flavour
Core (illustrative, not a leak): transformer equivalent circuit, slip of an induction motor, power factor correction idea, star vs delta line voltage, a diode vs thyristor one-liner, a stability question from control, a Thevenin circuit.
Software (illustrative): output of a pointer snippet, malloc vs new, normalisation, a JOIN, TCP vs UDP, complexity of binary search, a mutex.
You will not memorise 400 items. You will cover your GATE-ish syllabus once, then timed sets. Guessing without elimination is how 60 questions become 40 wrong.
3. Group discussion
5-minute prep, current affairs or ethics/sustainability/industry. Structure: define → 2 points → one risk → close. Do not dominate; do not vanish.
4. Technical interview - 45-75 min
Senior engineers. You pick 2-3 domains. They go deep. Projects and internships are read line by line.
Core example (EEE): “Why star-delta starting?” → current inrush → torque → when you would use a VFD instead. If you listed power electronics, expect a converter follow-up.
Software example: a C++ memory question, a join, then “how would you log a drive fault without losing time order?”
Worked mini-outline - induction motor starting:
- Direct-on-line: high inrush, simple.
- Star-delta: lower start current, torque trade-off.
- Soft starter / VFD: controlled ramp, more electronics.
- Tie to your lab or internship if you have one.
- Stop before you invent a story.
5. HR - ~20-30 min
Why ABB (electrification + automation + robotics, not “I like Switzerland”), Bengaluru vs Nashik vs Vadodara, safety culture, shifts, CTC around ₹7-13 LPA (or the lower core band if that is your JD). Ask one real question about the business unit - drives, robotics, electrification.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | Online test | ~110 min | Aptitude + branch technical |
| 2 | GD | Conditional | Structure, not volume |
| 3 | Technical | 45-75 min | Domain depth + project |
| 4 | HR | 20-30 min | Site, safety, fit |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week |
| Online test | 1 day | 110/110 pattern common |
| GD + interviews | Same day or next | Campus compression |
| Offer / paperwork | Days | Written letter + site |
| End to end | ~2-6 weeks often | Campus can be 48 hours |
Test pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Verbal + DI | Skip rules | Timed mock quiz |
| Attention to detail | Accuracy | One 15-minute set |
| Branch technical | 60 MCQs | 20 items/day in your stream |
| Interview domains | 2-3 topics deep | Oral with a friend |
| Coding (CSE) | Easy-medium | coding questions |
| HR | Site + Why ABB | Two STAR + relocation |
Where to practise for ABB
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 ABB
If a ABB 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 ABB sits around ₹7-13 LPA (candidate-reported - confirm the letter). Languages students mention most often: C++, Python, C, SQL. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): ABB GET eligibility is drive-specific. Common India reports: B.E./B.Tech in EEE, ECE, EIE, Mechanical, or related for core GET; CS/IT for software-adjacent posts; typically 7.0+ CGPA or 70% on many campus notices (some drives cite 60% throughout 10th/12th/degree); no active backlogs. Always verify abb.com/careers or your campus JD.
What you are training for: Typical GET loop: Online Test (often reported as 110 questions in 110 minutes - aptitude/verbal/analytical plus branch-specific technical) → Group Discussion on some campuses → Technical interview (45-75 min, deep on 2-3 domains you pick) → HR. End-to-end often 1-2 campus days or 2-6 weeks off-campus.
Short version of the prep split: Split time roughly: 35% branch technical (machines, power, control, or C++/DBMS if CSE), 25% aptitude/verbal/attention-to-detail, 20% interview depth on 2-3 domains, 10% light coding if the track asks it, 10% HR/GD. Languages: C, C++, Python; IEC 61131 for some automation roles.
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 ABB 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 ABB 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 ABB 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 ABB?” 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 ABB-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 ABB story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 ABB 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 ABB papers on three different days, then interview prep on the leftovers.
What ABB pays freshers (candidate-reported)
Figures are candidate-reported (as of August 2026). ABB does not publish a single GET CTC PDF.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software / digital GET & many engineering freshers | ₹7-13 LPA | Primary band used on this hub |
| Some core plant GET | Often cited lower (~₹5-8 in older public chatter) | Site and BU dependent |
| Experienced / specialist | Higher | Not campus default |
Confirm base, bonus, and joining site on the written offer.
Benefits students actually care about
- Health insurance
- GET training / rotations (ask whether they are real)
- Site allowances if posted to a plant
- Learning on electrification/automation products
How to talk CTC in HR
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.
Week-of-drive checklist
- Sleep, calculator policy (if any), ID
- Formula sheet of your 2-3 domains - then leave it at home if the test forbids
- Error-log only
- Site yes/no decided
- 60-second Why ABB
Offer-stage discipline
- Read location twice (plant vs Bengaluru office)
- Confirm joining vs exams
- Do not resign another offer until ABB’s letter lands
- Background check will match branch and percentages
Keep every email.
Domain mini-orals (10 minutes each)
Core: Draw torque-speed; explain one protection relay idea; PID in one analogy (car cruise control).
Software: Pointer vs reference; inner vs left join; process vs thread.
Automation: What a PLC scan cycle is; why you would not skip an interlock in software.
If you cannot speak them, you are not ready for a 60-minute technical.
110-Minute clock you can reuse
| Minute | Move |
|---|---|
| 0-5 | Skim: how many verbal vs DI vs technical. Confirm if sections are locked. |
| 5-45 | Aptitude block: skip after 45 seconds; attention-to-detail slowly. |
| 45-50 | Flagged easy verbal only. |
| 50-105 | Technical: easy definition items first, then derivation-style. |
| 105-110 | Guess only if the invite says no negative marking. |
If sections are separately timed (50+60), do not steal from technical to finish a puzzle. The 60 technical MCQs are where GET shortlists die.
Core domain pack - what “three questions deep” means
Pick two. Example pair: induction machines + power electronics.
Q1: Draw torque-speed. Mark starting, max, and rated.
Q2: Why not DOL for a large motor? (inrush, supply dip)
Q3: Star-delta vs VFD - when is electronics worth it?
If you listed control as domain three, add: what does a PID do to a step response in words, not a 20-pole derivation.
Interviewers who have run plants can smell a memorised one-liner. Derive or say “I do not remember the exact constant; here is the direction.”
Software track pack
- C++: RAII in one sentence; what invalidates a pointer into a
vector. - SQL: write a join; explain an index trade-off.
- OS: mutex vs a message queue for a fault log.
- DSA: one binary search or hash-map problem spoken, then coded if they ask.
You still need a Why ABB that mentions automation or electrification software, not “I only want FAANG.”
Gd structure (5 minutes prep)
- Define the topic in one line (e.g. “industrial decarbonisation”).
- Two facts or trade-offs (cost vs emissions, safety vs speed).
- One ABB-shaped angle (electrification, motors, robotics in factories) if it fits - do not force the brand.
- Close. Let others speak. Interrupt once at most, and only to add a number or a constraint.
Ethics/sustainability topics are common in prep-site notes. A rant is a fail. A structured 40-second turn is a pass.
Plant vs Bengaluru - decide on paper
Write three columns: must have city, can do 2 years, cannot do. If Nashik is “cannot,” do not tick “any location” on the form. HR will ask. Changing the story after the letter is how GET batches get messy.
Formula sheet - build IT, then leave IT at home
The night before a closed-book test, a one-page sheet is a memory tool, not a smuggle list.
Core page: induction-motor slip and torque-speed sketch; transformer turns ratio; star-delta line/phase; one power-factor triangle; PID in three bullets; one Thevenin step.
Software page: big-O of common structures; JOIN types; process vs thread; mutex vs atomic; HTTP vs HTTPS.
Write it by hand once. Recite it. Do not bring it into a lab that forbids notes. Interviewers may ask you to reproduce one sketch on a whiteboard - that is the point.
ABB vs Siemens vs Bosch vs L&T
Siemens and ABB overlap on electrification/automation; Siemens often feels more multi-division (energy, mobility, software). Bosch is automotive-heavy plus industrial. L&T is broader infra + services. All four can run long technicals. Prep your branch fundamentals for all; customise Why-company to motors/drives/robotics for ABB, not a generic “core company” paragraph.
Robotics vs electrification vs process automation
Freshers do not pick a BU like a menu, but HR may name one.
- Electrification: switchgear, protection, power quality, motors.
- Robotics: cells, safety interlocks, cycle time - more Mech/ECE + software.
- Process automation: PLC/DCS, scans, alarms, IEC languages.
If the PPT named a BU, learn five nouns from that slide. Do not pretend you have commissioned a robot cell if you have not.
Attention-to-detail section - why IT exists
ABB products fail expensive when a digit is wrong. The aptitude block’s “spot the difference / copy the figure” items feel childish until you miss three. Practice slowly. Speed here is a trap. Ten correct attention items beat one extra DI puzzle.
Interview stamina (45-75 minutes)
Bring water. If they ask a third domain you did not name, it is fair to say “that was not my elective; here is how I would start.” Inventing a protection-relay lecture you cannot finish is worse. Seniors prefer a clean boundary.
Halfway through, they may switch to the internship. Have one metric (efficiency, downtime, defect count) and one thing you would redo.
Six-week core revision if gate notes are dusty
| Week | Chapter focus | Output |
|---|---|---|
| 1 | Transformers + 1Φ/3Φ basics | 40 MCQs; one equivalent-circuit sketch |
| 2 | Induction + sync machines | Torque-speed drawn twice from memory |
| 3 | Power systems (faults, protection lite) | 30 MCQs; one relay one-liner |
| 4 | Control (stability, PID) + measurements | Oral with a friend |
| 5 | Power electronics / analog (your electives) | 30 MCQs |
| 6 | Full 110-min mocks + 2-domain orals | 2 mocks; error log closed |
ECE students swap machines-heavy weeks for signals/microcontrollers only if the JD is electronics/embedded, not if the PPT said electrification GET. Read the slide.
Sample technical follow-ups
Answer out loud. Stop if you are guessing constants.
- Why does starting current of an induction motor hurt the feeder?
- Star-delta: what happens to torque?
- One reason a VFD might be preferred over star-delta.
- What is slip? What if slip is zero?
- Power factor: one way to improve it at a plant.
- Difference between a fuse and a circuit breaker in one sentence.
- PID: which term fights steady-state error?
- Your project: what would you measure on day two?
Sample technical follow-ups
- Who owns the pointer after
push_backon avectorthat reallocates? - Clustered vs non-clustered index - one use each.
- Why log a timestamp with every drive fault.
- Mutex around a shared last-error string - what deadlocks look like.
- HTTP 500 vs 503 for a down PLC gateway (fresher depth).
Safety one-minute
You do not need an OSHA certificate. You do need: do not defeat an interlock, lock-out if the JD is plant, report a near-miss. If your lab had a stupid shortcut, say you would not repeat it. That 40-second story is more useful than “safety is our top priority.”
What a get year can look like
Rotations through design, testing, and a factory floor happen on some programmes and not others. Ask HR: “Is this GET rotational, and which site is home base?” A Bengaluru software GET and a Nashik manufacturing GET are different jobs that share a logo. Your prep should match the one on the mailer.
Gd topics worth 20 minutes of thought
- Industrial electrification vs coal in Indian factories
- Robotics and jobs - one trade-off, not a TED talk
- Safety vs productivity on a shop floor
- Sustainability reporting - what a fresher can actually influence (almost nothing; be honest)
- “Should engineers learn to code?” for a core panel - yes, for logs and tests, not for abandoning machines
Write four bullets per topic. Speak one minute. Sit down. That is GD. Debating your classmate into silence is how you fail a conditional round that was supposed to be easy.
What selected vs almost-selected looks like in technical
Selected pattern: named two domains, derived one sketch, admitted a gap, tied a project metric, asked a BU question.
Almost-selected: knew MCQ keys, went blank when asked “why,” listed five domains, argued about a constant, had no site answer.
The difference is not a secret book. It is oral practice. Find one person who will ask “why” five times.
Attention-to-detail drill (15 minutes)
Print two almost-identical wiring tables or number grids (or use a phone note). Circle every mismatch. Time yourself. The ABB aptitude block is not trying to be clever; it is trying to see if you rush. Rushing is how GET papers leak marks before the technical section even starts.
What to carry on campus get day
- ID + college ID
- Resume copies
- Marksheets if the cell asked for a file check
- Water
- A calm 60-second Why ABB
- The names of your two domains written on a small card you will not take into a closed-book test but will glance at before the interview cabin
Leave the 400-page handbook in the bag. Seniors ask you to talk, not to quote a chapter number.
Off-campus get vs campus super-day
Campus: test and interviews may be 24-48 hours. Off-campus: weeks, and the JD may be BU-specific (robotics vs electrification). Read the business unit. Prepping a generic “core company” speech for a robotics cell is a miss; prepping only Python for a switchgear GET is a miss. The 110-minute pattern still shows up often - confirm the vendor mail.
Negative marking - ask once
Prep blogs disagree. Your invite wins. If there is no penalty, finish every technical item you can eliminate to two options. If there is a penalty, blank is better than a 1-in-4 machines guess. Write the rule on the first page of your rough sheet so you do not change policy at question 80.
Robotics software vs plant get - two prep bags
If the JD says software/digital: C++, DBMS, light DSA, plus a Why-automation sentence. If the JD says GET electrical: machines, power, control, plus a Why-electrification sentence. Carrying both bags at 30% depth is how people fail both papers. Choose.
If a recruiter later names a different BU than the PPT, ask whether the test you sat still matches. A robotics software seat is not a consolation prize for missing switchgear GET, and the reverse is also true. Confirm site and title in the letter.
Keep a one-page error log from mocks: machines misses on the left, aptitude skips on the right. The night before, read only that page. Opening a new control-systems chapter at 1 a.m. is how people forget star-delta in the morning. Sleep beats one more MCQ set. Pack ID, resume copies, and a decided site answer (Bengaluru / Nashik / Vadodara) before you leave the hostel. If the cabin asks for a third domain you did not name, say so and start from first principles instead of inventing a lecture.
ABB hiring updates for 2026
- 110/110 written remains the pattern most prep sites and campus notes still describe - confirm your mailer.
- GD is optional by campus.
- Software GET seats exist; they are not a free pass to skip all electrical context if you join a drives team.
- Sites (Bengaluru, Nashik, Vadodara) show up in HR more than students expect.
- Treat ₹7-13 LPA as a reported band with core-plant variance, not a guarantee.
- Sustainability and safety language in GD/HR is more common than in 2018-era notes.
FAQs students ask about ABB placements
Process & papers
What is the ABB placement process?
Typical GET path: online test (often 110 Q / 110 min) → GD on some campuses → technical interview (45-75 min) → HR. Campus can finish in one or two days. Off-campus often 2-6 weeks.
How many rounds are there in ABB interview?
Usually 3 (test, technical, HR) plus a conditional GD. The technical is the offer-decider. Count the mailer.
Can I download ABB placement papers PDF?
Yes. Free ABB placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the paper archive.
What is the ABB online test pattern?
Widely reported: 110 questions in 110 minutes - about 50 aptitude (verbal, analytical, attention to detail) and 60 branch technical. Confirm negative marking and exact split on your invite.
Eligibility & offer
What is ABB eligibility criteria for freshers 2026?
Commonly reported: 7.0+ CGPA or 70%; some drives 60% throughout; B.E./B.Tech in listed branches; no active backlogs. Your notice overrides this page.
What is ABB salary for freshers in India?
Candidate-reported CTC often lands around ₹7-13 LPA for many software/digital GET and early-career engineering roles as of August 2026. Some core plant GET offers land lower. The written letter is the only number that matters.
Bengaluru, Nashik, or Vadodara?
Those are the India sites this hub emphasises. HR checks relocation. Be honest early.
Prep & ABB-specific
How to prepare for ABB placement?
Split time roughly 35% branch technical, 25% aptitude, 20% interview domains, 10% coding if CSE, 10% HR/GD. Details: preparation guide.
What programming languages are allowed in ABB?
C, C++, Python on software tracks; IEC 61131 discussion on some automation roles. Confirm the JD and test platform.
Is ABB only for EEE and ECE?
Core GET is EEE/ECE/EIE/Mech-heavy. CSE/IT appear on software and digital posts. Read the JD. Do not prep the other track’s paper.
Any pro tip for ABB placement preparation?
Pick 2-3 domains you can defend three questions deep. Bank the 110-minute test with skip rules. Rehearse Why ABB and your site answer.
Where can I read real interview experiences?
Start with ABB interview experience on this site, then recent campus blogs. Use them as maps, not formula sheets.
Is ABB test harder than a services aptitude test?
The aptitude half is familiar. The 60 technical MCQs and the long domain interview are the difference. Treat it as GATE-lite plus HR, not NQT with a logo swap.
Will they ask me to pick domains?
Often yes. Name 2-3 you actually studied. “All of electrical engineering” is how people get destroyed on the third follow-up.
Do I need PLC experience?
Helpful for automation JDs, not a universal GET requirement. An honest lab course beats a fake ladder-logic story.
ABB vs Siemens vs Bosch for core freshers?
All three run long technicals on branch fundamentals. Siemens is multi-division (energy, mobility, software). Bosch is automotive-heavy plus industrial. ABB’s story is electrification, automation, and robotics, with India sites that include plants as well as Bengaluru engineering. Prep machines/control or C++/DBMS to match your JD; customise Why-company for each logo.
ABB - recent candidate experiences
What to steal this week
Steal: 110/110 timing; 2-3 domains deep; honest site preference; technical as the offer round.
Ignore: memorising a FACE Prep MCQ key as if 2026 will clone it; quoting software CTC on a plant GET JD; skipping machines because “I’ll do GD well.”
If you only do three things: sit one 110-minute mock, pick two domains and speak them, and decide Nashik/Vadodara yes or no.
Campus get pattern (prep-site synthesis used as a 2026 map)
Three-stage core process with optional GD. Online test branch-splits technical content. Interviews last 45-75 minutes with senior engineers; candidates choose preferred domains. Takeaway: the written technical section and the long interview are the filters; aptitude alone does not save you.
Software vs core
CSE students on digital/software GET posts still face C++/DBMS and a professionalism bar. EEE students on plant GET still face machines. Mixing those prep lists is the most common unforced error.
What selected vs rejected patterns look like
Helped: accurate technical MCQs; derived answers in interview; a project sketch; honest site.
Hurt: guessed papers; shallow domain lists; refusing the plant after “any location”; treating safety as HR theatre.
Software vs core mix-up: CSE students on digital GET still face C++/DBMS. EEE students on plant GET still face machines. Mixing those prep lists is the most common unforced error.
Plant vs Bengaluru: write three columns - must have city, can do two years, cannot do. If Nashik is “cannot,” do not tick “any location.” HR will ask.
Oral practice: selected people named two domains, derived one sketch, admitted a gap, tied a project metric. Almost-selected people knew MCQ keys and went blank on “why.” Find one person who will ask “why” five times.
More narratives: ABB interview experience.