Infosys On-Campus Interview Experience
I recently went through an on-campus interview process with Infosys. The role wasn’t explicitly mentioned during the shortlist, and the entire interview ended up being quite thorough, lasting about 1 hr to 1 hr 15 minutes.
Sharing my complete experience below. I’d love to hear your thoughts on what role this might be for and how my chances look!
1. Online Assessment (OA)
- Performance: Solved 1.25 out of 4 questions.
- I didn't get shortlisted initially, but got called up later in an additional shortlist. No specific job role was mentioned in the mail.
2. Interview Live Coding & Pen Paper Round
Right at the start of the interview, the interviewer had me log into the Infosys Wingspan portal:
- Live Coding: There were 2 coding questions given, and I was asked to solve any one. I solved the first one completely in about 15 minutes and explained my approach along with time and space complexity.
- Rotten Oranges (Discussion): He gave me a pen and paper and handed me the "Rotten Oranges" problem. I explained my Multi-Source BFS approach, and he was satisfied without needing me to write the code.
- C++ Stack Implementation: Asked me to implement a stack class using an array in C++. I wrote the class (though I initially forgot to write the constructor) and demonstrated initializing an object and pushing elements.
- JavaScript OOP (Inheritance): Asked me to explain inheritance with an example and write the code for it in JavaScript, which I did successfully.
- Trees: Explained what a tree is and wrote the code for Inorder Traversal.
- Graphs & Cycle Detection: When asked to explain a data structure in detail, I chose graphs. He asked me to write code to detect a cycle. I directly wrote a function taking an adjacency list. He had some doubts about how the adjacency list worked, but I cleared them up by explaining how it's built from an edge array (though he seemed a bit unconvinced about something minor, the core approach was correct).
- Heap: He asked me to implement a heap. I was honest and said I wasn't entirely sure of the exact implementation off the top of my head, but explained the core functionality, how it maps to a tree structure, and the time complexities for operations.
3. Core CS Subjects (OS & DBMS)
- Operating Systems: Covered a wide range of topics processes, threads, context switching, paging, fragmentation, and virtual memory. My initial explanation of virtual memory was a bit shaky, so he corrected me, but I answered the rest.
- DBMS & SQL:
- Difference between SQL and NoSQL.
- What type of DB MongoDB is, and why I used it across my projects instead of PostgreSQL (I was honest that I didn't have a rigid architectural reason, just used it for convenience).
- Wrote a query to find the 2nd highest salary for each department using
LIMITandOFFSET, and explained how those keywords work. - Asked about window functions (couldn't recollect this and admitted it).
- Scenario-based question on SQL Joins (picked the right join and explained why).
4. Projects, Tech Stack & AI Discussion
- MERN vs. AI Projects: He noticed all my projects were full-stack MERN builds and questioned why I hadn't built AI projects when so many students are doing them. I clarified that while I didn't train models from scratch, I have integrated LLMs and RAG chatbots into my web apps.
- There was a team project in my resume which had WebRTC , he asked me how signaling worked in WebRTCs and i mentioned i did not implement the WebRTC tech it was done by a teammate of mine
- AI/LLM Follow-ups: This led to a few technical questions on AI, including the definition of an LLM and hallucinations. I couldn't clearly answer a couple of question on AI, which he noted.
5. Conclusion & Feedback
- The interview wrapped up with him taking a photo of me and telling me I could leave.
- When I asked for feedback, he said I answered most questions well and that the overall interview was good.
PS: Used AI to frame the post better
Hopefully i get selected ,if so what role can i expect ?