Simverse
← All simulations

Frontend Engineer simulation

Frontend day: the booking form that loses customers

Ghar · Home servicesFresher / 1–3 yrs 40 min

You're a Frontend Engineer at Ghar, a home-services app. Customers are dropping off at the booking form because it rejects the phone numbers their keyboards autofill. Fix it in a real editor (JavaScript or TypeScript), review a teammate's component for accessibility, push back on a design change that would hurt users, and own what happens after you ship.

💻 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.

Ghar · Frontend Engineer IDay 1 · 09:00 AM

Your first message

Ritu SharmaEngineering Lead, Booking09:00 AM

Morning!

Morning! FE-231 is yours today. Support says we're losing almost a fifth of bookings at the phone field. Ticket attached. What's your plan?

Your objective

Get customers through the booking form, keep it usable for everyone, and keep the app fast.

Your day

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

  1. 09:00 AMMorning! · Ritu Sharma
  2. 09:15 AMFE-231: Booking form rejects real phone numbers · Ritu Sharma
  3. 11:30 AMQuick review? SlotPicker 🙏 · Kabir Singh
  4. 01:10 PMTwo small design tweaks · Sana Khan
  5. 05:00 PMEOD? · Ritu Sharma

Before you start

  • It's 9:00 AM. The day ends at 6:00 PM.
  • Ritu leads the Booking team. Sana is the product designer. Kabir is a fellow frontend engineer.
  • Work in JavaScript or TypeScript: switch any time in the editor. Visible tests are yours to run; CI runs hidden edge-case tests when you open a pull request.
  • Most Ghar customers book on mid-range Android phones over 4G, and many use screen readers or large text.

You'll work in

Gmail Slack Jira VS Code Confluence Drive Grafana
Code editor + testsWritten deliverableJavaScript · TypeScript

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

  • Ritu Sharma · Engineering Lead, Booking
  • Sana Khan · Product Designer
  • Kabir Singh · Frontend Engineer
  • Meera Pillai · Customer Support Lead

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.