Mphasis Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about Mphasis. It is a volume recruiter, so the online test is the real filter.

• Thousands register for a single drive.
• The test alone cuts that to a few hundred.
• The interviews that follow are mostly a sanity check on your basics and whether you can hold a clear conversation.
• Clearing the test is not half the battle. It is closer to 70 percent of it.

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

For a mass recruiter, "getting the call" is less about a referral and more about being registered in the right pipeline and surviving the test. Nobody hand-picks a fresher resume out of a pile here. You enter through a gate, and the gate is a cutoff.

Campus route.

• If your college is a Mphasis hiring partner, your placement cell shares a registration link and an eligibility cutoff.
• The common bar is around 60 percent or 6.0 CGPA throughout 10th, 12th, and graduation, with no active backlogs at the time of the drive.
• Read the exact numbers on your drive's notice. A 60 percent drive and a 65 percent drive are different gates, and people get silently filtered for missing one of the three stages (10th, 12th, or degree) by a single point.
• Register the moment the form opens. Slots and test windows fill fast, and a late registration can mean no seat at all.

Off-campus route.

• Mphasis hires off-campus through its careers portal (careers.mphasis.com), through named hiring drives, and sometimes through aggregator platforms and partner assessment providers.
• Create a profile, keep your resume current, and apply to every "Fresher Engineer" or "Graduate Trainee" opening you qualify for.
• You will usually take the same style of online test as campus candidates, so the prep below is identical whichever door you come through.

Resume rules. Recruiters skim for a few seconds, and an Applicant Tracking System (ATS) scans before any human reads it.

• Keep it one page, plain formatting, no photo, no two-column tables that break parsers, standard section headers (Education, Skills, Projects, Experience).
• Lead with a quantified bullet. Weak: "Made a website for college fest." Strong: "Built a React + Node event-registration site used by 400+ students during the fest, cutting manual signups to near zero." The number is what makes a skimming recruiter stop.
• Mirror the keywords in the job post: the language (Java, Python, SQL), the concepts (OOP, DBMS, data structures), and the tools (Git, REST). ATS matching is literal, so if the post says "SQL" and your resume says "database queries," you can lose the match.
• List 2 to 3 real projects you can defend line by line. One project you understand deeply beats five you copied off GitHub. Every project on the page is a question the interviewer is allowed to ask.
• Put your strongest language and your CGPA near the top if they are good. If your CGPA is borderline, do not hide it, just do not lead with it.

3The loop at a glance#

What varies by drive.

• Some drives fold aptitude and coding into one long single test.
• Some add a short "communication assessment" (spoken or typed English, sometimes a repeat-the-sentence or describe-the-image task).
• The exact order and the exact time limits change by drive and by the assessment vendor running it, but the ingredients above are standard.
• Read the instructions screen before you start every section. It tells you the real time limit and whether you can revisit questions.

4The online test, the real gate#

This is where most candidates are eliminated, so treat it as the main event, not a warm-up.

How the test is built against you.

• It is timed and usually section-locked: once you leave a section you cannot go back.
• It often carries sectional cutoffs, meaning you must clear each section on its own, not just post a good total.
• That single rule kills more candidates than any hard question does. A person who scores 90 in quant and 40 in verbal fails. A person who scores 65 across the board passes.

Quantitative aptitude.

• Expect percentages, ratios and proportion, profit and loss, simple and compound interest, time-speed-distance, time and work, averages, ages, permutations and combinations, probability, number systems (LCM/HCF, remainders), and basic mensuration.
• The level is 10th-grade math. The pressure is the clock.
• If you are spending two minutes on a percentage question, you are too slow. Target under a minute on the standard ones.

Logical reasoning.

• Number and letter series, coding-decoding, blood relations, directions, seating arrangements (linear and circular), syllogisms, puzzles, data arrangement, and pattern recognition.
• Seating and puzzle sets eat time, so flag the heavy ones and come back if the section allows it.

Verbal ability.

• Reading comprehension, synonyms and antonyms, sentence correction, error spotting, fill in the blanks, para-jumbles, and basic grammar.
• This is the section strong engineers underrate and then fail on the sectional cutoff.
• Do one RC passage a day so it stops feeling slow.

Pseudo-code and programming.

• Many Mphasis-style tests include a pseudo-code section: short C-like snippets where you predict the output, find the bug, or identify what a loop computes.
• There may also be 1 to 2 hands-on coding problems in a language of your choice (commonly C, C++, Java, or Python) covering arrays, strings, loops, recursion, and simple logic.
• Below is the kind of snippet that shows up. Trace it, do not guess.

