cswork / libraryOpen practice workspace

Interview guides · Hexaware

Hexaware Software Engineer Interview Guide

Hexaware Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Hexaware, you are at the core of the company’s mission to deliver innovative, digital-first solutions for global clients. This role is not merely about writing code; it is about solving complex business problems through technology. You will contribute to the lifecycle of software products, from requirements gathering and design to development, testing, and deployment. Your work will directly impact Hexaware’s ability to drive digital transformation for its customers. Whether you are working on backend services, frontend interfaces, or cloud-native applications, you will be expected to demonstrate technical rigor, scalability, and a deep understanding of the problem space. The environment is fast-paced and collaborative, requiring you to work effectively with cross-functional teams, including product managers, architects, and quality assurance engineers.

This guide is scoped to a Software Engineer candidate at Hexaware.

Focus areas

  • Java
  • OOP (Object-Oriented Programming)
  • SQL

The Hexaware interview process

Hexaware candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Group Discussion

Initial screening to evaluate communication and teamwork skills.

What to demonstrate

  • Initial screening to evaluate communication and teamwork skills
  • Depth in Java

How to prepare

  • Answer aloud and timed: Explain the four pillars of OOP (Encapsulation, Inheritance, Polymorphism, Abstraction) with real-time examples.
  • Answer aloud and timed: What is the difference between HashMap and HashSet?

Online Assessment

Rigorous assessment including aptitude, logical reasoning, and coding tasks.

What to demonstrate

  • Rigorous assessment including aptitude, logical reasoning, and coding tasks
  • Depth in Java

How to prepare

  • Answer aloud and timed: Explain SQL Joins (Inner, Left, Right, Full) with examples.
  • Answer aloud and timed: How does the OSI Model work and what are its 7 layers?

Technical Rounds

In-depth evaluation of your technical knowledge and skills.

What to demonstrate

  • In-depth evaluation of your technical knowledge and skills
  • Depth in Java

How to prepare

  • Answer aloud and timed: Describe the difference between synchronous and asynchronous programming.
  • Answer aloud and timed: Write a program to find the second largest element in an array.

HR Interview

Final interview to assess cultural fit and discuss potential offer.

What to demonstrate

  • Final interview to assess cultural fit and discuss potential offer
  • Depth in Java

How to prepare

  • Answer aloud and timed: Implement a function to reverse a string without using built-in functions.
  • Answer aloud and timed: Write a program to check if a number is a palindrome.

Where candidates lose points

Master the Elevator Pitch

You will be asked "Tell me about yourself" in almost every round. Keep it concise, professional, and focused on your technical journey and project experience.

Focus on the Resume

Expect every line of your resume to be fair game. If you mention a project, know every technical decision made within it.

Prepare for the Group Discussion

Keep up with current tech trends (AI, Metaverse, Remote Work). During the GD, focus on being a contributor rather than a competitor—listen to others and build on their points.

Practice Pseudocoding

Many rounds use pseudocode to test logic without getting bogged down in language-specific syntax. Practice writing your logic on paper or a whiteboard.

Questions & practice

Describe the difference between synchronous and asynchronous programming.

Medium · Technical & Domain Fundamentals

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Write a program to find the second largest element in an array.

Medium · Coding & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Implement a function to reverse a string without using built-in functions.

Medium · Coding & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Write a program to check if a number is a palindrome.

Medium · Coding & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Explain your approach to finding the longest substring without repeating characters.

Medium · Coding & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Explain SQL Joins (Inner, Left, Right, Full) with examples.

Medium · Technical & Domain Fundamentals

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Why do you want to join Hexaware?

Medium · Behavioral & Cultural Fit

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Explain the four pillars of OOP (Encapsulation, Inheritance, Polymorphism, Abstraction) with real-time example

Medium · Technical & Domain Fundamentals

Explain the four pillars of OOP (Encapsulation, Inheritance, Polymorphism, Abstraction) with real-time examples.

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What is the difference between HashMap and HashSet?

Medium · Technical & Domain Fundamentals

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How does the OSI Model work and what are its 7 layers?

Medium · Technical & Domain Fundamentals

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Design a database schema for an Employee management system.

Medium · Coding & Problem Solving

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Walk me through your final-year project; what was your specific contribution?

Medium · Project & Experience Deep-Dive

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Which design patterns did you use in your project and why?

Medium · Project & Experience Deep-Dive

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What was the most complex problem you solved recently, and what was your approach?

