Infosys Software Engineer Interview: Questions & Prep (2026)

Infosys is one of India's largest IT services companies, and cracking a Software Engineer role here opens doors to large-scale enterprise projects, global client exposure, and a structured career path. As of July 2026, knok's job radar shows 62 open Software Engineer roles at Infosys, part of a nationwide pool of 5,395 such openings. Bangalore has the highest concentration of Software Engineer listings across the country.

The selection process typically covers three to four stages: an online assessment (candidates report sections on aptitude, verbal ability, and coding), one or two technical interviews focused on core CS fundamentals and project experience, and a final HR discussion. The exact rounds and their order can vary by batch and role level. Always confirm the current process with your recruiter or HR contact once you receive an invite.

These are questions that Infosys candidates commonly report across technical and HR rounds. Prepare a confident, specific answer for each one.

1. Explain the four pillars of object-oriented programming with examples from a project you built.
2. What is the difference between a process and a thread? When would you use each?
3. How does memory management or garbage collection work in your primary programming language?
4. Explain database normalization. Walk through the difference between 2NF and 3NF with an example.
5. Write code to reverse a linked list (candidates report this appears frequently in coding rounds).
6. What is a REST API? How does it differ from SOAP, and why do modern applications prefer REST?
7. Describe a project end-to-end: requirements, design decisions, implementation, and what you would do differently.
8. What are the SOLID principles? Give a real or hypothetical example for any two.
9. Explain different types of SQL joins with a practical example.
10. How do you approach debugging a production issue you cannot reproduce locally?
11. Tell me about a time you disagreed with a technical decision made by your team or lead. What did you do?
12. Where do you see your career in three years, and how does a role at Infosys fit into that path?

Each answer below follows the STAR format (Situation, Task, Action, Result). Adapt these to your own experience.

Q: Describe a challenging bug you fixed and how you approached it.

*Situation:* During a college final-year project, our web application's login module was silently failing for a subset of users after a recent code merge.

*Task:* I was the team member responsible for authentication, so tracking down and fixing the issue fell to me before our project demo.

*Action:* I added detailed logging to the authentication flow, compared the working and failing code paths side by side, and identified that a recent change had introduced a case-sensitivity mismatch in the username comparison. I wrote a targeted fix, added a unit test to cover the edge case, and had a teammate review it before merging.

*Result:* The bug was resolved before the demo, all reviewers could log in successfully, and the test I added later caught a similar issue introduced by another team member.

---

Q: Tell me about a time you had to learn a new technology quickly.

*Situation:* Midway through an internship project, the team decided to switch from a basic JDBC setup to Spring Boot to simplify dependency management.

*Task:* I had never used Spring Boot before and needed to get productive within a week so the project timeline was not affected.

*Action:* I worked through the official Spring Boot documentation, built a small standalone module with REST endpoints to practice, and paired with a senior intern for an afternoon to clarify concepts I found confusing. I kept a personal note of each error I hit and how I resolved it.

*Result:* By the end of the week I had migrated my assigned module to Spring Boot, and the team lead noted that the code was cleaner than the original JDBC version.

---

Q: Give an example of resolving a conflict within your project team.

*Situation:* In a group academic project, two team members had conflicting opinions on whether to use a relational database or a document store for the backend.

*Task:* As the person coordinating the backend design, I needed to help the team reach a decision without losing time to prolonged debate.

*Action:* I asked both sides to write a short list of trade-offs for their preferred approach, then organised a focused discussion where we mapped those trade-offs against our actual project requirements. It became clear that a relational database was the better fit for our structured data needs, and the team member who had proposed the document store agreed once we looked at the requirements together.

*Result:* We made the decision in one session and delivered the backend module on schedule.

STAR (Situation, Task, Action, Result) is the format Infosys interviewers expect for behavioural and situational questions. Keep each component tight: two to three sentences for Situation and Task combined, the bulk of your answer on Action, and a concrete Result.

For technical questions, use a think-out-loud approach: restate the problem in your own words, state any assumptions, then walk through your solution step by step. Interviewers at large IT firms typically value clear reasoning as much as a correct final answer.

For system design or open-ended questions (more common for experienced hires), structure your answer as: clarify scope, state constraints, propose a high-level design, then drill into the component the interviewer asks about. Do not jump straight to a solution before understanding what the interviewer is actually testing.

For HR questions such as 'Why Infosys?' or 'Where do you see yourself in three years?', prepare a two-part answer: one part anchored in something specific about Infosys (its scale, its client industries, its training programmes), and one part about your own career direction. Generic answers like 'I want to grow with the company' rarely stand out.

Infosys interviews for both technical competence and cultural alignment with its stated values: client focus, integrity, and continuous learning. Candidates report that interviewers pay close attention to three things.

CS fundamentals over framework knowledge. Infosys works across many technology stacks, so interviewers typically care more about whether you understand data structures, algorithms, and object-oriented design than whether you know a particular framework in depth.

Communication under pressure. You will often be asked to explain your thinking aloud while solving a problem. Candidates who go silent and then produce an answer tend to score lower than those who talk through their reasoning, even when the final answer is the same.

Genuine examples from your own work. Vague answers like 'I am a team player' without a specific story behind them are a red flag. Every behavioural answer should reference something you personally did, not what 'the team' did.

A focused preparation schedule that candidates report works well for Infosys interviews:

Week 1: Coding and data structures. Practice arrays, strings, linked lists, stacks, queues, and basic sorting algorithms. Write code by hand or in a plain text editor to simulate the actual test environment.

Week 2: Core CS subjects. Revise OOP concepts with your own code examples, SQL joins and normalization up to 3NF, and the basics of operating systems (process vs. thread, memory management). These topics appear in virtually every Infosys technical round.

Week 3: Project deep-dive. Pick one or two projects from your resume and prepare to explain every design decision. Know the technologies used, the problems faced, and what you would change if you rebuilt it today.

Week 4: Mock interviews and HR prep. Do at least three timed mock interviews with a friend or on an online platform. Prepare answers for the twelve questions listed in this guide. Research Infosys: its major service lines, recent publicly reported news, and the business unit you are applying to.

For salary context, Software Engineer roles in India currently show entry-level (0-2 years) at 6-12 LPA, mid-level (3-5 years) at 15-25 LPA, and senior-level (6-9 years) at 28-45 LPA, based on knok's job radar data.

Skipping the problem statement. Many candidates jump into coding without restating the problem or clarifying edge cases. Infosys technical interviewers commonly note this as a red flag.

Memorising answers word for word. Interviewers will probe with follow-up questions. If you have memorised a STAR answer rather than understood the underlying experience, the follow-up will expose it quickly.

Being vague about your own project. If you list a project on your resume, expect questions about every technology choice you made. 'The team decided' is not an acceptable answer for a decision in a project you owned.

Ignoring the HR round. Many candidates prepare thoroughly for technical rounds but treat the HR round as a formality. Questions about work preferences, relocation, and career goals are assessed and can influence the final outcome.

Not asking any questions. At the end of each round you are almost always invited to ask something. Having no questions reads as low interest. Prepare two to three specific questions about the team, the project, or the technology stack.

If you are actively applying, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf, including for Infosys openings.