short answer
List a hackathon in a Projects section, not under work experience. Give the project name, the event and year, your role, what you personally built and with which tools, and the result, then link the repo or demo. You do not need to have won. Hackathons help with jobs when the project can be checked and you can explain your part, but they do not replace an internship.
student hackathonson this page
Put it under Projects
A hackathon is a project you built, so it goes in a Projects section. MLH's resume post says exactly that, and the Tufts University career center suggests a separate section titled Projects, Hackathons or Technical Competitions.
Keep Experience for jobs and internships. A weekend event listed as a job invites the question of what else is padded.
Put any placement in the same entry: Winner, Finalist, or the exact track prize. Tufts says to include wins and special recognition. If you have several, a short Awards line can collect them.
Order by strength. MLH suggests moving projects toward the bottom if you have solid, relevant internship experience, leading with your most impressive relevant project, and keeping the resume to one page. If you organised a hackathon rather than competed in one, list it under Positions of Responsibility or Activities.
The entry: one header line, two or three bullets
Recruiters were not at the hackathon, as MLH's post points out, so the entry has to stand on its own.
Header line: Project name | Hackathon name, year | Placement, if any | link. Tufts adds your role (developer, designer, project manager) next to the event and date.
Bullet formula: action verb, then what you personally built, then the stack, then what it does or what happened. MLH's template runs: Developed a [thing] using [languages, frameworks, APIs] that [does what]. Its 2026 post adds the timeframe, the team size and a live link.
Example bullets (invented to show the pattern, not taken from anyone's resume):
- Built the FastAPI backend and Postgres schema for a canteen pre-order app in 36 hours; ran the live order flow in the final demo to judges.
- Trained an image classifier on 1,200 labelled leaf photos to flag crop disease from a phone camera; wrote the Flutter screen that shows the result offline.
- Designed the Figma flows and built the React front end for a Hindi-English chatbot that answers ration-card questions; team placed 2nd of 40 teams at [Hackathon name] 2026.
- Wrote the Solidity escrow contract and its Foundry tests for a freelancer payments app; deployed it to a public testnet and linked the verified contract in the README.
Each bullet names one thing you did. 'Worked in a team to build an innovative AI solution' names nothing.
Link something a recruiter can open
A link turns a claim into evidence. MLH tells you to put the project on GitHub and pin it, so recruiters can confirm you built it and read the code.
- Repo: public, with a README that covers the problem, a screenshot, how to run it, the team and which parts you wrote.
- Demo video: short and public. Devpost already requires submission videos to be public on YouTube or Vimeo so they embed for judges, so reuse that one.
- Project page: the submission page on the event platform. A Devpost submission keeps the description, video and Built with tags in one place.
- Live URL: only if it still loads. Test it before every application; a dead link costs more than no link.
LinkedIn and GitHub
On LinkedIn, add the project under Projects, one of the Recommended sections in LinkedIn's help page. The page notes that the Project URL field is not available for newly added projects, so attach the repo or video through Add media, then Add a link. Placements go under Honors & awards. Featured, another Recommended section, is a good spot for your strongest project.
Name your teammates in the description, and connect with them and your mentors before you leave the venue. MLH's 2026 post argues that a mentor or teammate who watched you work can later act as a reference.
On GitHub, pin the repo: GitHub's docs allow up to six pinned repositories and gists combined. Add a profile README too. Create a public repository named exactly like your username with a README.md in its root, and GitHub shows it on your profile. Give each hackathon project one line there, including your part.
If the team repo lives under a teammate's account, link it from your profile README and name the features you built. Your commits carry your name in its history.
Credit the team, claim only your part
Hackathons are team work, and the fastest way to lose an interviewer is to claim the whole project. Use we for the outcome and I for your part: 'We placed second; I built the API and the deploy.'
- State the placement exactly as the organisers announced it. A sponsor track prize, a finalist slot and an overall win are different lines.
- If you quote a field size, say what it counts. MLH's own example says 'out of 100 project submissions', which is not the same as registrations.
- A participation certificate is not an award. See what hackathon certificates are worth.
- If you started from a template, reused earlier code or relied on AI tools, be ready to say so, and check what the event's rules allowed. Hackathon AI rules covers this.
Talking about it in an interview
Expect 'tell me about a project' and follow-up questions on the code. MIT's career office describes STAR as Situation, Task, Action and Result. For a hackathon it maps like this:
- Situation: the event, the theme and the time limit.
- Task: the problem your team picked and the part you owned.
- Action: what you built, one technical decision and why, and one thing that broke and how you fixed it.
- Result: what worked in the demo, the placement if any, and what you would change now.
Be ready to share the repo on screen and walk through code you wrote. NACE's April 2026 release on resume skills tells students to be ready to explain their skills in interviews; as NACE CEO Shawn VanDerziel put it, 'Employers want to see examples.'
Do hackathons help you get a job?
Sometimes directly, more often as evidence. We found no independent data showing that hackathon participation on its own raises hiring rates, so be wary of anyone who promises that.
Direct route: some hackathons are hiring funnels. Flipkart GRiD 6.0, the 2024 edition on Unstop, said teams that reached the finale got a pre-placement interview (PPI) for a software role, and that 200 candidates would get a chance at PPIs. A PPI is an interview, not an offer.
Indirect route: NACE's Job Outlook 2026 Spring Update (185 employer respondents, surveyed February 12 to March 17, 2026) says employers want candidates who work in a team, solve problems and communicate, and want examples of those skills. A project you can show and explain is one.
MLH's 2026 post argues a hackathon weekend produces four things hiring managers screen for: code written with another person, a live URL, a real Git history and a reference. That is MLH's reasoning, MLH runs the events, and the post gives no hiring numbers.
The limit: the same NACE release says that when two candidates are equally qualified, employers overwhelmingly pick the one with internship experience. Hackathons strengthen an application; they do not replace an internship. For turning events into contacts, read hackathons to jobs, then browse open roles.
FAQ
Should I put a hackathon on my resume if I didn't win?
Yes, if the project is relevant to the role and you can link to it. MLH says winning is not required; the repo, the live link and your part in the build carry the entry.
Where do hackathons go on a resume?
In a Projects section, or a section called Hackathons or Technical Competitions. Keep work experience for jobs and internships, and put any placement inside the project entry.
Do hackathons help you get a job?
They can. Some, like Flipkart GRiD 6.0 in 2024, offered finalists pre-placement interviews. More often a hackathon gives you a concrete example of teamwork and problem-solving to show employers, but it does not replace internship experience.
How many hackathons should I list on my resume?
Only the ones relevant to the role, strongest first. MLH advises a one-page resume, so two or three well-described projects with links do more than a long list of event names.
Should I add hackathons to LinkedIn?
Yes. Add the project under Projects and attach the repo or video through Add media, put placements under Honors & awards, and name your teammates. Keep the details consistent with your resume.
sources
- MLH: How to put your hackathon project on your resume (2022) blog.mlh.com
- MLH: What a hackathon weekend shows a hiring manager (2026) blog.mlh.com
- Tufts Career Center: hackathons on your resume careers.tufts.edu
- NACE: skills students should show on resumes (April 2026) naceweb.org
- MIT CAPD interview primer capd.mit.edu
- GitHub Docs: pinning items to your profile docs.github.com
- GitHub Docs: managing your profile README docs.github.com
- LinkedIn Help: add sections to your profile linkedin.com
- Devpost Help: submission steps help.devpost.com
- Flipkart GRiD 6.0 on Unstop unstop.com
Checked against these pages when published. Rules and dates change, and the organizer's own page is the authority. Spotted an error? Send a correction.