How to Put a Hackathon Project on Your Résumé as a Fresher (With Examples)

Most freshers' résumés have the same problem: a strong Education section, a long list of skills, and very little proof that any of those skills were used to build something. A hackathon project fixes that, but only if it's written up properly. "Participated in XYZ Hackathon" tells a recruiter almost nothing.

This guide covers where a hackathon project belongs on your résumé, how to write the bullets so they show what you did, what to link, and what to save while you build so the write-up is easy afterwards. We've included sample entries for developers, designers and product people, plus a short section on using Productothon 01, HireDoor's free five-day build week, to get one onto your résumé this month.

Why a hackathon project is worth the résumé space

Recruiters at big companies have said plainly that hackathons count as experience. At a 2021 panel reported by Business Insider, a Google university programs specialist said past experience is a "must have" for internship applicants, but that "experience can come in many forms". For tech roles she listed computer science projects, student activities, research, hackathons and class projects as things that count.

Hackathon projects are also a natural fit for what employers say they look for. In the US-based NACE Job Outlook 2025 survey, 88.3% of responding employers said they look for evidence of problem-solving skills on a candidate's résumé, and 81.0% look for the ability to work in a team. A hackathon is a problem, a team and a deadline in one entry, so it can show both, as long as your bullets make them visible.

And you don't get long to make the point. Ladders' 2018 eye-tracking study found recruiters spent an average of 7.4 seconds on an initial résumé screen, and the résumés that held attention had clear section headers, bold titles and short bulleted accomplishments. That's the format to aim for below.

Where it goes on a fresher résumé

• No internship yet? Put a Projects section directly after Education, and put your best hackathon project first in it. For a fresher, it is the closest thing you have to work experience.
• Have an internship? Keep Internships (or Experience) first, then Projects. The hackathon still goes in Projects, not hidden under Achievements.
• Several hackathons? Tufts University's career centre suggests a dedicated section such as "Projects", "Hackathons" or "Technical Competitions". Two or three strong entries beat six one-liners.
• Won something? Mention the result inside the project entry. You can also repeat it in a one-line Achievements section, but the project entry is where the context lives.

Use a standard heading like "Projects". If you're applying through company portals, our guide to an ATS-friendly résumé for freshers explains why creative headings and two-column templates can get misread.

The anatomy of a strong hackathon entry

Tufts recommends a consistent format for each entry: the hackathon's name, the date, and your role on the team, followed by a short description of the problem and concise, action-led bullets. Put together, a good entry has five parts:

1. Header line: Project name, hackathon name, month and year. Example: ClinicQ, Productothon 01 (HireDoor), Nov 2026.
2. Role and team: "Backend developer, team of 4" or "Solo". This tells the reader how much of the work was yours.
3. One line on the problem: What was broken and for whom, in plain words. "Small clinics in tier-2 cities manage walk-in queues on paper."
4. Two or three bullets on what you did: Start each with an action verb (built, designed, integrated, tested, led), name the tools, and end with a result.
5. Links: A live demo and a GitHub repo (or a Figma file or case study for designers).

Use the X-Y-Z formula for the bullets

Google recruiters at the same panel recommended the X-Y-Z formula: "Accomplished [X] as measured by [Y] by doing [Z]." Their own before/after example was about a hackathon. The weak version was "Participated in a city hackathon, working on a facial recognition project." The stronger version was "Won second place out of 40 teams in the city hackathon, building facial recognition software that helps detect human emotions, using Python and Java." The second one shows the outcome, the scale and the skills.

If you didn't win, you can still measure something honestly: how many people tested it, how fast a page loads, how many features you shipped in the five days, or how many steps you cut from a task. Never invent users or numbers. An interviewer will ask, and a made-up metric falls apart in one follow-up question.

Sample entries you can adapt

These are example entries to show the structure. The project names and numbers are made up; replace them with what actually happened in your project.

Developer

ClinicQ, Productothon 01 (HireDoor), Nov 2026 | Backend developer, team of 4
Walk-in queue tracker for small clinics that currently manage patients on paper.

• Built the REST API and PostgreSQL schema in Node.js for token booking and live queue status, used by the team's React front end.
• Added SMS-style status updates with a mock gateway and wrote tests for the booking flow before the final demo.
• Deployed on a free cloud tier; demo tested end to end by 12 classmates during build week. [Live demo] [GitHub]

