How Challenges work

Challenge flow

Challenges are time-boxed prompts that help you ship a thin slice in public and leave proof on your Builder Passport.

Steps

1. Browse open challenges from Challenges
2. Join while the challenge is active
3. Build the smallest useful slice that meets the brief
4. Submit a URL + notes (what you built, how to run it, trade-offs)
5. Some challenges are judged — admins or judges may mark winners/finalists

Finished challenges appear on your Passport as evidence. Incomplete joins without submissions rarely help.

What makes a strong submission

• Runs for a cold visitor (README, demo link, or clear setup)
• Matches the brief instead of dumping an unrelated portfolio piece
• Honest about what is prototype vs production
• Credits libraries, teammates, and tutorial bases

Judging and leaderboards

Not every challenge has prizes. When judging exists, criteria are on the challenge page. Leaderboards reflect participation and outcomes configured for that challenge — not a global “pay to win” system.

Tips by persona

• Students: pick beginner challenges; focus on learning + a clean write-up
• Professionals: use challenges to show stack depth or speed
• Career switchers: one finished challenge beats five “planned” courses

If you miss a deadline, ship the project to your Passport anyway — proof still compounds outside the contest window.