Simverse
← All simulations

QA Engineer simulation

QA sign-off before the Diwali sale

Thela · Quick commerceFresher / 1–3 yrs 40 min

You're a QA Engineer at Thela, a quick-commerce app, on the day the Diwali sale build ships. Write test cases for the new coupon engine (CI plants realistic bugs and checks whether your cases catch them), file a bug you find in staging, hold your ground when a developer closes it, and give the release manager a sign-off you can defend.

💻 Simulations run best on a laptop or desktop.

Create an account to start

You can pause and come back. Time in the simulation only moves when you act.

Thela · QA Engineer IDay 1 · 09:00 AM

Your first message

Farhan QureshiQA Lead09:00 AM

Diwali build day

Morning! Big one today: the Diwali build ships at 6 PM. The new coupon engine (CHK-301) is the riskiest change. What's your test plan for today? Rules are attached.

Your objective

Ship the Diwali build without a coupon bug that costs money, and make every quality call with evidence.

Your day

What's scheduled. More will come up depending on what you do.

  1. 09:00 AMDiwali build day · Farhan Qureshi
  2. 09:15 AMCHK-301: Test cases for the coupon engine · Farhan Qureshi
  3. 11:30 AMYou found something in staging · Farhan Qureshi
  4. 03:00 PMGo / no-go for the 6 PM build? · Priya Iyer
  5. 05:00 PMWrap-up · Farhan Qureshi

Before you start

  • It's 9:00 AM. The Diwali sale build goes to the Play Store at 6:00 PM.
  • Your lead is Farhan. Priya runs the release. Aman is the checkout developer.
  • Write test cases in JavaScript, TypeScript or Python: switch any time in the editor. CI scores them by mutation testing: it plants realistic bugs in the coupon code and checks that your cases catch them.
  • Coupon mistakes during a sale cost real money and spread fast on Reddit and WhatsApp.

You'll work in

Slack Jira VS Code Confluence Drive PagerDuty
Code editor + testsWritten deliverableJavaScript · TypeScript · Python

Each app is laid out like the tool most teams in this role use. Simverse isn't affiliated with these companies.

People you'll work with

  • Farhan Qureshi · QA Lead
  • Aman Gupta · Software Engineer, Checkout
  • Priya Iyer · Release Manager
  • Neel Joshi · Growth Manager

What's assessed

  • Problem understanding

    Works out what is actually required, including constraints and unstated edge cases.

  • Problem solving

    Forms hypotheses and makes evidence-based decisions instead of random changes.

  • Coding

    Writes correct, readable, proportionate code that meets the requirements.

  • Debugging

    Finds the root cause from evidence, recovers from failures and verifies the fix.

  • Testing

    Verifies work with tests, covers edge cases and catches regressions.

  • Adaptability

    Changes approach when the evidence says so and responds to new information.

  • Autonomy

    Makes progress independently and uses hints and AI with judgment and verification.

  • Communication

    Explains reasoning, decisions and trade-offs clearly.