Articles
Online Assessment Technical Issues: What to Document and How to Contact Recruiting
Online assessment technical issue? Learn what evidence to save, who to contact, what not to do, and use a concise recruiter email template.
If an online assessment freezes, disconnects, or fails to submit, your first job is not aggressive troubleshooting. It is preserving a clear record of what happened. Note the time, remaining minutes, question or section, exact error, and the effect on your work. Then contact the assessment platform for technical investigation and the recruiter for any hiring-process remedy.
Act quickly, but stay factual. A short, timestamped incident report gives a recruiter more to evaluate than “the test broke.”
Quick Answer
When an online assessment has a technical issue, use this sequence:
- Pause repeated actions. Do not keep refreshing, opening new tabs, or restarting unless the platform tells you to.
- Document the incident. Record the local time and time zone, assessment name, question or section, remaining time, exact error, device and browser, and what stopped working.
- Preserve safe evidence. Capture the error or status area when permitted, but do not photograph or share confidential question content.
- Contact both owners. Platform support can investigate the technology; the recruiter or hiring team controls extensions, retakes, and hiring decisions.
Your invitation is the source of truth. Platform behavior and employer policies vary, so do not assume that refreshing, resuming, or starting a second attempt is allowed.
What Counts as an Online Assessment Technical Issue?
An online assessment technical issue is a platform, device, network, or permissions failure that prevents the assessment from behaving as instructed. The important question is not whether the experience felt difficult. It is whether a malfunction materially reduced your ability to access, complete, run, save, or submit the work.
Common examples include a frozen editor, a failed page load, lost connection, missing starter files, a compiler that never returns, a submission error, or required camera and screen-sharing permissions that cannot be established. Misunderstanding a prompt, failing hidden tests, or running out of time on a normally functioning platform is not the same kind of incident.
The First 60 Seconds: Stop, Observe, and Preserve
Stress often makes candidates click faster. That can destroy useful context or create activity that is hard to distinguish from the original failure. Take one breath and read the message on screen before changing anything.
First, check whether the platform provides an explicit instruction such as reconnect, retry, refresh, or contact support. If it does, follow that instruction once. If the page is still responsive, leave it open while you record the incident.
Be careful with a manual refresh. CodeSignal warns that refreshing during a connection problem may delete current code, although code that was previously executed may be recoverable from its History tab. HackerRank also states that its test timer continues during technical issues; an employer can add time, but the candidate cannot pause the clock independently.
Do not start a second session, change devices, disable proctoring, or use another account unless support or the recruiter explicitly authorizes it.
What to Document
A useful incident report is specific enough for support to locate the session and for recruiting to understand the impact.
| Evidence | What to record | Safe example |
|---|---|---|
| Identity | Name and email used for the invitation | Jordan Lee, jordan@example.com |
| Assessment | Company, role, platform, and test name | Backend Intern OA, CodeSignal |
| Time | Local timestamp, time zone, and approximate duration | 2:14 PM PDT; frozen for about 11 minutes |
| Location in test | Question number or section and remaining time | Question 3; 27:40 remaining |
| Failure | Exact error text or observable behavior | Run button stayed loading; editor stopped accepting input |
| Environment | Device, OS, browser version, and network | Windows 11, Chrome 140, home Wi-Fi |
| Actions taken | Each troubleshooting step, once, in order | Waited 60 seconds, used in-app reconnect, then contacted support |
| Impact | What work or time was lost | Could not run tests or submit the completed function |
Also save the invitation email, support ticket number, and any automated incident confirmation. If you receive a platform status alert, note its URL and the time you saw it.
Protect confidential test content
Evidence should prove the malfunction, not copy the assessment. If screenshots are allowed, crop to the error banner, timer, connection indicator, or blank editor state. Redact the prompt, code, test cases, candidate ID, and access link before forwarding an image outside the official support channel.
Never post the screenshot publicly or ask strangers to diagnose a live question.
Who Should You Contact First?
Contact platform support for diagnosis and the recruiter for process relief. In many cases, send both messages within the same short window rather than waiting for one organization to answer the other.
CodeSignal recommends contacting its support team promptly and alerting the company contact that sent the assessment. HackerRank says candidates should report a frozen editor, failed load, or submission error to recruiting; support can document platform findings, but the employer controls retests and workflow changes. CoderPad's retake process likewise sends the request to the test administrator for approval.
Use the support method in your invitation when one is provided. Otherwise, use the platform's official support form and reply to the recruiter thread.
Issue-Specific Playbooks
Internet disconnects or the browser crashes
Record when the connection dropped and whether the timer continued. Check whether the platform shows a reconnect instruction. If you must change networks, use a stable connection such as Ethernet or a personal hotspot only when the rules permit it.
CodeSignal lists weak Wi-Fi, congestion, firewalls, browser extensions, and low device power among possible causes. If the browser closes, reopen only the original invitation or recovery link; do not create another account.
The editor freezes, code will not run, or submission fails
Record whether typing, running tests, saving, and submitting are separately affected. Copying confidential code into an external editor may be prohibited, so do not move it elsewhere unless the instructions allow a local IDE.
Wait briefly for an in-product error, then use the permitted help route. If time is running, tell the recruiter how many minutes were unavailable.
Camera, microphone, or screen sharing fails
Do not bypass required proctoring. Confirm that you are using a supported browser, then check operating-system and browser permissions. Close another application that may already be using the camera or microphone.
CodeSignal recommends an updated Chrome or Firefox browser, a strong connection, and enabled camera, microphone, and screen-sharing permissions. Codility says recording functions have narrower browser requirements. Follow your assessment's instructions.
Power or device failure
Write down the outage time when the device returns. Tell support whether the attempt appears active, submitted, or inaccessible.
HackerRank documents that employers can reinvite candidates after a power outage or lost internet connection. That capability does not guarantee a retest; it shows why a concise report to the employer matters.
Email the Recruiter Without Overexplaining
Send a concise message soon after the incident. Use a neutral subject line, state the facts in chronological order, and ask for a specific next step. Do not demand a reset or accuse the platform of unfairness before the logs are reviewed.
Subject: Technical issue during [Role] online assessment on [Date]
Hi [Recruiter Name],
I experienced a technical issue during the [Assessment Name] for the [Role] position today at approximately [Time and Time Zone]. While I was on [Question/Section] with about [Remaining Time] left, [brief observable failure]. I followed the on-screen guidance by [one or two actions], but the issue continued for approximately [Duration] and prevented me from [run tests/save/submit/continue].
I have also contacted [Platform] Support under ticket [Ticket Number, if available]. I can provide a cropped screenshot of the error and my environment details through an approved channel. Could you please confirm whether I should wait, resume the existing attempt, or expect another instruction?
Thank you,
[Your Name]
For platform support, include the same timeline, invitation email, browser and OS, network type, and exact error. Ask whether the session logs show the interruption, then share the ticket number with recruiting.
What Response Can You Expect?
The employer may restore access, add time, issue a new invitation, accept the existing result, or decline a retest. There is no universal remedy because the severity, available logs, assessment design, and company policy all matter.
HackerRank's employer tools can add time during or after an attempt, and its documentation says the timer itself does not pause for a technical issue. CoderPad allows participating employers to approve or deny a retake request. These are platform capabilities, not promises that every recruiter will use them.
If told to resume, ask whether the timer, saved code, proctoring, and submission state were reset. If sent a new invitation, confirm whether the previous attempt will be ignored.
What Not to Do
Do not send repeated messages, contact executives, post confidential screenshots, alter timestamps, or describe a logic bug as a platform failure. Avoid anything that resembles rule evasion, including disabling monitoring, changing accounts, or continuing on another device without permission.
Prepare for a Restart or Retest
While waiting, create a short debrief. Note the data structures, implementation errors, and test cases that slowed you down without reproducing the confidential prompt. Then practice one timed set under the same browser, keyboard, and network conditions you intend to use.
Before a new attempt, update the browser, disable nonessential extensions, connect the device to power, test camera and screen-sharing permissions, and run the platform tutorial or compatibility check. Keep the recruiter and support instructions nearby, but close unrelated applications before starting.
Frequently Asked Questions
Should I email the recruiter or assessment platform first?
Contact both promptly when the failure affected a live attempt. Platform support can inspect technical logs, while the recruiter controls extra time, a retest, and your hiring workflow. Include the support ticket number in the recruiter message when available.
Will refreshing an online assessment lose my code?
It depends on the platform and whether your work was saved or executed. CodeSignal warns that a refresh during a connection issue may delete current code, although previously run code may be available in History. Follow the on-screen recovery instruction before refreshing manually.
Should I take a screenshot of the technical issue?
Only when the assessment rules allow it. Capture the error, timer, or status area and crop out confidential prompts, code, test cases, access links, and personal identifiers. Send evidence only through the official support or recruiting channel.
Can a recruiter give me extra time or a retest?
Sometimes. Major platforms provide employer-side options such as adding time or issuing another invitation, but the company decides whether to use them. A documented incident improves the quality of that decision; it does not guarantee a particular remedy.
What if support does not reply before the deadline?
Email the recruiter with the incident time, ticket number, and the exact impact before the deadline passes. Do not start an unauthorized second attempt. Ask whether to wait, resume, or expect a new invitation, and preserve the written response.
Final Takeaway
An online assessment technical issue is easier to resolve when you treat it like a small production incident: stop repeated actions, preserve evidence, separate technical diagnosis from hiring decisions, and communicate a precise timeline.
Document what happened without exposing the question, contact platform support and recruiting through official channels, and wait for an authorized instruction before changing sessions or devices.
Sources and Further Reading
- HackerRank: Ensuring a Great Candidate Experience
- HackerRank: Extend Test Duration for Candidates
- HackerRank: Reinvite Candidates to a Test
- HackerRank Status Page
- CodeSignal: Connection Issues
- CodeSignal: Technical Difficulties
- CodeSignal: Who to Contact During an Assessment
- Codility: Supported Browsers and Devices
- Codility: Candidate FAQ
- CoderPad: Screen Preparation Guide and Retake Requests
Research note: This guide was checked on August 25, 2026. Assessment behavior and employer remedies vary; your invitation, on-screen instructions, and recruiter message remain the source of truth.