Medium · Project & Experience Deep-Dive

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Exports duplicate a row range about once a week

Hard · leases · clock skew · idempotency

Roughly once a week an export writes a file containing a duplicated range of rows. The affected job_run rows show attempt = 1, status = succeeded, one started_at, and a lease_owner naming a different host from the one whose logs show the job starting. Leases last 30 seconds and are heartbeated every 10 from inside the handler; lease_expires_at is computed on the worker and compared against the database's now(). Find the mechanism, and give a fix that holds even if you cannot fix the clocks.

Approach

  1. Start from the fact that eliminates the obvious answer. attempt = 1 means no retry was recorded, so this is not a re-run after failure; two workers ran the same row concurrently and the takeover path never touched the counter. lease_owner naming a host other than the one that started the job is the same statement from the other side.
  2. Enumerate the mechanisms that cause a premature takeover, then find the signal that separates them. Either the lease genuinely expired because the heartbeat did not fire, which is what happens when the heartbeat runs on the handler's own thread and the handler makes a long blocking call, or it only appeared expired because two clocks disagree, since lease_expires_at is written from the worker's clock and evaluated against the database's. The discriminator is the distribution: incidents clustered on the longest exports indict the heartbeat, incidents clustered on one host indict skew. Measure both, and measure each host's offset against the database directly.
  3. Read the reclaim query precisely. In PostgreSQL now() is transaction start time, not statement time, so a reclaimer holding a long transaction compares against an older timestamp than expected; clock_timestamp() is the statement-time function. This is worth ruling in or out before you redesign anything, because it changes which rows look expired.
  4. Remove the second clock rather than trying to synchronise it. Issue and extend the lease in the database, with lease_expires_at = now() + interval '30 seconds' in both the claim and the heartbeat, so exactly one clock is ever compared and worker skew stops mattering to this predicate.

Follow-up

  • The displaced worker has already streamed half the file to object storage. What makes that side effect safe to repeat?
  • You now count takeovers. What alert fires on that counter, and at what threshold?

Suggested practice checklist

Built from the rounds and topics Hexaware candidates report.

Day 1 — Map the Hexaware loop

  • Write out the reported sequence: Group Discussion, Online Assessment, Technical Rounds, HR Interview.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work Java

  • Spend the session on Java, which Hexaware candidates report being tested on.
  • Write one worked example in Java and time yourself on it.

Deliverable: One timed worked example in Java.

Day 3 — Work OOP (Object-Oriented Programming)

  • Spend the session on OOP (Object-Oriented Programming), which Hexaware candidates report being tested on.
  • Write one worked example in OOP (Object-Oriented Programming) and time yourself on it.

Deliverable: One timed worked example in OOP (Object-Oriented Programming).

Day 4 — Work SQL

  • Spend the session on SQL, which Hexaware candidates report being tested on.
  • Write one worked example in SQL and time yourself on it.

Deliverable: One timed worked example in SQL.

Day 5 — Answer out loud: Technical & Domain Fundamentals

  • Answer aloud, timed: Explain the four pillars of OOP (Encapsulation, Inheritance, Polymorphism, Abstraction) with real-time examples.
  • Answer aloud, timed: What is the difference between HashMap and HashSet?

Deliverable: Spoken answers to 2 reported Technical & Domain Fundamentals question(s), under time.

Day 6 — Answer out loud: Coding & Problem Solving

  • Answer aloud, timed: Write a program to find the second largest element in an array.
  • Answer aloud, timed: Implement a function to reverse a string without using built-in functions.

Deliverable: Spoken answers to 2 reported Coding & Problem Solving question(s), under time.

Day 7 — Answer out loud: Project & Experience Deep-Dive

  • Answer aloud, timed: Walk me through your final-year project; what was your specific contribution?
  • Answer aloud, timed: Which design patterns did you use in your project and why?

Deliverable: Spoken answers to 2 reported Project & Experience Deep-Dive question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

How do you handle a scenario where a client requests a feature that is impossible to deliver within the deadli

Medium · Project & Experience Deep-Dive

How do you handle a scenario where a client requests a feature that is impossible to deliver within the deadline?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle conflict or pressure within a team?

Medium · Behavioral & Cultural Fit

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Where do you see yourself in the next 5 years?

Medium · Behavioral & Cultural Fit

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Are you comfortable with relocation or shift flexibility?

Medium · Behavioral & Cultural Fit

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?