IT services
Capgemini
Testing practices, automation basics, and scenario answers.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
What they tend to probe
- Test techniques
- Automation basics
- Performance basics
- CI/CD
- Scenario thinking
Question 1 · Techniques · Easy
Explain state transition testing with a login lockout example.
Answer guide
States: active, failed once, failed twice, locked. Events: wrong or right password, time passing, admin unlock. Cover valid and invalid transitions, not just the path to lockout.
Question 2 · CI/CD · Medium
Where should automated tests run in a pipeline and what blocks a release?
Answer guide
Unit and lint on commit, API and smoke on merge, wider regression nightly or pre-release. Block on smoke and critical-path failures; report the rest. Keep the gate fast or people bypass it.
Question 3 · Performance · Medium
A page loads in 8 seconds for some users only. How do you investigate?
Answer guide
Reproduce by region, device and network, compare waterfall and API timings, check payload size, caching and third-party scripts, then isolate front end vs back end before blaming either.
Question 4 · Automation · Medium
What makes a locator strategy robust, and what would you ask developers for?
Answer guide
Stable test ids, role and label based locators, avoid index and deep XPath. Ask for data-testid on key controls and agree it in the definition of done.
Question 5 · Scenario · Hard
You inherit an automation suite with 30% flaky tests. What is your first month?
Answer guide
Quarantine flaky tests, classify causes (timing, data, environment, real bugs), fix the top causes, add a flake dashboard, and set a rule that new tests must pass 20 consecutive runs.
Question 6 · Process · Easy
What is the difference between verification and validation, with a project example?
Answer guide
Verification checks we build it right against the spec; validation checks it is the right thing for users. A feature can match the spec and still fail validation.