Hexaware Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about Hexaware: this is a volume hire, and the online test is the real filter.

• Most candidates are rejected at the test, not in the interview.
• The funnel: a drive pulls thousands, cuts to a few hundred who pass the test, then interviews most of those and offers a large share.
• So the test eliminates maybe 85 to 90 percent of the field, and the interviews are far gentler.
• Treat the aptitude and pseudo-code sections as the hard gate, and the interviews as a "do not give them a reason to say no" conversation.

2Getting the call (the part most guides skip)#

There are three realistic ways in.

On-campus (the easiest path). Hexaware visits engineering colleges directly and runs the test on campus or a shared platform.

• If your college has a tie-up, your placement cell registers you. You do not apply yourself.
• Keep CGPA, backlog status, and branch eligibility clean. Most services firms set a minimum (often around 60% or 6.0-6.5 CGPA, no active backlogs).
• Watch your placement portal and the training-and-placement board daily in placement season. The call lands there with 24 to 48 hours of notice.
• Miss the registration window and you simply do not get a test link. There is no appeal.

Off-campus / drives. Hexaware runs off-campus drives and posts openings on its careers site and job platforms.

• Apply the moment a drive opens. Slots fill fast, and some drives cap registrations and close within a day or two.
• You register with college details, branch, graduation year, and a resume, then get a test link by email.
• Check spam. The automated test invite often lands there, usually with a fixed window (for example, "complete within 72 hours").
• Miss the window and you wait for the next drive.

Referrals. A referral will not skip the test, but it gets your resume looked at faster and keeps you in the loop before drives go public.

• Message seniors from your college on LinkedIn who joined Hexaware.
• A polite, specific note beats a mass request: name the drive or track, mention one concrete thing you built, and ask for an internal-portal referral.
• "Hi, I saw you joined Hexaware from [college]. I am applying to the Java fresher track and have built a Spring Boot inventory API. Could you refer me?" beats "please refer me sir" every time.

Resume rules. Recruiters skim for seconds, and an ATS reads it first.

• One page, plain single-column formatting, no photos, no graphics, no two-column templates that scramble parsing.
• Save and send as PDF unless the portal demands a .docx.
• Lead with skills and projects, not a generic objective line.

Quantify your project bullets. Instead of "built a web app," write:

Built a student attendance web app (Java, MySQL) used by 3 classes of ~120 students, cutting manual roll-call time from ~10 minutes to under 1 minute per class.

That bullet does three things in one line: a tech stack the recruiter can match to the track, a real user count, and a before/after number.

• Do the same for every project, even course projects.
• There is almost always a number hiding in there: rows of data, users, percent accuracy, time saved.

ATS keywords to include naturally: your core language (Java / Python / C++), SQL, Data Structures, OOP, DBMS, OS, Git, plus the specific track you want (testing.NET, cloud, data engineering).

• Mirror the exact words in the job post. If it says "Selenium," write "Selenium," not "automation testing tool."
• The first pass is a keyword match, not a human reading for intent.

3The loop at a glance#

A few things shift between drives, the measured bar does not.

• Some drives fold technical and HR into one sitting of 30 to 45 minutes.
• Some add a short communication or versant-style English check: read sentences aloud, answer spoken prompts into a mic.
• The order can move around, but the three things being measured are always the same: can you clear the test, do you know your basics, can you communicate clearly in English.
• Strong on all three and the specific sequence does not matter.

4The test & technical rounds, patterns, not problems#

The online test is where offers are won and lost, so this section gets the most detail.

• Four kinds of sections, and most are sectionally timed.
• You cannot bank leftover minutes from aptitude to finish coding.
• Budget each section on its own clock.

Quantitative aptitude. Standard placement-test topics, high-school level but time-pressured.

• Percentages, profit and loss, ratio and proportion, averages, time-speed-distance, time and work, simple and compound interest, permutations and combinations, probability, number systems, basic data interpretation (charts and tables).
• Questions are not deeply hard, but they are often under a minute each. Speed matters as much as accuracy.
• Highest-yield move: memorize squares to 30, cubes to 15, fraction-to-percent conversions (1/7 = 14.28%, 1/8 = 12.5%, 1/6 = 16.67%), and percentage-change shortcuts.
• Half of quant speed is not doing arithmetic you could have recalled.

Logical reasoning. Drill the common forms until they feel automatic.

