The case: PulseGym
PulseGym is a growing gym with about 3,000 members. Members buy their membership, book classes and pay through the PulseGym app and website. The gym's manager has four problems. Every track takes one of them, and you pick the one you want to solve.
- Members
- About 3,000
- Plans
- Monthly, quarterly and annual
- Classes
- 20 spots each, booked in the app
- Payments
- Online, through a payment provider
- Member rules
- 21 rules, 4 of them updated this month
What's going wrong
-
Computer Science
Classes get overbooked
When a popular class opens, hundreds of members tap "Book" at the same moment and the app sells more spots than the class has.
Your job: build a booking backend that never overbooks and keeps a fair waitlist.
See the track
-
Artificial Intelligence
Staff answer the same questions all day
Freezing, guests, refunds, opening hours. The answers are in the member rules, but the rules are long and some just changed.
Your job: build an assistant that answers only from the rules, in Arabic or English, and says when it doesn't know.
See the track
-
Data Science
Members leave without warning
About one in four memberships isn't renewed, and the team only finds out after the member is gone.
Your job: predict which members are about to leave and explain why, using the gym's real-world, messy data.
See the track
-
Cybersecurity
The member portal has security gaps
It was built fast. It works, but members can see and change data that isn't theirs, and payments can be faked.
Your job: find the gaps, prove each one on your own local copy, and fix the code.
See the track