Description
Tech Marathon is a team-based, multi-stage technical competition designed to test sustained problem-solving, programming, debugging, logical thinking, and engineering skills.
Teams of 2–4 members will first complete a short screening/qualifier and receive a briefing on the competition format, submission process, scoring system, and rules. Shortlisted teams will then participate in the main marathon, where they will solve a sequence of technical challenges released in multiple stages.
The challenges may include programming, debugging, logical reasoning, optimization, and practical engineering problems. Each stage will have a fixed time limit and clearly defined submission requirements. Teams will be evaluated primarily on correctness, with additional consideration given to efficiency, robustness, reasoning, and code quality.
Duration
Total Duration: 3–5 hours
Rules & Guidelines
The competition is team-based, with 2–4 members per team.
Each participant may be part of only one registered team.
Teams must complete the registration and eligibility verification before participating.
A screening/qualifier round will be conducted before the main marathon.
Participants must attend the rules and format briefing before the competition begins.
The challenges will be released in multiple stages.
Each stage will have a clearly announced time limit and submission deadline.
Teams must submit their solutions through the official submission platform or method provided by the organizers.
Only submissions received before the announced deadline will be considered.
Teams may use only the programming languages, software, libraries, and other resources permitted by the organizers.
Unauthorized assistance, communication with other teams, or use of prohibited resources is not allowed.
Teams must submit their own original solutions.
Any attempt to copy, manipulate submissions, or violate the competition rules may result in disqualification.
Solutions will be evaluated primarily based on correctness and successful test-case execution.
Additional scoring may be awarded according to the published criteria for efficiency, robustness, reasoning/documentation, and code quality.
Participants must report technical problems to the event support team as soon as they occur.
Technical issues with the official platform will be handled according to the event's published contingency procedure.
The final score will be calculated using the published scoring system.
In case of a tie, the earlier accepted/final qualifying submission time will be used as the tie-break, unless another tie-break is announced before the competition.
Judges' decisions regarding evaluation and rule interpretation will be final.
Teams must remain available during the designated competition period and follow organizer instructions.
The organizers may take necessary operational decisions to ensure fair and smooth conduct of the competition.