• Series (number and letter), coding-decoding, blood relations, directions, syllogisms, seating arrangements (linear and circular), puzzles, pattern recognition.
• Seating arrangements and syllogisms eat time if you have not drilled them.
• Draw a quick diagram or a Venn sketch instead of holding it in your head. The 20 seconds you spend sketching saves a minute of re-reading.

Verbal / English. This section does double duty as a signal of your communication quality.

• Reading comprehension, sentence correction, error spotting, fill-in-the-blanks, synonyms/antonyms, para-jumbles.
• A bad verbal score plus a weak spoken answer later reads as "will struggle in a client-facing role."
• For RC, read the questions first, then scan the passage for answers rather than reading the whole thing twice.

Pseudo-code / basic coding. This is the part freshers underprepare, and the single most common reason a borderline candidate fails the test.

• You get a small block of logic and answer what it outputs, what the loop does, or what value a variable holds after it runs.
• To clear these, get comfortable tracing code by hand: loops, conditionals, array indexing (watch off-by-one and zero-based indexing), basic recursion, operator precedence.
• Build the habit of a tiny variable table as you trace. For a loop, write down i and each changing variable on every pass.
• It feels slow for two snippets, then it is faster than reading, and it kills the careless errors that cost you three questions.

A concrete taste of what hand-tracing looks like:

x = 5
y = 2
result = 0
while x > 0:
    if x % y == 0:
        result = result + x
    x = x - 1
print(result)

Trace it: x=5 not even, skip. x=4 even, result=4. x=3 skip. x=2 even, result=6. x=1 skip. Loop ends. Output is 6. If you tried to "read" this instead of tracking x and result in a table, you would likely miss that both 4 and 2 get added. That is the whole skill.

If there is a live coding part, it stays at easy string/array manipulation, pattern printing, factorials, prime checks, reversing a number, simple sorting/searching. Not hard algorithmic puzzles.

• Know these cold so you can type them from muscle memory: reverse a string, reverse an integer, check palindrome, check prime, Fibonacci, factorial (loop and recursion), find max/min in an array, count vowels, bubble/selection sort, linear and binary search, and classic nested-loop pattern prints (right triangle, pyramid).
• That is a short, finite list. Memorize the twelve and you have covered the realistic range.

Difficulty level. Lighter than a product-company DSA screen.

• The challenge is breadth and speed, not depth.
• Nobody is asking you for dynamic programming or graph algorithms here.

How to practice. Do timed sets, not untimed drills. This is the single biggest mistake.

• Untimed, everyone can solve these. The test is a speed test wearing a knowledge-test costume.
• Give yourself the real per-question budget: often under a minute for aptitude, around two to three minutes for a pseudo-code trace.
• For pseudo-code, take 20 to 30 short snippets, predict the output before running them, then verify against a real interpreter so you cannot fool yourself.
• Keep an error log of every topic you miss, one line each (topic, what I got wrong, the fix), and revisit it every few days.
• Patterns repeat, and the error log turns your weak spots into your warm-up.

How to win the technical interview. When you get a coding or logic question, do not rush to the answer. The interviewer is grading your thought process more than the final code, so narrate it.

• Clarify the input, output, and edge cases out loud first. "So the input is an array of integers, could it be empty, could it have negatives?"
• Communicate your approach before you write. Talk through the plan in one or two sentences so they can redirect you early if you are off track.
• State complexity. Mention roughly how fast your solution runs (linear, quadratic) and whether it can be simpler. Even a basic "this is O(n), one pass" signals you think about efficiency.
• Test with a small example, including an empty or single-element case. Walk your own code with one input before you say "done."

The bar here is a calm, structured thinker, not a perfect optimizer.

• Interviewers care less about a perfect optimal solution and more about seeing someone who can explain themselves.
• A candidate who talks through a slightly imperfect solution clearly will usually beat one who silently writes perfect code.
• The job is client-facing, and communication is half the role.

5CS fundamentals (the core of the technical interview)#

For a services-company fresher round, strong fundamentals matter more than fancy algorithms. Expect questions across four areas, and expect follow-ups that tie the concept back to your own project ("you used MySQL, so what did you normalize?").

OOP. Know the four pillars with real examples, not textbook definitions.

• Encapsulation, abstraction, inheritance, polymorphism.
• Overloading (same method name, different parameters, resolved at compile time) vs overriding (subclass redefines a parent method, resolved at runtime).
• Abstract class vs interface, and when to use each. Constructors and constructor chaining.
• If you listed Java: collections (ArrayList vs LinkedList vs HashMap, when each wins), checked vs unchecked exceptions, and why == compares references while .equals() compares values for objects.
• Be ready to point at a line in your own project and say "this class uses inheritance because..."

