Candidates / Guide
Take a coding assessment
The coding workspace keeps the problem, editor and execution output together. Check each result before moving on.
On this page
Read before you write
Choose the intended problem. Read Statement, Examples and Constraints, along with the displayed points, time and memory limits. Check the available language before writing.
Keep the remaining session time and the organizer’s rules in mind. A successful example does not establish that the solution handles the problem’s full constraints.
Keep draft, Run and Submit separate
Write and check the active file
Confirm the problem, file and selected language. A Saved or All changes saved indicator concerns the draft on this device; it is not a scored submission or a promise that the code has reached the judge.
Run for feedback
Use Run to test against the sample cases. If the Custom tab is available, use its controls to try your own input. Read compiler feedback and test output. Runs send the code for execution but do not count as scored submissions.
Submit for scoring
Use Submit to send the current solution for evaluation. Check the Attempts panel for that problem. Queued or running means the result is not final; wait for the recorded verdict and test results.
Check again after editing
A previous run or submission belongs to the code sent at that time. Editing afterwards does not update that attempt. Submit the revised solution if you want it evaluated.
Read the recorded outcome
Use the attempt history to distinguish a pending evaluation from a final verdict. Review any available compiler diagnostics, passed tests, execution time and memory information for the selected attempt.
If a run times out or a request cannot be confirmed, read the displayed message. Do not assume that no result exists, or that clicking again has replaced an earlier attempt. Check the history and use the organizer’s support channel when the status remains unclear.
Report a problem and confirm it was sent
Open Report an incident
Choose the issue and add what happened, the problem involved and the approximate time. Device diagnostics accompany the report; avoid unrelated personal information.
Select Submit report
Wait for Report sent before treating it as delivered. You can then use Back to contest.
If you see Report not confirmed
Read the error, retry when appropriate, and contact your organizer through the round’s support channel if delivery remains unconfirmed. Do not assume someone received the report or that a reply will arrive immediately.
Confirm the session finish separately
Check your scored attempts
Before choosing Finish contest, confirm the submissions you intended to have scored. Review the confirmation, then choose Finish and exit only when you are ready. Finishing the session does not turn every saved draft into a scored submission.
Read the Finish receipt
While “Finishing your session…” is shown, keep the window open. “Session finish confirmed” means the server acknowledged the finish request; scored submission results remain a separate check.
Handle an unconfirmed finish
If Access says “Could not confirm session finish”, ask the invigilator to check your session and submissions. A confirmed draft save does not confirm the session finished. The screen does not keep retrying after you leave.
Return through the app
Use Check results status or Back to home after the receipt. If Access reports that device settings still need restoration, follow its recovery guidance and seek help if it cannot complete.
Still need help?
Contact your assessment organizer for invitation, timing, or in-round support. For other questions, contact the Access team.