> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hackersquad.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a team

> Find teammates, use the HackerSquad Discord effectively, and build a balanced team for your hackathon project.

Hackathons move quickly, so finding the right teammates early can make a big difference. A strong team usually combines a clear project idea with a mix of skills that helps the group actually ship something by the end of the event.

## Use Discord to find teammates

HackerSquad has a Discord where builders can connect with other participants before and during the hackathon.

Use Discord to post:

* Your project idea
* Your technical skills
* What kind of project you want to work on
* What kind of teammates you are looking for

This makes it easier for other builders to understand whether they are a good fit for your team.

## What to include in your post

When you introduce yourself in Discord, be specific enough that people know how to respond.

A strong post usually includes:

* Your name or handle
* Your core skills, such as frontend, backend, AI, design, or product
* Whether you already have an idea or want to join someone else's
* The kinds of tools or technologies you want to use
* The type of teammate you are hoping to find

The more clearly you explain your skills and interests, the easier it is for compatible teammates to reach out.

## Good team formation advice

Try to build a team with complementary strengths. A good hackathon team does not need to be large, but it should cover the work needed to design, build, and explain the project clearly.

Helpful team qualities often include:

* At least one person who can build quickly
* Someone who can explain the product clearly
* Teammates who communicate well under time pressure
* A realistic project scope for the event timeline

It is often better to have a small, aligned team than a larger team with unclear roles.

## How to choose teammates well

When you talk to potential teammates, ask simple questions like:

* What do you want to build?
* What are you strongest at?
* How hands-on do you want to be?
* Are you trying to win a specific prize or explore a specific technology?

These conversations help you figure out whether you are aligned on goals, pace, and project direction.

## Be clear about roles early

Once you find teammates, agree on a rough plan early. You do not need a perfect structure, but it helps to know who is leading which part of the project.

For example, you might decide who will focus on:

* Product direction
* Frontend implementation
* Backend or infrastructure
* Demo preparation and submission

Clear ownership reduces confusion later in the event.

<Tip>
  If you do not have a project idea yet, that is okay. Posting your skills and the kinds of problems you want to work on is often enough to find a strong team.
</Tip>

## Next steps

<Columns cols={2}>
  <Card title="Submit a project" icon="folder-plus" href="/builders/submit-a-project">
    Learn what your team will need when it is time to submit.
  </Card>

  <Card title="Builder home" icon="house" href="/builders/home">
    Return to the Builder Portal and keep exploring the event.
  </Card>
</Columns>