Mphasis Interview Questions 2026 — Fresher Hiring Process & Model Answers
Mphasis officially screens technology graduates on a 60% average academic score, then runs elimination rounds: an aptitude test, a personal interview and a communication test. Candidates commonly report an AMCAT-based aptitude test (logical, quantitative, verbal and programming MCQs), followed by technical questions on C pointers, OOP, DBMS and simple programs such as prime or Armstrong numbers, and an HR round.
Preparing for your Mphasis Interview?
Practice a simulated AI Mock Interview using real Mphasis questions and receive instant feedback.
Mphasis is a Bengaluru-headquartered IT services company that hires engineering and MCA freshers through campus and off-campus drives for roles such as Associate Software Engineer. Its fresher process is shorter than many mass recruiters’, but each round is an elimination round, and the communication test catches many candidates who prepared only for aptitude.
The Mphasis Selection Process
Mphasis’s own careers information centre describes the steps for technology-school applicants. The right-hand column adds what candidates commonly report.
| Stage | Official description | Commonly reported by candidates |
|---|---|---|
| Academic screening | Minimum average academic score of 60% | No active backlogs, limited gaps, BE/BTech or MCA (prep-site reports) |
| Aptitude test | Elimination round | AMCAT: logical, quantitative, verbal and programming/pseudocode MCQs with sectional cutoffs; some drives add 2 basic coding questions |
| Personal interview | Elimination round | Technical (30–45 min) on C, OOP, DBMS, DSA basics and project; HR (around 15 min) |
| Communication test | Elimination round | Spoken and written English assessment; some prep sites call it a Versant-style test (not confirmed) |
| Offer | Letter of Intent, then training batch scheduling; permanent offer letter after joining | — |
A group discussion appears in some candidate reports and not in others — it depends on the drive.
🚀 Start Free Mphasis Mock Interview
Practice Mphasis technical, HR and communication-round questions with real-time AI feedback on pacing and filler words.
Start Free Mock InterviewTechnical Interview Round: Key Focus Areas
1. Programming Fundamentals
- Commonly reported topics: pointers, structure vs union, recursion, simple number programs (prime, Armstrong, sum of digits, palindrome).
2. Object-Oriented Programming
- Commonly reported topics: the four pillars, overloading vs overriding, constructors, abstract class vs interface.
Check whether your resume clears automated screening before your Mphasis application. Scan Resume with ATS Checker →
3. DBMS and Data Structures
- Commonly reported topics: ACID, SQL command categories (DDL/DML/DCL/TCL), basic joins, stacks and queues, arrays and linked lists.
4. Communication
- Practise reading aloud, short spoken answers, and listening comprehension. Record yourself and check for pace and filler words.
3-Week Mphasis Preparation Plan
- Week 1 — Aptitude: daily timed sets of quant, logical and verbal questions plus pseudocode tracing; one full AMCAT-style mock.
- Week 2 — Technical: C and OOP basics, DBMS, stacks/queues; code 20 basic programs by hand.
- Week 3 — Interview and communication: rehearse your project, “tell me about yourself”, and 10 common HR answers out loud.
Our HR interview questions Indian recruiters ask and how to crack IT interviews without experience guides cover the HR side in more depth.
Practice communication, confidence, pacing, filler words, and HR responses. Try Mphasis HR Mock Interview →
Salary and Offer Details
Mphasis does not publish fresher pay. PrepInsta lists approximately INR 4 LPA for Associate Software Engineer (Applications) — an unofficial, approximate figure. Use the CTC to in-hand salary calculator to understand monthly take-home, and read any service-agreement clause in your offer documents carefully.
Resume Tips for Mphasis
- Format: one page, single column, with your aggregate percentage clearly shown (the 60% filter is applied early). Build your resume and check your ATS score.
- Keywords: C, Java or Python, OOP, SQL, Data Structures, SDLC, Agile, Git, Testing.
- Templates: start from the Fresher Resume India example.
- Keywords Map: use the Software Engineer ATS Keywords and QA Engineer ATS Keywords sheets.
- Company Hub: visit the Mphasis Company Hub. Also applying to similar mid-size IT firms? See the Persistent Systems interview guide and Hexaware interview guide.
Sources
Checked November 2026:
- Mphasis Careers — Application process: careers.mphasis.com
- Mphasis Careers — Information centre: careers.mphasis.com
- PrepInsta — Mphasis eligibility criteria and pattern (prep-site summary): prepinsta.com/mphasis/eligibility-criteria
- GeeksforGeeks — Mphasis interview experience (2021–22): geeksforgeeks.org
- GeeksforGeeks — Mphasis on-campus interview experience (2023): geeksforgeeks.org
Items marked “commonly reported” are candidate accounts, not official Mphasis statements.
Mphasis Interview Questions with Model Answers
These are real questions asked in Mphasis interviews in India, with model answers that interviewers have told us they score highly. Each answer is self-contained.
A pointer is a variable that stores the memory address of another variable; you declare it with an asterisk (int *p) and dereference it with *p to read or write the value at that address. A NULL pointer is a pointer that intentionally points to nothing (address 0); it is the safe default for an uninitialised pointer and should be checked before dereferencing. A dangling pointer points to memory that has already been freed or has gone out of scope — for example, a pointer to a local variable returned from a function, or a pointer used after free(). Dereferencing it causes undefined behaviour. The fix is to set pointers to NULL immediately after free() and never return addresses of local variables.
Pointer questions are commonly reported in Mphasis technical rounds. A tiny code example on paper helps.
In a structure, every member has its own memory location, so the size of a structure is at least the sum of its members' sizes (plus padding), and all members can hold values at the same time. In a union, all members share the same memory location, so its size equals the size of its largest member, and only one member holds a meaningful value at a time — writing one member overwrites the others. Unions are used to save memory when a variable can be one of several types, such as in embedded systems or when parsing protocol packets.
State the sizes with an example: a struct with an int and a char is typically 8 bytes with padding; a union of the same is 4 bytes.
Overloading is defining multiple methods with the same name but different parameter lists in the same class — for example add(int a, int b) and add(double a, double b). The compiler chooses the version at compile time, so it is compile-time (static) polymorphism. Overriding is redefining a parent-class method in a child class with the same signature — for example a Vehicle class with a start() method that a Car class overrides. The call is resolved at runtime based on the actual object, so it is runtime (dynamic) polymorphism.
Commonly reported question. Keep the answer short, then offer the example — interviewers like candidates who structure answers.
ACID describes reliable transactions. Atomicity: all operations in a transaction succeed or none do. Consistency: data remains valid according to rules and constraints. Isolation: concurrent transactions do not interfere with each other. Durability: committed data survives a crash. DML (Data Manipulation Language) commands work on the data inside tables: SELECT, INSERT, UPDATE and DELETE. DCL (Data Control Language) commands manage permissions: GRANT gives a user privileges and REVOKE takes them back. For completeness, DDL (CREATE, ALTER, DROP) defines structure and TCL (COMMIT, ROLLBACK, SAVEPOINT) controls transactions.
Candidates report ACID and SQL command categories. Listing all four categories (DDL, DML, DCL, TCL) in one breath shows you know the full picture.
A stack is LIFO (last in, first out): elements are added with push and removed with pop from the same end, the top. A queue is FIFO (first in, first out): elements are added at the rear (enqueue) and removed from the front (dequeue). Stack uses: function call stack, undo in editors, browser back button, balanced-parentheses checking, and expression evaluation. Queue uses: printer job scheduling, CPU process scheduling, handling requests on a web server, and breadth-first search. Both support push/pop or enqueue/dequeue in O(1).
Be ready to implement either one with an array or a linked list, including overflow and underflow checks.
An Armstrong number equals the sum of its digits each raised to the power of the number of digits — for example 153 = 1 cubed + 5 cubed + 3 cubed. Steps: count the digits n; copy the number to temp and set sum = 0; while temp is greater than 0, take digit = temp % 10, add digit to the power n to sum, then temp = temp / 10; finally compare sum with the original number. In Python: def is_armstrong(x): s = str(x); n = len(s); return x == sum(int(d) ** n for d in s). Time complexity is O(d) where d is the number of digits.
Basic number programs (primes, Armstrong, sum of digits, palindromes) are commonly reported. Handle edge cases such as 0 and single-digit numbers.
Structure it in under two minutes: the problem and users; the tech stack and why you chose it; the modules you personally built; one technical challenge and how you solved it; and the result (for example accuracy, users or time saved). Then pause and let the interviewer drill down. Prepare to explain the database tables, the main algorithm, and what you would improve with more time.
GeeksforGeeks candidate reports describe detailed project discussions. Rehearse with a friend asking 'why?' after each sentence.
Answer honestly after understanding the terms: 'Yes. I understand training a fresher is an investment for the company, and I plan to build my career here for the long term. I am open to relocation and shifts as the project requires. Could you share the agreement duration and terms so I can review them properly?' If you have a genuine constraint, state it clearly now rather than later.
A candidate report notes HR asked about signing a 2-year agreement. Asking for the terms politely is professional, not negative.
Use a present–past–future structure in about 90 seconds. Present: 'I am a final-year B.Tech Computer Science student at [college], strongest in Java and SQL.' Past: one project and one achievement with a number, for example 'I built a library management system used by 200 students and cut issue time from 5 minutes to under 1.' Future: 'I want to start my career at Mphasis because I want to work on enterprise applications for clients in banking and insurance, and grow into a strong full-stack engineer.' Avoid repeating your resume line by line or sharing personal details unrelated to the job.
This is the warm-up question in almost every HR round — it also feeds the communication assessment, so pace and clarity matter.
Common Mistakes in Mphasis Interviews
These are the mistakes that eliminate candidates at this stage — often before the technical round even begins.
- Ignoring the communication test — it is an official elimination round, and fluent but rushed answers can still score poorly.
- Skipping pseudocode/programming MCQ practice because the role is 'just a fresher role'.
- Not knowing C basics (pointers, structures, unions) even when your main language is Java or Python.
- Agreeing to a service agreement without asking for the terms, or refusing it without reading them.
- Memorising a generic 'tell me about yourself' answer that sounds recited.
Frequently Asked Questions
Ready to Land Your Offer at Mphasis?
Practice with real interview questions and optimize your resume using FundoCareer's placement prep suite.