For Pharos University students

One week. Four tracks. One internship.

Choose a track, build a working solution to a real technical problem, and submit it online by December 1.

Time left to submit

7days
00hours
00minutes
00seconds

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

  1. 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
  2. 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
  3. 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
  4. 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

Pick one track

You enter alone, and only one track. Every track is scored on the same sheet, so no track is easier to win.

Computer Science

The booking engine

Build a booking backend that never overbooks, even when hundreds of requests hit the last spot at the same moment.

You build
An HTTP API in any language that follows our spec, with a waitlist, double-tap protection and all-or-nothing updates.
We test
We start it with one command and fire many requests at once. Then we check that every class adds up.
You get
The API spec, Docker templates for Node, Python, Java, .NET and PHP, and a check script to run before you submit.

Artificial Intelligence

The member assistant

Build an assistant that answers members only from the gym's rules, in Arabic or English, and says "I don't know" when the rules are silent.

You build
A small API that answers questions, cites the rule it used, follows the newest rule, and refuses medical advice.
We test
30 hidden questions: simple ones, tricky ones, Arabic ones, and ones the rules don't cover.
You get
The gym rules, the API contract, 10 sample questions and a check script. Free AI models are enough.

Data Science

Who is about to leave?

Clean a messy year and a half of gym data, predict which memberships will be cancelled, and explain why in words a manager understands.

You build
A model you can trust, with honest validation and no peeking at the future, plus charts that tell the story.
We test
We know what really happened to every membership on your list, and score your predictions against it.
You get
Seven CSV files: members, memberships, check-ins, payments and complaints. Missing values and typos included.

Cybersecurity

Break it, then fix it

Find the security gaps in a small member portal, prove each one safely on your own machine, then fix the code without breaking it.

You build
A clear security report ranked by severity, and a fixed version of the app that still works for real users.
We test
We check which gaps you closed, and run our own tests to make sure nothing else broke.
You get
The full app with three test accounts. Run it locally with one command. Test only your own copy.

How the week goes

  1. Nov 24

    Pick your track

    Read the brief and download the starter pack. It has everything you need to start.

  2. Nov 24 to Dec 1

    Build it

    Seven days, on your own. Use AI tools if they help, then tell us how you used them.

  3. Dec 1, 11:59 pm

    Submit online

    Send your work through the submission form before the deadline (Cairo time). Late entries aren't accepted.

  4. December

    Judging

    The Creiden team lead for each field judges that track, using our tests and a full review of your code and write-up.

  5. After judging

    Interviews

    We email the four track winners to set up interviews.

Track winners 4 interviews CS AI DS SEC 1 internship

Four winners.
One internship.

The best entry in each track gets an internship interview at Creiden. From those four, the strongest gets the internship.

We don't announce winners publicly. We contact them directly.

How we score you

Out of 100, the same sheet for every track. A simple solution you can explain beats a fancy one you can't.

Passes the hidden test
We run tests you haven't seen. The starter pack has a smaller public version so you know you're on track.
Quality of the approach
Is the solution sound, simple and well thought out?
Edge cases and thinking ahead
What happens when things go wrong, or when someone does something odd?
Clear explanation
Your README or report. Could someone new understand what you did and why?
Presentation
Easy to run, easy to read.

The rules

  • Open to Pharos University students.
  • Individual work. One person, one track, one entry.
  • AI tools are allowed. Tell us which ones and how you used them.
  • Cybersecurity: test only your own local copy. Testing any real system means disqualification.
  • Your work stays yours. We use it only to judge the challenge.
Do I need to pay for an AI model?

No. Free options are enough: the Gemini API free tier, the Groq free tier, or a local model with Ollama. Paid models earn no extra points.

Which programming language should I use?

Any. For the CS track, your app just has to follow our API spec and start with docker compose up --build. The starter pack has templates for five languages.

I've never used Docker. Is that a problem?

The templates do most of it for you. Install Docker Desktop, copy the template for your language, and run one command. Learning it this week is part of the fun.

Can I enter more than one track?

No. Pick the one you want to go deep on. One strong entry is better than two rushed ones.

Can I work with a friend?

No. Entries are individual. You can ask for help understanding a concept, but the work must be yours.

What do I submit, and where?

Each brief lists exactly what to submit. Use the form at the bottom of this page and share links to your work. There are no file uploads.

How will I know if I won?

We email the winners directly after judging. Results are not posted publicly.

Ready when you are.

Submit before December 1 at 11:59 pm, Cairo time.

  • Share links only, no file uploads. A GitHub repo, a Google Drive folder, Kaggle or Colab all work.
  • Make sure we can open your links without asking for access.
  • Changed something? Submit again with the same email. Your latest entry counts.

Your entry

Your track

Your code and README. For Data Science, include predictions.csv.

Winners are invited to an interview, so we read your CV with your entry. Make sure the link opens without asking for access.

We use your details only to judge the challenge and contact you about it.