How to Complete a Remote Technical Assessment

The assessment is often the first hard filter after your CV. A foreign employer can't meet you in person, so they use a HackerRank test, a live coding call or a practical task to check you can do the work. This guide covers the main types of remote technical assessment, what proctored tests actually record, how to manage your time inside a timed test, and how to handle live rounds across time zones. It also explains what to do if NEPA takes light halfway through, and how to spot fake "assessments" used by scammers.

Quick answer

A remote technical assessment is an online test of job skills. It might be a timed coding test, a live coding call, a practical task or a system design discussion. To pass one, read the invitation's rules (time, monitoring, allowed tools, AI policy). Practise on the same platform, and take the test on a laptop with backup power and a second internet connection. Solve the easiest problems first. If anything breaks, email the recruiter straight away.

What counts as a remote technical assessment

Employers use the term loosely. Developers, data analysts, QA testers, DevOps engineers and IT support staff can all be asked to do one. The common formats are below.

Many hiring processes combine two or three of these. A common pattern is an automated online test first, then a live round with an engineer for people who pass.

For non-technical roles, the format is different enough that we cover it separately: see our guides to the remote customer service assessment, the remote writing assessment and the remote UX design challenge.

Before you start: read the invitation like a contract

The invitation email and the test's landing page are the rulebook. Two tests on the same platform can run under completely different settings, because the employer chooses them. Before you click "Start", find the answers to these questions:

• How long, and is it one sitting? Most timed tests can't be paused once started. Check whether the time limit covers the whole test or each question.
• When does the link expire? Note the deadline in Lagos time, not the sender's time zone.
• Which languages are allowed? Pick the one you write fastest in, not the one you think looks impressive.
• What monitoring is switched on? Look for webcam, screen sharing, full-screen mode or a desktop app.
• What is the AI policy? If the invite doesn't say, ask the recruiter (more on this below).
• Is there a sample or practice test? If there is, take it a day or two before the real one.

If anything is unclear, email the recruiter before you start. A clarifying question costs you nothing. Starting a test under the wrong assumptions can cost you the role.

What proctored tests actually record

A proctored test is one that is monitored to check you work alone and follow the rules. Candidates in Nigeria sometimes worry that a single glance away will disqualify them. The reality is more specific, and it's better to know exactly what is tracked.

HackerRank's own test integrity documentation (as of October 2026) describes three modes that employers can switch on:

• Secure Mode: the test runs in a controlled browser environment, forces full-screen, blocks copy and paste, does not allow multiple monitors, and alerts you if you switch tabs.
• Proctor Mode: everything in Secure Mode, plus AI analysis of screenshots, plagiarism detection and webcam anomaly detection.
• Desktop App Mode: everything in Proctor Mode, plus monitoring at operating-system level through a HackerRank app you install.

HackerRank also tracks some things on every test, with no setup by the employer. Copy-paste actions in coding questions are recorded and the pasted content appears in the report. Tab proctoring records how often and how long you leave the test window. Employers can also switch on image proctoring, which needs your webcam on before you start and takes periodic snapshots. Some tests also ask you to take a photo of yourself before you begin.

What this means in practice:

• Don't paste code from another tab, even your own snippet library, unless the rules allow it. The paste is visible to the reviewer.
• Close WhatsApp Web, Slack and email before starting, so a notification doesn't tempt you into switching windows.
• If the test needs a webcam, sit facing a light source, not with a bright window behind you.
• Tell anyone at home that you're in a timed test, so nobody walks into the frame talking to you.

Other platforms such as CodeSignal, Codility and TestGorilla offer their own monitoring options. The details differ by platform and by employer, so the invitation remains the authority for your specific test.

Set up your workspace for a Nigerian reality

Most remote technical assessments are timed, and many can't be paused. That makes your setup part of the test. A power cut 40 minutes into a 90-minute test is a real risk in most Nigerian cities, so plan for it.

Power

• Charge your laptop fully and plug it into an inverter, solar setup or UPS, not straight into grid power.
• If you rely on a generator, start it before the test, not when the lights go.
• Check your laptop's battery health. An old battery that shows 100% but dies in 30 minutes is a common trap.

Internet

