Loading...
Nail the 'Why mainframe over cloud?' question at Infosys with STAR-format answers, insider tips, and exact phrasing that impresses interviewers.
Let me be real with you. When an Infosys interviewer asks, "Why do you want to work in mainframe technology when most companies are moving to cloud?", most candidates freeze. They either mumble something vague about "job security" or go on a defensive rant trying to prove mainframe isn't dead.
Both approaches tank your interview. Here's what the interviewer is actually testing ā and how to flip this question into a story that makes you look like exactly the candidate they want to hire.
This isn't a trick question. Infosys has a massive mainframe practice serving banking, insurance, and government clients. When they ask this, they're checking for three things:
A weak answer sounds like: "Mainframe is still relevant and I want to learn it."
A strong answer sounds like: "I researched Infosys's financial services clients, I understand the transaction volumes only mainframe handles reliably, and here's a specific experience that shaped my view."
See the difference? One is generic. One shows you did your homework and have a real story.
Here's the thing most people miss ā this is a behavioral question wearing a technical costume. The interviewer isn't quizzing you on COBOL syntax. They want your reasoning, your values, and your self-awareness.
Most candidates prepare for mainframe technical questions (JCL, VSAM, CICS) but completely neglect the behavioral side. At Infosys specifically, behavioral questions carry more weight than you'd expect, especially for campus hires and junior roles. They use a competency framework ā and "Learning Agility" and "Drive for Results" are two competencies this question directly targets.
STAR stands for Situation ā Task ā Action ā Result. It's the gold-standard structure for behavioral answers. Let me walk you through exactly how to apply it to this question.
Set the context. Where were you? What were you exposed to that made you form an opinion about mainframe?
Example: "During my internship at a regional bank, I worked on a project that required pulling transaction data from a legacy IBM z/OS system..."
What was your role or challenge in that situation?
Example: "My task was to help migrate summary reports to a new dashboard, but I kept running into bottlenecks because the source data on the mainframe was structured differently than anything I'd worked with before..."
This is the meat. What did YOU do? What did you learn? What decision did you make?
Example: "I spent two weeks learning JCL job streams and VSAM file structures on my own time. I realized the mainframe was processing 10,000+ transactions per second with sub-millisecond reliability ā something our cloud prototype couldn't match under load. That gap fascinated me..."
What happened? What did you take away? Connect it to why you're sitting in this interview.
Example: "The project delivered on time, and I left with a deep respect for what mainframe infrastructure actually does in critical environments. That's what drew me toward building expertise here rather than following the crowd to cloud."
Here's a complete, polished answer. Don't memorize it word-for-word ā internalize the structure and personalize it with your own experience.
"Great question ā and honestly, it's one I've thought about a lot.
During my final year project, our team was tasked with building a transaction reconciliation module for a simulated banking environment. We started with a cloud-first approach using AWS Lambda and DynamoDB. [Situation]
My specific responsibility was ensuring data consistency during high-concurrency scenarios ā basically, making sure no transaction got lost or double-counted when thousands happened simultaneously. [Task]
When we stress-tested the cloud setup at scale, we hit latency spikes and eventual consistency issues that, in a real banking scenario, could mean regulatory violations. I started researching how actual banks solve this. That research led me deep into mainframe architecture ā IBM z/OS, CICS transaction management, and how financial institutions like HDFC and Citi run billions of transactions daily with five-nines uptime. I built a small COBOL prototype just to understand the execution model. [Action]
What I found completely reframed my thinking. The result wasn't just a better project ā it was a career direction. I realized that mainframe isn't a dying technology; it's a specialized, critical technology that most developers are running away from, which means expertise here is genuinely rare and valuable. Infosys works with some of the largest BFSI clients in the world, and I want to be the engineer who understands the core of what keeps those systems running. [Result]"
Your answer lands harder when you can drop a few real facts. Here are stats interviewers love hearing:
| Fact | Source |
|---|---|
| 95% of ATM swipes touch a mainframe | IBM |
| $3 trillion in daily commerce runs on mainframe | IBM |
| 71% of Fortune 500 companies use mainframes | Gartner |
| Mainframe COBOL processes more transactions daily than Google searches | Reuters estimate |
You don't need to cite these formally. Just weave one or two in naturally: "When I learned that the majority of global financial transactions still touch a mainframe, it completely changed how I thought about 'legacy' technology."
This signals business awareness ā a huge green flag for Infosys interviewers.
If the interview turns technical (and at Infosys it often does even after a behavioral question), you should be comfortable talking about what you've seen or tried. Here's a simple COBOL snippet to have in your mental toolkit:
IDENTIFICATION DIVISION.
PROGRAM-ID. CALC-INTEREST.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 WS-PRINCIPAL PIC 9(9)V99 VALUE 100000.00.
01 WS-RATE PIC 9(3)V99 VALUE 5.75.
01 WS-INTEREST PIC 9(9)V99.
PROCEDURE DIVISION.
COMPUTE WS-INTEREST = WS-PRINCIPAL * (WS-RATE / 100)
DISPLAY 'Annual Interest: ' WS-INTEREST
STOP RUN.You can reference this kind of code and say: "What struck me about COBOL was how explicit and readable the financial logic is. Every field is typed with precision. That's not accidental ā it's designed for auditability in regulated industries."
That one observation shows technical curiosity and business understanding. Interviewers remember candidates who connect the two.
And if you've played around with JCL (Job Control Language), here's what a basic job submission looks like:
//CALCJOB JOB (ACCT),'INTEREST CALC',CLASS=A,MSGCLASS=X
//STEP1 EXEC PGM=CALC-INTEREST
//SYSOUT DD SYSOUT=*
//SYSIN DD *
INPUT DATA HERE
/*Even surface-level familiarity here signals initiative ā exactly what Infosys looks for in a candidate explaining their motivation.
Let me tell you the three places I see candidates crash on this question:
1. Going negative on cloud Don't trash cloud to make mainframe sound better. Saying "Cloud is overrated and unreliable" makes you sound uninformed. The interviewer knows both technologies have their place. Show that YOU know that.
2. Generic passion statements "I've always been passionate about mainframes" ā unless you're 45, this isn't credible. Ground your answer in a real experience, even if it's small. A weekend tutorial, a college project, a conversation with a mentor ā all of these work.
3. Failing to connect to Infosys specifically This is a company-specific question. Research Infosys's mainframe clients, their Modernization practice, their IBM PartnerWorld relationship. Drop one specific thing. "I noticed Infosys recently expanded its mainframe modernization offerings for BFSI clients ā that's exactly the intersection of legacy expertise and forward thinking I want to be part of."
4. Not having a follow-up ready The interviewer WILL ask a follow-up. If you don't have one ready, all the momentum from your great STAR answer evaporates.
Here's how the conversation typically flows ā and what to say at each beat:
Opening the answer: "That's actually something I feel strongly about, so let me share a specific experience that shaped my thinking..."
Transitioning into the STAR structure: "When I was working on [project/internship], I ran into a situation where..."
Bridging to your motivation: "That experience made me realize that mainframe expertise isn't a step backward ā it's a specialization that's genuinely rare and deeply needed..."
Closing confidently: "So when I looked at where I could build unique, durable expertise early in my career, mainframe ā especially in a company with Infosys's client base ā felt like the right bet."
That last line does something smart: it frames your choice as strategic, not desperate. You're not here because you couldn't get another job. You're here because you thought about it.
Be ready for these ā they're almost guaranteed:
"How do you see mainframe and cloud coexisting in the next 5 years?" ā Talk about hybrid integration. Mainframe as the transaction backbone, cloud for analytics and front-end. Mention IBM Z and AWS/Azure connectivity.
"What do you know about COBOL or JCL?" ā Be honest about your level. If you're a beginner, say: "I've gone through the fundamentals and built a small exercise ā I know I have a lot to learn, and I'm ready for that." Honesty here builds more trust than bluffing.
"Where do you see yourself in 3 years in this role?" ā Talk about certifications (IBM Certified System Programmer), client-facing work, becoming a subject matter expert your team relies on.
"Aren't you worried your skills will become obsolete?" ā This is a confidence test. Answer calmly: "Mainframe has been 'dying' for 30 years and still processes most of the world's critical transactions. The real risk is everyone running toward cloud leaving mainframe understaffed ā which actually makes this a great place to build irreplaceable expertise."
These responses will make an Infosys interviewer mentally cross your name off the list:
Here's what to keep in your pocket walking into that Infosys interview room:
If you walk in with a genuine story, a bit of technical awareness, and the confidence to frame this as a deliberate career choice, you're already ahead of 80% of the candidates in the room. Go get it.