AI Hardware Hackathon
The team builds a working prototype, presents it at a booth and solves a mystery task.
- Grade
- Grades 7–9
- Team
- Exactly 3 participants, 1 mentor
- Final
- Up to 20 teams, one per region
Sections
Where mentors should start
- Apply for AI Hardware Hackathon on the RoboZerde website.
- Select “Create a team” at robozerde.artisan.education, register at learn.artisan.education or sign in to your existing account, and create a team.
- Share the link provided after team creation with all three students so they can register, join the team and begin learning.
Stages and deadlines
| Stage | Dates |
|---|---|
| Registration | 5–26 November |
| Training and project | 1–26 November |
| Video and presentation | 1–26 November |
| Selection results | Preliminary — 28 November; final — by 30 November |
| PiBody Lite kits for finalists | 30 November — 1 December, after the finalists are confirmed |
| Preparation for the final | 30 November — 4 December |
| Final | 5–6 December |
Registration runs from 5 to 26 November inclusive, until 23:59 on 26 November, Astana time. Training takes place from 1 to 26 November. Videos and presentations are accepted from 1 to 26 November; submissions close at 23:59 on 26 November, Astana time.
Video and presentation
The team completes the courses, builds its project and submits a video and presentation by 23:59 on 26 November, Astana time. Assessment takes place on 27–28 November; preliminary results are published on 28 November, and the final list of finalists is approved by 30 November after appeals have been reviewed.
4.1. Training on the platform (1–26 November)
1. Participants take the general hackathon course at learn.artisan.education. It includes lessons in programming, 3D‑modelling, AI and “Startup”.
2. Training points are awarded to the team: the progress of all three participants in the general hackathon course counts towards the score. Progress is calculated automatically.
3. The courses open on 1 November. Teams that register later complete the training on an accelerated schedule.
4.2. Project
1. The team develops an idea for an AI‑device that solves a real problem and builds a working prototype.
2. The prototype may be built using any electronics: Arduino, micro:bit, Raspberry Pi, LEGO, PiBody and other kits.
3. The project must include a role for AI in the device and a 3D‑model.
4.3. Video (1–26 November, until 23:59)
| Requirement | Specification |
|---|---|
| Where | any service: YouTube, Google Drive, Instagram, etc. |
| How to submit | as a link in the email containing the presentation, sent to info@artisan.education |
| Access | accessible via the link without requesting access |
| Format | any format, up to 3 minutes |
| Language | Kazakh or Russian |
| On screen | all 3 participants |
1. Recommended structure: team and problem (0:00–0:30), prototype in operation (0:30–1:30), role of AI and 3D‑model (1:30–2:30), benefits and plans (2:30–3:00).
2. The video is not uploaded to the platform — the jury views it via the link.
3. The video must not be deleted or access to it restricted up to and including 25 November. If the video is inaccessible, the team is eliminated from the selection stage.
Keep the video available by link while judging is under way.
4.4. Presentation (1–26 November, until 23:59)
| Requirement | Specification |
|---|---|
| Where to send | info@artisan.education |
| Email subject | “AI Hardware Hackathon — [team name] — [region]” |
| In the email | video link, team name, region, school, full names of participants and mentor |
| Length | 8–10 slides |
| Format | PDF, 16:9, up to 20 MB; larger files — a Google Drive link with public access |
| Language | Kazakh or Russian |
Slide structure:
1. Slide 1 — project title, team, school, region.
2. Slides 2–3 — the problem and who faces it.
3. Slides 4–5 — the solution: how the device works, a diagram, a 3D‑model.
4. Slides 6–7 — the role of AI, photos of the prototype, test results.
5. Slides 8–10 — users and benefits, plans, team roles.
The presentation template can be downloaded from the hackathon website robozerde.artisan.education in the “Documents” section.
Materials submitted after 23:59 on 26 November will not be assessed.
- Email subject
- AI Hardware Hackathon — [team name] — [region]
Qualification scoring
The selection stage is scored out of 100 points: 50 for training on the platform and 50 for the video and presentation.
| Component | What is assessed | Points |
|---|---|---|
| Training | Completion of the general hackathon course, combined progress of all three participants, calculated automatically | 50 |
| Video and presentation | Idea: a real problem and a clearly defined user. Prototype: the device is assembled and works. The role of AI in the device and a 3D-model. Delivery: a clear structure, with all participants appearing in the video. | 50 |
| Total | 100 |
1. The team with the highest score in its region advances to the final.
2. Selection assessment takes place on 27–28 November. The preliminary list is published on 28 November; appeals are accepted within 24 hours of publication. The final list of finalists is approved by 30 November after appeals have been reviewed.
3. Selection points do not carry over to the final.
Final: booth, pitch and mystery task
The final takes place on 5–6 December; every team must present its project at a stand and complete a secret task.
1. Day 1 (5 December): all teams display their projects at stands. Anonymous judges work among the guests: they listen as ordinary visitors and assess the projects. Teams are selected to pitch based on their assessments.
2. Day 2 (6 December): the selected teams deliver a pitch to the jury.
3. All teams complete the secret task: on the first day — a practice round with simple tasks; on the second — the main task.
6.1. Preparation of finalists
1. After the final list of finalists is approved, from 30 November to 1 December, each finalist team is sent a PiBody Lite kit.
2. From 30 November to 4 December, the team completes projects on the platform and prepares its stand, project explanation and pitch.
3. The selection-stage project may be refined before the final. Replacing it with a different project is not permitted.
6.2. Project: stand and pitch
1. At the stand: a working prototype, a poster (problem, solution, team), and a 3D‑model on screen or as a printout.
2. The organiser provides a table and a power socket. The team brings everything else itself.
3. The stand operates on the first day. The team explains its project to every visitor — some of them are anonymous judges.
4. The pitch takes place on the second day, for selected teams only: up to 5 minutes for the presentation and up to 5 minutes for questions from the jury. Any participant may answer.
5. The order of presentations is determined by drawing lots.
6.3. Secret task
1. The engineering task is performed using Artisan kits: no assembly is required, only programming — in Python or Blockly.
2. A practice round with simple tasks is held on the first day. The main task specifications are revealed on the second day.
3. Multiple attempts are permitted; the best attempt counts towards the score.
7. Final scoring
The final is scored out of 100 points separately from the selection stage: 50 for the project and 50 for the secret task.
| Component | How it is assessed | Points |
|---|---|---|
| Project: stand and pitch | Anonymous judges assess the project at the stand; for selected teams, they also assess the pitch and answers to questions | 50 |
| Secret task | Points for each completed item; the best attempt counts towards the score | 50 |
| Total | 100 |
1. The criteria for the secret task are published with the main task specifications on the second day.
2. Winners and prize winners are determined by the total points scored in the final.
Allowed and not allowed
Disqualification, appeals and contacts
A team is eliminated from the category if it:
1. Deletes its video or restricts access to it up to and including 25 November.
Keep the video available by link while judging is under way.
2. Passes off someone else’s project, video or presentation as its own.
3. Violates the prohibitions for the final set out in clause 6.4.
4. Includes a person who was not declared at registration, without the organiser’s consent.
Appeals:
1. For the remote selection stage, the mentor submits an appeal to info@artisan.education within 24 hours of publication of the preliminary results, in accordance with clause 6.2 of the Regulations.
2. In the final, an appeal is submitted to the chief judge before the results are announced.
3. The decision on an appeal is final.