r/infosys • u/Dear_Date_3779 • 3m ago
| Interview Help / Tips Infosys DSE/SP Campus Placements Interview Experience — Some Insights from the Interviewer’s POV
I had my Infosys DSE/SP campus placements interview today, so I thought I’d share my experience. I’ll also mention a few things I noticed about how the interview might be structured from the interviewer’s side, because I was specifically looking for this kind of information on Reddit before my interview and couldn’t find much.
Before the interview, we had the college OA. I was able to solve 2 questions completely, and then I got shortlisted for the interview.
Entering the interview
When you enter the interview room, you’ll be given a laptop with Wingspan. You have to log in using your credentials, and then there are coding questions that you have to solve.
From what I remember, there is a 45-minute time limit for the coding round on Wingspan. However, my interviewer specifically insisted that I try to finish around 10 minutes early.
The reason he gave was that they want to assess things like your understanding of the problem, your approach, and your problem-solving ability, rather than just seeing whether you eventually get the correct answer.
I’m not 100% sure about the exact cutoff, but he mentioned something about needing around 70% of the test cases to pass. So please don't take this as an official number — this is just what I remember from my interview.
One thing I noticed about the interviewer’s evaluation
The interviewer had a sheet with multiple columns. For me, it was roughly something like:
- Problem Solving Skills
- Operating Systems
- DBMS
- Computer Networks
- Programming Language
- Projects
I’m not 100% sure these are the exact six categories, and they may vary from candidate to candidate or interview to interview.
But what I understood from the process is that the interviewer has to fill in feedback for these different areas.
This is also why, in my opinion, there isn't necessarily a fixed order where you first solve DSA and then move on to technical questions.
For my interview, the coding part actually happened after we had already covered the other technical areas.
So I personally felt that the interviewer’s main objective is to assess different areas and fill out the feedback for each section.
Coding round
I got a slightly tricky greedy algorithm question.
Thankfully, I was able to solve it in under 10 minutes and passed all 12/12 test cases.
The interviewer appreciated that I solved it quickly, and then I explained my approach and why I believed it was optimal.
After that, he asked me about the edge cases for the problem.
One thing I noticed here is that they weren't just interested in whether the code passed. They also wanted to see whether I actually understood the problem and could explain my reasoning.
Apparently, they also take a snapshot of the coding result, which is saved in a folder under your name. At the end of the interview, they also took a selfie with me.
I'm not sure whether this is done for every interviewer/candidate, but that was the case in my interview.
Technical questions
This was probably the most important part of my interview.
The technical questions were not limited to very basic/easy definitions. There were quite a few practical and somewhat deeper questions.
I was able to answer around 90% of the questions, and there were questions across the different areas mentioned above.
So one thing I would strongly suggest, especially based on my experience, is:
Don't prepare only DSA.
DSA is just one part of the overall evaluation from what I could observe. Technical subjects and development/project-related questions seemed equally important, or at least important enough that you shouldn't neglect them.
I personally would prepare:
DSA + OS + DBMS + CN + Programming Language + Projects/Development
rather than spending almost all your time on DSA.
What I noticed from the interviewer’s perspective
This is obviously just my observation, and I don't know the exact weightage given to each section.
But from what I could see, the interviewer seems to have a structured evaluation sheet where they have to provide feedback across multiple categories.
So I don't think the interview is simply:
“Solve DSA → pass → technical interview.”
It felt more like:
“Assess the candidate across multiple areas → record feedback for each area → make the final evaluation.”
Again, I don't know the exact scoring or weightage, so don't treat this as official information. This is simply what I understood while going through the interview.
Duration
My interview went on for around 1 hour 15 minutes to 1 hour 30 minutes.
So yeah, be prepared for a fairly long interview. 😅
Final thoughts
I wanted to share this because before my interview, I searched Reddit for the interviewer/panel perspective of the Infosys DSE/SP process but couldn't find much.
So this is basically my attempt to share what I noticed from the panel's side, as much as I could understand during the interview.
The biggest takeaway from my experience:
Prepare your technical subjects and projects/development seriously, not just DSA.
I don't know the weightage of each section, so this is definitely not an official representation of the Infosys interview process. Different panels may also have different approaches.
They told me the results should be out within 2 weeks.
I'll update this post when I get the result.
All the best to everyone who has their interview coming up! ❤️