Learn from Mphasis interview experiences shared by candidates who cleared recent campus and off-campus drives. Patterns shift by year, college and role, so treat this as a prep map rather than a script.
Reported eligibility (from student and placement-cell reports): B.E./B.Tech/M.Tech/MCA, roughly 60% or 6.5 CGPA across Class 10, Class 12 and graduation, and no active backlogs at the time of the drive. Cutoffs differ by drive - always confirm against your own placement email.
Candidate Profile: Final year Computer Science student, ~7.5 CGPA, tier-2 college, steady DSA practice
Round 1 - Online assessment
Proctored online test with quantitative aptitude, logical reasoning and verbal ability sections plus technical MCQs
The MCQ section pulled from OOPs, DBMS, operating systems and networks
Two coding questions at easy-to-medium difficulty; partial marks for passing some test cases
Sectional timers meant speed mattered as much as accuracy
Tip: Do timed sectional mocks. Most eliminations here come from running out of time, not from hard questions.
Round 2 - Group discussion
Conducted for this campus drive only; a general awareness / workplace topic
Panel watched for whether you structured a point and let others speak
Tip: Enter early with one clear framing statement rather than fighting for airtime later.
Round 3 - Technical interview (30-45 min)
Started with a resume walkthrough and then the academic project in detail: why that stack, what broke, what you would rebuild
Coding: level-order traversal of a binary tree, then a follow-up on detecting a cycle in a linked list
Core CS: OOPs pillars with real examples, SQL joins and a GROUP BY query, normalisation basics
Asked to state time and space complexity for every solution
Result: Selected
Tip: Say the approach out loud before writing code. Interviewers scored the reasoning as much as the final answer.
Round 4 - HR interview (20-30 min)
Background, why IT services, and why Mphasis specifically
Flexibility on location and on shift timings for client-facing work
One behavioural story about working in a team under a deadline
Final Result: Offer received
Tip: Have two or three concrete facts about Mphasis ready - its service lines and the kind of clients it works with beat generic praise.
Key Takeaways: Clear the online assessment on speed, know your own projects better than the interviewer can, and be able to explain complexity in plain language.
Short call covering background, skills claimed on the resume and interest in the role
No technical depth here; it was a filter for eligibility and availability
Tip: For off-campus routes, expect a screening call in place of the campus GD round.
Round 2 - Online assessment
Same aptitude plus programming structure as the campus test
Verbal ability section was the tightest on time
Tip: Do not skip verbal. Candidates who prepare only quant get caught by the sectional cutoff.
Round 3 - Technical interview
More conversational than a rapid-fire quiz
Python and SQL questions since both were on the resume: list vs tuple, exception handling, joins, aggregate functions and a window-function follow-up
One string-manipulation problem solved on a shared editor
Result: Selected
Tip: Only list technologies you can defend for ten minutes. Everything on the resume is fair game.
Round 4 - Managerial round
Situational questions: a missed deadline, a disagreement with a teammate, how you would handle unclear requirements from a client
Some discussion of prior internship work
Tip: Use a plain situation-action-result structure. Short and concrete beats long and abstract.
Round 5 - HR interview
Cultural fit, career goals, compensation and benefits discussion
Relocation willingness across Mphasis delivery locations
Final Result: Offer received
Key Takeaways: Depth on the two or three technologies you actually know beats a long resume of buzzwords, and the managerial round is a real filter in drives that include it.
Candidate Profile: Electronics and Communication student, selected candidate
HR interview (20-30 min)
Conversational and friendly rather than adversarial
Questions included:
Tell me about yourself
Why Mphasis, and what do you know about what we do?
Why an IT services career after an ECE degree?
Are you comfortable relocating and working in shifts if the client needs it?
Where do you see yourself in five years?
Do you have any questions for us?
The interviewer spent time explaining the training programme and the service line the role sat in
Final Result: Offer received
Key Takeaways: For a non-CS branch, have a clear and honest answer for why software. Prepare a few real facts about Mphasis, and always close with a question of your own.
Common interview questions from the Mphasis process
After the technical rounds, Mphasis usually closes with a short HR / hiring-manager conversation: motivation, location and shift flexibility, joining timelines, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
Pro Tip: Round lists differ between campus and off-campus Mphasis drives - some include a group discussion, some a managerial round, some neither. Confirm the sequence with your placement cell before you plan your preparation.
