Hackathon “Attack” Guide
In recent years, Web3 hackathons have gradually emerged globally, becoming major events for developers in the industry. A group of developers from all over the world gather during these events to brainstorm and form tightly-knit teams, creating fully functional applications in hopes of winning great prizes. However, success is always rare. Apart from the technology itself, how to stand out in the competition might be a question every developer has. Recently, Yilmaz, a judge for the ETHGlobal Taipei 2025 hackathon, shared his advice on how participants can stand out in hackathons. Below is the full content.
How Can Developers Stand Out in the Competition?
You travel halfway around the world to participate in a hackathon. Your code is clean and concise, so good that you almost want to lick the screen. Yet, you return empty-handed with no prizes. What happened? Hint: This isn’t a technical issue.
This situation is more common than you think. Talented developers and outstanding builders often leave empty-handed. It’s not because they lack technical skills, but because they overlooked certain key aspects of the hackathon.
Recently, I represented Citrea as a judge at the ETHGlobal Taipei event. Citrea sponsored the event and hosted competitions such as “Best Bapp by Citrea” and “Experimental DeFi Bapps.”
During most of the event, I was not only judging but also observing—moving between booths and tables, listening to developers’ ideas, and brainstorming together. Watching these scenes reminded me of my days as a participant, when I learned how to deconstruct the rules of the game to win rewards.
This article will share some insights on how to truly “conquer” a hackathon—from the experience of someone who has been a former architect, now a developer relations (DevRel) expert, and a judge in multiple Web3 hackathons.
The Hackathon Starts Before the Official Kickoff
One of the biggest mistakes is thinking that a hackathon only starts on the first day. In fact, that’s not true. I’m not saying you should pre-build your project (that will get you disqualified immediately), but there are many things you can prepare in advance.
Observation
You might be a student or an experienced developer wanting to dive into the Web3 ecosystem. But do you know which area you want to dive into? You should start observing the industry early. Not just idly chatting on Twitter, but truly researching the field to see what others are doing. What are the gaps or weaknesses you can fill or improve, what upcoming improvements are on the horizon, and which projects are performing well in which tracks?
Having a general understanding of the area you want to get into will be extremely helpful. I’ve seen many developers try to win rewards from an area they almost know nothing about. This rarely works because you don’t even know what to build. Judges, hackers, and advisors may offer some help during the hackathon, but it’s far from enough.
Build Networks and Teamwork
If you enter the competition without a team, you are already at a disadvantage. Before the hackathon kicks off, you still have days or even weeks to form your team—this gives you time to screen members, test compatibility, enhance team collaboration, or adjust the roles of team members.
However, entering solo is not hopeless. Maybe you intend to form a team on-site, brainstorming with people from diverse backgrounds to spark unique creativity.
If you don’t have a team, be proactive: participate in some pre-event activities, cocktail parties, and keynote speeches. Engage with developers, designers, product managers, DevRel personnel, and even business development people. They may not know how to code, but they know many people and can help you find the perfect teammate.
In Taipei’s Ethereum hackathon, I helped form two teams before the event. They didn’t know each other before, but one of the teams ended up winning.
Check the Tracks Early
Before the hackathon officially starts, check the tracks and the projects offering sponsorships as early as possible. Surprisingly, many participants don’t look into this until the event begins. Tracks are usually announced days or even weeks in advance, allowing participants time to strategize.
For example, ETH Global announced the tracks two weeks before the hackathon began. Some developers contacted the project teams early to discuss ideas and ensure they aligned with the tracks. This proactive approach enabled them to adjust their ideas or choose the right track, maximizing their chances of winning.
Break the Norms
Creativity is crucial. Even if you have the cleanest codebase, you could still fail. Why? Because your creativity is not compelling enough. It doesn’t hit product-market fit, or the judges have already seen too many similar products. If what you submit is just another AI wallet interface, and it’s almost identical to the six submissions from the past two months, you have no chance. The judges won’t be interested in your code if they’re not interested in your idea/concept in the first place.
Judges have limited time to review each submission, so it’s difficult to dive deep into every line of code. Thus, the product concept or idea becomes crucial. Is it reasonable? Is it unique, or does it provide a real improvement over existing products on the market? Does it feel fresh?
Let me give you a real example. At the Taipei Ethereum hackathon, a team from the Philippines stood out. They had a Web2 background with no Web3 experience, but their concept was so innovative that it immediately caught the judges’ attention. They didn’t even submit to our track, but we are now working with them in our incubator project, Citrea Origins. That’s the power of a great idea—it grabs attention immediately.
Think from the perspective of the judges. After two days, they’re exhausted from reviewing over twenty projects. You only have a few minutes to win them over.
Talip (Citrea DevRel) Can Spot Pre-built Projects Instantly
Interact with the Judges
Want to improve your chances? Try engaging with the judges—they can provide far more help than you imagine. Before you start building, explain your idea and discuss it with the judges.
This not only helps refine your idea but also increases visibility. If the judges have seen your face, heard your pitch, and then see your project again in the submissions—they’ll remember you. That gives you an edge.
Stand Out
Make sure your project stands out. Once you have a fantastic idea and a solid team, start building—but don’t stop there. You might have an idea that could stand out, but to win, you need to present it well. Many times, participants neglect the demo part and simply post a GitBook. That might work, but it’s not ideal. You don’t need to create a flashy demo, but you should have a clear, well-explained presentation.
Give it a great name—yes, names are important. It sets the tone.
Design the architecture—draw diagrams, simplify explanations.
Create a clickable demo—more impactful than videos, allowing the judges to experience it firsthand.
Prepare a concise and clear PowerPoint presentation—your slides should explain everything without needing too much elaboration.
Unless absolutely necessary, don’t spend too much effort on video demonstrations. Judges aren’t interested in a 5-minute UI demo. Provide interactive content. Let the judges experience the application themselves.
One of my architecture professors once said, “If I have to ask questions, your demo has failed.” That might sound extreme, but consider it a guideline for your demo. From a broader perspective, your demo is essentially your Pitch Platform.
Wait, It’s All About Attention?
Yes, it always has been.
Not Just the Prizes
Finally, remember: while the prizes are nice, they’re not the real reward.
A hackathon is an attention economy. Everyone is watching. Even if you don’t win, leaving a strong impression on the right people can open doors for you: incubation opportunities, partnerships, job offers. Prizes are short-term; your reputation is long-term.
Also, don’t participate in five obscure hackathons just for the sake of it. Nobody will care. Build something that helps you grow, making each hackathon add value to your portfolio.
In short, how to participate in a hackathon:
- Form a team early
- Come up with an innovative idea
- Think from the judges’ perspective, interact more
- Create a clickable, well-made demo
- Pitch it as if your future depends on it (because it does)
Original article reprinted in cooperation with: PANews