HackerMate

Inspiration

Hackathons are supposed to be about building, but one of the hardest parts often happens before the building even starts: finding the right teammates.

Most participants still rely on WhatsApp groups, Discord servers, spreadsheets, or random last-minute messages to form teams. That usually means people choose teammates based on who replies first rather than who actually complements their skills, experience, and goals.

We built HackerMate to make team formation more intentional and to give hackathon teams a single place to go from finding each other to actually shipping together.

What it does

HackerMate is a team operating system for hackathon builders.

Participants can create builder profiles that showcase their skills, interests, availability, projects, and track record. They can then discover other builders based on what their team is missing instead of scrolling through hundreds of unstructured messages.

Once a team is formed, HackerMate provides a shared workspace where members can:

• Chat and coordinate
• Manage tasks
• Brainstorm ideas
• Share useful resources
• Connect GitHub activity
• Track progress and deployments
• Review their pitch
• Organize the team from one place

HackerMate also includes hackathon discovery, team pages, connections, notifications, messaging, and tools designed specifically around the hackathon journey.

For organizers, HackerMate can also support dedicated event-based team matching through custom participant links, helping participants form teams before the hackathon starts.

Our goal is simple:

Find → Review → Merge → Build → Ship.

How we built it

HackerMate is built as a modern full-stack web application using:

• Next.js
• React
• TypeScript
• Supabase
• PostgreSQL
• Supabase Auth
• Realtime features
• Vercel

The platform uses structured builder profiles and team data to create a more useful discovery experience than a traditional participant directory.

We built separate experiences for builder discovery, profiles, teams, team workspaces, messaging, hackathons, notifications, onboarding, and collaboration tools while keeping them connected through the same product.

A major focus during development was ensuring that HackerMate works well across both desktop and mobile devices, since hackathon participants frequently use the platform while actively attending events.

Challenges we ran into

One of the biggest challenges was building something that goes beyond simply being another teammate directory.

Team formation is only useful if the platform remains valuable after the team is created, so we had to think about the complete participant journey: discovery, evaluation, team formation, collaboration, and eventually submission.

We also had to work through challenges involving:

• Real-time collaboration and messaging
• Authentication and authorization
• Privacy around builder profiles and personal information
• Team permissions and workspace access
• Responsive design across many complex product surfaces
• Maintaining consistent data across builders, teams, hackathons, and collaboration features
• Designing a product that stays useful during the fast-paced environment of an actual hackathon

As HackerMate grew, maintaining consistency across a large number of pages and workflows became another major engineering and product-design challenge.

Accomplishments that we're proud of

We're proud that HackerMate has grown from a teammate-matching idea into a much more complete hackathon ecosystem.

Some of the things we're especially proud of include:

• A real builder discovery and profile system
• Team creation and discovery
• A complete collaborative team workspace
• Messaging, connections, and notifications
• Hackathon discovery and event-specific experiences
• GitHub and project-oriented collaboration features
• Pitch and team-building tools
• A responsive experience designed for both desktop and mobile
• A platform that is already being positioned for collaborations with hackathon organizers

Most importantly, HackerMate is a working product rather than just a prototype or landing page.

What we learned

Building HackerMate taught us that matching people is not only a technical problem.

A good teammate cannot be represented by a single skill tag. Availability, complementary skills, experience, proof of work, interests, and team requirements all matter.

We also learned how quickly complexity grows once a product supports real users, teams, permissions, collaboration, messaging, events, and multiple workflows at the same time.

That pushed us to think much more carefully about product architecture, privacy, authorization, responsive design, and the overall user journey rather than treating each feature independently.

What's next for HackerMate

The next step is expanding HackerMate from a team-formation and collaboration platform into a broader operating layer for hackathons.

We are exploring features for offline events such as:

• Participant QR passes
• Venue check-in
• Meal and food-coupon redemption
• Swag distribution tracking
• Organizer dashboards
• Team attendance visibility
• Event announcements
• Mentor and participant coordination

The idea is for organizers to eventually use HackerMate not only to help participants find teammates, but also to manage important parts of the participant experience during the event itself.

We also plan to continue improving matching quality, builder reputation and track records, team collaboration, organizer tools, and integrations with the wider hackathon ecosystem.

Our long-term goal is for HackerMate to become the infrastructure that connects the entire hackathon journey — from finding the right people to shipping the final project.

Built With

• javascript
• next.js
• python
• supabase
• typescript