Designer

ClinicQ, Productothon 01 (HireDoor), Nov 2026 | UI/UX designer, team of 4

• Ran 5 short interviews with clinic staff and turned them into 2 user flows (patient check-in, receptionist dashboard).
• Designed a 9-screen Figma prototype and a small component library that the developers built from directly.
• Simplified check-in from 6 steps to 3 after a hallway usability test with classmates. [Figma] [Case study]

Product manager

ClinicQ, Productothon 01 (HireDoor), Nov 2026 | Product lead, team of 4

• Wrote the one-page brief and cut scope to 3 must-have features so the team could ship a working build in 5 days.
• Ran daily 15-minute check-ins, tracked tasks on a shared board and kept the demo script under 3 minutes.
• Presented the final demo and wrote the README covering the problem, setup steps and next steps. [Demo video] [Brief]

Notice what each one does: it says who the product was for, what this person personally owned, which tools they used, and gives a reviewer something to click.

Links: the part most freshers get wrong

Tufts also recommends linking the GitHub repo or a demo. A link only helps if it works when a recruiter clicks it weeks later, so check these before you apply:

• The demo is still up. Free hosting tiers can sleep or expire. If yours might, record a 60–90 second demo video and link that as a backup.
• The repo has a real README. GitHub's own docs describe the README as the place to tell people why the project is useful, what they can do with it and how to use it. Add a screenshot, the problem, the tech stack, setup steps and who built what.
• Your commits show your work. In a team repo, a reviewer may look at contribution history. Commit your own work from your own account.
• The link text is readable. Use short, clickable links in your PDF, not long raw URLs.

What to save during build week (so the résumé writes itself)

The best time to collect material for your résumé is while you're building, not three weeks later when you've forgotten the details. Keep one shared doc and add to it daily:

• Day 1: The problem statement in your own words, who it's for, and your role on the team.
• Every day: Two lines on what you personally built or decided, and anything you had to learn fast.
• As you go: Screenshots of the product at each stage, and any numbers you can honestly measure (test users, load time, steps saved).
• Last day: The demo video, the final README and the submission link.

That log also prepares you for interviews. When someone asks "Tell me about a project you're proud of", you'll have the story ready. Our guide to answering "Tell me about yourself" shows how to fit a project like this into your intro.

Mistakes to avoid

• "Participated in" with nothing else. Participation isn't the accomplishment. What you built is.
• Claiming the whole team's work. Write "built the API", not "built the app", if the API was your part. Interviewers often ask who did what.
• A tools list with no context. "React, Node, MongoDB, Docker, AWS" means little unless a bullet shows what you did with them.
• Dead links or an empty repo. A broken link costs you more than no link.
• Inflated numbers. "10,000 users" for a five-day prototype will be questioned. Small, honest numbers are fine.
• Burying it. If it's your best project, it goes at the top of Projects, not at the bottom under Hobbies.

Need a project to write about? Build one at Productothon 01

If your Projects section is thin, Productothon 01 by HireDoor is a free way to fill it with something real. Here's how it works, from the official schedule:

• Who: Developers, designers and PMs, solo or in teams of up to 4. Entry is free with a HireDoor account.
• When: Registration closes at 12:00 AM IST on 30 October 2026, the moment the problem statements drop. The build runs for five days, 1–5 November, with judging planned for 6–7 November and results planned for 8 November.
• Tracks: AI and automation, education and career tech, fintech, healthcare and wellness, sustainability and social impact, productivity and developer tools, and open innovation.
• Prize No. 1: A CodeCrafters membership worth $1,260. More prizes are being revealed before build week.

Whether or not you place, you finish with a shipped project, a repo, a demo and a team story: everything this guide needs. Use the build-week log above from day one.

Register for Productothon 01 (free) before 30 October, and use the Team Lab on the Productothon site if you still need teammates.

Then put it to work

Once the project is on your résumé, use it. Plenty of entry-level roles on HireDoor ask for exactly this kind of proof; one backend role posted this week lists its experience requirement as "0-3 years (freshers with strong projects)". Browse the latest fresher jobs and internships on HireDoor, and tailor your project bullets to each job description before you apply.