Can You Retake Codility for Another Employer? Reused Tests, Deadlines, and Company Rules

A Codility test for one employer does not automatically become a reusable credential for another employer. Codility offers different Screen and Interview workflows, task types, expiration settings, and report controls. A second company may invite a new session, ask to review prior evidence, or decline to reuse an old result. The employer owns that decision. Use the new invitation exactly as delivered, keep the two application records separate, and ask before starting a second attempt when the question or deadline is unclear.

Quick answer

Question	What the evidence supports	Practical move
Is a Codility result portable?	A result can be shared only through an employer-approved workflow or explicit request.	Ask whether the new employer wants a new test or prior evidence.
Are Screen and Interview the same?	They are distinct Codility products with different report and playback surfaces.	Name the product in your question to recruiting.
What if the invite expires?	Expiration is controlled by the invitation and account settings.	Contact the owner before or immediately after the deadline.
Can I restart a session?	The employer may reopen or re-invite when its plan and policy allow it.	Do not create a duplicate login to force a reset.
Does a new task mean a new report?	Usually the owner receives the report for the configured session.	Keep timestamps and the exact test title.

Read this article in three layers. An official provider or employer source establishes what the product or process says. A candidate report can suggest a useful preparation drill, but it does not prove that every candidate sees the same configuration. The final layer is an inference: a tactic that follows from the evidence. Keeping those layers separate prevents a familiar platform name from turning into an invented universal rule.

Start with the product name

Codility's own support taxonomy separates Screen, Interview, candidate reports, session replay, and invitation expiration. A candidate asking about a retake should quote the product name and the test title. 'Codility' alone is too broad to identify the relevant rule. If the page says Screen, the employer may have a report with task scores and timeline information. If it says Interview, the session can be a live collaborative room with a different review flow.

Reused questions are not reused permission

Two employers can choose similar tasks from a vendor library, but that does not grant a candidate permission to copy a prior solution or reuse an old session. Follow the second employer's rules about outside code, references, and AI. If you recognize a task, tell the recruiter only when the recognition affects fairness or access, and ask whether a replacement is available. Do not paste a remembered solution to manufacture a clean-looking attempt.

Deadline and expiration recovery

Save the invitation's expiration time and timezone before beginning. If the link expires, send the owner the exact message, the time you first opened it, and whether you submitted anything. Codility's recruiter documentation includes invitation-expiration controls, but the candidate cannot safely infer that support will reopen every expired session. A clear request for a new invitation is better than repeated retries that create confusing logs.

What a candidate report can show

Codility documentation describes overall and task scores, correctness and performance components, a timeline, and, for selected tasks or accounts, replay or integrity signals. Those fields belong to the configured session. A new employer may not be able to access an old report, and even the same employer may see a different report for a different task type. Ask which result is being considered and whether the employer needs a fresh completion.

A fair retake request

Use a short message: identify the role, test title, date, and account email; state whether you submitted; describe the reason for the request; and ask whether the owner prefers a reopen, extension, or new invitation. Mention an accommodation or outage factually. Do not accuse the platform, attach source code, or speculate about a hidden score. The goal is to let the assessment owner choose a documented path.

How to prepare when a new attempt is confirmed

Reset your preparation rather than memorizing the first task. Rehearse the underlying skill, test from a clean supported browser, and verify camera or identity permissions before the timer starts. If the employer allows a prior result, ask whether a new session would replace it or simply add another report. Save the confirmation and the final submission state for your own records.

A focused preparation and recovery plan

Step	What to do	Evidence to keep
1. Confirm	Read the invitation, role page, or assessment landing page. Record the deadline, timezone, timer, allowed tools, identity checks, and accommodation contact.	A screenshot or saved message with private details redacted.
2. Baseline	Complete one representative exercise without changing the rules. Measure correctness, time, and the point where you became uncertain.	The prompt, your approach, and a short error log.
3. Diagnose	Separate a content problem from a platform, network, account, or evidence problem. Do not refresh repeatedly while a timer is running.	Timestamped notes, browser version, and visible error text.
4. Rehearse	Repeat the narrow skill this article identifies. Add one adversarial case and one explanation of what would change at larger scale.	A corrected solution or one-page decision record.
5. Escalate	If the official owner must change a deadline, reopen a session, or explain a report, send a concise factual request.	The original invite, incident timeline, and requested remedy.

Frequently asked questions

Can another Codility employer see my old score?

Only if the result is shared through an employer-controlled workflow or you provide it. The platform name alone does not establish access.

Can Codility reopen an expired test?

The assessment owner decides whether to reopen, extend, or issue a new invitation.

Should I create a second Codility account?

No. Use the invited account and ask the employer to correct access.

Are Codility Screen and Interview reports interchangeable?

No. They are separate products and can expose different review fields.

What if I recognize a task from an earlier test?

Stop and ask whether the owner wants a replacement; do not reuse a solution outside the stated rules.

Before you start

Turn the article into a small decision record before you act. Write the exact question you need to answer, the source that could answer it, and the consequence of being wrong. For an assessment, that might be whether the timer stops, whether a second display is allowed, or whether a previous result can be reused. For a technical interview, it might be whether the system promises per-key ordering, whether the verifier can prove a loop is bounded, or whether a cache update can be replayed. This framing keeps preparation tied to the target rather than to a list of fashionable keywords.

Next, separate hard constraints from choices. A deadline, access rule, memory limit, privacy boundary, or source-of-truth requirement is a constraint. A page size, data structure, model pair, retry policy, or practice order is a choice that you should justify. Write one default choice, one alternative, and the signal that would make you switch. Interviewers and recruiters can then see judgment instead of a memorized answer.

Finally, decide what evidence will close the loop. Save a confirmation, a source position, a benchmark row, a test result, a metric, or a recovery ticket. Do not collect private assessment content or credentials. The evidence should be sufficient for the next person to reproduce the decision without exposing information they are not authorized to see. If the evidence is missing, label the conclusion provisional and ask the owner for the exact next action. That discipline is useful whether the page is about a hiring platform, a production system, or a candidate-reported study.

A final quality check is simple: remove any claim that depends on an unnamed company policy, an undated forum anecdote, or a number whose denominator you cannot explain. Replace it with the narrower fact, the verification step, or the limitation. Readers usually need a safe next move more than a confident-sounding prediction. That editorial boundary also makes the draft easier to update when a platform changes its controls or a new hiring cycle starts. Use the same discipline for every source and every handoff.

How to decide what to trust

The live invitation and the instructions shown inside the assessment outrank a generic article. The provider's current help center explains default product behavior, but employers can choose different question types, timers, proctoring controls, report fields, or deadlines. An official employer page establishes the published role or event context; it does not establish every team's interview sequence. Candidate reports are useful when they identify the role, date, and product, yet they remain samples. When two sources disagree, record the conflict instead of averaging it into a made-up number. If a technical incident is involved, preserve the state first, then use the platform's support route or the recruiter who owns the invitation. This approach is slower than guessing, but it gives the reader an action that can be defended and repeated.

Final takeaway

A Codility retake is a controlled employer decision. Keep application records separate, ask which session is authoritative, and follow the new invitation without copying an old solution.

Sources and Further Reading

• Codility: Reading a candidate test report
• Codility Getting Started
• Codility: Screen invite expiration
• Codility Assessment Guide

Research note: Sources checked 2026-09-06. Platform settings, recruiting schedules, and technical documentation can change; verify the exact invitation or current release before acting.