Skip to content

Safe Coding Assessments: Help Candidates Verify Employers

Send safe coding assessments with an independent employer verification route, clear setup instructions, a pause policy, and a reusable invitation template.

Ernest Bursa

Ernest Bursa

Founder · · 10 min read
A senior hiring lead reads a document beside a closed laptop on a San Francisco waterfront bench.

A safe coding assessment starts with a hiring process candidates can verify independently. Publish a contact route on your official website, identify the expected repository and setup, explain the environment requirements, and let candidates pause without losing their place. An independent company check helps confirm who sent the task; it does not establish that the code is harmless.

That distinction matters when a realistic interview can lead to an unsafe repository. Your job as an employer is to make reasonable checks easy and give candidates a practical alternative when they cannot meet the setup requirements.

What the Binance report establishes

Binance’s preliminary account connects a fake hiring process to code executed on a work computer. Treat its account as an attributed incident report, not a completed independent investigation.

In its November 3 initial findings, Binance says a convincing recruitment flow, including live interviews, preceded the assignment setup. Separately, the FBI attributes the October 29 attack to North Korea. The official attribution does not independently establish every detail of the recruitment entry chain.

Other investigations show why appearances are a weak test. Atlassian’s investigation of Contagious Interview describes recruitment lures involving plausible personas and repositories. Fireblocks’ account of a recruiting impersonation scam shows the value of candidates checking a supposed opportunity directly with the company being impersonated.

These are separate investigations. They do not establish that every incident belongs to the same campaign, or tell us how often a coding assessment is malicious. They do support a concrete change for legitimate employers: stop treating a polished profile, video call, or familiar repository host as enough reassurance.

Give candidates an independent verification route

Publish a way to confirm the vacancy, recruiter, and assessment through a channel the candidate can find without following the invitation’s links. A reply to the same unverified sender is not an independent check.

A company website alone is not enough. Atlassian also found front companies and custom domains in its investigation. Candidates should corroborate the company through independently found information and contacts, or pause if they cannot.

Put the verification instructions on your official careers or contact page. Name the hiring team or contact role that handles enquiries, and make sure someone actually monitors the route. If an agency recruits for you, explain how candidates can confirm that relationship.

Candidates should be able to start at your company website, navigate to the relevant page, and ask whether the invitation matches your process. An address inside a suspicious message can be copied or substituted. Tell candidates where to find the contact for themselves.

Use this checklist before the first invitation goes out. The controls below are recommendations for your process, not a certification standard.

Area What the employer provides What the candidate can check
Identity Official contact route, role title, named recruiter or agency The independently reached company confirms the opportunity and sender
Assessment Expected repository owner, task name, and revision where practical The supplied repository matches the confirmed assignment
Setup Required tools, dependencies, expected setup actions, and external services The request matches the written brief before anything runs
Environment Agreed isolation requirements and a statement that production credentials are unnecessary A suitable environment is available without using an employer’s work machine
Response A monitored question channel, pause policy, and alternative format A discrepancy can be raised without pressure to continue

Do not ask candidates to send identity documents or sensitive account information merely to report a suspicious invitation. Collect enough to locate the process: role, sender, date, and a description of the request. Your security team can decide what further evidence it needs.

Explain what the assessment will run

Tell candidates what setup involves before they accept the task. “Clone the repository and follow the README” leaves the important decision until after they enter unfamiliar material.

Your brief should state the runtime and tool versions, dependencies, expected network access, and whether any installation or setup step executes code. Identify required accounts and permissions. Use dummy data and test credentials where credentials are needed; never require access to the candidate’s current employer, production systems, personal wallet, or unrelated accounts.

Assign an engineering owner to review the repository and its setup instructions before release. Record the intended repository and, where practical, its revision in the invitation. If it changes after you send it, explain the change through the established channel and give candidates time to check it.

These measures make discrepancies easier to spot. They do not make code safe by themselves. A private repository, a known hosting service, a lockfile, or a successful scan is not a security attestation. Nor does reading a short setup command reveal everything its dependencies might execute. Fireblocks’ investigation is a useful reminder that ordinary-looking setup can sit inside a convincing impersonation flow.

For the usability side of the brief, use the take-home assignment instructions user test. Clear instructions and a clear verification route solve different problems; you need both.

Offer a safe way to pause or change the format

Give candidates permission to stop before a disputed setup step and keep the hiring decision separate from that pause. A warning has little value if the deadline still pressures someone to run the task immediately.