DBMS. Know the classics, and be ready to write SQL on the spot.

• Normalization (1NF to 3NF) and why we do it (reduce redundancy and update anomalies).
• Primary vs foreign keys, joins (inner/left/right with a one-line example of each).
• WHERE (filters rows before grouping) vs HAVING (filters after grouping).
• Indexes (speeds reads, costs writes and storage), and the ACID properties with one line each.

-- second highest salary
SELECT MAX(salary) FROM employee
WHERE salary < (SELECT MAX(salary) FROM employee);

-- count employees per department
SELECT department, COUNT(*) AS headcount
FROM employee
GROUP BY department;

• Know the second-highest query two ways (subquery and LIMIT ... OFFSET), because the follow-up is often "now do it without a subquery."

Operating systems. The usual fresher set.

• Process vs thread (separate memory vs shared memory within a process).
• Deadlock and its four necessary conditions (mutual exclusion, hold and wait, no preemption, circular wait).
• Scheduling basics (FCFS, round robin, shortest job first) and the tradeoffs.
• Paging vs segmentation.
• Semaphore vs mutex (a mutex is a lock owned by one thread, a semaphore is a counter allowing N).

Computer networks. Know the layer names and the walk-through.

• OSI vs TCP/IP layers (know the layer names in order).
• TCP vs UDP (reliable and ordered vs fast and connectionless, and when you would pick each).
• What happens when you type a URL and press enter (DNS resolution, TCP handshake, HTTP request, server response, render).
• HTTP vs HTTPS (TLS adds encryption and identity).

6Behavioral & culture fit#

Hexaware's public brand leans on being a technology-and-BPS services partner, and its stated culture emphasizes customer centricity, continuous learning, collaboration, and integrity. You do not need to recite marketing lines.

The HR round is checking three things.

• Can you communicate clearly.
• Will you stay, not treat this as a backup until something "better" comes along.
• Are you flexible on location and shifts.

Read the subtext: the firm invests months training a fresher, so churn is expensive. The whole HR round is a bet on whether you will still be there in two years.

Prepare a few stories in STAR format (Situation, Task, Action, Result). Here is one worked example for "tell me about a time you handled a tight deadline":

• Situation: In my final-year project, our 3-person team was building a library management system, and two weeks before the demo a teammate dropped out.
• Task: I had to take over the database and reporting module on top of my own front-end work, without slipping the deadline.
• Action: I re-scoped the features into must-have vs nice-to-have, rebuilt the schema to cut two redundant tables, wrote the core queries first, and did a daily 15-minute sync with my remaining teammate to unblock fast.
• Result: We shipped all must-have features and demoed on time, and the project scored 9/10, the highest in our batch of 12 groups.

Why that works: a real crisis, a specific action list, and a measured result. Weak STAR answers stall on Situation and never reach Result. Keep yours to about 60 to 90 seconds spoken, land the number, and stop.

Also rehearse clean answers for these.

• "Tell me about yourself" (60 seconds: present, then path, then why here, not your life story).
• "Why Hexaware" (tie a real thing about the firm or track to your own goal, never "I need a job").
• "Where do you see yourself in 3 years" (growing within IT services, signal staying).
• "What are your strengths and weaknesses" (a real weakness plus the fix you are working on, not "I work too hard").
• "Are you okay relocating / with any shift" (decide your honest answer before the room, and if yes, say yes plainly).

Keep them short, honest, and specific. Rehearsed but not robotic.

7Your prep plan#

4-week plan

• Week 1: Lock quantitative aptitude, one topic per day, timed sets each evening. Start an error log on day one.
• Week 2: Logical reasoning and verbal/English. Keep doing short daily aptitude revision so week 1 does not decay.
• Week 3: Pseudo-code output tracing (20-30 snippets) plus CS fundamentals (OOP, DBMS). Write simple SQL and small programs daily, by hand first, then verify.
• Week 4: OS and CN fundamentals, mock tests end-to-end under time pressure, STAR stories, and HR answers. Do 2-3 full mock interviews, out loud, ideally with a friend playing interviewer.

2-week plan

