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 process felt pretty domain-driven and got tougher as it went on. My first round was a technical screen over Zoom with an interviewer who focused on the skills I had listed on my CV, especially Python and SQL. It wasn’t a deep algorithm round so much as a series of code examples and practical checks to see whether I could actually work through the basics I claimed. That round was straightforward, but they did probe a bit into how I’d use those skills in a real project context.
After that, the interview became more varied. I had a coding round, then an in-person round, and finally a managerial round. The coding questions were described as tricky rather than hard in a textbook sense, and the whole thing took about 30 minutes for the technical portion I went through. They also asked a mix of questions tied to the role and my background: Java fundamentals, including the difference between Java 8 and Java 17, plus questions around my internship and projects. In the later rounds, the focus widened into system design, backend concepts, cloud and AWS, DevOps, testing, and even ML/NLP depending on the profile. One thing that stood out was how much they cared about whether you had cloud certifications, especially AWS, and they asked directly why I hadn’t done any yet.
Overall, it was a fair interview, but definitely not uniform across candidates because they tailor it to the domain and the resume. The interviewer I had was knowledgeable and kept things aligned with my profile, which made it feel less random. I didn’t get an offer in the end, but the process itself was clear: expect a coding screen, then a mix of technical depth and project discussion, and be ready for design and cloud-related follow-ups if your background points that way.
Prep tip from this candidate
Be ready to defend the exact skills on your resume with live Python/SQL examples, and don’t ignore cloud topics like AWS certifications, microservices design patterns, API management, and Java memory usage. They also seem to care a lot about project and internship discussion, so prepare to explain those clearly and technically.
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 | |
| 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 | |
| Swap Variables | |
| The Longest Journey | |
| Check Matching Parentheses | |
| String Palindromes | |
| Cloud-Agnostic Deployments | |
| Safe Deployments | |
| Text Editor With OOP | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Relational Migration | |
| Your Strengths and Weaknesses | |
| ReLu vs Tanh | |
| Student Tests | |
| Empty Neighborhoods | |
| Prime to N | |
| Subscription Overlap | |
| Employee Salaries | |
| Size of Joins |
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.