Companies / Infosys

Infosys practice pack

IT services. Strong basics, clear communication, and delivery discipline.

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 strategy basics
  • API testing
  • Java or Python for automation
  • Communication
  • Agile testing

Business areas used for scenarios

  • banking
  • insurance
  • retail
  • energy

6 questions

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

  1. 1

    What goes into a test plan and what do you leave out so it stays useful?

    easyStrategy

    A strong answer covers

    Scope, risks, environments, entry and exit criteria, schedule, roles. Leave out detail that belongs in test cases. Mention that a plan nobody reads is a failed plan.

  2. 2

    How do you test a REST endpoint that creates an order? Go beyond the happy path.

    mediumAPI testing

    A strong answer covers

    Status codes, schema and field validation, auth and permissions, idempotency on retry, concurrency, large payloads, rate limit, error body shape, and checking the side effect in the database or downstream call.

    Likely follow-up: How do you test idempotency?

  3. 3

    You have 400 manual regression cases. Which do you automate first and why?

    mediumAutomation

    A strong answer covers

    Stable, high-value, repeatable flows with clear assertions. Skip volatile UI, one-off checks, and anything where setup cost beats run count. Use a simple score of risk x frequency / effort.

  4. 4

    What does QA do in sprint planning, in the sprint, and in the retro?

    easyAgile

    A strong answer covers

    Planning: question acceptance criteria, estimate test effort. Sprint: test early, pair with devs, keep a running regression. Retro: raise escaped defects and fix the process, not the person.

  5. 5

    A developer says your bug is 'works as designed'. How do you handle it?

    mediumCommunication

    A strong answer covers

    Check the requirement first. If unclear, take it to the product owner with evidence. Keep it about the user impact, not who is right. Record the decision so it does not return.

  6. 6

    Write a function that checks whether two strings are anagrams and say what test cases you would run.

    mediumCoding

    A strong answer covers

    Normalise case and spaces, compare sorted characters or a frequency map. Tests: empty, single char, different lengths, repeated letters, unicode, whitespace.

    Likely follow-up: Time complexity of both approaches?

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