• Days 1-4: Aptitude (quant + logical) timed sets, error log.
• Days 5-7: Verbal + pseudo-code tracing.
• Days 8-10: CS fundamentals (OOP, DBMS, OS, CN), one line definition + example + why for each topic.
• Days 11-12: Full-length mock tests; fix the top weak spots your error log keeps flagging.
• Days 13-14: STAR stories, HR answers, and your project deep-dive.

2-day crash plan

• Day 1: Rapid aptitude revision (one formula sheet), 30 pseudo-code snippets traced by hand, one full timed mock test.
• Day 2: Skim all four CS-fundamentals areas, memorize your project talking points cold, rehearse "Tell me about yourself," "Why Hexaware," and 2-3 STAR stories out loud until they flow without reading.

8Why people get rejected at Hexaware#

1. Failing the online test. Most eliminations happen here, usually from running out of time on aptitude or skipping the pseudo-code section entirely because it came last and the clock ran out. Fix: timed practice and section-by-section budgeting.
2. Weak core CS. Candidates who cannot explain the OOP pillars, write basic SQL, or distinguish process vs thread get filtered in the technical round. These are closed-book, finite topics, there is no excuse for being shaky on them.
3. Poor communication. Mumbling, over-long rambling answers, or weak English in a client-facing services firm is a real blocker, because the clients are often US and European enterprises.
4. No depth in their own project. Listing a project on the resume but being unable to explain the design, your specific contribution, or why you chose the stack. If you cannot defend it, do not list it.
5. Stability doubts. Signaling that Hexaware is a backup, or hesitating hard on relocation and shift flexibility. The interviewer hears "will quit in six months."
6. Eligibility and honesty gaps. Undisclosed backlogs, inflated marks, or mismatched details. Services firms verify thoroughly during onboarding, and a mismatch after an offer can cost you the offer. Say the true numbers.

9The offer, comp & negotiation#

What the package looks like.

• Fresher packages are typically in the ~Rs 3.5-7 LPA range: lower band for standard engineer roles, higher band for premium/digital or specialized tracks (cloud, data, niche skills).
• The structure is usually a fixed base plus a smaller variable/performance component.
• There is often a training period at the start during which your effective pay may be lower.
• There may be a service agreement or bond for a set period. Read it before signing: the duration, any payout if you leave early, and whether it starts from your joining date or the end of training.

Negotiation reality. For a mass-recruiter fresher role, there is limited room to move base pay, the band is largely fixed by track. You still have some leverage.

• Use a competing offer honestly. A genuine offer, mentioned politely, can sometimes move you to a higher track or band. Do not bluff. If they ask for proof and you have none, you lose credibility.
• Negotiate the track, not just the number. Ask whether you qualify for a premium/digital role. The gap there (often the distance between the Rs 3.5 and Rs 7 LPA ends of the band) is far larger than any base bump you could argue on the standard track.
• Clarify the full picture. Confirm location, joining date, bond terms, and the variable split in writing before you accept, so nothing surprises you on the first payslip or posting letter.

On a volume hire, the track you land is worth more than any number you can argue for.

10FAQ#

Q: Does Hexaware have a named test like TCS NQT or Infosys InfyTQ? A: Hexaware typically runs its own online assessment rather than a famous branded test. The format (aptitude + logical + verbal + pseudo-code/coding) is similar to other IT-services screens, so general placement-prep practice transfers directly. If you have prepped for TCS NQT or a Cocubes/AMCAT-style test, you have already prepped for most of this.

Q: How hard is the coding section for freshers? A: Light. Think pseudo-code output tracing and easy string/array programs, not competitive-programming puzzles. Being able to read and hand-trace code reliably matters more than advanced algorithms. Master the dozen classic programs in section 4 and you have covered the realistic range.

Q: What CGPA or percentage do I need? A: Thresholds vary by drive, but a common bar is around 60% / 6.0-6.5 CGPA with no active backlogs. Always check the specific eligibility criteria on the drive notice, because some premium tracks set a higher bar.

Q: Will they ask about my final-year project? A: Very likely, and it is one of the easiest places to score points. Know your project cold: the tech stack and why you chose it over alternatives, the database design, your specific contribution versus your teammates', the hardest bug you fixed, and what you would improve with more time.

Q: Is relocation or night shifts expected? A: Possibly, depending on the role and client. Support and some client-aligned roles can involve shifts tied to US or European hours. Being genuinely flexible on location and shifts is a plus in the HR round, so decide your honest answer in advance rather than freezing when asked.

Want this turned into a personalized, dated study schedule that counts down to your exact drive date? Build your own week-by-week plan and walk in knowing you did the work.