Frequently Asked Questions

Build nights are community gatherings where developers, designers, founders, students, and builders work together on hands-on projects. Build Over Nights is a Kiro x Quick hackathon version of a build night: teams spend an overnight sprint turning ideas into working prototypes for real-world challenges.

Build Over Nights is open to students and working professionals interested in building solutions to real-world challenges. Participants do not need to come from a purely technical background, as the hackathon is designed for multidisciplinary teams.

Yes. Registration for Build Over Nights is free. Participants should bring their own laptop and any equipment they need for their project.

Not necessarily. Build Over Nights is designed for multidisciplinary teams, with roles that may include software development, project management, UI/UX design, and pitching. Teams are encouraged to combine different skills to build their solutions.

Teams may have up to four members. Smaller teams are welcome. Participants are expected to form their own teams before registering, but solo participants are also welcome to register.

No. Workshop participation is not required to join Build Over Nights. However, attending the workshops is highly encouraged, as they provide participants with an opportunity to become familiar with the technologies and tools that may be used during the hackathon. Participants who attend may have an advantage in preparing for the hackathon.

Teams may have up to four members. Solo participants are also welcome to register.

Team changes may be requested while registration is open. Once applications have been reviewed and accepted, changes may require approval from the organizers.

Accepted participants will be notified by email after the application review process. Further announcements will also be shared through the event's official communication channels.

Applications submitted after the registration deadline may not be accepted. If additional slots become available, waitlisted participants may be invited.

Build Over Nights will take place on October 3–4, 2026. The venue is still to be announced — we will share it, along with event-day details and instructions, with participants before the event.

Participants should bring a laptop, charger, and any hardware or equipment required for their project. You are also encouraged to bring personal comfort items, such as pillows, to help you stay comfortable during the overnight build.

Food and refreshments will be provided during the event. Further details about meals and arrangements will be shared with participants before the event.

Venue facilities and event-day logistics will be shared with participants through the official participant guidelines.

Yes. Kiro and Quick are required technologies for Build Over Nights, and other technologies may be added depending on the requirements of your chosen track. Teams are expected to incorporate the required technologies into their development workflow.

Yes. Teams must pick one focus track: Climate Change, Educational Crisis, or Health and Well-Being. See the Tracks section on this page for what qualifies in each track. A generic app with a loosely related feature does not qualify.

Teams may conduct research, brainstorm ideas, and prepare materials such as wireframes before the event. However, the actual development and building of the project should take place during the official hackathon period.

Yes. Teams may use publicly available open-source libraries, frameworks, and similar resources to support development. However, the project itself should not be an existing product that was already built before the hackathon.

Yes. Other AI tools are welcome, but Kiro and Quick are required for this hackathon.

Directly address an environmental problem, such as climate resilience, waste, energy, water, pollution, sustainable agriculture, biodiversity, or resource efficiency. A generic app with a "green" feature does not qualify.

Address a specific barrier in education, such as limited access to learning resources, cost, location, language, learning pace, accessibility, or lack of personalized learning support. A generic app that simply adds an educational feature does not qualify.

Directly address a health or well-being challenge, such as physical health, mental wellness, accessibility, prevention, healthcare access, healthy habits, or community well-being. A generic app with a health-related feature does not qualify.

Teams will be asked to submit key information about their project, including details about the problem they are addressing, their proposed solution, implementation, and overall project direction. Specific submission requirements, formats, and instructions will be announced before the event.

Projects will be evaluated based on several factors. The detailed judging rubric and evaluation guidelines will be shared with participants before the event.

Late submissions may not be accepted. Teams are strongly encouraged to submit all required materials before the deadline to avoid last-minute technical or submission issues.

Winning teams will receive exclusive recognition and prizes. Other prizes and additional details will be announced at the event.

Winners will be announced during the Closing Ceremony and may also be featured through the event's official communication channels after the hackathon.