The Capgemini QA Interview Guide
Capgemini places a heavy emphasis on Agile testing practices and Behavior-Driven Development (BDD). If you are applying for an automation role, you must be comfortable with Cucumber alongside Java/Selenium.
The Interview Stages
Capgemini looks for testers who understand the entire Software Testing Life Cycle (STLC) within an Agile framework.
Round 1: Core Automation (Java/Selenium/BDD)
- BDD Focus: You must know the syntax of Gherkin (Given/When/Then).
- Question: "What is the difference between a Feature file, a Step Definition file, and a Test Runner class in Cucumber?"
- Selenium Question: "How do you handle multiple windows or iframes in Selenium?"
Round 2: SQL and Backend Validation
Enterprise applications require backend validation.
- SQL Focus: You will be asked to write
JOINqueries or useGROUP BY. - Question: "After your Selenium script submits a user registration form, how do you verify via SQL that the data was actually saved in the database?"
Round 3: Agile and CI/CD Scenarios
Capgemini wants testers who can integrate their work.
- Agile: "In a 2-week sprint, when exactly do you start writing your automation scripts?" (Discuss In-Sprint automation and writing scripts based on Acceptance Criteria before the dev finishes coding).
- CI/CD: "How do you trigger your Selenium test suite automatically after a developer commits code?" (Discuss Jenkins, Git, and setting up a build pipeline).
Round 4: Managerial Fit
- "Describe a situation where a critical bug slipped into production. How did you handle the post-mortem?"
- They will also check your willingness to learn new tools (like moving from Selenium to Tosca or Playwright) if the client demands it.
Final Advice: Have a clear, rehearsed 2-minute explanation of your daily routine in an Agile sprint. Mentioning daily standups, sprint planning, executing regression suites via Jenkins, and raising bugs in Jira shows you are a mature, plug-and-play candidate.
