Academic snapshot
Marks: 60% or 6.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related)
Backlogs: None active
Gap: Typically max ~2 years
Mphasis is a global IT services and digital transformation company founded in 2000 and headquartered in Bengaluru. With over 47,000 employees, it delivers application development, infrastructure, and cloud services to enterprise clients. Mphasis is a regular campus recruiter for engineering and analyst roles in India.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Mphasis is a Bengaluru-headquartered volume hirer with an Associate / ASE campus track. The academic floor matches other mid-size IT services firms; the interview is often a fundamentals quiz on what you claimed.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college % list, batch OA | Aptitude + coding bar |
| Careers / portals | Form + invite | Same 90-minute flavour |
| Referral | Visibility | You still sit OA and tech |
Off-campus does not mean easier quant. It often means more applicants who never timed a mock.
Is 6.0 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. A 6.3 who finishes one coding problem and can explain a resume SQL query beats an 8.7 who freezes on OOP pillars.
10th / 12th: They count. Keep scans.
Gaps and backlogs: No active backlogs. Max about 2 years gap in many tables. Full-time degrees only.
What helps the resume screen: One project with a stack you can defend. See certifications after aptitude and one language.
Academic snapshot
Marks: 60% or 6.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related)
Backlogs: None active
Gap: Typically max ~2 years
Skills they actually filter
OA: Aptitude + technical MCQs + 1-2 coding
Interview: Resume, OOP, SQL, light DSA
Languages: C, C++, Java, Python
Differentiator: You can defend every line on the CV
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 60% or 6.0 | Mailer wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | CS/IT plus listed circuital | Confirm drive |
| Backlogs | None live | Clear before joining |
| Relocate | Bengaluru and other cities | HR will ask |
Good fit: You can finish a 90-minute mixed paper, you will move to Bengaluru if asked, and you can explain your project without reading the resume aloud.
Harder path: You padded the resume with frameworks you cannot spell; you skipped quant; you want only remote product work. Mphasis HR is a logistics-plus-fit round.
Branch myth: Listed ECE students still write code. The OA does not grade your branch code.
Download 2026 Mphasis placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Mphasis does not publish a permanent official paper set. Papers on this site are pattern trainers for the 90-minute filter and resume-led technicals.
| Round (typical) | What to practice |
|---|---|
| Aptitude | Quant, logical, verbal under time |
| Technical MCQ | OOP, DBMS, DS basics |
| Coding | 1-2 array/string/interval-style submits |
| Technical interview | SQL, OOP, resume algorithms (DFS/C++ in one ASE note) |
| HR | Why Mphasis, city, hobbies, company knowledge |
Think of papers as simulators for mixed-section stamina. Themes repeat more than exact clones.
| Theme you saw | Drill next | Why Mphasis asks it |
|---|---|---|
| Arrays / strings | Two easies | OA coding |
| Merge intervals / top-K | Sorting + heap lite | OA cousins |
| SQL JOIN / GROUP BY | One query from your project data | Technical |
| OOP pillars | One class from the resume | Technical |
| DFS / graphs | Only if on CV | Resume-led quiz |
Mphasis hires freshers through campus cells, careers / portals, and referrals. After eligibility, the shape is mid-size IT services: mixed OA, resume-led technical, short HR.
Campus recruitment
Through college placement cells. PPT (listen for Associate vs other titles), then OA and interviews.
Online applications
mphasis.com careers and job portals. Follow the assessment mail for platform and duration.
Referrals
Help the screen. You still need the 90-minute filter.
60% throughout, listed branches, no live backlogs. Gate. Inflated CGPA is a later integrity fail.
| Section (typical) | What shows up | Prep move |
|---|---|---|
| Aptitude | Quant, logical, verbal | Skip-rule timed sets |
| Technical | Programming, DS, DBMS, OOP | One-liners |
| Coding | 1-2 problems, C/C++/Java/Python | One complete submit |
Pass habit: bank coding green, then mop MCQs. Older tables cite sectional plus overall cutoffs (~60-65% overall). Your invite wins.
The Dec 2023 ASE note: questions focused on resume content and fundamental concepts (SQL, OOPs, DFS/C++). That is the prep brief.
Pass habit: every library on the CV gets a two-sentence story. If you listed C++, expect a pointer or STL question. If you listed SQL, write a JOIN on paper.
Company knowledge, hobbies, Why Mphasis, city, compensation expectations. Keep it short. Know ₹4-5 LPA Associate from public reports and say you will read the letter.
| Phase | Duration | Notes |
|---|---|---|
| Apply / screen | 3-5 days | Eligibility list |
| OA | 1 day | Platform per invite |
| Shortlist | 2-3 days | |
| Technical + HR | Same day or +1 week | ASE note: stacked interviews |
| Offer | Days | Written letter wins |
| End to end | ~2-3 weeks common | Calendars slip |
| Component | Focus | Prep move this week |
|---|---|---|
| Quant / LR / verbal | Speed | Timed mock quiz |
| Technical MCQ | OOP, SQL, DS | 20 one-liners |
| Coding Q1 | Arrays / strings | Two timed easies |
| Resume quiz | SQL, OOP, listed algo | Explain four pillars + one query |
| HR | Why Mphasis, city | Two STAR + one city sentence |
A clean one-page resume beats a three-page stack museum.
Saturday 10:00: 90-minute OA.
Saturday 12:00: 20-minute resume oral (OOP + SQL + project).
Sunday 11:00: one more coding complete submit.
Sunday 12:00: HR including city and Why Mphasis.
Two weekends of that beat twelve nights of random services dumps.
10th, 12th, all semesters, ID, photo if asked, resume one page. Name and percentages must match the form.
Mphasis is headquartered in Bengaluru. Even if the PPT names Chennai or Pune, recruiters still ask whether you will move. Answer a city. “I prefer Bengaluru, I can do Pune for the first year” is a sentence. “Anywhere in India, maybe remote” is how you look unprepared.
If you already live in Bengaluru, say that. If you do not, do not invent a fake local address. Background checks compare forms.
The company story is digital transformation for banks and healthcare. The OA is still school math plus one program. Do not spend October reading HL7 or Basel III PDFs. Spend October on skip-rule quant and a JOIN. In HR, one sentence is enough: “I want to learn delivery on BFSI accounts and I already write Java/SQL.” That is more useful than a fake domain essay.
Interviewer opens your PDF. Points at a project. Asks:
The 2023 ASE note (SQL, OOPs, DFS/C++) is that pattern. DFS appeared because it was on the CV. If your CV says “implemented DFS for a campus navigator,” you will dry-run DFS. If it does not, they will not invent it.
Prep move: print the resume. For every bullet, write a 20-second answer in the margin. Delete bullets you cannot fill.
Campus forms say Associate or ASE. Blogs say Software Engineer at 8 LPA after two years. Those are different rows. You are sitting the fresher row. Prep the fresher OA. Do not walk into HR quoting a 2-3 YOE Glassdoor scrape.
OA coding is “submit a passing array/string program.” Cabin coding, when it happens, is shorter: reverse a string, explain a loop, write a JOIN. People fail the OA by attempting a heap when an O(n) scan was enough. People fail the cabin by refusing to pick up a pen. Practise both: typed submit and handwritten dry-run.
| Minute | Job |
|---|---|
| 0-3 | Skim all sections; mark easy quant |
| 3-35 | Quant + easy logical |
| 35-50 | Verbal + leftover logical |
| 50-55 | Technical MCQs you know |
| 55-80 | Coding: one complete submit |
| 80-90 | Mop skipped MCQs; do not start a second algorithm if Q1 is still red |
If your invite uses a different split, rewrite this table on paper the night before. The habit is the point.
You get a technical slot, not an offer. Use the waiting days to rehearse the resume oral, not to start a new DSA sheet. The interviewer will not ask last night’s random hard. They will ask what you already claimed.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Week-by-week calendars live on the preparation guide. This section is the focus split.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed aptitude | 40% | One 90-min mock at cutoff pace |
| One complete coding submit | 30% | Green arrays/strings |
| Resume fundamentals | 20% | OOP + SQL + listed algo dry-run |
| HR | 10% | Why Mphasis + city |
The biggest miss is a padded resume meeting a fundamentals interviewer. Delete what you cannot defend, then practise what remains.
Mon-Tue: two full OAs.
Wed: coding only, two complete easies.
Thu: resume oral.
Fri: HR.
Sat: combined mock.
Sun: error log, sleep.
If you have eight weeks, use the nested guide.
Reuse timed aptitude and one coding language. Mphasis-specific extra is the resume oral: SQL, OOP, whatever algorithm you listed. Virtusa may add SpeechX and a 2-year clause. HCL pools may add GD. Do not invent three new syllabi. Keep one error log.
Set a timer. Speak out loud.
Record it once. The second take is the interview. If you cannot fill minute 12, the resume is too empty or too fake. Fix the PDF, not the speech.
You will be staffed on an account. You will learn a stack the project already uses. You will attend stand-ups. You will not redesign the bank’s core. HR wants to hear that you know this. “I want to learn delivery and I already write Java/SQL” is the Associate sentence. “I will only do research” is how you fail a 20-minute HR.
Campus loops often finish in 2-3 weeks. Off-campus portals can sit for a month. Do not pause all other applications while you wait for a Mphasis mail. Keep HCL/Virtusa/Infosys live until a PDF exists.
Name mismatch (Aadhaar vs 10th vs resume), a 12th percentage that does not match the form, and a backlog you “forgot” are the boring ways to lose an Associate seat after HR smiled. Scan everything into one folder tonight. If you use a shortened name on LinkedIn, the offer PDF still needs the legal name. Ask the cell how they want initials written. That 10-minute chore is part of eligibility, not an afterthought.
If a recruiter asks you to re-upload marksheets after OA, do it the same day. Delayed documents are how people drop off a shortlist they already earned. Keep the same file names (10th.pdf, 12th.pdf, grad.pdf) so you do not attach the wrong year under pressure. If your college uses a grading conversion, keep the official conversion letter with the scans. Mphasis HR will not reverse-engineer your internal 10-point scale from a WhatsApp screenshot. If you repeated a year, write the honest dates once and reuse them on every form so the story does not change between OA and offer. A one-year gap with a skills story is easier to defend than three different gap dates across three portals. Pick one timeline and keep it.
If a Mphasis invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Mphasis sits around ₹4-5 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported campus floors commonly cite 60% or 6.0+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT and related); final-year and recent grads (often within 2 years); no active backlogs; max about 2 years education gap; full-time degrees. Always verify the drive notice.
What you are training for: Common fresher shape: online assessment (~90 min: aptitude, technical, 1-2 coding) → technical interview (~30-45 min, often resume + OOP/SQL/DSA basics) → HR (~20-30 min). A December 2023 ASE GFG note matches aptitude → technical → short HR. End to end is often 2-3 weeks.
Short version of the prep split: Split time roughly: 40% timed aptitude, 30% one complete coding problem in C/C++/Java/Python, 20% OOP/SQL/resume fundamentals, 10% HR (Bengaluru/other cities, Why Mphasis). Clear the 90-minute filter first. Full plan: /mphasis/preparation-guide/.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Mphasis previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Mphasis drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Mphasis usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Mphasis?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Mphasis-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Mphasis story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Mphasis papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Mphasis papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Mphasis-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role, location (Bengaluru and other cities), hiring year, and written components.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Associate / ASE (fresher) | ₹4-5 LPA | Primary band for this hub |
| Associate (1-2 YOE blogs) | ₹6-7 LPA | Not the campus default |
| Software Engineer (2-3 YOE) | ₹8-10 LPA | Lateral |
| Specialist / BA-style posts | Wide | Different loop |
Confirm base vs variable on the written offer. Do not treat blog midpoints as guarantees.
Health insurance, training, shift norms, relocation to Bengaluru/Chennai/Pune/Hyderabad. Digital-transformation is the PPT story; day-one work is still an account team.
Know ₹4-5 LPA Associate. Ask joining city. Ask any service agreement if the PPT named one.
Associate / ASE title persists
Campus language is still Associate-style CTC, not a sudden 12 LPA product band.
Technical stays resume-led
The 2023 ASE GFG note is still the useful warning: SQL, OOP, whatever you listed.
90-minute mixed OA
Aptitude plus coding remains the door. Skip-rule quant still matters.
Bengaluru gravity
HQ city shows up in HR. Have a relocate sentence.
Net for 2026: do not wait for Mphasis to become a design-round company. Double down on timed aptitude, one program, and a defensible resume.
Yes. Free Mphasis placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
OA (~90 min) → technical → HR. Often 2-3 weeks. Details: online assessment.
Usually 3 after apply. Count the mailer.
A 2023 ASE GFG note: resume content and fundamentals (SQL, OOPs, DFS/C++). Prepare what you wrote, not a secret hard paper.
Commonly ~90 minutes: aptitude, technical MCQs, 1-2 coding. Sectional plus overall cutoffs in older tables. Invite wins.
C, C++, Java, Python on most invites. Pick one for OA and interview.
Commonly 60% or 6.0 throughout; listed CS/IT/related degrees; no live backlogs; gap ≤ ~2 years. Your mailer wins.
Many notices include circuital cousins. You still sit coding. Read the branch list.
Associate / ASE ~₹4-5 LPA (candidate-reported, August 2026). Confirm the letter.
Bengaluru HQ plus Chennai, Pune, Hyderabad and other centres in student chatter. HR will ask relocation.
Timed aptitude, one complete coding submit, resume fundamentals, HR city. Guide: preparation guide.
Bank one OA coding submit and a resume you can defend in SQL and OOP. Technical is often a quiz on what you wrote.
Same volume-services family and similar 4-5 LPA Associate/GET bands. Virtusa ASE notes sometimes add a long multi-section paper and a 2-year agreement. HCL pools may add GD/paper-pen. Mphasis technical is especially resume-led. Prep aptitude+one language for all.
Not for the default Associate loop. Know how your project stores data. Save TinyURL for product companies.
No. The 2023 ASE interviewer asked DFS/C++ because it was on the CV. List what you can dry-run.
Default Associate loops stay on resume fundamentals (SQL, OOP, light DSA). Save TinyURL-style design for product companies. If a specialist title is on the form, read that mailer.
“Throughout” language on many JDs will still block you. Some drives list only graduation. Your notice wins. Do not hide a 12th marksheet; background check will see it.
Aptitude → technical → HR. Writer: “the second round was a Technical Interview, where the questions focused on the content of our resumes and fundamental concepts” (SQL, OOPs, DFS/C++), then a short HR chat on company knowledge and hobbies. Takeaway: the CV is the syllabus. Source: GeeksforGeeks ASE.
What to steal: 90-minute OA stamina; one complete coding submit; SQL + OOP dry-run on your own project; honest resume.
What to ignore: Paying for dumps; treating Mphasis as a hidden FAANG paper; quoting 8 LPA on Associate.
Technical composite: Candidates who could write a JOIN and name four OOP pillars with an example from their project passed short interviews. Candidates who listed Spring, Kafka, and “ML pipeline” and then blanked on a class vs object question did not. Average fundamentals are the bar.
OA composite: A 90-minute mixed paper feels easy until coding is left with 8 minutes. Takeaway: submit one program before you polish the last seating puzzle.
HR composite: Company-knowledge questions are not a Wikipedia quiz. Two facts (Bengaluru HQ, BFSI/healthcare delivery) plus Why Mphasis in 30 seconds is enough. Hobbies questions are a check that you can talk like a person. One real hobby beats three fake “reading about AI” lines.
Resume composite: Candidates who deleted “Kafka, K8s, GenAI” and kept “Java Spring CRUD + MySQL JOIN I wrote” had shorter, cleaner interviews. Candidates who kept the museum list got asked the one tool they feared. Edit tonight.
Mphasis is Bengaluru-centric services Associate hiring. ₹4-5 LPA is a real job. The OA is a mixed filter. Technical is a resume quiz. Students who treat the CV as marketing copy and aptitude as optional are the ones those notes are about.
Use timed papers on this site. Follow the preparation guide for a week calendar. Read interview experience and the HR page. Finish one program. Delete one fake skill from the resume tonight. Print 10th and 12th. Then sit the drive.
If Mphasis and HCL/Virtusa/Infosys all land the same week, compare city, joining date, and any agreement clause. A 4.5 LPA Associate in a city you will actually join beats a rumour 5.5 LPA you will reject in HR. Classroom “selected” is not a letter. Wait for the PDF.
Day-one work is still an account and a stack you are assigned. “I will only do GenAI” is a bad HR answer. “I will learn the stack and I already write Java/Python” is the Associate answer.
Interview day logistics: Laptop charged if OA is remote; college ID if on campus; the exact resume PDF you uploaded. Do not sit a proctored test on flaky hostel Wi-Fi.
Keep practising until skip rules, one green submit, and a 90-second project story are automatic. That is Mphasis. Everything else is decoration.
More narratives: Mphasis interview experience.
HCL · Virtusa · Infosys · TCS · Wipro · Hexaware
Last updated: August 2026.