Builder Guide

HackerSquad AI Remote Hackathon — Official Rules

1. Build something with AI

Your project must use AI as a meaningful part of its functionality. Agents, developer tools, research applications, creative tools, and other AI-powered projects are welcome.

2. Participate solo or in a team of up to four

Every team member must be registered and approved for the hackathon. Each participant may join one team, and each team may submit one project.

3. Show what you built during the hackathon

The building period runs from October 23, 2026 at 6:30 PM Pacific through November 8, 2026 at 7:30 PM Pacific.

You may build on an existing project, but clearly identify what existed beforehand and what your team created during this period. Judges will evaluate the work completed during the hackathon.

4. Use the tools that help you build

AI coding assistants, APIs, open-source libraries, starter templates, and no-code tools are allowed.

Credit substantial third-party contributions, follow applicable licenses, and explain your team’s contribution. You must understand and be able to explain your submission.

5. Submit a working prototype

Your project must demonstrate its core functionality. Clearly label mocked features, sample data, and unfinished components. Slides or a concept alone are insufficient.

6. Make your Git repository public

Your project’s Git repository must be public and accessible without an invitation or access request so organizers and judges can review your work. Include its URL in your submission and keep it public throughout judging and review.

The repository must contain:

• The project’s source code.
• A README explaining what the project does and how it uses AI.
• Instructions for setting up and running the project.
• Required dependencies and environment variables, documented using placeholders.

Never commit API keys, credentials, or private data.

7. Provide a complete submission

Your submission must include:

• A project name, short description, and team roster.
• The problem you address and how your project uses AI.
• A demo video of up to three minutes showing the project in action.
• Your public Git repository URL.
• A working app link or instructions for running the project.
• A brief disclosure of pre-existing work, major tools, third-party components, and material assistance from outside your team.

8. Meet the submission deadline

Submit through the official HackerSquad submission page by November 8, 2026 at 7:30 PM Pacific Standard Time (UTC−8).

Keep your repository and demo links accessible throughout judging.

Identify the Git commit or release that represents your submission at the deadline. Later changes will not count toward evaluation unless organizers announce an extension for everyone.

9. Judging criteria

Judges will assess what your project demonstrates and what your team can substantiate. They may request clarification or a walkthrough.

10. Respect people, privacy, and security

Treat participants, mentors, judges, and organizers respectfully. Harassment, discrimination, plagiarism, fabricated results, and interference with another team’s work are prohibited.

Use only data and systems you have permission to access. Do not expose private information, publish credentials, or conduct unauthorized security testing.

11. Keep ownership and give proper credit

You retain ownership of your original work. Submit only material you have the right to use and share, and credit third-party contributions. Participation does not require transferring your intellectual property, but a public Git repository is required.

Mentorship and general advice are welcome. Disclose material outside assistance and any relationship with a judge that could create a conflict of interest. Judges must not score projects where they have a conflict.

12. Follow official event updates and decisions

The HackerSquad event page is the source of truth for submission instructions, judging announcements, and any prizes. Rule or deadline changes will be communicated to all participants.

Organizers may disqualify entries for material rule violations and will explain the reason. Judging decisions are final.