Software Engineer
Anonymous
7 hrs ago
On-campus, 2024. It started casually — instead of the usual "tell me about yourself", the interviewer just asked how I was doing. That small shift set the tone: it felt less like an interrogation and more like a chat from the first minute.
I walked through what I'd built on the MERN stack, focusing on the real-world side rather than listing technologies — what problems it solved, and the difficulties I ran into. We then spent time on my internship and what I actually did day to day.
Rooted in Java and OOP — function overloading vs overriding came up, which I was expecting, so that part felt comfortable.
This caught me a little off guard. The classic hard work vs smart work question, which I had to back with an actual example rather than a definition, plus a team-based scenario testing how I'd navigate a tricky situation with colleagues. Nothing outrageous, but it made me think on my feet more than the technical questions did. The standard "why Capgemini" was in there too, and I'd prepared for it.
The moments where I didn't fully know an answer taught me the most — staying calm and simply admitting it landed a lot better than trying to bluff.
Selected.
Sign in to join the discussion.
Sign in to commentNo comments yet — be the first to respond.