1. LandOffer
  2. Blog
  3. All articles
  4. Codility Assessment Timing: Open the Invite, Save Work, and Submit Safely

Job search

Codility Assessment Timing: Open the Invite, Save Work, and Submit Safely

Prepare for a Codility invite by checking the test window, understanding the non-pausable timer, preserving code, and confirming submission.

9 min readLandOffer team

If you receive a Codility invitation, open the link early enough to read the assessment instructions and check the task count and total time. Codility says you can leave and return before pressing Start. After you start, the timer cannot be paused, so begin only when you can stay for the full session. The employer’s deadline to start and the timed session are separate limits; check both in your invitation and on the intro page.

Codility also says it saves code automatically, but saving is different from submitting. You can move among tasks before submitting; once you submit a solution, you cannot modify it. Run the available tests, review the task instructions, submit deliberately, and look for the completion state shown for your assessment. The hiring team controls whether you later see results. Once you have planned your session, browse recent roles on LandOffer.ai if you are still building a shortlist.

A candidate reviews an assessment invitation, checks a single uninterrupted timer, and moves a saved code draft through test and final submission checkpoints.

Check the invite before starting the clock

The assessment link can be useful before you are ready to take the test. Codility’s candidate guidance says the introductory page can show the assessment policies set by the testing team, how many tasks you will solve, and the time limit. You may leave and return before pressing Start. Use that preview to decide whether the session fits your schedule and whether the stated language or environment suits the invitation.

Read the employer’s own instructions carefully. They set the testing window and may describe permitted resources, accommodations, environment requirements, or a separate follow-up step. The invitation’s “complete by” date is not necessarily the amount of time you have once you begin. Codility describes the testing window as the administrator’s allowed period to start; the assessment countdown begins with the session. Write down both times in your local time zone if the invite gives a date or deadline.

The exact assessment length is set by the administrator and appears on the intro page. Codility says many assessments take between 30 minutes and two hours, but that typical range does not tell you what your invitation contains. Use the time displayed for your own test. It applies to the full assessment, not necessarily to each individual task. If you cannot tell when the timer starts, whether you can return, or which time zone applies, ask the recruiter or assessment contact before starting.

Before you press Start, check that you have:

  • Enough uninterrupted time for the displayed session, plus a small buffer to read the intro and verify the ending.
  • A reliable connection, a charged device, and a supported browser or required app if the invite specifies one.
  • The correct invitation and employer instructions, with the testing window still open.
  • A clear understanding of which languages, tools, references, or other resources are allowed.
  • Any approved accommodation or setup confirmed with the employer before the timed session.

Opening the invitation to read its preview is different from starting the assessment. If you see a timer, a warning that the session has begun, or unclear start wording, stop and read the page before selecting another control. Do not assume that refreshing, opening another tab, or closing the browser will pause a live timer.

Treat auto-save, tests, and Submit as different steps

Codility’s candidate help says code saves automatically and can be resumed if the browser closes and reopens. It also says candidates can move among tasks without submitting them. That is useful recovery behavior, but it is not a reason to intentionally close an active session: the same guidance says the assessment timer cannot be paused. Keep the invite page open, avoid unnecessary refreshes, and follow the on-screen instructions if the connection drops.

Use the controls for their stated purposes. A Run or Test action lets you check work in the environment; it is not the same as Submit. The visible tests may help catch errors but do not guarantee that every hidden case passes. Codility says submitted solutions are evaluated after submission and completion for correctness and scalability. Your employer chooses the tasks and policies, so the task-specific instructions and interface remain authoritative.

Before submitting a task, review its requirements and the language selection, compile or run the available checks, and confirm that the code in the editor is the version you mean to hand in. Submit only when you are ready: Codility says a submitted solution cannot be changed. If the test has multiple tasks, verify what the page marks as submitted for each task. Do not infer that saving a draft or moving to another task completed the handoff.

Codility documents a fallback for a connection problem that prevents clicking Submit: code present in the IDE when time expires is submitted automatically as the final submission. Treat this as a last-resort behavior described by the vendor, not as a recommended way to finish. The safer path is to use the explicit button while time remains and confirm the page’s resulting status. If the screen does not confirm submission, record the visible message and contact the employer promptly through the channel in the invitation.

Make a small time plan that survives a difficult task

The goal is not to finish every task at any cost. Use the total time to protect time for reading, testing, and submitting. When the session starts, scan all task titles and instructions before deciding where to spend most of your time. Note the task count and any visible point or completion information, but do not invent a scoring formula from it.

