Company interview guide
Mphasis interview process and practice questions
Mphasis is known for its work with banking, capital markets and insurance clients, and its interviews often reflect that domain. Candidates commonly report an online assessment for fresher drives, technical interviews on fundamentals, coding and their projects, and an HR round. It publishes five cultural principles, including 'Ready, fire, aim' and 'Disagree but Commit', which make useful material for behavioural answers.
As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026.
The interview process
- 1Campus drive, online application or referral
- 2Online assessment for many fresher drives: aptitude, English and coding
- 3Technical interview on fundamentals, coding and your projects
- 4For experienced roles: a second technical or managerial round
- 5HR interview
Outside India
Candidates elsewhere more often report:
- Online application and recruiter screen
- Technical interviews with the team
- Manager or client interview (for many roles)
- HR discussion
What interviewers listen for
- Mphasis first
- Growth mindset
- Ready, fire, aim
- Work for each other
- Disagree but Commit
- Fundamentals and clean, testable code
- Interest in banking and insurance technology for many roles
- Clear communication with clients and teammates
Behavioral questions
Tell me about a time you tried something quickly, it didn't work, and you learned from it.
A good answer covers
- What you tried and why speed mattered more than a perfect plan
- How you found out it didn't work
- What you changed and what the second attempt achieved
Tell me about a time you disagreed with a decision but committed to it once it was made.
A good answer covers
- Your view and the decision that went the other way
- How you made your case, respectfully and with reasons
- How you then backed the decision fully, and what happened
Tell me about a time you stepped outside your role to help your team get something done.
A good answer covers
- What was at risk and why you stepped in
- What you did that wasn't in your job description
- The result for the team
What's a skill you've had to work hard to improve, and how are you doing it?
A good answer covers
- The skill and why it didn't come easily
- Your plan: practice, feedback, courses
- The progress you can show so far
Role and technical questions
What is a database transaction, and what do the ACID properties mean?
A good answer covers
- A group of steps that succeed or fail together, such as a money transfer
- Atomicity, consistency, isolation, durability: one line each
- What goes wrong without them, for example money debited but not credited
How would you design the tables for a simple bank account system with deposits and withdrawals?
A good answer covers
- Tables for customers, accounts and transactions, with keys
- Storing each transaction rather than only overwriting the balance
- Rules such as no overdraft, and how you'd keep balances correct
What is the difference between authentication and authorisation? Use a banking app as the example.
A good answer covers
- Authentication checks who you are: password, OTP, biometrics
- Authorisation checks what you're allowed to do: view, transfer, approve
- Why both matter, and a mistake that would expose data
Explain exception handling in your language, and what you'd log when a payment fails.
A good answer covers
- Try, catch and finally (or the equivalent), and when to rethrow
- Logging useful context, such as a transaction ID and error code, but never card or password data
- Showing the user a clear message and leaving the system in a safe state
Two withdrawals hit the same account at the same moment. What could go wrong, and how would you prevent it?
A good answer covers
- The race: both read the old balance and the account goes below zero
- Fixes: database transactions with locks, or a check-and-update in one step
- How you'd test for it
For experienced candidates: tell me about a legacy system you worked on and how you changed it safely.
A good answer covers
- What the system did and why changing it was risky
- How you protected it: tests first, small steps, feature flags or parallel runs
- What you changed and how you knew nothing broke
Why Mphasis? Fit and HR questions
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
Why Mphasis?
A good answer covers
- Something specific: its work in banking or insurance, or its cultural principles
- How that fits your skills or interests
- What you'd like to learn there
Would you be happy to work in financial-services domains such as banking or insurance? Why?
A good answer covers
- An honest answer and what interests you about the domain
- Anything you already know, such as how payments or claims work
- How you'd learn the domain quickly
What would you want to learn in your first year here?
A good answer covers
- One or two concrete skills linked to the role
- How you'd learn them on the job and on your own
- A question back about how new joiners are supported
Tips
- Revise database transactions, SQL and one language well; banking and insurance work leans on them.
- Read Mphasis's five cultural principles and prepare a short example for 'Disagree but Commit' and 'Ready, fire, aim'.
- Learn some basic banking and insurance words (account, transaction, settlement, policy, claim) so domain questions don't surprise you.
- Be ready to explain one project end to end, including how you tested it.
Practise it out loud
A mock interview asks the way Mphasis'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 Mphasis's own public pages and what candidates commonly report. Orbit isn't affiliated with Mphasis. 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.