Companies / Capgemini

Capgemini practice pack

IT services. 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.

Skills this role is usually tested on

  • Test techniques
  • Automation basics
  • Performance basics
  • CI/CD
  • Scenario thinking

Business areas used for scenarios

  • financial services
  • telecom
  • public sector
  • manufacturing

6 questions

Answer out loud first, then open the guide. Most people read the guide too early.

  1. 1

    Explain state transition testing with a login lockout example.

    easyTechniques

    A strong answer covers

    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.

  2. 2

    Where should automated tests run in a pipeline and what blocks a release?

    mediumCI/CD

    A strong answer covers

    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.

  3. 3

    A page loads in 8 seconds for some users only. How do you investigate?

    mediumPerformance

    A strong answer covers

    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.

  4. 4

    What makes a locator strategy robust, and what would you ask developers for?

    mediumAutomation

    A strong answer covers

    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.

  5. 5

    You inherit an automation suite with 30% flaky tests. What is your first month?

    hardScenario

    A strong answer covers

    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.

  6. 6

    What is the difference between verification and validation, with a project example?

    easyProcess

    A strong answer covers

    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.

Now say it to an interviewer

Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.

Start a mock interview Build a plan from a job description