Author: Yilmaz, Citrea DevRel (Developer Relations)
Compiled by: Felix,
In recent years, Web3 hackathons have gradually emerged around the world and become a developer event in the industry. During the event, a group of developers from all over the world brainstormed and worked closely together to create a functional app that would win the grand prize. But there are always a few who succeed, and in addition to the technology itself, how to come out on top in the competition may be a question for every developer. Yilmaz, a judge of the ETHGlobal Taipei 2025 Hackathon, recently posted his own suggestions on how the contestants can stand out from the hackathon. The following is the full text.
You crossed half the globe to attend a hackathon. Your code is clean and concise, making it hard not to want to lick the screen. However, you returned empty-handed, without any prizes. What’s going on? Hint: This is not a technical issue.
This situation is not uncommon. Excellent developers and outstanding builders often end up with nothing. This is not because their skills are lacking, but because they overlook certain key aspects of the hackathon.
Recently, I served as a judge at the ETH Global Taipei event on behalf of Citrea. Citrea sponsored this event and held competitions such as “Best Bapp on Citrea” and “Experimental DeFi Bapps.” For most of the event, I was not only responsible for judging but also observing—moving between booths and tables, listening to developers’ ideas, and brainstorming together. Seeing these scenes reminded me of my days participating in competitions, during which I learned how to break down the rules of the game in order to have a chance at winning rewards.
This article will share some insights on how to truly “crack” a hackathon - from the experience of someone who has served as an architect and now works in developer relations (DevRel), having judged multiple Web3 hackathons.
The hackathon has already started before the competition day.
Thinking that the hackathon only starts on the first day is one of the biggest mistakes. In fact, this is not the case. I’m not saying that you should build your project in advance (as that would disqualify you immediately), but there are many things you can prepare ahead of time.
Observe
You might be a student or an experienced developer looking to get involved in the Web3 ecosystem. But do you know which area you want to venture into? You should observe this industry as early as possible. Not just chatting casually on Twitter, but truly delving into the field to see what everyone is doing. What are the weak or blank spots that you can fill or improve upon, what upcoming improvements are on the horizon, and which projects are performing strongly in which tracks.
Having a holistic understanding of the field you want to venture into can be very helpful. This is said because many developers attempt to gain rewards from areas they know almost nothing about. This is often unworkable because you have no idea what you are building. Judges, hackers, and consultants may provide some assistance during hackathons, but it is still far from enough.
Building connections and teamwork
If you step into the arena without a team, you are already at a disadvantage. Before the hackathon starts, you have a few days or even weeks to assemble a team—this gives you time to screen members, test the compatibility of team members, enhance team collaboration skills, or adjust the roles of team members.
However, participating as a solo competitor is not without hope. Perhaps you intend to form a team on-site, brainstorming with people from diverse backgrounds to spark unique ideas. If you don’t have a team yet, be proactive: attend some surrounding events, cocktail parties, and themed talks before the hackathon starts. Engage with developers, designers, product managers, developer relations personnel, and even business development folks. They might not understand programming, but they know a lot of people and can help you find the perfect teammates.
Individuals helped form two teams before the Ethereum hackathon in Taipei. They did not know each other before, but one of the teams eventually won a prize.
Check the track as soon as possible
Before the first day of the hackathon competition, check the tracks and the projects that provide funding as early as possible. Surprisingly, many participants only pay attention to this point until the event starts. The tracks are usually announced several days or weeks in advance, giving participants time to formulate strategies.
For example, the ETH Global hackathon announced its tracks two weeks before the competition. Some developers will reach out to the project parties in advance to express their ideas and ensure alignment with the tracks. This proactive approach allows them to adjust their ideas or choose the right track, thereby maximizing their chances of winning.
Break the Norm
Creativity matters. Even if you have the most concise codebase, you can still fail. Why? Because your creativity doesn’t stand out enough. It doesn’t meet the product-market fit, or the jury has seen too many similar products. If you’re submitting yet another AI wallet interface with little to no improvement over what six teams have submitted in the last two months, you’re hopeless. Since the judges are not interested in your idea/concept at the first stage, it can be difficult to attract the judges’ attention to your code.
The judges have limited time to evaluate each submitted work and cannot delve deeply into every line of code. Therefore, the product concept or idea is crucial. Is this concept reasonable? Is it unique, or does it provide a real improvement over existing products in the market? Does it feel novel?
Take a real case as an example. At the Ethereum hackathon in Taipei, there was a team from the Philippines. They had a Web2 background and no Web3 experience, but their creative idea completely broke the norm and immediately caught the judges’ attention. They didn’t even submit to our track, but are now collaborating with us in our incubation project Citrea Origins. This is the power of an outstanding idea that can gain attention immediately.
Think from the perspective of the jury. After two days, the jury is exhausted from reviewing over twenty projects. You only have a few minutes to win the judges’ favor.
The list of thoughts in my mind is as follows:
- What product is this?
- Is this concept novel?
- Does it have potential product-market fit?
- Is this just a copy of other products?
- Is this coded during this hackathon, or pre-built/repeatedly submitted?
The judges have seen it all. If your project is just superficial, it will be quickly recognized.
Talip (Citrea DevRel) can easily recognize pre-built projects at a glance.
interact with the jury
Want to increase your chances of winning? Why not communicate with the jury? The help they can provide is beyond your imagination. Before you start building, articulate your ideas and discuss them with the judges.
This not only improves your ideas but also increases attention. If the judges have seen your face, heard your proposal, and then see your project again in the submitted works - they will remember you. Then you naturally have an advantage.
Eye-catching
Make sure your work stands out. Once you have a great idea and a solid team, start building - but don’t stop there. You may have an idea that can shine, but to ensure it wins, you need to present it well. Many times, contestants overlook the presentation section, just sending a GitBook, which might work. It’s not that you need to create a colorful presentation, but it should be a clear and detailed explanation.
- Give it a good name - that’s right, the name is important. It can set the tone.
- Design Architecture - Draw diagrams, simplify explanations.
- Create clickable demos - more powerful than videos, allowing judges to experience it firsthand.
- Build a concise and clear PPT - your slides should be able to explain everything without you needing to elaborate too much.
Don’t invest too much effort in the video presentation unless absolutely necessary. If it’s just a five-minute user interface demonstration, the judges won’t be interested. Provide some interactive content. Let the judges feel the application and experience it.
A professor of architecture once said to me: “If I need to ask questions, it means your presentation has failed.” This may sound a bit extreme, but take it as a guideline for your presentation. Because from a broader perspective, your presentation is essentially your Pitch Platform.
Wait, everything is just to attract attention? It has always been.
is more than just a bonus
Finally, please remember: bonuses are nice, but they are not the real prizes.
A hackathon is a form of attention economy. Everyone is paying attention. Even if you don’t win, you can leave a deep impression on the right people, and doors of opportunity will open for you: incubation opportunities, partnerships, job opportunities. The rewards are short-term; your reputation is long-term.
Also, please don’t participate in five unknown hackathons just to make up the numbers; no one will care. Create something that helps you grow, and let each hackathon add value to your portfolio.
In short, how to participate in a hackathon:
- Form a team as soon as possible
- Innovative ideas
- Think from the perspective of the jury and interact more.
- Create a clickable and beautiful presentation
- Sell it like your future depends on it (because it does)
Related Reading: Electric Capital Annual Developer Report: 39,000 New Developers Join, Over Half of Ethereum Developers Focus on L2