int f(int n) {
    int r = 1;
    for (int i = 1; i <= n; i++)
        r = r * i;
    return r;
}
// f(4) returns 24. It computes n factorial.

The traps in these are always the same.

• Off-by-one on the loop bound.
• Pre-increment vs post-increment (++i vs i++).
• Integer division truncating (7 / 2 is 3, not 3.5).
• Operator precedence.
• Write the variable values on scratch paper for each iteration and you will not fall for them.

Difficulty. Easy to medium. Nothing exotic, no dynamic programming, no graph theory. The challenge is speed under a clock, not cleverness.

How to win this round.

1. Practice timed, not relaxed. Do full mock tests with a running clock on screen. Accuracy at speed is the exact skill being measured, and you cannot build it doing untimed practice.
2. Respect sectional cutoffs. Do not spend 15 minutes crushing quant and then bomb verbal because you ran out of time. Budget minutes per section before you start and stick to it.
3. For pseudo-code, trace by hand. Write the state of each variable per loop iteration on paper. This is the single highest-return habit for this section.
4. Attempt, do not freeze. If there is no negative marking (confirm on the instructions screen for your drive), guess rather than leave a blank. If there is negative marking, skip only true unknowns.
5. Nail the easy coding problem first. Get one problem fully correct, passing all test cases, before chasing a harder second one. A clean working solution scores more than two half-done ones that fail hidden cases.

5Core CS fundamentals (your technical interview backbone)#

For freshers, the technical round is mostly core computer science plus one coding question. You do not need system design.

What the interviewer is really deciding.

• Can I put this person in front of a client's codebase in a few months.
• Are the foundations solid, and can they reason out loud rather than recite a textbook.
• The interviewer is usually a project lead, not an algorithms specialist.

Data structures and algorithms (light).

• Arrays, strings, linked lists, stacks, queues, hashing, recursion, basic sorting (bubble, selection, insertion, merge, quick), binary search, and simple trees.
• Be ready to write and dry-run one problem, usually string or array based: reverse a string, check palindrome, find duplicates, Fibonacci, factorial, prime check, pattern printing.
• Know that merge and quick sort are O(n log n) while bubble and selection are O(n squared), and be able to say why in one sentence.

OOP.

• The four pillars: encapsulation, abstraction, inheritance, polymorphism, each with a real example, not a definition.
• Difference between a class and an object.
• Overloading vs overriding (compile-time vs run-time).
• Interface vs abstract class.
• These come up in almost every Java or C++ interview, and the follow-up is always "give me an example from your own project."

DBMS.

• Primary key vs foreign key, normalization (1NF, 2NF, 3NF explained in plain words, not formal definitions), joins (inner, left, right), ACID properties, and simple SQL.
• Expect the classic "write a query to find the second highest salary." Have an answer ready:

SELECT MAX(salary)
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

• If you also know the DENSE_RANK version, mention it, but the subquery above is enough and easy to explain.

Operating systems.

• Process vs thread.
• Deadlock and its four conditions (mutual exclusion, hold and wait, no preemption, circular wait).
• Scheduling basics (FCFS, round robin).
• Paging vs segmentation in one line each, and what a semaphore does.

Computer networks.

• OSI vs TCP/IP layers.
• Difference between TCP and UDP (reliable and ordered vs fast and connectionless).
• What happens when you type a URL and press enter (DNS lookup, then TCP connect, then HTTP request, then render).
• The basics of HTTP, DNS, and IP.

Your projects.

• Expect "explain your project," then "why did you choose this tech," then "what was the hardest bug and how did you find it."
• Know your own code cold. This is where fake projects die in a single follow-up.

6Behavioral and HR round, fit and communication#

The traits that land well.

• Mphasis positions itself around customer-centricity and its "Front2Back" (F2B) transformation approach, applying cloud and cognitive tech to put the customer experience first.
• You do not need to recite the marketing, but showing you genuinely value customer focus, learning agility, teamwork, and adaptability helps, because those are the traits that keep a fresher billable on a client project.
• The firm also talks publicly about responsible, inclusive work and continuous reskilling, so curiosity and a real willingness to pick up whatever tech a project throws at you are safe, honest themes to lean on.

Common HR questions.

• "Tell me about yourself."
• "Why Mphasis," "Why IT services."
• "Are you okay with relocation, night shifts, or any technology stack we assign."
• "Where do you see yourself in 3 years."
• "Tell me about a time you worked in a team, faced a conflict, or failed at something."

On flexibility, be honest. Saying you are open to relocation and any tech stack genuinely helps for a services role, because freshers get placed wherever the client demand is, and that can change month to month.

Structure your stories in STAR (Situation, Task, Action, Result) so answers stay structured and land a concrete number in the result.

