Editorial review: 9 October 2026
Prepare truthful project answers for an Infosys application
An interview preparation page should help you explain work you actually did. It should not promise the questions a company will ask, invent a universal number of rounds or turn a practice answer into a selection guarantee. The questions below are original preparation exercises, not questions reported by Infosys recruiters. Their usefulness is in the evidence and limitations of each answer.
The official Infosys graduate careers page provides a route to graduate opportunities, including its India careers navigation. It does not establish that a particular vacancy is currently open or that every role uses the same assessment. Follow the actual position's instructions and prepare for its responsibilities. A technical exercise may suit one role while another needs different evidence.
Check the invitation before preparing for its format
The Infosys recruitment fraud alert says the company does not charge hiring fees or security deposits. It describes at least one virtual or in-person interview and says it does not conduct interviews on instant messaging applications. These are specific verification points, not a complete interview-round timetable.
The alert also warns that a displayed sender address can be spoofed. Seeing a company-looking address alone is therefore insufficient verification. Navigate through the official careers route and compare the invitation with your actual application. Do not pay a claimed recruitment deposit or supply documents through an unverified link merely because the message uses a familiar logo.
Once an invitation is verified, record what it actually specifies: role, assessment medium, time, any permitted resources and the work you are asked to discuss. If it does not describe the question types, leave that unknown. Do not replace the missing information with a coaching site's claim that all candidates face identical rounds.
The fictional project fact sheet
The following candidate and project are invented for this guide. Rhea is an ongoing computer-science student. For an independent practice assignment, she built a small local script that checks six invented records for an empty item code. She used no client information and deployed no production service.
The assignment's stated rule is narrow: flag a record when its item-code field is empty. It does not say the code is valid, unique or authorised merely because the field is populated. Rhea wrote the check and printed the flagged record identifiers. She then ran it against this supplied set:
| Record | Item-code field | Expected result under the stated rule |
|---|---|---|
| P1 | A10 | Not flagged |
| P2 | Empty | Flagged |
| P3 | B20 | Not flagged |
| P4 | A10 | Not flagged |
| P5 | Empty | Flagged |
| P6 | C30 | Not flagged |
The actual output in this fictional fact sheet is P2 and P5. P4 repeats P1's code, but duplicate detection is outside the supplied empty-field rule. There is no supervisor approval, client benefit, automated correction or measured time saving in these facts.
Before answering a practice question, keep this boundary visible. You may explain the implemented rule and the six checked records. You cannot upgrade an independent assignment into employment or imply that two flags prove the quality of every possible input.
Question 1: explain your project and your contribution
Original practice question: “What did your project do, and what part did you own?”
A complete bounded answer is:
For an independent student practice assignment, I wrote a local check for empty item-code fields in invented records. I implemented the empty-field condition and printed the identifiers it flagged. In the six-record set I checked, the output was P2 and P5, which matched the supplied expected results. I did not build a production inventory system or verify whether populated codes were valid.
The answer gives a context, a task, owned work and a checked result. It does not need a fabricated percentage improvement to be concrete. Saying “I improved data quality by 100%” would overstate a six-record check and introduce an outcome not measured here.
Follow-up: “Why wasn't P4 flagged?” A supported answer is: “P4 had a populated code. The supplied rule concerned empty fields only, so it was not flagged. Detecting repeated codes would be a separate requirement and would need its own implementation and checks.”
This distinction matters because a good explanation accounts for what the script intentionally checks as well as what it leaves outside its scope. An interviewer may request a broader task; that request would create new work, not retroactively change what this assignment already did.
Question 2: investigate an unexpected output
Original practice question: “Suppose a new supplied record has three spaces in its code field and is not flagged. What would you do?”
This is a separate hypothetical input, not an observed failure in Rhea's six-record run. The original rule does not define whether whitespace counts as empty. The answer should clarify that ambiguity before presenting a proposed change as a fix.
I would first confirm the expected treatment of whitespace. The original exercise specified empty fields but did not define a field containing only spaces. If the requirement is amended so that a spaces-only value counts as empty, I would update the condition accordingly and check that new case alongside the six original records. I would not report the amended behaviour as implemented or tested until I had actually done both.
If you know the relevant programming language, you can explain how you would represent and test that condition. An honest answer does not require naming a framework you did not use. If the assessment permits code, write and run it within the stated rules; if it does not, describe the proposed logic without claiming execution.
Follow-up: “Does trimming every value solve all input problems?” No such result follows. Trimming may address the newly defined whitespace case. It does not automatically establish handling of missing fields, invalid code formats, duplicates or unauthorised records. Those are separate requirements.
Question 3: discuss a disagreement about scope
For another explicitly fictional scenario, a practice partner suggests labelling P4 as an error because its code repeats. Rhea has only the empty-field rule and the six-record expected table. The partner is not described as the assignment's requirements owner.
Original practice question: “How would you respond to that suggestion?”
I would explain that P4 is not an empty-field failure under our supplied rule. I would record duplicate detection as a proposed extension and ask whoever owns the assignment requirements whether it should be added. Until that is confirmed and implemented, I would keep the original output separate from the proposal. I can acknowledge the suggestion without claiming we changed the assignment or completed a duplicate check.
This answer preserves the actual rule while allowing a reasonable request for clarification. It does not assume the partner is wrong about all future needs. It also avoids inventing agreement, ownership or a successful team outcome that the scenario has not supplied.
Follow-up: “What would your handover say?” A suitable note is: “Empty-field check: six supplied records produced P2 and P5. Duplicate-code detection: proposed, outside the current requirement, not implemented or tested.” That note is useful because another person can distinguish a completed finite check from an unfinished idea.
Use your own evidence rather than memorising the example
Replace this fictional fact sheet with your actual project context, contribution, inputs and observations. Remove claims you cannot support. If you only planned a feature, say it was planned. If a teammate wrote a component, name your own contribution rather than taking credit for the whole application.
The fresher resume guide can help you keep the written version consistent with an interview explanation. The teamwork guide develops individual contribution and shared-result distinctions. Neither changes the employer's actual selection criteria.
Practise a brief initial answer, then answer follow-ups from the facts. The goal is a clear account you can defend and correct, not a polished script that collapses under one question about what was really tested.
Frequently asked questions
Are these actual Infosys interview questions? No. They are original exercises for project explanation, debugging and collaboration, clearly separated from official recruitment guidance.
Does every Infosys role require this coding exercise? That is not established. Use the particular role and verified assessment instructions to choose relevant preparation.
How many interview rounds should I expect? This guide does not establish a universal count. The official fraud alert's minimum interview statement does not determine every position's complete process.
Can I use a student project if I have no job experience? You can describe your actual work accurately as student or independent practice. Do not call it client delivery, employment or production work unless those descriptions are true.