Milestone map
Milestone map
3 milestones
Enter a hackathon and ship a working demo
1 weekend
Enter a real, judged hackathon and ship a working prototype by the deadline. Scope small enough to finish and demo live. Finishing a demo under pressure is the first skill to prove.
Proof required
Link the hackathon page, your submission (Devpost or equivalent) with a demo video, and the code repository.
What gets checked
- A judged event with other teams
- Demo shows the core feature working
- Code committed during the event window
Common mistakes
- Over-scoping and demoing slides
- Code written before the event
- No demo video
Powstik Guide
A working hackathon demo, submitted on time.
Steps
- Pick one problem and one core feature.
- Build the demo path first, extras last.
- Stop coding in time to record the demo.
- Submit with a clear two-line pitch.
Template
Submission Problem (one line): What it does (one line): Demo video: Repo: Built with: What we'd build next:
What gets sent back
- A slide deck instead of a demo.
- Code written before the event.
- No submission link.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check commit times against the event window
- Watch the demo
- Check the event was judged
You'll sign in first, then come straight back here.
Improve your pitch and judging fit
1 weekend plus prep
Enter a second hackathon, using feedback from the first. Read the judging criteria first and design around them. Many good builds lose on pitch and fit, not code.
Proof required
Link the second submission and a short note (150+ words) comparing it to the first: judging criteria, what you changed, and any judge feedback.
What gets checked
- Judging criteria named and addressed
- At least one change from the first event
- Judge feedback recorded if given
Common mistakes
- Ignoring the judging criteria
- Repeating the same mistakes
- No comparison written
Powstik Guide
A second entry designed around the judging criteria.
Steps
- Copy the judging criteria before you start.
- Map each criterion to a demo moment.
- Rehearse a two-minute pitch twice.
- Ask judges for feedback after.
Template
| Criterion | How our demo shows it | |-----------|-----------------------| Change from event 1: Judge feedback:
What gets sent back
- Criteria ignored.
- No change from the first event.
- No comparison note.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check the criteria are addressed in the pitch
- Compare the two submissions
- Read the feedback note
You'll sign in first, then come straight back here.
Place in the top three
1–6 months
Keep entering until you place first, second or third in a competitive hackathon. Record the result and what made the difference. A placing from real judges is the proof.
Proof required
Link the official results page or organiser announcement showing your placing, your submission, and a short note on what made the difference.
What gets checked
- Official result from the organiser
- At least several competing teams
- Note explains the winning factor
Common mistakes
- A participation badge counted as a win
- An event with no real competition
- No official result
Powstik Guide
An official top-three hackathon placing.
Steps
- Pick events that fit your strengths.
- Reuse what worked in your last pitch.
- Save the results page when announced.
- Write what made the difference.
Template
Event: Date: Teams competing: Placing: Results link: What made the difference:
What gets sent back
- Participation prizes.
- Events with only a few teams.
- No official result link.
Resources
Foundationstart here
What a verifier looks for
- Check the result on the organiser's page
- Check team count
- Match the submission to the result
You'll sign in first, then come straight back here.