Taro Logo

AWS/DevOps Engineer Interview Experience - United States

June 27, 2025
Negative ExperienceNo Offer

Process

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. 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 two to three 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 three to four 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.

Questions

They covered topics from my professional experience and included Python coding questions.

Interview Statistics

The following metrics were computed from 1 interview experience for the Capgemini AWS/DevOps Engineer role in United States.

Success Rate

0%
Pass Rate

Capgemini's interview process for their AWS/DevOps Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Capgemini's AWS/DevOps Engineer interview process in United States.