Infosys Fresher Interview Questions

“In a hackathon I was placed in a team with three students from other colleges. We had one day. I suggested we each say what we were good at and what we did not want to do, which took ten minutes and saved hours. One teammate and I disagreed on whether to build the app or a web page first. Instead of arguing, we agreed to build the smallest web version and add the app only if time remained. I kept a shared list of who was doing what. We finished with your result. I learned to make roles clear early with new people.”

“During my internship, a senior engineer reviewed my first pull request and left many comments. The main one was that my functions did too many things and nobody could test them. I felt bad for an evening. The next day I asked him for ten minutes and he showed me how he would split one of them. I rewrote the whole change with small functions and wrote tests for each. He approved it and later asked me to review a junior's code the same way. The result was your result. Now I read my own code as a reviewer before I send it.”

“First I would find out the real format from the client, such as fixed length, letters and digits only, and whether the last character is a check character. Before validating, I would trim spaces and convert to upper case, because people type serial numbers from a label in many ways. Then I check length, allowed characters and the check character, in that order, so the message tells the person exactly what is wrong. I would test with a correct number, one that is too short, one with a letter O instead of zero, one with spaces around it, and an empty string.”

“For finding one product by its exact code, I would use a hash map, because it gives the answer in roughly constant time no matter how many products there are. A hash map cannot answer a range question well, since it has no order. For products between two prices, I would keep products in a structure sorted by price, such as a balanced tree, and walk from the lower bound to the upper bound. That costs the log of the number of products to find the start, then the number of results. In a real store these become database indexes, one on code and one on price.”

“I would create a read endpoint for service centres that takes a latitude and longitude as query parameters, plus an optional limit. It is a read, so it uses the get method and can be cached for a short time. The response is a list of centres with name, address, distance, opening hours and a link to each centre's details. If the location is missing or malformed, it returns a bad request status with a message naming the problem. No centres nearby is not an error, so it returns an empty list. A failure inside the service returns a server error status without exposing internal details.”

“I would start with a normal cart and a normal discount and check the exact total by hand. Then the edges: an empty cart should give zero, a discount of zero should change nothing, and a discount bigger than the total should never make the total negative. I would test a cart with several units of the same item, and totals that end in fractions, to see that rounding is done once at the end and in the way the client expects. Negative prices or quantities should raise a clear error. Each test has one purpose and a name that says what it checks.”

“I would not just rerun the pipeline and hope. I would read the log to find the first real failure, not the last message. Then I compare my machine with the pipeline: language version, dependency versions, environment variables, and whether the tests run in a different order or in a different time zone. A common cause is a test that depends on a file or a database left behind by another test. I would try to run the tests the way the pipeline does, from a clean folder. When I find the cause, I fix it properly and write a short note in the ticket so the next person knows.”

“I want my first years to be about learning how software is built and improved when real customers use it every day. Infosys works on that kind of platform for client companies, such as online stores, telecom apps and dealer portals, and I would see how a change goes from an idea to something a customer touches. I know it means working in teams with client engineers, following their standards and learning whatever tools the project uses. I like that variety. In a few years I want to be an engineer a squad relies on for careful, tested work.”