short answer
Yes, non-programmers can join most hackathons; MLH's organizer guide says you do not have to be a programmer to attend. Most hackathons still judge a working build, so your job is to make that build better: design the screens, talk to users, script the demo, bring domain knowledge, clean the data or build in a no-code tool. Pick events whose rubric rewards that work, such as design-a-thons, ideathons and PPT-round hackathons.
beginner hackathonson this page
Yes, you can join without coding
MLH's organizer guide says it directly: you do not have to be a programmer, and you do not have to study computer science. MLH's required registration fields ask for your school and level of study, not your languages. Indian listings sometimes spell it out: Udbhav'26 at Sage University, Indore listed management, arts, commerce and science students as eligible alongside engineers.
The catch is what gets judged. MLH's standard rules, which MLH uses for its digital events and its own prize categories and which organizers may adopt, tell teams to demo what they built and say pitches are discouraged. Their four criteria, weighted equally, are technology, design, completion and learning, and the rules state that pitch quality and idea quality are not judged. Under rules like these, a non-coder earns points through the build itself.
Six roles and what each one ships
Lead with a deliverable, not a title. Each role below ends the weekend with something a judge can see.
- Design and UX: the user flow, wireframes, then final screens in Figma, plus a small style sheet (colors, type sizes, spacing) the developers can copy. This feeds the design criterion directly.
- Research and user interviews: five short interviews in the first hours, a one-line problem statement backed by what people said, and a test of the prototype on two or three people before judging.
- Product and pitch: the scope list (what is in, what is cut), the project page, the demo script and the demo video. Devpost's judging guide counts the demo video among the criteria hosts use most.
- Domain expert: a medicine, law, finance or farming student who knows the real problem. You supply realistic sample data, edge cases and answers when judges ask "would anyone use this?"
- Data: find a public dataset, clean it in a spreadsheet, check the numbers and make the charts the app displays.
- No-code builder: a clickable prototype or working front end in a no-code tool, which doubles as a backup demo if the coded version breaks. FigBuild 2026 required teams to embed Figma prototypes or Figma Make files.
Hour by hour in a 24-hour event
- Hours 0-2: agree on one user and one problem. The researcher runs quick interviews with mentors, sponsors and other hackers. The designer sketches the core flow on paper.
- Hours 2-6: the designer ships wireframes for the two or three screens the demo needs. The domain expert writes sample data. The product lead posts the scope list where everyone sees it.
- Hours 6-14: final screens and exported assets go to the developers. The data person hands over a clean file. The no-code builder wires a clickable backup demo.
- Hours 14-20: test the build on two or three people, write down where they got stuck and feed fixes to the coders. Start drafting the project page.
- Hours 20-23: record a demo video of about 2 minutes (MLH's recommended length), finish the project page and rehearse the live demo.
- Final hour: make sure you are registered on the submission platform and added to the project. MLH's organizer guide stresses that every team member must be added.
How judging rubrics reward non-code work
Read the rubric before you pick a role. The weighting decides how much a non-coder can move the score.
- MLH standard criteria: technology, design, completion and learning, equal weight. Design is a full quarter of the score, and the rules say pitch quality is not judged.
- Devpost's guide lists the six criteria hosts use most often: technological implementation, ease of use, demonstration video, potential impact, quality of the idea and design. Only the first is about code.
- Udbhav'26 on Unstop scored its 24-hour final on innovation (25%), technical execution (25%), real-world impact and feasibility (20%), problem-solution fit (15%) and presentation and demo (15%). Half the score sat outside the code.
- FigBuild 2026 judged design execution and UX, craft, storytelling and presentation, problem-solution fit, and innovation. Its brief said feasibility was not being judged.
One warning: for large categories such as Best Design, MLH's judging plan suggests narrowing to the top overall teams first. Great screens on a broken build may never reach the design judges. More on rubrics in hackathon judging criteria.
Events that suit non-coders
- Design-a-thons: FigBuild 2026, Figma's student design competition, ran online March 6-9, 2026 for college students 18+ in the US, Canada, India and Australia, in teams of 2 to 4. Teams submitted a 3 to 5 minute video and Figma Slides, competing for $30,000 in cash, including $1,500 each for Best Design and Best Storytelling. Dates for the next edition were not announced when this was written (November 2026).
- Design prizes inside regular hackathons: MHacks 2026 ran a Figma Best Design Track with three winners, and Technica 2026 listed UI/UX design among its judging criteria and offered a Best UI/UX Hack prize.
- Ideathons: judges score the problem, the solution and the pitch, and code is usually optional. See what is an ideathon.
- PPT rounds: some Indian college hackathons on Unstop open with a slide round. Udbhav'26 used one to shortlist its top 50 teams, and Tech Eximius 2026 judged its Round 1 deck on innovation, feasibility, problem-solving approach and clarity of presentation. That round is where a researcher and a pitcher carry the team; see the hackathon PPT guide.
- Low/No Code tag: Devpost tags some events Low/No Code. FigBuild 2026 and IceHacks 2026 both carried it. Check the rules anyway: MLH's standard rules require public code, so ask whether a no-code project link counts.
How to find a team as a non-coder
Pitch yourself by what you will hand over and when. A post like "Product designer. User flow and four final Figma screens by hour 8, demo video by hour 22. Looking for two developers." gets replies. "Non-technical, happy to help" does not.
On Devpost, open the hackathon's Participants page, tick the box saying you are looking for teammates, and use the text box to introduce yourself and the teammates you want. The Team-up request button emails a participant from your Devpost address, once per person. Post the same intro in the event's Discord or Slack; MLH's guide recommends organizers run event chat there.
Bring one link that proves your skill: a Figma file, a case study, a research summary or a published analysis. Aim for at least two people who can code on your team. MLH's recommended rule caps teams at four, so you are one of four, not one of ten. The team formation guide covers the rest.
Mistakes that sink non-coders
- Spending ten hours on a deck at an event that judges the demo. Check the rubric first.
- Designing screens the developers cannot build in time. Agree on scope at hour 2 and design only what is in it.
- Not being on the submission. If your name is not on the project, the work does not count as yours.
- Claiming market sizes or user numbers without a source. It costs credibility. The pitch script guide shows how to frame the problem without them.
FAQ
Can non-programmers join hackathons?
Yes. MLH's organizer guide says you do not have to be a programmer or a computer science student to attend. Check the event's eligibility rules, since some events limit entry to college students or set an age floor.
Can I win a hackathon without coding?
It depends on the rubric. Design-a-thons such as FigBuild 2026 judge design and storytelling, and ideathons judge the idea and pitch. Hackathons using MLH's standard rules judge what was built, so you win there as part of a team that ships a working demo.
What should a non-coder do at a hackathon?
Own one deliverable: the screens, the user research, the demo video and project page, the domain knowledge, the data, or a no-code prototype. Agree on scope early so your work lands in the final build.
Is a hackathon without coding the same as an ideathon?
Not quite. An ideathon is built around pitching an idea, and code is usually optional. A hackathon usually expects a working project, though some, like FigBuild 2026, accept prototypes instead of code.
Do no-code projects count at hackathons?
Only if the rules allow them. MLH's standard rules require code to be public, while FigBuild 2026, a design-a-thon tagged Low/No Code on Devpost, asked for Figma prototypes instead of code. Ask the organizer before you build.
sources
- MLH organizer guide: what is a hackathon guide.mlh.com
- MLH standard hackathon rules and judging criteria github.com
- MLH organizer guide: judging plan guide.mlh.com
- MLH organizer guide: judges guide.mlh.com
- MLH organizer guide: hackathon rules guide.mlh.com
- MLH organizer guide: hackathon scheduling guide.mlh.com
- Devpost: understanding submission and judging criteria info.devpost.com
- Devpost help: participants page and forming a team help.devpost.com
- FigBuild 2026 on Devpost figbuild2026.devpost.com
- MHacks 2026 on Devpost mhacks-2026.devpost.com
- Technica 2026 on Devpost technica-2026.devpost.com
- IceHacks 2026 on Devpost icehacks.devpost.com
- Udbhav'26 on Unstop unstop.com
- Tech Eximius 2026 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.