Hackathon Projects

All teams must submit a slide deck that describe at least:

1. The team members and project name.

2. The problem that your solution addresses. Include:

   1. Who is impacted (teachers? students? someone else?) and how.

   2. Any contextual background that might help a non-expert evaluate the project (e.g., if your project was a personalized learning tool, you might have a slide that briefly explains what personalized learning is and why it’s valuable). 

3. The solution you're proposing. Include:

   1. How your technology works and would address the problem.

   2. Any advantages or disadvantages of your solution over existing solutions

   3. Ideally, a demo or video of your MVP solution. 

Each project will be evaluated using the following rubric:

1. Exclusive Presentation Opportunity at StartEd Shark Tank (Virtual, Q2):

• As the winning team, you will present your solution in front of industry-leading investors, educators, and entrepreneurs during our virtual StartEd Shark Tank. This platform is designed to help promising innovations gain visibility and valuable feedback from top-tier professionals in the education technology sector.
  
  

2. Fast-Track to EDTECH WEEK 2025’s Shark Tank:

• Priority consideration: Your team will receive priority consideration for pitching at EDTECH WEEK 2025’s prestigious Shark Tank.

• Guaranteed Registration: Your team will enjoy 1 guaranteed registration to EDTECH WEEK 2025 ($800 value).

• Chance for a Six-Figure Investment: Compete for the top prize—a six-figure investment—while connecting with influential investors and leaders in the EdTech ecosystem.

• Team Size: Teams can be any size but we recommend 3-6. We may need to adjust recommended sizes once we know how many participants there are, to ensure there aren't too few or too many projects for the judges

• Team Formation:  Teams will form during our kickoff meeting on January 27th at 6:30pm. Participants will use this FigJam board to form teams (opens during kickoff). You will have time to introduce yourself to people in breakout rooms to form teams. Feel free to start connecting offline! 

• Support Forming Teams: Reach out to us at edtech-hackathon-leads@googlegroups.com if you want help finding a team or if you’re experiencing any interpersonal difficulties.

• Team Coordinator: Each team should elect a team coordinator who can be responsible for ensuring the team is making progress and provide updates to the hackathon staff. We’ll check in periodically to make sure everyone is on track!

Our Pledge

In the interest of fostering an open and welcoming environment, we as participants, judges, and organizers pledge to make participation in our hackathon and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

• Using welcoming and inclusive language

• Being respectful of differing viewpoints and experiences

• Gracefully accepting constructive criticism

• Focusing on what is best for the community

• Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

• The use of sexualized language or imagery and unwelcome sexual attention or advances

• Trolling, insulting/derogatory comments, and personal or political attacks

• Public or private harassment

• Publishing others’ private information, such as a physical or electronic address, without explicit permission

• Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Organizers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Organizers have the right and responsibility to remove, edit, or reject comments, communications, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any participant or judge for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the organizers at edtech-hackathon-leads@googlegroups.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The organizers are obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Organizers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the hackathon leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq

The hackathon organizers don’t have any claim to your intellectual property, but we are allowed to share anything you share with us.

The following terms apply to participation in this hackathon ("Hackathon"), and are provided by Google Open Source. 

• Entrants may create original solutions, prototypes, datasets, scripts, or other content, materials, discoveries or inventions (a “Submission”). The Hackathon is organized by the Hackathon Organizer.

• Entrants retain ownership of all intellectual and industrial property rights (including moral rights) in and to Submissions.

• As a condition of submission, Entrant grants the Hackathon Organizer, its subsidiaries, agents and partner companies, a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to use, reproduce, adapt, modify, publish, distribute, publicly perform, create a derivative work from, and publicly display the Submission.

• Entrants provide Submissions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.