Worked STAR example, "Tell me about a time you solved a problem under pressure":

• Situation: During my final-year project, our team's inventory web app crashed two days before the department demo whenever more than a few users logged in at once.
• Task: As the backend owner, I had to find and fix the cause fast without breaking the working features.
• Action: I reproduced the crash, traced it to database connections that were opened but never closed, and switched us to a connection pool. I also added simple error logging so we could see failures instead of guessing.
• Result: The app handled all 30 demo users smoothly with zero crashes, and our project scored the highest in a batch of 12 teams. The logging I added helped two juniors debug their own issues the next semester.

Why that answer works.

• It names a concrete number (30 users, 12 teams).
• It shows a real debugging method rather than luck.
• The result ties back to the team, not just you.
• Keep each answer to 60 to 90 seconds. Speak slowly and clearly. In the communication round, how you speak carries nearly as much weight as what you say, because this is the one skill a client-facing services firm cannot train out of you in a bootcamp.

7Your prep plan#

4-week plan (ideal).

• Week 1: Lock quant fundamentals (percentages, ratios, TSD, time-work, interest, P&C, probability). One timed section daily.
• Week 2: Logical reasoning and verbal. Daily reading comprehension plus a reasoning set. Start pseudo-code tracing.
• Week 3: Core CS. OOP, DBMS, OS, CN, one subject every two days with short notes you can revise in 10 minutes. Daily 2 easy coding problems.
• Week 4: Full-length timed mocks in the test format. Revise CS notes. Write and rehearse 6 STAR stories. Mock HR with a friend who will interrupt you.

2-week plan (realistic).

• Days 1-4: Quant and reasoning, timed sets daily.
• Days 5-7: Verbal, pseudo-code tracing, 2 coding problems per day.
• Days 8-11: Core CS crash (OOP, DBMS, OS, CN) and revisit your own projects until you can defend every line.
• Days 12-14: Two full mocks, STAR stories, HR practice out loud (not in your head).

2-day crash plan (emergency).

• Day 1 morning: One full aptitude mock, then review every single wrong answer. Afternoon: pseudo-code tracing plus OOP and DBMS basics.
• Day 1 evening: 5 classic coding problems (palindrome, reverse a string, second-highest salary, Fibonacci, find duplicates).
• Day 2 morning: OS and CN one-liners, SQL query practice, re-read your resume and projects out loud.
• Day 2 afternoon: Write and say aloud 4 STAR stories plus "Tell me about yourself" and "Why Mphasis."

8Why people get rejected at Mphasis#

1. Missed a sectional cutoff. Scored great in quant, flunked verbal, auto-rejected before any human saw the profile. Each section stands alone.
2. Froze on the coding or pseudo-code. Left the programming section blank, or submitted code that compiled but failed the hidden test cases.
3. Could not explain their own project. A resume project they clearly did not build, exposed by the first follow-up question. The interviewer is not angry, they just move on.
4. Recited without understanding. Gave a clean textbook definition of polymorphism but could not give a real example or answer "why would you use it."
5. Weak communication. Mumbled, rambled past 90 seconds, or gave unclear answers in the HR round. For client-facing services work this is a real disqualifier, not a soft mark.
6. Rigid on flexibility. Said no to relocation, to shifts, or to "any technology we assign." That makes a fresher hard to place, and placement is the entire point of the role.

9The offer, comp and negotiation#

What to expect.

• For fresher Engineer roles, expect roughly Rs 3.5 to 7 LPA, varying by the specific role, your skills, and the hiring drive.
• The structure is typically a fixed base, a smaller performance or variable component, provident fund, and standard benefits.
• Higher-skill or specialized tracks, and some lateral or premium drives, land toward the upper end.
• Standard trainee offers sit lower, often near the Rs 3.5 to 4.5 LPA zone for a general drive.

Negotiation reality for freshers. Most entry offers at large services firms are standardized by band, so there is not much room to push the number on your first offer. Pretending otherwise just wastes goodwill. That said, there are real moves:

1. Use a competing offer honestly. If you hold another genuine written offer at a higher band, mention it politely. It is the single strongest lever you have, and the only one that reliably moves a standardized number.
2. Ask about the role and growth, not just money. Clarify the technology track, training and certification support, and promotion timelines. A better project placement early can matter more to your next job than a small CTC bump now.
3. Negotiate joining logistics respectfully. Joining date, location preference, and relocation support are sometimes more flexible than base pay. Be gracious. These firms hire in volume, and the recruiter who liked your attitude is the same person who approves your location request.

Want this turned into a personalized, dated study schedule built around your test date and your weak areas? Tell me your timeline and I'll map out exactly what to study each day.