Companies / Mphasis

Mphasis practice pack

IT services. Banking and cloud-focused testing with solid automation basics.

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

  • Automation basics
  • SQL
  • API testing
  • Test case design
  • Cloud testing

Business areas used for scenarios

  • banking
  • insurance
  • cloud services

6 questions

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

  1. 1

    Design test cases for a loan eligibility calculator.

    mediumBanking

    A strong answer covers

    Income, age, credit score, existing loans and employment type as inputs. Boundary values at cut-offs, combinations in a decision table, rejection reasons shown, and rounding of the offered amount.

  2. 2

    Find accounts with more than one transaction on the same day for the same amount.

    mediumSQL

    A strong answer covers

    GROUP BY account, date, amount HAVING COUNT(*) > 1. Mention how to treat legitimate repeats and the time zone of the date.

  3. 3

    What changes when you test an app deployed on autoscaling cloud infrastructure?

    mediumCloud

    A strong answer covers

    Scale-out and scale-in behaviour, statelessness, session handling, config and secrets per environment, cost-aware load tests, and cleanup of test resources.

  4. 4

    How do you keep test data from breaking parallel runs?

    mediumAutomation

    A strong answer covers

    Each test creates and owns its data with unique ids, no shared mutable records, and cleanup through the API.

  5. 5

    What is the difference between PUT and PATCH, and how do you test each?

    easyAPI testing

    A strong answer covers

    PUT replaces the whole resource, PATCH changes part. Test missing fields, partial updates, idempotency, and that untouched fields stay unchanged.

  6. 6

    Explain how you would run a defect triage with developers and a product owner.

    mediumProcess

    A strong answer covers

    Short fixed meeting, sorted by severity, one owner and a target for each, decisions written down, and trends reviewed weekly.

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