Decide whether the project earns space

A hackathon can produce useful resume evidence even when the project never became a product. Include it when the work illustrates a skill the target role asks for and you can explain your part without relying on the event name. A working prototype, a user-research finding, a test plan, or a clear presentation can each be relevant for different jobs.

If you have substantial professional work in the same area, compare the project with your strongest recent examples. An old weekend prototype may be less useful than a current work accomplishment. For an internship or entry-level application, however, a well-described build may provide concrete evidence that a course list cannot.

  • What problem did the team choose, and who was the intended user?
  • What part did you personally design, build, test, organize, or present?
  • What could the team actually demonstrate by the end of the event?

Label the result as a prototype, not a shipped product

Start with a compact project name and context, such as “Volunteer scheduling prototype | campus hackathon | October 2025.” Name the deliverable in ordinary terms: a clickable flow, a working import screen, a dashboard mock-up, or a tested concept. If the demo used sample data, say so where that distinction matters.

Do not describe a one-day proof of concept as a production launch or imply that a demo had real customers. Likewise, winning a prize is a separate fact from the quality or adoption of the product. If the prototype was expanded later, distinguish what existed at the event from the later work.

Write bullets around your own contribution

For a team project, use the pattern “action + specific component or decision + purpose or verifiable result.” For example, if true: “Built the event-signup form and validation for a team volunteer-scheduling prototype; demonstrated a complete signup flow using sample entries.” This identifies the individual work and the status of the demo.

A non-coding contribution can be equally concrete: “Interviewed event volunteers, summarized recurring scheduling problems, and used the findings to shape the team demo.” Replace the sample with your actual evidence; do not claim interviews you did not conduct. “Created an award-winning app” alone hides both your role and what was built.

  • Weak: Worked with a team to make an innovative app.
  • Clearer, if accurate: Designed the check-in screens for a team prototype and tested the demo path with teammates before presentation.
  • If you only proposed a feature, say “proposed” rather than “built” or “launched.”

Choose a section and link with care

Most hackathon work belongs in Projects, with the project name, event, date, and one or two useful bullets. If the event was part of your paid role, the work may fit under that job instead. Put a genuinely relevant prize under the project or in Awards, but avoid repeating the same recognition in both places.

Link to a repository, portfolio write-up, or demo only when it is public, works, and reflects the contribution you describe. A private repository or broken demo link adds no proof. If teammates own the code or design assets, check what you are allowed to share and explain your role in a short write-up rather than presenting the whole team deliverable as yours.

Tailor the details to the job posting

A software role may warrant the component you implemented, the tool you used, and the behavior you tested. A design role may benefit more from the decision behind a flow and what the prototype demonstrated. For an operations role, coordination under a short deadline may matter, but still name a real artifact such as a task board, handoff, or presentation plan.

Use the job posting to choose which true details to foreground. Do not add unfamiliar tools to a skills section because teammates used them. If the project is not relevant to the role, leave it in your master draft and use the space for stronger evidence in that application.

Run a final credibility and PDF check

Read every verb as an interviewer would. Can you explain what the team built, what you owned, what worked in the demo, and what remained unfinished? Confirm that dates, prize names, and public links match the underlying record. Remove claims about adoption, performance, or impact that you cannot support.

Keep the entry short enough to scan alongside your other experience. CreateResume can help you revise a structured project entry, preview the page layout, and prepare a PDF-ready resume. Open the exported file and check that the project title, bullets, and any link remain legible before applying.