Blog · Nov 11, 2026
How to Find Hackathon Teammates (Even Remotely, Even as an Adult)
Most team-finding advice assumes you are a student in a dorm who can lean over and ask the person next to you. If you are an adult working from a spare bedroom, in a different time zone from everyone else, you need a different plan.
The good news: a team is often optional, and when you do want one, there are only a handful of places worth looking.
First, do you need a team?
Check the rules. Many events allow solo entries, and some allow teams of only a few people. A solo entry means no coordination overhead, no arguments about the idea, and you keep the whole prize. The cost is that you have to cover design, code, demo and pitch alone.
A team makes sense when the idea needs skills you don't have, when the event is short and the work parallelizes, or when you simply enjoy working with others. Two people is often the sweet spot for remote events, since each extra person adds more messages than output. Also check how the rules split prize money, which we cover in the choosing checklist.
Where to look
The event's own channels
Many events run a chat server or a forum, or have a participants area on the registration page. Look for a channel called something like "team formation" or "looking for group." People there have already committed to the same event, which means they have the same deadline and the same rules. This is the best place to start.
The sponsor's community
Sponsor-run events usually draw from the sponsor's own developer community. Their forums and chat groups are full of people who already use the product, which is what you want if you must build with it.
Local meetups and coworking spaces
For in-person events, a local developer or startup meetup is a great source. You can meet people over coffee before the event rather than negotiating in a 48-hour rush. The same goes for coworking spaces, where people already share a room.
Your own network
Colleagues, former coworkers, friends from past projects. The best teammates are people whose work you have seen. A short message to three people you trust often beats a post to three hundred strangers.
Past teammates and past events
If you've entered one hackathon, ask the people you liked working with if they'd do another. A tested team is the cheapest asset in this game.
When you are searching for the event itself, our online list is a good starting point for remote-friendly options, and you can filter by deadline so a team has time to form.
How to pitch yourself
Whether you're posting in a channel or messaging one person, make it easy to say yes. A decent message has five parts:
- Who you are in one line. Your role and what you've shipped.
- What you can do. Name skills and tools, not adjectives.
- What you're looking for. The role you need, not "anyone."
- Logistics. Time zone, hours you can commit, and whether you'll be on a call or async.
- A first step. "Reply here or DM me, and we can do a 15-minute call to compare ideas."
Here is an example. "Backend developer in the US Central time zone, comfortable with Python and cloud APIs. Looking for a designer and someone to handle the demo video for the online event closing next week. I can put in evenings and one weekend day. DM me and we'll talk for 15 minutes." That's specific, short and low-pressure.
Avoid: long manifestos about your startup idea, vague "looking for rockstars" posts, and claiming skills you don't have. Be careful about sharing a secret idea with strangers; most hackathon ideas are less valuable than the execution, and you can always keep the business angle to yourself.
Vet before you commit
Before you agree, do a short call. Ask what they've built, how they like to work, how many hours they can actually give, and what happens if someone drops out. Look at their previous projects. Agree on the rules of the road up front: who decides when you disagree, which tools you'll use, and how you'll split any prize.
It is worth confirming everyone is eligible for the event. As we said in our post on hackathons for adults, some rules require every team member to qualify.
Roles for non-coders
You do not need to write code to be a valuable teammate. Three roles that matter on nearly any team:
- Product manager. Chooses the one problem and the one user, keeps the scope small, tracks the clock and says no to extra features. On a fast project that discipline is worth a lot.
- Designer. Sketches the flow, builds clean screens in a design tool, and makes the demo look credible. Judges respond to polish.
- Pitch and storyteller. Writes the one-line summary, the description and the video script, records the demo and rehearses the delivery. A lot of good projects lose because nobody could explain them.
There's also a fourth: research and testing. Someone who talks to a potential user and tries to break the app is rare and useful. If you're a non-coder, say which role you want in your pitch and show an example of your work. Plenty of events also have no-code or AI-assisted building tracks; browse AI hackathons and beginner hackathons if you are newer to this.
Working remotely
- Pick one chat tool and one shared document on day one.
- Write down the demo path and split it into tasks with owners.
- Do a short check-in at fixed times, and let people work async the rest of the time.
- Time zones: put everyone's local times in the doc and plan handoffs around sleep.
- Merge early and often, so there is a working version at all times.
If it falls apart
Teammates vanish. Plan for it by keeping the scope small enough that two people, or even one, can still submit. Keep notes and code where everyone can reach them. And if you end up solo, the event isn't lost; read how to win a hackathon and trim the demo to what one person can build.