• Have two connections ready: your main ISP or MiFi, and a phone hotspot on a different network (MTN and Airtel, for example).
• Run a speed test on both an hour before. Video-proctored and live tests need a stable upload, not only download.
• If you have Starlink or fibre, still keep the hotspot ready. Routers reboot and fibre gets cut.
• Buy enough data for a video call plus a margin. Running out of data mid-test is avoidable.

Device and browser

• Use a laptop or desktop. Phones and tablets are a poor fit for coding tests and some platforms don't support them.
• Use an up-to-date Chrome or the browser the invite names, and update it the day before, not during the test.
• Grant camera, microphone and screen-sharing permissions during the practice run, so no permission pop-up surprises you on the day.
• Use one monitor if the rules say so. Unplug the second screen rather than just turning it off.

If your laptop is old or underpowered, our planned guide to equipment for a remote job covers what's realistic on a budget.

Time zones: book live rounds at hours you can actually perform

Live coding and system design rounds are scheduled calls, and you often get to choose the slot. Lagos is on West Africa Time (WAT, UTC+1) all year, with no daylight saving. The other side changes its clocks, so the gap moves:

Note the timing this season: UK clocks went back on 25 October 2026, and US clocks go back on 1 November 2026. A call booked before that weekend for a date after it can easily land an hour off. Confirm every slot in writing with the time zone stated ("Tuesday 4pm WAT / 10am EST"). Also add it to a calendar that shows both zones.

For US West Coast rounds, an evening slot is normal. Pick the one where you'll still be sharp, and think about your area's usual power pattern at that hour. For more on this, see our guide on answering questions about working across time zones.

How to complete a timed online coding test

Timed online tests are usually scored automatically. Your code runs against test cases, including hidden ones you can't see. That changes how you should spend your time.

A practical order of work

1. Read every question first (2 to 5 minutes). Note which looks easiest, and what the input sizes are. Large inputs mean a slow solution will fail hidden tests.
2. Solve the easiest problem completely. A fully passing question usually scores better than two half-finished ones.
3. Write a correct solution before a clever one. A brute-force answer that passes the small cases earns points. Improve it if time allows.
4. Test edge cases yourself. Try empty input, one element, duplicates, negative numbers, very large values and off-by-one boundaries. The visible sample cases rarely cover these.
5. Submit or save as you go. Don't keep all your work in an unsaved buffer for the last five minutes.
6. Watch the clock at fixed points. Check it at the halfway mark and again with 15 minutes left. If you're stuck, move on and come back.

Multiple-choice and SQL sections

Some assessments mix code with multiple-choice questions on concepts (HTTP, Git, data structures) or SQL queries against a sample database. For multiple-choice questions, check whether wrong answers cost marks before guessing. For SQL, run the query and read the output rather than trusting it by eye, and watch for NULLs and duplicate rows.

Example (hypothetical): planning a 90-minute, three-question test

Tunde, a backend developer in Ibadan, opens a 90-minute HackerRank test with three coding questions. He spends four minutes reading all three. Question 2 is a string problem he's confident about, question 1 is a medium array problem and question 3 is a hard graph problem.

He solves question 2 first in 20 minutes, including his own edge-case tests. He then spends 35 minutes on question 1. With 30 minutes left, he writes a simple solution to question 3 that passes the small cases, adds a short comment explaining the faster approach he'd use, and submits with three minutes to spare. He doesn't finish everything, but he banks two solid answers and partial credit on the third.

How to handle a live coding interview

A live coding round tests how you think as much as whether your code runs. The interviewer is usually an engineer who would work with you, and they are judging whether they'd enjoy debugging with you on a Tuesday afternoon.

• Repeat the problem back in your own words and ask about inputs, constraints and edge cases before typing.
• Say your plan out loud before coding: "I'll use a hash map to count occurrences, which makes this linear time."
• Keep talking while you code, but in short, useful sentences. Silence for five minutes leaves the interviewer guessing.
• Test your code by walking through an example line by line, then fix what you find. Catching your own bug is a good signal.
• Admit what you don't know. "I don't remember the exact method name; in practice I'd check the docs" is fine. Bluffing is not.

Before the call, test the tool the company uses (CoderPad, a shared Google Doc, VS Code Live Share or a screen share). Check your microphone and camera too. Our guide to setting up your camera and microphone covers the basics. Have a short written message ready in case the call drops: "Lost connection, rejoining on hotspot now."

