Capgemini AWS/DevOps Engineer interview questions

The interview process was well-structured and smooth. It began with an initial HR screening to understand my experience, skills, and alignment with the role. This was followed by two technical rounds. The first technical round focused on assessing my core technical skills, hands-on experience, and problem-solving abilities. The second technical round went deeper into scenario-based questions, real-time challenges, and project-level understanding to evaluate my practical expertise and approach to complex situations. After the technical discussions, the final HR round covered role clarity, compensation details, and the next steps. The overall process was professional, transparent, and well-coordinated, with timely communication at every stage.

I applied directly through the portal for a position, and a recruiter reached out to me shortly after. She asked for some basic details and scheduled the L1 round. A few days later, I was informed that I had cleared L1, and there wouldn’t be a client round—just an L2 round with the same Capgemini interview panel. After completing the L2 round, I waited for 2–3 weeks without any updates. I sent follow-up emails and called the recruiter multiple times, but there was no response. When I finally got through to her, she told me the position had gone on hold and that she was trying to map me to another role. I’m actively looking for a job change and had waited several weeks expecting feedback. In the end, I feel like I wasted 3–4 weeks on this process. It was a disappointing experience. At the very least, they should have informed me right after the interview if the role was on hold, so I wouldn’t lose valuable time. If you're actively job hunting, I'd suggest confirming upfront whether the role is genuinely open and whether the company is actually hiring. It could save you a lot of time and frustration.