Description:
QISKIT 102 – Implementation Track is an individual hands-on coding competition focused on implementing basic quantum-computing concepts using Qiskit and Python.
Participants will receive a practical quantum-programming challenge with a problem statement, constraints, starter code/notebook, expected outputs, and submission requirements. Before the main challenge, participants will complete an environment check and a short practice task to verify that their Qiskit setup is working correctly.
During the competition, participants will design, implement, execute, and submit their quantum programs within the specified time limit. Submissions will be evaluated primarily on functional correctness, followed by Qiskit implementation quality, interpretation of results, documentation, and reproducibility.
Prior Qiskit experience is helpful, but participants are expected to have basic Python knowledge and an interest in quantum computing.
Duration:
Total Duration: 2–2.5 Hours
Rules & Guidelines:
The competition is individual, with one participant per entry.
Participants should have basic knowledge of Python.
Basic familiarity with quantum-computing concepts is recommended.
Prior Qiskit experience is helpful but not mandatory unless specified by the organizers.
Participants must complete the environment/setup check before the main challenge.
Participants must use the Qiskit environment and versions specified by the organizers.
The challenge problem, constraints, submission format, and evaluation criteria will be provided before the implementation period begins.
Participants must submit their solution before the announced submission deadline.
Late submissions will not be considered unless an official extension is announced by the organizers.
Submitted programs must execute successfully in the specified evaluation environment.
Participants must follow all stated problem constraints.
Participants may use only the resources explicitly permitted by the organizers.
Use of unauthorized AI tools, external assistance, copied solutions, or communication with other participants is prohibited if the competition's published policy disallows them.
Participants must submit their own original work.
Judges may reproduce and execute submitted code to verify correctness.
Submissions that cannot be reproduced because of missing files, dependencies, or required components may receive reduced or no credit according to the published rubric.
Any attempt to manipulate results, submit another person's work, or violate the competition rules may result in disqualification.
The organizers may conduct technical verification or plagiarism/duplicate-submission checks where required.
The final score will be calculated using the published judging criteria.
Judge decisions regarding scoring and rule interpretation will be recorded and followed.
Participants must submit all required code, notebooks, result files, and documentation in the specified format.
The competition rules and judging criteria will not be changed after the challenge begins except where required to correct a technical or administrative issue affecting participants equally.