Hexaware SPGET / GET campus loops emphasize aptitude+coding, AI communication screens, manageable technicals, and deep managerial filters. This page synthesizes those patterns into round tables, outcome notes, and prep traps.
DELETE removes rows (can rollback depending on engine/transaction); TRUNCATE deallocates/reseeds behaviour differs - state your DB’s semantics carefully
Polymorphism: compile-time vs runtime with a tiny C++/Java sketch
Tip: Prefer precise DB wording over buzzwords
Internship storytelling
What you built, APIs touched, Docker/Node if claimed
Metrics and failures - managerial rounds probe soft claims
Result: Clears when examples are specific
Tip: Never list a tool you cannot define in one sentence
Key takeaways: Resume inflation dies in Hexaware managerial rounds. List less; defend more.
Takeaways
What decided it: Specific internship examples (APIs, Docker/Node if claimed) with metrics and failures
Common fail: Listing tools you cannot define in one sentence under managerial follow-ups
How to practise: Prune resume; one-sentence definitions for every tool; rehearse failure metrics
GET on-campus 2024 - communication cut deep
GET 2024 GEC experience
Candidate profile: GET-2024 hiring; online Superset process
Rounds 1–2
Aptitude + domain (pseudocode and computer fundamentals)
Communication test (~60 min) on Mettl: read-aloud, listen-and-speak, one-minute extempore (weather, sports, smart vs hard work), grammar MCQs
Result: Most eliminated here - only 4 of many reached technical in one account
Tip: Audio clips often play once; use headphones and a quiet room
Technical + HR
Technical ~18–20 min; HR ~10–15 min after clearance
HR: projects, Hexaware knowledge, service agreement and relocation, family background
Tip: If you clear technical, HR is often logistics - still prepare bond/relocation answers
Key takeaways: Communication eliminates more candidates than coding on many GET drives.
PGET on-campus 2025 - Superset + Cocubes coding
PGET 2025 five-round funnel
Candidate profile: PGET path; aptitude cleared from ~242 candidates in one funnel snapshot
GET base rounds
Online aptitude + domain; group discussion on some calendars; HR discussion (~10–20 min, friendly basics)
Tip: GD themes vary - practice structured speaking, not dominance
PGET coding (Superset + Cocubes)
Language choice: C/C++/Java/Python; two easy–medium problems (~40 min)
Example funnel: 43 sat coding → 24 selected for EC
Tip: Pick one language and rewrite old solutions until syntax is automatic
EC interview
~25 min general + technical mix on Superset
Example funnel: 13 interviewed → 7 PGET offers
Tip: EC cross-questions coding approaches and project decisions together
Key takeaways: PGET adds measurable coding + EC depth on top of GET elimination rounds.
HR interview experience
HR interview experience
Candidate profile: Final-round SPGET candidate
Short HR chat
Interests outside academics
Why Hexaware
Location / bond awareness when discussed in PPT
Final result: Offer on successful tracks
Key takeaways: Keep energy up even in a 5-minute chat - it is still scored.
Sample answers for high-frequency questions
Use these as frames, not scripts.
Technical
Q. 3rd largest element without sorting? A. Track first, second, third while scanning once - O(n) time, O(1) space. Handle duplicates explicitly if the prompt requires distinct values.
Q. DELETE vs TRUNCATE? A. DELETE: row-wise, can use WHERE, transactional in InnoDB. TRUNCATE: deallocates table storage quickly, resets identity in many engines, usually cannot WHERE. Confirm engine-specific behaviour if unsure.
Q. Polymorphism in C++? A. Compile-time: overloading / templates. Runtime: virtual functions and base pointers calling derived overrides. Sketch a tiny Animal::speak example.
HR
Q. Why Hexaware? A. PPT-specific delivery/automation theme + learning path for SPGET/GET + location fit. Avoid generic “IT company” only.
These links are research inputs used to map Hexaware SPGET and GET communication filters - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Confirm SPGET vs GET and service-agreement terms against the drive mail.
