Academic snapshot
Marks: 60% or 6.0 CGPA throughout 10th, 12th, UG (and PG if taken)
Degree: B.E./B.Tech/MCA in CS/IT/ECE/EEE and listed circuital cousins
Backlogs: No active / live backlogs at registration
Gap: Typically max ~1 year
Hexaware is a global IT services and digital transformation company with an automation-first story across BFSI, healthcare, and travel. India hiring for freshers splits into GET and PGET. The written is a volume aptitude+domain filter; the communication assessment is a real cut; PGET adds coding for the higher CTC band.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Hexaware is a volume campus hirer with two named fresher tracks. The academic floor is usually the same; the coding round is what separates PGET.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus / pool | PPT, college % list, headcount can change late (GFG 2024) | Aptitude + communication bar |
| Careers / Superset | Form + platform invite | Same written + SpeechX flavour |
| Referral | Visibility | You still sit every elimination round |
Off-campus does not mean easier quant. It often means more applicants who skip speaking practice and die on Mettl.
Is 6.0 CGPA enough? It matches many mass-hiring guides (or 60%). The phrase that matters is throughout 10th, 12th, and graduation. A 7.8 B.Tech with 58% in 12th is how people get dropped after OA. A 6.2 who finishes aptitude, speaks clearly, and (for PGET) submits two programs beats an 8.5 who mumbles on SpeechX.
10th / 12th: They count. Keep marksheets. “Throughout” is not a slogan.
What helps the resume screen: Readable English, one project, any internship. Automation buzzwords without a sentence you can say aloud do not help. See certifications after aptitude and speaking, not instead of them.
Academic snapshot
Marks: 60% or 6.0 CGPA throughout 10th, 12th, UG (and PG if taken)
Degree: B.E./B.Tech/MCA in CS/IT/ECE/EEE and listed circuital cousins
Backlogs: No active / live backlogs at registration
Gap: Typically max ~1 year
Skills they actually filter
Written: Aptitude + domain/pseudocode
PGET extra: 2 easy-medium coding problems
Communication: Read, listen, grammar, short speak
Languages: Java, Python, C++
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 60% or 6.0 | Mailer wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | CSE/IT/ECE/EEE/ETC/EIE/ICE style lists | Confirm drive |
| Backlogs | None live | Clear before joining |
| Shifts / relocate | Often mandatory language | HR will ask |
Good fit: You can finish a 60-minute aptitude paper without freezing, you will speak English into a mic, and you will relocate to Chennai or Pune. If you want PGET, you already finish two array/string problems without an IDE panic.
Harder path: You only practiced coding and skipped quant; you freeze on read-aloud; you refuse shifts; you want to “see the bond later.” Hexaware HR is a logistics round.
Branch myth: Circuital branches are welcome on listed drives. The communication round does not care that you are ECE. The coding round (PGET) does not care either; it cares that you submit.
Gaps: Over ~1 year is the usual hard stop in eligibility tables. Live backlogs at exam time are a no.
Download 2026 Hexaware placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Hexaware does not publish a permanent official paper set. Papers on this site are pattern trainers for aptitude+domain, PGET coding, and interview themes.
| Round (typical) | What to practice |
|---|---|
| Aptitude | Verbal 20 + logical 20 + numerical 20 under time |
| Domain / tech | ~30 MCQs: pseudocode, CS fundamentals, MS Office/email on some GET notes |
| Coding (PGET) | 2 easy-medium arrays/strings/loops |
| Communication | Not a PDF; you still must practise speaking |
| Technical / HR | OOP, DBMS, projects; location, bond, CTC |
Think of papers as simulators for 60-minute aptitude stamina. Hexaware reuses themes (time-work, syllogism, pseudocode output) more than exact clones.
| Theme you saw | Drill next | Why Hexaware asks it |
|---|---|---|
| Time-work / percentages | Speed arithmetic | Volume aptitude |
| Verbal | Grammar + vocab under clock | Same paper |
| Pseudocode | Trace loops on paper | Domain section |
| CS fundamentals | OOP, DBMS one-liners | Domain + tech interview |
| Two coding | Complete submit | PGET ₹6 LPA gate |
Hexaware hires freshers through campus cells, careers/Superset, and referrals. After eligibility, the shape is classic Indian IT services with two twists: a named PGET coding extra and a communication round that actually fails people.
Campus recruitment
Primary path. PPT (listen for GET/PGET and bond), written, communication, interviews. Strong Chennai/Pune presence.
Online applications
hexaware.com careers or Superset/CoCubes invites. Follow the assessment mail for platform.
Referrals
Help the screen. You still need aptitude accuracy and a SpeechX pass.
60% throughout, branch list, no live backlogs. Gate.
| Section | Questions (cited) | Notes |
|---|---|---|
| Verbal | 20 | Part of ~60 min aptitude block in GFG-style 60Q/60min |
| Logical | 20 | Skip monsters |
| Numerical | 20 | Time-pressured |
| Domain / tech | ~30 / ~30 min | Pseudocode + computer fundamentals |
PrepInsta 2025 also describes ~75Q/75min including domain. placementpreparation.io composite ~90Q/90min. Your invite wins.
Pass habit: 45-second skip rule on quant. Trace pseudocode on scrap paper. No negative marking is claimed on some pages; still do not random-fill if your mailer says otherwise.
2 problems, easy-medium, arrays/strings/loops, Java/Python/C++. Complete passing solutions beat a clever half-write. Fail here and some drives still offer GET.
Clock: 3 minutes read + name the pattern, 15-20 minutes code each, 5 minutes tests. Do not start a third algorithm.
Read/listen/repeat, grammar, short speak. GFG 2024: large drop here before technical. AI scoring cares about fluency and completeness, not a TED accent.
Pass habit: Speak in full sentences. If you freeze, restart the sentence. Practise in a noisy hostel once.
Resume language, OOP, DBMS, DSA basics, project. Clearing tech is often described as near-final before HR. Short, specific answers. “We used React” is not a project story; “I wrote the login API and fixed a null on empty email” is.
Personality, relocation, shifts, Why Hexaware, failure handling, service agreement. Some drives mention GET→PGET upgrade later via coding + EC. Know ₹4 vs ₹6 LPA.
| Phase | Duration | Notes |
|---|---|---|
| PPT / register | Days | Read bond slide |
| Written + comms + coding | 1-7 days (split or same week) | Platforms: Superset, CoCubes, Mettl |
| Technical + HR | Days to 2 weeks | Sometimes same day |
| Offer / college list | Days | Headcount can still move (2024 GFG) |
| End to end | ~2-6 weeks often | Services calendars slip |
If you will not practise two coding problems, register mentally as GET and still take PGET if the college puts everyone in one funnel (failing coding may map to GET). If you already finish easy LeetCode, aim PGET and treat communication as the round that can still steal ₹2 LPA from you.
| Day | 15-minute drill |
|---|---|
| 1 | Record intro. Cut fillers. Re-record. |
| 2 | Read a paragraph aloud; listen back |
| 3 | 20 grammar MCQs |
| 4 | Project in 40 seconds |
| 5 | “Why Hexaware / automation” in 30 seconds |
| 6 | Full mock: intro + project + why |
| 7 | Best take once. Sleep. |
This will not make you a debater. It will stop a blank SpeechX submit.
Log every mock: which of the five ate the clock. That log is the prep plan.
Saturday 10:00: 60-minute aptitude.
Saturday 11:15: 30-minute domain/pseudocode.
Saturday 12:00: two coding (if PGET).
Saturday 16:00: 20-minute speaking + grammar.
Sunday 11:00: 20-minute technical oral (OOP + SQL + project).
Sunday 12:00: HR including bond and city.
Two weekends of that beat twelve nights of random YouTube.
Domain/tech MCQs often look like a 12-line loop with a counter and a break. Trace on scrap paper with a table: line, variables, output. Do not “see the pattern” from a Telegram screenshot.
Habit: one dry-run per day for 10 days. That is the entire domain prep if your fundamentals (OOP, DBMS one-liners, binary vs linear search) are already OK. GET notes that mention email/MS Office/fundamentals are still one-liners: what is a primary key, what does CC mean, what is a deadlock. Not a 3-hour PowerPoint course.
Public 2026 tables often print 3 years / about ₹2 lakh. Your drive may differ.
Write three lines before HR:
Asking is professional. Discovering the clause after you said yes in a classroom is how people panic-sign and then ghost, which burns the college’s next Hexaware cycle.
If you already hold a 5 LPA offer with no bond, compare site, bond, and joining date before CTC ego. ₹6 LPA PGET with a clause you cannot live with is not a win.
LinkedIn GET notes mention later upgrade via coding + EC. Treat it as one report.
In HR you may ask: “Does this batch have a documented GET to PGET upgrade? What is the window and the bar?” If they say yes, smile and still prepare to join as GET. If they say no, do not argue with a screenshot of someone else’s year.
10th, 12th, all semesters, ID, photo if asked, resume one page. Throughout 60% means the 12th PDF matters. A missing marksheet is a silly way to stall after SpeechX.
Name, percentages, and dates must match Superset/Naukri/college form. Hexaware background checks are not a rumour.
A Hexaware campus can take a large batch. That is not a participation trophy. Aptitude still deletes a chunk. Communication still deletes a chunk. Technical still deletes people who cannot explain their project. Your job is to be easy to say yes to: complete written, clear speech, two coding submits if PGET, documents ready, bond answer ready.
College final lists can shrink after interviews (GFG 2024). Do not resign another offer until the PDF lands and the cell publishes a stable list.
GET/PGET tables sometimes split stipend months then full CTC. Ask HR when ₹4 LPA / ₹6 LPA starts. Do not spend the stipend month as if the annual number is already in your account. Confirm PF and tax on the letter like an adult.
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 Hexaware 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 Hexaware sits around ₹4 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): Campus and prep-site reports commonly cite 60% or 6.0 CGPA throughout 10th, 12th, and graduation, B.E./B.Tech/MCA in CS/IT/circuital branches, no active backlogs, and max about 1 year academic gap. Some PrepInsta notes say M.E./M.Tech are not eligible. GET and PGET share this academic floor; PGET adds a coding round. Verify your college mailer.
What you are training for: GET: aptitude + domain written → communication assessment (SpeechX/Mettl style) → technical/EC interview → HR. PGET adds a coding round (2 problems, easy-medium) on Superset/CoCubes in many reports. All rounds are elimination. Timeline often 2-6 weeks. Failing PGET coding can still yield a GET offer on some drives.
Short version of the prep split: Prioritise aptitude accuracy (60 questions in 60 minutes is a common pressure report), domain/pseudocode MCQs, then spoken English for the communication round. If you want PGET, add two easy-medium coding problems. HR: location, shifts, bond. Full plan: /hexaware/preparation-guide/.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Hexaware 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 Hexaware 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 Hexaware 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 Hexaware?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. 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 Hexaware-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 Hexaware story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Hexaware papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Hexaware papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Hexaware-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Figures are candidate-reported / public explainer bands as of August 2026.
| Track | Typical CTC | Training note | Agreement (often cited) |
|---|---|---|---|
| GET | ₹4 LPA | Stipend ~₹15-25k/month for 3-6 months in some tables | ~3 years / ₹2 lakh |
| PGET | ₹6 LPA | Stipend ~₹25k/month for ~3 months in some tables | Same style |
| Hub range on this site | ₹4-6 LPA | Matches GET-PGET | Drive-specific |
Confirm base vs variable, stipend months, and bond on the written offer. Do not negotiate like a product company.
Health insurance, learning/certifications on the job, shift norms (ask), relocation to Chennai/Pune/Mumbai/Bengaluru/Noida. Automation-led delivery is the PPT story; day-one work is still project staffing.
Know ₹4 LPA GET vs ₹6 LPA PGET. Ask whether failing coding maps to GET. Ask stipend vs full CTC date. Ask the service agreement amount in the letter.
GET / PGET split is the story
Coding remains the PGET extra. GET is still a real offer, not a consolation meme, if you want the 4 LPA track.
Communication still cuts
GFG 2024-style Mettl drops are the warning. Speak every week, not the night before.
Aptitude is time-limited
60Q/60min or 75Q/75min reports. Accuracy under clock, not CAT books.
Bond language persists
3-year / ~₹2 lakh appears in 2026 explainers. Verify each drive.
Net for 2026: do not wait for Hexaware to become a coding-only company. Double down on timed aptitude, SpeechX, and two programs if you want PGET.
Yes. Free Hexaware placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
GET: written (aptitude+domain) → communication → technical → HR. PGET adds coding. All elimination. Often 2-6 weeks. Platforms: Superset/CoCubes + Mettl/SpeechX in student reports.
4 for GET, 5 for PGET after resume, plus optional GD. Communication counts.
GET ~₹4 LPA without a mandatory coding round on many playbooks. PGET ~₹6 LPA with 2 coding problems. Same academics and communication. Failing PGET coding can still become GET on some drives.
AI-scored English: read, listen, grammar, short speak (~20-30 min). GFG 2024: many rejected here. Practise out loud. Details sit on online assessment.
Java, Python, or C++ for PGET coding. Interview follows your resume language plus OOP/DBMS.
Commonly 60% or 6.0 throughout 10th, 12th, graduation; B.E./B.Tech/MCA in listed branches; no live backlogs; gap ≤ ~1 year. Some pages exclude M.E./M.Tech. Your mailer wins.
GET ~₹4 LPA, PGET ~₹6 LPA (candidate-reported / public tables, August 2026), plus training stipend months on some posts. Confirm the letter.
Often cited: 3 years / about ₹2 lakh. Drive-specific. Decide before HR. Ask for the clause in writing.
Chennai, Pune, Mumbai/Navi Mumbai, Bengaluru, Noida. Relocate and shifts are common mailer language.
Timed aptitude, domain/pseudocode, speaking drills, plus two coding problems for PGET. Guide: preparation guide.
Treat communication as a ranked round. Time 60 aptitude questions. If you want ₹6 LPA, finish two coding submits. Know the bond number before the cabin.
All volume services with aptitude gates. Hexaware’s twist is GET/PGET pricing plus a harsh communication cut. Coforge sometimes runs communication first too. Prep aptitude+speaking for both; add Hexaware’s two-track CTC story for HR.
Some LinkedIn GET notes mention later upgrade via coding + EC. Treat as one report, not a promise. Ask HR if it exists on your batch.
Some 2025 PrepInsta tables say no. Some colleges include them. Read your notification.
Some playbooks still offer GET (~₹4 LPA) if other rounds cleared. Ask HR. Do not assume. Still finish two programs if you want ₹6 LPA.
Similar volume aptitude. Hexaware adds a communication elimination and a PGET coding extra. NQT does not split GET/PGET the same way. Practise speaking either way.
Tough, time-limited aptitude (many cut). Mettl communication (another large reject wave). Technical and EC, then HR. Candidate cleared interviews; final college shortlist still cut. Takeaway: communication is not a formality; campus headcount can move after you think you are done. Source: GeeksforGeeks PGET 2024.
Written including domain pseudocode/fundamentals; coding for the eligible track; tech on resume languages/projects; HR on location and salary expectations. Takeaway: pattern is not frozen at “only aptitude.”
GET path OA → tech → HR. Mentions possible later upgrade to PGET via coding + EC, with PGET CTC cited as ₹6 LPA in that post. Takeaway: treat upgrade as a rumour until HR writes it; still prepare as if GET is the offer you must accept or decline.
What to steal: 60-minute aptitude clock; weekly speaking; two coding submits for PGET; bond decided before HR; 10th/12th scans ready.
What to ignore: Paying for “Hexaware dumps”; assuming communication is optional; quoting 6 LPA while sitting a GET-only drive.
SpeechX composite: Candidates who practised only grammar MCQs still failed read-aloud because they whispered and restarted every line. Candidates who recorded a paragraph daily for a week sounded “average” and passed. Average is the bar. Silence is not.
Aptitude composite: A 2024-style 60Q/60min paper feels easy in the first 15 minutes and brutal in the last 15 if you chased one seating puzzle. Takeaway: skip rules are the syllabus.
Headcount composite: Clearing HR and still missing the college list is a real Hexaware story. Keep a backup services process running until the offer PDF and the cell Excel agree.
Hexaware is volume services with a priced coding extra. GET is a real 4 LPA job. PGET is a 6 LPA job with two programs. Communication is a ranked round. Bond language is common. Students who treat SpeechX as optional and aptitude as “I’ll manage” are the ones the GFG 2024 write-up is about.
Use timed papers on this site. Follow the preparation guide for a week calendar. Read interview experience for PGET 2024 notes and the HR page for location and agreement questions. Record your intro twice. Finish two coding problems if you want PGET. Print 10th and 12th. Decide the bond on paper. Then sit the drive like an adult, not like a dump-PDF scavenger.
If Hexaware and Coforge/Virtusa/Mphasis all land the same week, compare bond, city, and whether communication already passed. A 6 LPA PGET you will actually join beats a rumour 7 LPA with a clause you cannot live with. Keep the same email thread from PPT to offer. Classroom “selected” is not a letter. Wait for the PDF. Then resign other holds if you mean it. Name, percentages, and dates must match every form. Background check is not a rumour. Shifts are not a rumour. Chennai and Pune are not optional flavour text on the PPT. If you will not go, say so in HR and take the other offer. That is cleaner than a day-one no-show.
Automation-first is the company story. Day-one work is still a project and a stack you are assigned. “I will only do GenAI” is a bad HR answer. “I will learn the stack on the project and I already write Java/Python” is the GET/PGET answer. Keep that sentence ready.
Interview day logistics: Laptop charged if the OA is remote; college ID if on campus; quiet room for SpeechX (fans and roommates wreck listen-repeat). Do not sit Mettl on hostel Wi-Fi that drops every three minutes. Have a hotspot. If the platform flags you for looking away, you will not get a debate. Practise looking at the camera while you speak.
EC interview: some PGET notes mention an extra evaluation/communication round after technical. Treat it as “explain your code and your project in English.” Same short-answer habit. If you mumbled on SpeechX and somehow passed, this round will catch you.
Salary expectations in HR: say you understand GET ~₹4 LPA and PGET ~₹6 LPA from public reports and you will read the letter. Do not demand 8 LPA on a GET drive. Do not pretend you never heard of a service agreement if the PPT showed one.
Pool campus: more colleges, denser aptitude. Same SpeechX. Same two coding problems for PGET. Your college rank in the pool does not replace a complete submit.
Keep practising until skip rules and a 60-second intro are automatic. That is Hexaware. Everything else is decoration.
Week plans stay on the preparation guide. OA section tables stay on online assessment. This hub is the map: GET vs PGET, SpeechX, 60% throughout, ₹4 vs ₹6, bond, Chennai/Pune.
Print 10th and 12th tonight. The drive will not wait for a missing pen-drive PDF at 8 a.m. Name and percentages must match Superset. That is eligibility in the only way that still matters after you can speak and code.
If you miss Hexaware, the same aptitude muscle and speaking drills transfer to Virtusa, Coforge, and Mphasis. Reuse them. Do not start a new dump site. Two PGET problems, complete submits, then HR. That is the loop. If the college publishes a revised shortlist after you already told another firm you were “selected,” wait for Hexaware’s PDF before you resign. Headcount movement is documented in the 2024 GFG PGET note for a reason. Keep a backup process live until both the letter and the cell list agree. A classroom “selected” announcement is still not an offer PDF.
More narratives: Hexaware interview experience.
Mphasis · Virtusa · Coforge · Persistent Systems · CGI