Skip to content

IT services

Coforge

BFSI, insurance and travel flavoured automation and strategy.

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

  • Playwright or Selenium
  • API testing
  • BDD
  • Domain testing
  • Test architecture
  1. Question 1 · Domain · Medium

    Test a quote-and-buy flow for an insurance product with several riders.

    Answer guide

    Premium rules per age and cover, rider combinations, eligibility, tax, rounding, quote expiry, payment failure, duplicate policy, and a calculation oracle independent of the UI.

  2. Question 2 · BDD · Medium

    When does BDD help and when does it become overhead?

    Answer guide

    Helps when product, dev and QA write examples together. Overhead when scenarios are just UI scripts in Gherkin. Keep steps declarative and few.

  3. Question 3 · Architecture · Hard

    Design an automation architecture for a web app, a mobile app, and a set of APIs owned by one team.

    Answer guide

    Shared test data and API layer, UI tests for few journeys, API tests for rules, reusable page and screen objects, one report, one pipeline, contract tests for the APIs.

  4. Question 4 · API testing · Medium

    How do you test a booking API that must not double-book a seat?

    Answer guide

    Concurrent requests for one seat, idempotency keys, expiry of held seats, retries after timeout, and checking the final state in the database.

  5. Question 5 · Playwright · Medium

    How do you speed up a Playwright suite that logs in before every test?

    Answer guide

    Log in once through the API or UI, save storage state, reuse per worker or project, and keep one test that covers the login itself.

  6. Question 6 · Banking · Hard

    A nightly batch posts interest. How do you test it without waiting a night?

    Answer guide

    Trigger the job on demand in a test environment, control the clock, seed accounts with known balances, compare to an independent calculation, and test reruns and failure mid-batch.