For the questions that come before and after the coding itself, use our software engineer interview questions and the wider remote interview preparation guide.

Take-home tasks: a short note

A take-home task is a small project you complete in your own time, often over two to seven days. Treat the stated time estimate as a signal of the expected scope. Polish beats extra features. Write a clear README that explains how to run the project, what you'd improve with more time and any assumptions you made. If the task looks like real production work that would take days, ask the recruiter about its scope.

Our separate guide to preparing for a take-home coding test goes into structure, testing and submission in detail.

Using AI during a technical assessment: follow each employer's rule

Can you use ChatGPT, Claude or Copilot in a technical assessment? Only if that employer says so for that stage. Policies differ sharply between companies and between stages of the same process, so there is no general answer.

Two published policies show the range (both checked October 2026):

• Greenhouse asks candidates not to use AI to supplement their performance in a live interview unless instructed or agreed in advance. For some take-home and work assessments, it says candidates will be encouraged to use AI. However, the submission must reflect the candidate's "own synthesis, decisions and point of view, not unedited AI output". Undisclosed AI use outside its guidelines may lead to disqualification (Greenhouse AI guidelines).
• Anthropic tells candidates to complete take-home assessments without AI unless it explicitly says AI is allowed for that task. It also asks for no AI assistance in live interviews unless indicated otherwise (Anthropic candidate AI guidance).

So the same behaviour (using AI on a take-home) is encouraged at one company and against the rules at another. The safe approach:

1. Look for the AI policy in the invite, the careers page or the test instructions.
2. If you can't find one, ask the recruiter in writing before starting.
3. If AI is allowed, be ready to explain every line you submit and why you accepted or changed the AI's output.
4. If AI isn't allowed, don't use it. In a proctored test, an AI answer usually means pasting from another window, and the report shows both the paste and the window exits.

You can use AI freely to prepare: generating practice problems, explaining a concept you're weak on, or reviewing your practice code after you've written it. Both companies above encourage or allow AI for preparation and research.

If something goes wrong mid-test

Power cuts, router failures and browser crashes happen. Whether you recover depends mostly on what you do in the next ten minutes.

1. Switch to your backup connection and reopen the test link. On many platforms, reopening the invitation takes you back into the test, but the timer may keep running while you're away.
2. Take screenshots or phone photos of any error message, and note the exact time it happened.
3. Email the recruiter immediately, while the details are fresh. Keep it short and factual: what happened, when, how many minutes you lost, and that you'd appreciate extra time or a new link.
4. Don't start a fresh attempt on your own, for example by using a new email address. That looks like trying to game the test.

Employers do have tools for this. HackerRank lets the hiring team add a fixed number of extra minutes to make up for lost time such as connectivity problems, during the test or after it (HackerRank time accommodation documentation, as of October 2026). Whether they use that tool is up to the employer, which is why a prompt, polite email matters.

Example (hypothetical) email:

Subject: Connection lost during HackerRank assessment, Backend Developer

Hi Sarah, I was taking the assessment today and lost power and internet at 2:47pm WAT (1:47pm GMT). I reconnected on a backup network at 3:01pm, so I lost about 14 minutes. I've attached a screenshot of the error. Would it be possible to add the lost time or send a new link? Thank you, Chiamaka Obi

Asking for accommodations before you start

If you have a disability, a health condition or another reason you need adjusted conditions, ask before you begin the test. On HackerRank, a hiring team can extend a test's duration by 25%, 50%, 75% or 100% (or a custom percentage in steps of five), but only before the candidate starts. You don't have to share medical details beyond what's needed. A line like "I'd like to request extra time as a disability-related accommodation" is enough for most recruiters to act on.

How to prepare in the week before

Preparation matters more than last-night cramming. A realistic seven-day plan for someone who already codes daily:

Match your practice to the role. A data analyst should practise SQL and pandas, not graph algorithms. A DevOps candidate should rehearse Linux commands, Docker and debugging a broken config. Our role guides for the data analyst career path and the QA engineer career path list the tools those employers test most.

Spotting a fake technical assessment

Scammers copy real hiring steps, including tests. A real technical assessment never requires you to pay for anything. Treat these as red flags:

• A "test" sent over Telegram or WhatsApp by someone you can't link to a real company domain.
• A request to pay for "assessment software", a training course or equipment before or after the test.
• An instruction to install unknown software or browser extensions from a link that isn't the platform's real domain.
• A "trial task" that is a full piece of production work (a complete app, a month of content) with vague talk of payment later.
• An offer letter arriving minutes after a trivial test, followed by a request for your BVN, bank login or passport.

Check that the test link goes to the real platform's domain (hackerrank.com, codesignal.com, codility.com and so on), and that the sender's email matches the company. For a fuller checklist, read our guide to remote job scams in Nigeria and the planned piece on recognising fake remote job interviews.

After you submit

Send a short thank-you note to the recruiter only if you've been in direct contact. For automated tests, no message is needed. Write down what you found hard while it's fresh, because the same topics tend to come up again at other companies. If you hear nothing within the timeline you were given, a single polite follow-up is reasonable; see how to follow up after applying. If you're rejected, ask whether feedback is available. Some companies give it and many don't, but asking costs nothing.

Frequently asked questions

Can I use Google or documentation during a remote technical assessment?

It depends on the employer's rules for that test. Some allow official documentation and some forbid leaving the test window entirely. Many proctored tests record tab switching, so read the instructions and ask the recruiter if they're unclear.

Does HackerRank know if I switch tabs?

Yes. HackerRank's tab proctoring records how often and for how long a candidate leaves the test window, and it also records copy-paste actions in coding questions. The hiring team sees this in the candidate's report, as of October 2026.

What happens if NEPA takes light during my coding test?

Switch to your backup power and connection, reopen the test link and email the recruiter at once with the time and screenshots. The timer may keep running while you're offline. Some platforms, including HackerRank, let employers add extra minutes for lost time, but it's the employer's decision.

Is it allowed to use ChatGPT in a coding assessment?

Only if the employer explicitly allows it for that stage. Greenhouse, for example, encourages AI on some take-home work but not in live interviews. Anthropic asks candidates not to use AI on take-homes unless told otherwise. When the rule isn't stated, ask in writing before you start.

How long does a remote technical assessment take?

Timed online tests commonly run from about 45 minutes to two hours, and live coding rounds are usually around an hour. Take-home tasks can come with a deadline of several days. The invitation states the actual time limit, and it varies by employer and role.

Which programming language should I use in an online coding test?

Use the language you're fastest and most accurate in, as long as the test allows it. Python is popular for algorithm questions because it's concise. If the job is specifically for Java or Go, using that language shows direct fit.

Can I retake a technical assessment if I do badly?

Usually not for the same role, at least not straight away. Some employers allow a new attempt after a set period, and some reissue a test after a documented technical failure. Ask the recruiter rather than starting a new attempt yourself.

Do I need a webcam for a remote technical assessment?

For proctored tests with image or video monitoring, yes. Most laptops have a built-in camera that is good enough. If yours doesn't work, contact the recruiter before the deadline to ask about alternatives, rather than starting without it.

Key takeaways

• The invitation and test landing page set the rules: time limit, monitoring, allowed languages and the AI policy. Read them fully before starting.
• Proctored platforms such as HackerRank can record tab exits, copy-paste, webcam snapshots and screenshots, depending on the employer's settings.
• In Nigeria, power and internet backup are part of test preparation: inverter or UPS, a charged laptop and a second network.
• In timed tests, solve the easiest problem fully first, test edge cases yourself and save as you go.
• AI rules differ between companies and between stages, so follow each employer's written policy or ask.
• If a connection fails, document it and email the recruiter immediately; never start a new attempt on your own.
• No genuine technical assessment asks you to pay.

Next steps

Pick the role you're applying for and match your practice to it, using our remote career guides and the interview question guides by role. When you're ready to apply, browse remote tech jobs open to applicants in Nigeria. After a search, choose "Get email updates" to get a free daily digest of new matching roles. If you'd like one-on-one interview prep sessions with someone on our team, that is part of WorkRemote Premium (₦29,999 a month). Premium also includes an interview-invite guarantee in your first week, which is an invite to interview, not a job offer.

Sources

• HackerRank Test Integrity, HackerRank Knowledge Base
• Extend Test Duration for Candidates, HackerRank Knowledge Base
• AI guidelines for our interviewing process, Greenhouse
• Guidance on candidates' AI usage, Anthropic