Infosys Software Engineer interview typically runs 3 rounds: aptitude/assessment, technical interview, and HR. The process usually takes about 2 to 3 weeks and is straightforward, with strong emphasis on fundamentals and communication.
$66K
Avg. Base Comp
$142K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
We’ve seen a consistent pattern across candidate experiences at Infosys: the company is rarely looking for one dazzling specialty, and much more often for reliable fundamentals plus clear explanation. Multiple candidates reported being pressed on the basics of Java, SQL, OOP, DBMS, OS, and networking, even when the role sounded more modern or stack-specific. At the same time, the interviewers often anchored the conversation in the candidate’s own resume — projects, internships, certifications, and the exact technologies listed there — which means the bar is less about reciting theory and more about whether you can defend the choices you made.
A recurring theme is that Infosys likes to widen the lens once it sees a fit. Candidates who came in expecting only light screening were surprised by follow-ups on cloud, AWS, DevOps, testing, system design, and even domain-specific topics like airline workflows or Salesforce triggers. We also saw repeated emphasis on communication under pressure: interviewers asked candidates to compare programming to cooking, explain architecture in plain language, or justify why they chose a stack. That tells us the real signal here is not just correctness, but whether you can stay composed while moving across coding, fundamentals, and project discussion without losing clarity.
The non-obvious make-or-break factor is consistency. Several candidates described interviews that felt friendly and manageable, yet still ended in rejection because one area was weak or the resume discussion exposed gaps. Others got offers by sounding steady, practical, and well-prepared across a broad surface area. In our view, Infosys rewards candidates who can connect their experience to the role cleanly and who don’t treat “basic” questions as throwaways — because at Infosys, those basics are often the whole interview.
Synthetized from 20 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Infosys process.
The part that stood out most to me was how much the interview leaned on practical cloud knowledge rather than anything overly theoretical. I went through a coding assessment first with four questions, and after that there was a final one-to-one interview. In the assessment and the follow-up, I was asked a mix of Python, SQL, and cloud-related questions, plus a few basic coding tasks in Python and SQL. The cloud portion was not just definitions either; there were questions around cloud computing concepts and GenAI, so I had to be ready to explain how I would think about those topics in a real system or project context.
The process itself felt fairly structured: an initial round of about 30 minutes that was fairly approachable, followed by a scenario-based round, a managerial round, and then an HR round. The later rounds were less about writing code and more about how you troubleshoot and make decisions. K8s troubleshooting and Linux came up, which made the interview feel very platform-oriented. I would not call it extremely hard, but it did require being comfortable switching between coding, cloud concepts, and operational scenarios. I did not move forward in my process, so the outcome was disappointing, but the interviewers were professional and the process was clear enough. If you are preparing, I would focus on being able to write simple Python and SQL quickly, then spend time on Kubernetes troubleshooting, Linux basics, and explaining cloud and GenAI concepts in a practical way.
Prep tip from this candidate
Be ready for a short coding assessment with 4 questions, then practice scenario-based Kubernetes troubleshooting and Linux questions for the later rounds. Also review basic Python and SQL coding since those came up alongside cloud and GenAI concepts.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Infosys
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Find the Missing Number | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Normalize Grades | |
| Hurdles In Data Projects | |
| Ticket Agent Analysis | |
| Find Duplicate Numbers in a List | |
| Digitizing Student Test Scores | |
| Concurrent LLM Serving | |
| Swap Variables | |
| The Longest Journey | |
| Check Matching Parentheses | |
| String Palindromes | |
| Seller Type Modeling | |
| Cloud-Agnostic Deployments | |
| Pipeline Transformation Failures | |
| Safe Deployments | |
| Text Editor With OOP | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure | |
| Why Do You Want to Work With Us | |
| Relational Migration | |
| Your Strengths and Weaknesses | |
| ReLu vs Tanh | |
| Student Tests |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with an online aptitude and/or coding assessment. Depending on the hiring track, this can include aptitude questions, reasoning, and 2-3 coding problems ranging from easy to hard, often with DSA-heavy topics like arrays, trees, graphs, dynamic programming, and SQL-style problem solving.
If shortlisted, candidates move to one or more technical interviews, either virtual or in person. Interviewers usually focus on resume-based discussion, core fundamentals, and live coding, with questions in Java, Python, SQL, OOPs, DBMS, OS, networking, and project-specific technologies like React, Spring Boot, Angular, AWS, or Salesforce depending on the profile.
Some candidates report a managerial round after the technical interview, where the discussion broadens to system design, backend concepts, cloud/DevOps, testing, and how the candidate handled projects or internships. This round also checks communication, problem-solving approach, and whether the candidate can explain technical decisions clearly.
The final round is usually an HR discussion covering self-introduction, strengths and weaknesses, motivation for joining Infosys, teamwork, adaptability, relocation, and compensation expectations. In some cases, this round is brief and feels like a formality after technical clearance.