A structured 60-90 second summary, not your whole life story
Education, the technologies you actually work in, and one project worth asking about
A clear link to the role you are interviewing for
Sample answer:
“I am a final-year Information Technology student. My core strengths are Java and SQL - I have used both in a college inventory-management project where I designed the schema and wrote the reporting queries. During my internship I worked on bug fixes in an existing web application, which is where I got comfortable reading someone else’s code. I am looking for a role where I can work on enterprise systems with a real training programme behind it, which is why I applied to Mphasis.”
Tips:
Use a present-past-future structure and end on why you are here today
Name specific technologies rather than “I know coding”
Plant one project you want to be asked about
Tell me about your family background
What they’re looking for:
Usually context and rapport rather than a scored answer
Practical signals about relocation and support
Sample answer:
“I am from Coimbatore. My father runs a small business and my mother is a school teacher. They have been supportive of me taking a role in another city, so relocation is not an issue for me.”
Tips:
Keep it brief and factual
Connect it to relocation if that is genuinely your position
Especially important if you are from a non-CS branch
Sample answer:
“I like that IT services work puts you in front of a real business problem rather than a purely academic one. In my internship the most interesting part was figuring out what the users actually needed before writing anything. I also want the exposure of working across different clients and systems early in my career, which is harder to get in a single-product role.”
Tips:
Be honest - a rehearsed answer about “passion for technology” is transparent
If you are from a non-CS branch, address that switch directly and without apology
Reference actual experience where you can
What interests you about software development?
What they’re looking for:
Genuine engagement with building things
Some evidence beyond coursework
Sample answer:
“I enjoy the debugging side more than I expected. Working out why something fails - reading logs, narrowing down the cause, confirming the fix - is the part of my project work I actually looked forward to. I also like that the feedback loop is immediate; you find out quickly whether your reasoning was right.”
Tips:
Pick a specific part of the work rather than the whole field
Back it with a real example
Avoid clichés about “changing the world with technology”
A link between what Mphasis does and what you want to do
Sample answer:
“Mphasis works heavily in cloud, data and applied AI for large enterprise clients, with a long history in banking and financial services delivery. My project work has been on the data and SQL side, so that is the kind of work I would like to grow into. I also value that freshers go through a structured training programme before being put on a project - I would rather learn the standards properly than pick things up ad hoc.”
Key points you can genuinely reference:
Headquartered in Bengaluru; an IT services and solutions company serving large enterprise clients
Focus areas including cloud, applied AI and data, cybersecurity and digital transformation
A strong presence in banking, financial services and insurance delivery
A structured fresher training programme before project allocation
Tips:
Verify these against the current Mphasis careers site before your interview - service-line emphasis changes year to year
Connect one fact to one of your own projects
Never answer this with “it is a good company with good culture”
Are you willing to relocate and work in shifts?
What they’re looking for:
Flexibility for client-driven delivery work
Honesty about any real constraints
Sample answer:
“Yes, I am open to relocating to any of the delivery locations. On shifts, I understand client work sometimes needs overlap with other time zones, and I am comfortable with that. If there were ever a constraint on my side I would flag it early rather than let it become a problem for the team.”
Tips:
Answer honestly - agreeing to something you cannot do creates a problem later
If you have a genuine constraint, state it calmly and early
Tell me about a time you had to learn something quickly
What they’re looking for:
A repeatable learning method
Evidence you can be productive on an unfamiliar stack
Sample answer:
“For my final-year project we needed a REST API and I had only written standalone programs before. I spent two days on the official documentation and a small throwaway prototype before touching the real project, then rebuilt it properly once I understood routing and error handling. Starting with a throwaway version is now how I approach anything new.”
Tips:
Use STAR - situation, task, action, result
Name the actual technology
End with what you now do differently
Where do you see yourself in five years?
What they’re looking for:
Realistic ambition within an engineering track
Some intention to stay long enough to be worth training
Sample answer:
“In five years I would like to be the person on the team who owns a module end to end - designing it, not just implementing tickets - and to have gone deep on one area, most likely data engineering. Longer term I would like to mentor freshers the way I would be mentored coming in.”
Tips:
Stay within a realistic engineering progression rather than jumping to management titles
Pro Tip: The single most common weak answer in this round is “Why Mphasis?”. Prepare three concrete facts about the company’s actual business and connect one of them to your own project work - that alone separates you from most of the queue.