Here is a fictional planning example, not an observed Codility assessment: a candidate sees three tasks and a 75-minute total limit. They reserve five minutes to read the instructions, ten minutes at the end to retest and submit, and roughly twenty minutes per task. They spend the first work block outlining a string-processing solution and checking edge cases, the second writing a partial graph traversal, and the third completing a smaller parsing task. When the graph task takes longer than expected, they keep its current code saved, move on, and return if time permits. In the final ten minutes, they run checks, submit only solutions they have reviewed, and verify the visible task status. The task types and schedule are illustrative only; the invite’s own timer and the candidate’s judgment determine an appropriate plan.

A fictional 75-minute, three-task plan places review time before Start, reserves a final check window, and keeps task work in progress separate from submitted solutions.

During the assessment, leave a few minutes for a final pass: run a relevant check, look for unfinished TODOs or accidental debug output, and verify that you selected Submit for the solution you intend to send. If one task remains incomplete, submit only the state you are willing to hand in. An unfinished but deliberate submission is generally clearer than assuming an unsubmitted draft will count, but follow the assessment’s exact instructions if they specify a different process.

Do not let a timer push you into violating the employer’s rules. The invitation may prohibit external tools, copying code, communication with another person, or other resources. This article does not replace those instructions. If an accommodation or accessibility need affects the time limit, contact the employer before starting. Codility’s help center describes administrator controls for changing a candidate’s time limit in eligible sessions, but that is an employer-side process and should not be assumed to apply automatically to an assessment already in progress.

Recover carefully if something goes wrong

If the browser freezes, the connection drops, or a button appears unresponsive, avoid repeated clicks that might submit twice or create a new session. Note the time, task, last visible status, and any error text. If the page reconnects, confirm whether the timer is still running and whether your code is present before continuing. Codility’s auto-save guidance describes code recovery after reopening, but it does not promise that a particular interruption leaves every session state unchanged.

If the page closes, use the original invitation link and the employer’s instructions to return to the same assessment. Check for a message that says whether the session is active, expired, completed, or needs attention. Do not start a second invitation or account to work around a problem. If the original link no longer opens the session, contact the test administrator or recruiter with the invitation identifier, approximate time of interruption, and the exact message shown. Ask whether they can confirm the session state or reopen it.

If time expires before you can use Submit, the official candidate help says the code present in the IDE is submitted automatically as the final submission. The result may still depend on the task, the employer’s settings, and what was actually present in the editor. If you had a connection problem, tell the employer what happened rather than claiming the submission was complete without evidence. Save a screenshot only if the employer’s rules allow it; never include confidential task content in an unrelated support request.

For a missing confirmation, check the assessment page first. Look for a completed or submitted status, a confirmation message, or an instruction to continue to another step. The exact screen may vary. If the assessment appears complete but the employer has not acknowledged it, send a short message before the invitation window closes:

I completed the Codility assessment linked to [role] at approximately [time and time zone]. The page showed [exact status or message]. Could you confirm that the session is recorded on your side?

Include only information needed to identify the assessment. Do not send your solution unless the employer requests it through an approved channel.

What happens after you submit?

After submission and completion, Codility says the solutions are evaluated against multiple test cases for correctness and scalability, and results go to the assessment administrator. That does not mean every candidate sees a score. Codility’s help page says whether results are shared depends on the administrator and purpose of the test; hiring teams may keep them confidential. If no report appears in your account, that alone does not show whether you passed or failed.

Keep the invitation, completion message, role name, and submission time until you receive a response or the employer confirms receipt. If the hiring team gave a follow-up timeline, use it. Otherwise, a concise confirmation request is more useful than repeating the assessment link or creating another attempt. For active roles, you can browse recent openings on LandOffer.ai and check each employer’s application instructions before you apply.

Common Codility timing questions

Can I open the invitation without starting the test?

Codility says you can open the link before Start to read introductory information and return later. The testing window set by the employer still applies, so check the deadline and time zone.

Can I pause the Codility timer?

Codility’s candidate guidance says the timer cannot be paused or stopped after Start. Arrange your time and environment first. Ask the employer about accessibility or timing needs before the session begins.

Does Codility save my code automatically?

Codility says it saves code automatically and that you can resume after closing and reopening the browser. A live timer remains a separate concern; do not close the session intentionally to try to pause it.

Does auto-save mean that I submitted?

No. Auto-save preserves code in the editor. Codility separately says Submit locks a solution so it cannot be changed. Check the task status and the final page state for your own assessment.

Will I see my results immediately?

Not necessarily. Codility says result sharing depends on the assessment administrator. Some hiring teams share results; others keep them confidential.

Sources and Further Reading