September 28, 2026
INFOSYS LATEST OFF CAMPUS INTERVIEW QUESTION
Infosys Interview Experiences
Explore candidate-reported Infosys interview experiences covering DSA, SQL, Core CS, projects, APIs, AWS, machine learning, programming fundamentals and resume-based discussions.
Share Your Interview Experience
Recently interviewed at Infosys? Share your journey and help another candidate prepare with a more realistic picture of the process.
Submit Your Interview Experience
You can submit a selected, rejected or ongoing interview experience. Please avoid confidential company information, private interviewer information or proprietary assessment material.
Candidate Interview Experiences
Read the reported journey first, then use the preparation analysis to identify what you should revise.
The candidate described an initial conversation with the interviewer before the discussion moved toward WingSpan and coding. Two coding problems were presented, with the candidate being asked to focus on completing one problem and explaining the approach.
The reported problem involved children's greed factors and cookie sizes. A child could be satisfied when the cookie was large enough and the cookie and greed factor followed the specified parity rule. Each child could receive at most one cookie.
The reported approach was to sort both arrays and scan the cookies, ignoring cookies that were too small or did not satisfy the parity condition. The candidate explained why assigning the smallest valid cookie can preserve larger cookies for later children.
Resume & Machine Learning Discussion
- ACID properties
- ROC-AUC
- Accuracy vs ROC-AUC
- Production performance problems despite high local accuracy
- Vanishing-gradient problem
- Bagging vs boosting
- Binary search and complexity
- Software architecture/design patterns
Prepare DSA together with SQL and core CS. If your resume contains ML or cloud projects, expect the discussion to move beyond definitions into practical implementation and production-related questions.
The candidate reported starting with an introduction followed by a discussion around projects, including what the project does, its technology stack and implementation details.
Two tables, Customers and Orders, were used to identify customers who had registered but had never placed an order.
The candidate reported being asked to perform a step-by-step dry run of Quick Sort and explain partitioning and complexity.
WingSpan Coding Discussion
The reported experience included pairing and strict-element style problems. The candidate was expected to explain the reasoning, constraints and complexity rather than only producing an answer.
Core CS Questions
- Operating System
- TCP/IP model
- DNS and its purpose
- Accessing a website using an IP address
- OOP and its four pillars
- Dependency Injection
- Process vs thread
- Deadlock
Project Discussion
- What does your project do?
- What problem does it solve?
- Technology stack
- RAG implementation
- Overall architecture
- Technology selection
- Exception and API failure handling
This experience is a good reminder that project discussion can connect directly to CS fundamentals. Prepare your project architecture, database design and API flow instead of memorizing only a project description.
The candidate reported that the interview began directly with a WingSpan coding problem and later moved toward project, SQL, backend/API and AWS discussions.
The reported problem allowed adding an integer x to one array element and required finding the maximum adjacent-element sum after the modification.
SQL • 10th Highest Salary
The reported discussion involved joining employee data and identifying the 10th-highest salary using a ranking-based approach.
Topics included FastAPI, REST APIs, GraphQL, request validation, HTTP errors and choosing an API technology for a project.
AWS
- Amazon EC2
- AWS Lambda
- When Lambda can be preferred over a continuously running server
- API and database communication in AWS
Candidates with backend or cloud projects should be prepared to explain not only what a technology is, but why it was selected, how it fits into the architecture and how failures are handled.
The candidate reported beginning with an introduction before moving into DSA, SQL and project-related questions.
The reported problem involved finding the smallest contiguous subarray whose sum reaches at least a target value.
The reported reasoning relied on the array containing positive integers, allowing the window to expand and contract predictably.
Follow-up Questions
- Why does the approach fail with negative numbers?
- Sliding window vs two pointers
- Can prefix sums solve the problem?
- What changes for a circular array?
SQL • Salary Above Department Average
Project Discussion
- Explain your architecture.
- What was your contribution?
- Which APIs did you use?
- How did you handle errors?
- How did you test the application?
- How did you design the database?
- What happens when the API server is unavailable?
For DSA, focus on explaining why the selected technique works. For projects, prepare the complete request-to-database flow, error handling and the decisions behind your architecture.
The candidate described a technical discussion covering DSA, database concepts, dynamic programming and project implementation.
The reported problem asked for the element that occurs once when every other element occurs twice.
Bit Manipulation Follow-ups
- Checking whether a number is even using bits
- Checking whether the k-th bit is set
- Left shift vs right shift
- Using XOR to swap values conceptually
Dynamic Programming
The reported discussion included a standard DP problem where the candidate was expected to explain the state, recurrence, base cases, calculation order and complexity.
SQL & DBMS
- Primary key vs foreign key
- Normalization
- Views
- ACID properties
- Indexes
- When indexes improve performance
Project Questions
- How did you design the project?
- How does data flow through the system?
- Why did you select these technologies?
- What was the most difficult implementation problem?
- How would you scale the project?
Don't prepare DSA as isolated coding questions. Practice explaining the intuition, state transitions, edge cases and complexity while also revising SQL and DBMS fundamentals.
The candidate reported an interview beginning with an introduction and project discussion before moving into DSA, Core CS and SQL.
The reported problem involved selecting the maximum number of non-overlapping intervals.
Core CS Questions
- Process vs thread
- Deadlock
- Four necessary deadlock conditions
- Inheritance
- Polymorphism
- Abstraction
- Encapsulation
- Virtual memory
SQL
A useful follow-up is understanding the difference between WHERE and HAVING: WHERE filters rows before grouping, while HAVING filters groups after aggregation.
Project Discussion
- Database design
- API flow
- User authentication
- Invalid input handling
- Performance improvements
Freshers should revise OS and OOP alongside DSA. For SQL, practice GROUP BY, HAVING, joins and self-join questions instead of preparing only basic SELECT queries.
The candidate reported that the interview began with an introduction and discussion around projects listed on the resume. The conversation then moved into coding, SQL and implementation concepts.
The reported discussion involved a DP problem where the candidate first considered a recursive approach and then explained how to convert the solution into dynamic programming.
How to Explain DP in an Interview
- Define the state.
- Explain the transition.
- Identify the base cases.
- Explain calculation order.
- Discuss time and space complexity.
SQL • Employee Salary vs Manager
This is a self-join because employee and manager records are stored in the same table.
Java / Backend Questions
- Creating a REST API
- Exception handling
- Java file handling
- Alternatives for exception handling
- Checked vs unchecked exceptions
- GET, POST, PUT and DELETE
Database Follow-ups
- Views
- Primary keys
- Self-referencing foreign keys
- Foreign keys
- Manager-employee relationships
Final Project Discussion
- What does the project do?
- What problem does it solve?
- Complete architecture
- Frontend-to-backend communication
- Data storage
- API failure handling
- Scaling the project
Resume-based questions can become a large part of a technical interview. Be able to explain every major technology, database, API and architectural decision mentioned in your project.
What to Prepare for Infosys Interviews
Based on the experiences presented above, these are the major areas worth revising before an interview.
DSA
Greedy, arrays, sorting, sliding window, bit manipulation, binary search and dynamic programming.
SQL / DBMS
Joins, self joins, ranking, GROUP BY, HAVING, subqueries, indexes, normalization and ACID.
Core CS
OOP, OS, processes, threads, deadlock, TCP/IP, DNS and fundamental database concepts.
Projects
Architecture, APIs, database design, authentication, error handling, technology choices and scaling.
Interview experiences are candidate-reported accounts and should be treated as preparation resources rather than an official Infosys question list. Hiring processes, questions, eligibility and interview formats may change between candidates and hiring cycles.