Overview
TechCal’s Hackathon Team Formation system helps you:- Create teams for upcoming hackathons
- Join existing teams looking for members
- Find compatible teammates based on skills
- Collaborate in real-time with team chat
- Track participation and team analytics
Team formation is only available for hackathons listed on TechCal. Not all hackathons support this feature (depends on organizer integration).
Discovering Hackathons
Hackathons appear in:- Discover page: Filter by category = “Hackathons”
- Calendar view: Look for purple-colored event blocks
Hackathon Detail Page
Click any hackathon to view:- Event details: Dates, location/virtual, rules, prizes
- Teams tab: Browse existing teams or create your own
- Register button: Official hackathon registration link
Creating a Team
Click Create Team
Fill out the team creation form:Required fields:
- Team Name: Unique name for your team (3-50 characters)
- Description: What your team is working on or looking for (max 500 characters)
- Looking for Members: Toggle ON if you want others to join (default: ON)
Team Creator Privileges
As the creator, you can:- Edit team name and description
- Toggle “Looking for Members” status
- Delete the team (only if no other members have joined)
You can only create one team per hackathon. This prevents spam and ensures commitment.
Joining a Team
Browse Teams Tab
On the hackathon page, go to the Teams tab to see all teams.Teams are displayed with:
- Team name
- Description
- Member count (e.g., “3 / 5” if max size is 5)
- “Looking for members” badge
- Creator’s name
View Team Details
Click a team card to see:
- Full description
- List of current members
- Skills represented on the team
- Team chat preview
Click Join Team
If the team is accepting members, click Join Team.Validation checks:
- Team must have space (not full)
- You can’t already be in another team for this hackathon
- Hackathon registration must still be open
Leaving a Team
To leave:- Go to the team page
- Click Leave Team button
- Confirm in the dialog
Leaving a team does NOT unregister you from the hackathon. You’re still participating, just without a team.
Team Capacity Validation
Max Team Size
Each hackathon sets a max team size (typically 2-10 members):- Small teams (2-3): Focus, agility
- Medium teams (4-5): Balanced roles
- Large teams (6+): Complex projects
Current Capacity Display
Team cards show:3 / 5 membersThis means 3 current members, 5 maximum. Still 2 spots available.
Finding Compatible Teammates
Skill-Based Matching (Basic)
When you register for a hackathon, TechCal asks for your skill proficiencies:Skill Proficiencies Form
Skill Proficiencies Form
For each skill, select your level:
- Beginner: Just learning, can contribute with guidance
- Intermediate: Comfortable, can work independently
- Advanced: Expert, can mentor others
- Expert: Deep expertise, can architect solutions
- Frontend: React, Vue, Angular
- Backend: Node.js, Python, Django
- Mobile: iOS, Android, React Native
- AI/ML: TensorFlow, PyTorch
- Design: Figma, UI/UX
Finding Compatible Teammates
Browse registered participants to find teammates with complementary skills. Look for users who have:- Skills that complement your team’s needs
- Similar experience levels for your target difficulty
- Matching collaboration preferences
Looking for: Backend developer, AI/ML specialist [View Profile] [Invite to Team]
This feature requires completing your hackathon registration form with detailed skill proficiencies.
Team Chat
Real-Time Collaboration
Every team has a built-in chat:- Real-time messaging
- User mentions (@username)
- Link previews
- Message history (persists for duration of hackathon)
Accessing Team Chat
- Go to your team page
- Click the Chat tab
- Type messages in the input box at the bottom
Chat Features
Real-Time Updates
Messages appear instantly for all team members using WebSocket connections.
User Presence
See who’s online with green status dots next to names.
Message History
Scroll up to view past messages (last 100 messages loaded).
Link Previews
Paste URLs and see automatic previews (GitHub repos, design files, etc.).
Chat Best Practices
Coordinate Early
Coordinate Early
As soon as your team forms, hop in chat and:
- Introduce yourselves
- Share timezones and availability
- Discuss project ideas
- Assign roles (frontend, backend, design, etc.)
Use External Tools for Code
Use External Tools for Code
TechCal chat is for coordination, not code collaboration. Use:
- GitHub: Code repositories
- Figma: Design files
- Google Docs: Planning documents
Set Check-In Times
Set Check-In Times
Agree on regular check-ins (e.g., “Let’s sync in chat at 9am PST daily”) to keep everyone aligned.
Respect Timezones
Respect Timezones
Hackathon teams often span multiple timezones. Use tools like worldtimebuddy.com to find overlapping hours.
Hackathon Registration Data
When you register for a hackathon in TechCal, you provide:Required Information
- Participation status:
registered: Signed up, no team yetteam_formed: Joined or created a teamsubmitted: Submitted projectwinner: Won a prize
Optional Team-Building Fields
Preferred Team Role
Preferred Team Role
What role do you want on the team?
- Frontend Developer
- Backend Developer
- Full-Stack Developer
- Designer (UI/UX)
- Data Scientist / ML Engineer
- DevOps / Infrastructure
- Product Manager
- Marketing / Business
Collaboration Style
Collaboration Style
How do you prefer to work?
- Pair programming
- Independent tasks with check-ins
- Mob programming (whole team codes together)
- Async (work on your own time)
Team Size Preference
Team Size Preference
Ideal team size:
- Solo (just me)
- Small (2-3 people)
- Medium (4-5 people)
- Large (6+ people)
Communication Preferences
Communication Preferences
How should the team communicate?
- Voice chat (Discord, Zoom)
- Text chat only
- Video calls
- Async messages
Mentorship Preference
Mentorship Preference
Are you looking for mentorship or willing to mentor?
- Seeking mentorship
- Willing to mentor
- Peer collaboration (no mentorship)
Availability Pattern
Availability Pattern
When can you work on the project?
- Weekdays only
- Weekends only
- Full availability
- Specific hours (e.g., “Evenings PST”)
Project Type Preferences
Project Type Preferences
What do you want to build?
- Web app
- Mobile app
- AI/ML project
- Game
- Hardware/IoT
- Blockchain
- Open source contribution
Participation Analytics
Track your hackathon journey:Your Hackathon Dashboard
Go to Dashboard → Hackathons to see:- Total hackathons participated: Count of hackathons you’ve registered for
- Teams formed: How many teams you’ve created
- Teams joined: How many teams you’ve joined
- Projects submitted: Count of submissions
- Wins: Prizes won
Team Analytics (Team Page)
On your team page, view:- Member activity: Who’s been active in chat
- Skill coverage: Visual breakdown of team skills
- Collaboration score: How engaged the team is
Analytics are private to team members only. Other users can’t see your team’s activity level.
Team Lifecycle
Before Hackathon
-
Team Formation (1-4 weeks before)
- Create or join team
- Discuss project ideas in chat
- Assign roles
-
Preparation (1 week before)
- Finalize project idea
- Set up repos and tools
- Coordinate schedules
During Hackathon
-
Kickoff (Day 1)
- Quick sync in chat or voice
- Divide tasks
- Start building
-
Collaboration (Days 1-N)
- Regular check-ins
- Share progress
- Help each other with blockers
-
Submission (Last day)
- Finalize project
- Prepare presentation
- Submit via hackathon platform
After Hackathon
- Post-Event
- Update participation status to
submitted - If you win, update to
winner - Team chat remains accessible for 30 days post-hackathon
- Update participation status to
Common Scenarios
- I'm a Beginner
- I Have a Project Idea
- I'm Looking for Teammates
- My Team Isn't Active
Finding your first team:
- Look for teams tagged as “Beginner-friendly” or “Open to newcomers”
- In your registration, set Mentorship Preference to “Seeking mentorship”
- Browse teams and message creators directly: “Hi! I’m new to hackathons and would love to join. I know basic Python and am eager to learn.”
- Offer to handle non-coding tasks: documentation, testing, design (if applicable)
Troubleshooting
Can't create a team
Can't create a team
Possible causes:
- You already have a team for this hackathon
- Registration deadline has passed
- Hackathon status is not “active”
- Delete your existing team (if no other members joined)
- Or leave your current team first
- Check registration deadline in hackathon details
Team is full but shows 'Looking for members'
Team is full but shows 'Looking for members'
Cause: Team creator forgot to toggle off the “Looking for members” setting.Solution: Try joining anyway—TechCal will show an error if truly full. If it persists, message the team creator.
Chat messages not appearing
Chat messages not appearing
Cause: WebSocket connection lost or network issue.Solution:
- Refresh the page
- Check your internet connection
- Try a different browser
- If issue persists, contact support@techcal.com
Can't join any team
Can't join any team
Possible causes:
- You’re already in a team for this hackathon
- All teams are full
- Registration deadline passed
- Leave your current team if you want to switch
- Create your own team
- Check registration deadline
Team creator left the team
Team creator left the team
What happens: If the team creator leaves, the next member (by join date) becomes the new creator automatically.If all members leave, the team is deleted.
Best Practices for Successful Teams
Start Small, Think Big
Start Small, Think Big
Don’t over-commit. Build a minimum viable project first, then add features if time allows. Many winning projects are simple but polished.
Assign Clear Roles
Assign Clear Roles
Within the first hour of forming, assign:
- Tech lead: Makes final tech decisions
- Frontend: UI implementation
- Backend: APIs and data
- Design: Mockups and UX
- PM: Keeps team on track, manages time
Set Milestones
Set Milestones
Break the hackathon into phases:
- Hour 1-2: Ideation and planning
- Hour 3-12: Core feature development
- Hour 13-20: Integration and testing
- Last 4 hours: Polish, presentation, submission
Over-Communicate
Over-Communicate
Check in every 2-4 hours:
- “Just finished the login API, working on auth next”
- “Stuck on a bug, need help with state management”
- “Taking a 1-hour break, back at 3pm”
Prepare Your Demo Early
Prepare Your Demo Early
Don’t wait until the last hour. By the 80% mark, have:
- A working demo (even if incomplete)
- A slide deck or script
- A video walkthrough (if required)
Next Steps
Find Hackathons
Browse upcoming hackathons on the Discover page
Complete Your Profile
Set up your public profile to attract teammates
Ready to build something amazing? Find a hackathon, form a team, and ship your project with TechCal.