Loading...
Registration is on the organizer’s site. Opens a new tab.
Digital divide/deserts, statistics, visualization. Worldwide university students and young professionals.
Topic: Digital divide/deserts, statistics, visualization. Worldwide university students and young professionals.
Format and location: Hybrid; Online → Geneva
Period: 05.01.2026 — 11.09.2026
Registration or submission deadline: deadline not confirmed
Current status: Registration closed
Kazakhstan eligibility: Yes — direct
Target audience: Students and young professionals
Age and other criteria: Under 30 years old
Team: 3–5
Primary language: EN
Fee: not published in verified materials
Awards: Top teams present; winner receives travel/subsistence to Geneva
ITU UMC Data Hackathon 2025–2026 is an event in the field of "artificial intelligence, agents, and data." The recorded thematic formulation is: Digital divide/deserts, statistics, visualization. Worldwide university students and young professionals.. The practical value of participation should be assessed not only by the size of the prize, but also by the quality of the task, access to experts, the suitability of the result for a portfolio, the cost of preparation, and the probability of completing a strong submission in the available time. The status in the catalog is Registration closed, and the editorial priority is A — monitor next cycle. This helps determine the order of work, but is not a rating of the organizer and does not guarantee selection or victory.
For this topic, the central product question is: what user solution is improved by the model and why a standard deterministic process is not enough. A strong team will be able to answer this in one sentence and then prove the answer with a working result. The most appropriate type of final artifact: a working vertical scenario, a set of test cases, an evaluation log, an explanation of the data and model, as well as safe error handling. This is an editorial recommendation derived from the topic; the official mandatory format should only be taken from the event website.
In the card, eligibility is marked as Yes — direct. The basis that was successfully recorded: Worldwide university students and young professionals.. 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" does not always mean the absence of restrictions on citizenship, residency, place of study, age, or sanctions compliance. If the meaning contains "conditionally," 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.
Target audience: Students and young professionals. Fixed criteria: Under 30 years old. Team composition info: 3–5. Before registration, each participant must independently confirm compliance with age, student status, residency, and other personal conditions. Unless permission for solo participation is explicitly stated, do not assume it is allowed. 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," a rational distribution of roles looks like this: 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 for the product, technical result, quality assurance, and final submission. It is useful to agree in writing in advance on contributions, the right to present the project, repository access, use of the result after the event, and the distribution of any 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 designate a person capable of confidently answering jury questions in the required language. For an English-language submission, it is better to use short sentences, labels on diagrams, and subtitles for the demonstration. The goal is precision, not complex style.
Fixed format — Hybrid, location — Online → Geneva. Start: 05.01.2026; end: 11.09.2026; deadline: deadline not confirmed. Travel information: Only after selection; Swiss visa risk. Availability of an online component per card: yes; signs of mandatory in-person presence: no. These signs are derived 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 upload speed for large videos, and the availability of all APIs. Create a technical buffer of at least a few hours and do not leave registration until the moment of submission. For an in-person or hybrid format, first calculate the full budget: visa, flights, accommodation, insurance, local transport, food, and refundable deposits. The wording "travel support" does not mean automatic coverage of all expenses. The value recorded for this event: Only after selection; Swiss visa risk.
Participation cost is recorded as not published in verified materials. Prize information: Top teams present; travel/subsistence to Geneva for the winner. Before making a decision, separate cash payments, grants, cloud platform credits, subscriptions, equipment, mentorship, and marketing wording about total value. Clarify the number of awarded teams, currency, deadlines, taxes, restrictions on receipt, and the necessity to attend the ceremony. If TBA, page discrepancies, or a re-verification 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, public demonstration, feedback, or access to a community. However, paid services, travel, and several weeks of work have an opportunity cost. It is better to make the decision to participate based on three questions: can mandatory requirements be met; can a convincing result be assembled on time; will the created artifact be useful after the winners are announced.
For this direction, the following sequence is useful:
This strategy is not an official evaluation criterion. Its task is to help turn a broad topic like Digital divide/deserts, statistics, visualization. Worldwide university students and young professionals. into an honest, verifiable, and completed prototype.
Fixed risk: Registration closed 31.12.2025; travel only for selected teams.. Next recommended step: Subscribe to ITU Academy and the next UMC call.
The current card does not sufficiently confirm: the exact time and time zone of the deadline; the cost of participation and mandatory payments. These points should be considered open questions, not permission to act on the most convenient assumption.
Practical go/no-go criterion: it is worth applying if the team documentarily meets the eligibility, has access to the mandatory stack, has time to complete the 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 are unclear.