Skip to content

Company interview guide

Hexaware interview process and practice questions

Hexaware hires freshers through campus and off-campus drives and trains new graduates through Mavericks, the graduate talent programme within its HexaVarsity learning framework. Candidates commonly report an online assessment of aptitude, English and coding, followed by technical and HR interviews; experienced candidates usually describe technical rounds with the team and a manager or HR discussion.

As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026.

The interview process

  1. 1Campus drive, off-campus registration or online application
  2. 2Online assessment for many fresher drives: aptitude, English and coding
  3. 3Technical interview on fundamentals, testing or cloud basics, and your projects
  4. 4For experienced roles: a second technical or managerial round
  5. 5HR interview

Outside India

Candidates elsewhere more often report:

  1. Online application and recruiter screen
  2. Technical interviews with the team
  3. Manager or client interview (for many roles)
  4. HR discussion

What interviewers listen for

  • Put People First
  • Create Customer Value
  • Innovate Relentlessly
  • Be Sustainable
  • Come On In
  • Programming, SQL and testing basics
  • Interest in automation and cloud work
  • Communication and teamwork

Behavioral questions

  1. Tell me about a time you put a teammate's needs ahead of your own plan.

    A good answer covers

    • What they needed and what you gave up
    • How you made the trade-off without dropping your own work
    • What it meant for them and for the team
  2. Tell me about a time you automated or simplified a repetitive task.

    A good answer covers

    • The task, who did it and how long it took
    • What you built or changed: a script, macro, test or template
    • Time or errors saved, ideally with a number
  3. Tell me about a time you made someone new feel welcome in a team or group.

    A good answer covers

    • Who they were and what made joining hard
    • What you did in the first days
    • How quickly they settled in and contributed
  4. Tell me about a time you missed a deadline. What did you change afterwards?

    A good answer covers

    • The deadline and why you missed it, owned plainly
    • When you told people and how you limited the damage
    • The planning habit you changed since

Role and technical questions

  1. What is the difference between manual and automated testing, and when is automation worth it?

    A good answer covers

    • Manual: a person runs the steps; automated: scripts run them
    • Automation pays off for repeated regression checks, not one-off or fast-changing screens
    • Tools you know, such as Selenium or a unit-test framework
  2. Explain the difference between IaaS, PaaS and SaaS, with an example of each.

    A good answer covers

    • IaaS: rented servers and storage you manage yourself
    • PaaS: a platform where you deploy code without managing servers
    • SaaS: ready software used over the web, such as email or a CRM
  3. What is a join in SQL? Explain inner, left and right joins with a small example.

    A good answer covers

    • Inner join keeps only matching rows
    • Left and right joins keep every row from one side, with nulls where there's no match
    • An example such as customers and orders, and how a join can repeat rows
  4. How would you automate a daily report that someone currently builds by hand in a spreadsheet?

    A good answer covers

    • Understanding the steps, data sources and who uses the report
    • A tool choice: SQL plus a scheduled script, or a reporting tool
    • Checks so the automated version is trusted, and what happens when data is missing
  5. A scheduled job that ran fine for months failed last night. How would you investigate?

    A good answer covers

    • Reading the job's logs and the exact error
    • Checking what changed: data volume, credentials, a release, a server
    • Rerunning safely, fixing the cause and adding an alert
  6. For experienced candidates: tell me about a cloud migration you were part of. What was hardest?

    A good answer covers

    • What moved, from where to where, and why
    • Your part and the hardest problem
    • How it was solved and what you'd plan differently

Why Hexaware? Fit and HR questions

  1. Tell me about yourself.

    A good answer covers

    • Your degree or experience and the technologies you know best
    • One project with your part in it and a result
    • Why this role, in under two minutes
  2. Why Hexaware?

    A good answer covers

    • Something specific: its graduate training, its automation and cloud work, or its values
    • How that fits your skills or plans
    • What you'd like to learn first
  3. What do you expect from a graduate training programme, and how will you make the most of it?

    A good answer covers

    • Realistic expectations: structured learning, mentoring, project exposure
    • What you'll put in: practice outside sessions, asking questions, certifications
    • How you'll show you're ready for a project
  4. Do you have any questions for us?

    A good answer covers

    • One or two thoughtful questions about training, the first project or the team
    • Nothing already answered on the careers site
    • A brief thank-you

Tips

  • Hexaware lists its values as Put People First, Create Customer Value, Innovate Relentlessly, Be Sustainable and Come On In; have a short story for two or three.
  • If you've automated anything (a script, a macro, a test), bring it up; it fits the work many teams do.
  • Revise SQL joins and basic testing terms; they come up across development and testing roles.
  • Read about the Mavericks graduate programme before the HR round so you can say what you want from it.

Practise it out loud

A mock interview asks the way Hexaware's interviewers are known to, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer.

About this guide

Written by Orbit from Hexaware's own public pages and what candidates commonly report. Orbit isn't affiliated with Hexaware. The questions are practice questions in the style of its interviews, not questions taken from them. Processes change, so check the job post and what your recruiter tells you.

Sources