Participation of a team from Kazakhstan

In the card, eligibility is marked as Conditional. The basis that was captured: Students in grades 9–11; exact selection geography is not disclosed.. These two lines must be read together. The phrasing "Kazakhstan is not excluded" is weaker than a direct invitation to participants from all over the world, and the word "international" by itself does not always mean the absence of restrictions on citizenship, residency, place of study, age, or sanctions compliance. If the value contains "conditional," if the evidence is indirect, or if legal rules have not yet been published, it is worth getting a written response from the organizer before spending time.

The recommended request to the organizer should state the country of residence and citizenship, the proposed team composition, age or student status, the method of receiving the prize, and the chosen format of participation. It is better to save the response together with a snapshot of the rules version. Separately, check whether the platform applies its own restrictions, whether a Kazakhstani bank can receive the payment, whether a tax form is required, and whether it is permitted to participate on behalf of a company. These are not additional rules for this hackathon, but a standard risk check for an international application.

Who it is suitable for and how to assemble a team

Stated audience: School students. Recorded criteria: Grades 9–11. Information about team composition: not published in verified materials. Before registration, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. If permission for individual participation is not explicitly stated, it should not be considered permitted. If the maximum team size is unknown, do not register extra people until you receive a response from the organizer.

For a task in the field of "artificial intelligence, agents and data", the rational distribution of roles is as follows: ML/agent engineer, product/backend developer, UX/domain researcher and eval/demo lead. One person can combine several functions, but there must be clear owners of the product, technical result, quality assurance and final presentation. It is useful to agree in writing in advance on the contribution, the right to represent the project, access to the repository, the use of the result after the event and the distribution of the potential prize. Such an internal agreement is a recommendation and does not replace the platform's terms.

The working language is specified as EN. Even if the team communicates in Russian or Kazakh, prepare a unified glossary of terms in advance and a person capable of confidently answering the jury's questions in the required language. For an English-language presentation, it is better to use short sentences, labels on diagrams and subtitles for the demonstration. The goal is accuracy, not a complex style.

Format, calendar and logistics

The fixed format is In-person, location — Almaty. Start: 03.04.2026; end: 04.04.2026; deadline: deadline not confirmed. Transport information: Not required. Availability of an online component by card: no; signs of mandatory in-person attendance: yes. These signs are obtained only from the field text and do not override event-specific rules.

For an online format, it is important for a team from Kazakhstan to convert the deadline to their time zone, check the time of mandatory sessions, the download speed of large video and the availability of all APIs. Create a technical buffer of at least a few hours and do not leave registration for the moment of submission. For an in-person or hybrid format, first calculate the full budget: visa, flight, accommodation, insurance, local transport, food and refundable deposits. The wording "travel support" does not mean automatic coverage of all costs. The value fixed for this event: Not required.

Entry fee, prizes and real value

The participation cost is recorded as not published in verified materials. Prize information: 250k / 200k / 150k ₸. Before making a decision, separate cash payments, grants, cloud platform credits, subscriptions, equipment, mentoring and marketing wording about total value. Clarify the number of winning teams, currency, deadlines, taxes, receipt restrictions and the need to be present at the ceremony. If TBA, page discrepancies or a re-check requirement appear in the field, the amount cannot be used as guaranteed income.

Even without a cash prize, an event can be useful if it provides a strong case, a public demonstration, feedback or access to a community. But paid services, travel and several weeks of work have an opportunity cost. It is better to make a decision about participation based on three questions: is it possible to fulfill the mandatory requirements; is it possible to assemble a convincing result on time; will the created artifact be useful after the winners are announced.

Recommended project strategy

For this direction, the following sequence is useful:

This strategy is not an official evaluation criterion. Its goal is to help turn a broad topic AI/programming. Students of grades 9–11; exact selection geography is not disclosed. into an honest, verifiable, and completed prototype.

Known risks and gaps

Fixed risk: Invited/regional selection is possible.. Next recommended step: Clarify geography with the organizer in March 2027.

The current card does not sufficiently confirm: exact deadline time and time zone; team formation limits and rules; participation cost and mandatory payments. These points should be considered open questions, not permission to act on the most convenient assumption.

Practical go/no-go criterion: you should apply if the team documentarily meets eligibility, has access to the mandatory stack, has time to complete a verifiable scenario, and accepts financial and logistical risks. Participation should be paused if the admission of Kazakhstan, submission rights, mandatory in-person presence, cost of critical services, or the procedure for paying a significant prize is unclear.

Sources and confidence level