Atlassian recommends dedicated, isolated assessment environments and avoiding corporate workstations with production credentials. Arrange the environment requirements with your engineering or security team. Do not turn “use a container” into a promise of safety: isolation depends on configuration, access, and what is shared with the host.

If you cannot provide an appropriate environment, offer a discussion of supplied code, a design exercise, or a walkthrough of the candidate’s own non-confidential work. Pick an alternative that still tests the skill you need, and explain its evaluation criteria. Do not require a candidate to disclose a current employer’s code to avoid running yours.

Make the pause policy operational. Name who receives the question, who can extend the deadline, and who decides whether the assessment resumes. Recruiters should not have to improvise a security verdict during a live interview.

A coding assessment invitation you can adapt

A useful invitation brings the verification route, setup expectations, and pause policy together. The example below is fictional; replace every bracketed field and confirm the promises with your team before sending it.

Subject: [Company] [role] assessment: details and verification

Hi [name],

We’d like to invite you to [assessment name] for [role]. It tests [specific skills], takes about [working time], and is due [date and time zone]. [State payment terms, if applicable.]

Before opening the repository, you can verify this invitation independently. Start at our company website, open [careers/contact page], and use the published [hiring contact route]. Ask the team to confirm [recruiter’s name], this role, and this assessment. You do not need to rely on links in this email.

The expected repository is [owner/repository], at [revision, if applicable]. Setup requires [tools and versions] and involves [installation, code execution, network access, and required accounts]. The instructions explain [test data and any test credentials]. No production credentials or access to your current employer’s systems are required.

Please use [agreed assessment environment]. If that environment is unavailable, something differs from this brief, or you have a security concern, stop and contact [team]. We will pause the deadline while we resolve it. We can offer [alternative format] to assess the same skills.

We will evaluate [criteria]. [Named contact or team] owns questions about the task and will explain any changes before you continue.

Thanks, [Name and role]

Keep the public verification route free of private task details. Candidates need to confirm that a process exists without exposing the assessment brief or their application to everyone browsing your website.

When a suspicious assignment needs escalation

An unexplained mismatch calls for a pause; suspected execution of malicious code calls for an incident response. The table below is a suggested ownership model, not a diagnosis of any particular message or repository.

Situation Immediate action Owner and condition for continuing
Candidate cannot confirm the recruiter or role Pause the assessment and check through the independently found company contact Hiring lead confirms the sender and vacancy before resuming
Repository or setup differs from the confirmed brief Do not execute the disputed material; preserve the invitation and repository details Engineering owner investigates and provides a confirmed explanation or replacement
Request demands production secrets, disabled protections, or unexplained access Stop the task and escalate the request Security team reviews it; recruiter arranges an alternative or ends the request
Code already ran and compromise is suspected Stop, disconnect the affected device, and contact security through a trusted channel The candidate’s security team or incident responder directs containment and recovery

For suspected compromise, preserve messages, sender details, repository references, and the timing of what happened. Follow your organization’s incident process. Atlassian’s guidance includes device isolation and credential action from a clean device; have responders determine the scope rather than promising that deleting the repository fixes the problem.

A candidate’s caution is not evidence of poor engineering ability. Likewise, an awkward README is not proof of an attack. Resolve the discrepancy and record the decision without making the candidate prove malicious intent.

This threat also differs from fraudulent applicants seeking employment. If that is your problem, see the separate guide to North Korean IT worker hiring fraud.

Keep the assessment brief and process aligned in Kit

A consistent hiring workflow helps you communicate the agreed task, but it cannot replace independent verification or security review. Keep those responsibilities with named people on your team.

Kit’s code assignment configuration holds the GitHub template, instructions, estimated effort, duration, and extension settings. Its GitHub template setup supports creating private candidate repositories from your configured template. Assignment briefs can carry the stage instructions and assignment facts into a per-candidate PDF.

Use the public process description to explain what candidates should expect and where they can verify the invitation. Keep private task material in the appropriate brief; the candidate experience documentation explains the distinction between public stage descriptions and private task instructions.

A private repository or stamped PDF is a workflow artifact. Kit does not verify employer identity, scan assessment repositories, or provide a secure execution sandbox.

Before your next invitation, check that a candidate can independently confirm the sender, understand what will run, and pause with a named contact. Start by updating one real assessment brief and having a colleague follow its verification route from your public website.

Related articles

Try Kit for 30 days.

Hiring, security reports, and training in one account, for teams where none of it is a full-time job. Free for 30 days, card required. Cancel before it ends and you pay nothing.

Get started free