Coding Online Assessment (OA): HackerRank and CodeSignal Formats and Proctoring

What an online assessment is and where it sits in the pipeline

An OA is a screening step: you receive a link, take the test alone within a deadline, and a score or report goes to the hiring team. Where it sits depends on the company and the level. Amazon calls the OA the first step for its student and graduate software development roles, and for SDE II it places the OA between the application and the interview loop. Google's hiring page says you may be asked to take the Google Hiring Assessment, which measures workstyle skills, and role-related assessments such as a coding exercise before interviews begin.

The table collects what those official pages published on November 14, 2026. Treat it as an illustration of the range rather than a promise about your invitation: Amazon's student page says its full-time OA comes in one or two parts depending on the country and tells candidates to check the OA email for the structure that applies to them. The pages are not perfectly consistent with each other either, which is one more reason to trust the invitation over any summary.

• Amazon Jobs: Online assessment prep for SDE roles (students and graduates)
• Amazon Jobs: Online Assessment Prep, Software Development Engineer II
• Amazon Jobs: SDE II Interview Prep
• Google Careers: Our hiring process
• Microsoft Careers: How we hire

HackerRank assessment: format, scoring and what is recorded

HackerRank's candidate FAQ says you do not need a HackerRank account: you open the link from the invitation, and the test duration, set by the recruiter, is shown in the invitation and on the login page. A sample test is linked from the instructions on that page. Inside the test, Run Code compiles your solution and runs it against the test cases as often as you like without affecting your score, while Save & Proceed submits the answer. A test case passes only when your output matches the expected output exactly, and some test cases are hidden. The timer keeps running if you lose your connection, logging out ends the attempt, and if time runs out the last compiled version of your code is submitted.

Does HackerRank use the camera? Only when the hiring company turns on a feature that needs it. The candidate FAQ says the invitation email tells you if a test is proctored and that a proctored test needs a webcam-enabled computer; HackerRank's image-proctoring article says that feature is disabled by default. HackerRank's integrity documentation, written for employers, lists what exists. Two features are described as built in and on by default: copy and paste tracking, which records copy and paste actions and puts pasted content into your report, and tab proctoring, which records how often and for how long you leave the test window. That overview was last updated about a year ago. HackerRank's plagiarism best-practices guide for employers, of similar age, also says copy and paste tracking is enabled by default, and it recommends that employers leave the on-screen alert off, so do not expect a warning when a paste is recorded.

Companies can add stricter modes. Secure Mode enforces full screen, blocks copy and paste, prevents multiple monitors and warns when you switch tabs. Proctor Mode adds AI-powered screenshot analysis, plagiarism detection and webcam anomaly detection; its own article says candidates first review the rules and give consent, must grant webcam and screen-sharing access and use a single monitor, and that screenshots are captured periodically during the test. Desktop App Mode adds operating-system-level monitoring through an app you install. Separately, image proctoring captures webcam snapshots at intervals for the report, and photo identification captures your image before the test. Which of these apply is the hiring company's choice, so the rules screen of your own test is the final word.

When a question reads from standard input and writes to standard output, a stray debug line makes the output differ from the expected text, and that is a wrong answer. The template below is a common shape for such a solution in Python. Run locally with the input “8” and “-2 1 -3 4 -1 2 1 -5” it prints 6; with the input “1” and “-7” it prints -7, a single negative value being the kind of edge case hidden tests check.

import sys


def best_streak(gains: list[int]) -> int:
    """Largest sum of a contiguous run of daily gains (Kadane's algorithm)."""
    best = current = gains[0]  # assumes n >= 1; check the stated constraints
    for gain in gains[1:]:
        current = max(gain, current + gain)
        best = max(best, current)
    return best


def main() -> None:
    tokens = sys.stdin.read().split()
    n = int(tokens[0])
    gains = [int(token) for token in tokens[1:1 + n]]
    print(best_streak(gains))  # the only line written to stdout


if __name__ == "__main__":
    main()

• HackerRank candidate support: Frequently Asked Questions Before the Test
• HackerRank candidate support: Frequently Asked Questions During the Test
• HackerRank support: HackerRank Test Integrity
• HackerRank support: Proctor Mode
• HackerRank support: Image Proctoring and Image Analysis
• HackerRank support: Plagiarism Best Practices Guide

CodeSignal assessment: GCA structure, score and proctoring

CodeSignal's best-known test is the General Coding Assessment (GCA). Its knowledge base describes four questions of varying difficulty and 70 minutes in one sitting, unless the company has configured a different duration. All four questions are open from the start, you write code in CodeSignal's own editor because outside IDEs are not permitted, and you may submit as often as you want: the highest-scoring submission for each question is the one that counts, and you must submit before leaving a task for its code to be saved. The knowledge base says responses are scored on correctness, speed, implementation and problem solving. The result is an Assessment Score from 200 to 600, built from base points for the questions you solve plus bonus points for fully completing a module, and it is certified only if no unusual activity took place during the session.

CodeSignal proctoring is explicit about what it records, and the Assessments page shows whether proctoring is required before you start. For a proctored assessment you are asked to share your camera, microphone and screen for the duration of the session, to take a photo of your face and to show a government-issued photo ID; the recording is reviewed afterwards by CodeSignal's proctoring verification team, and the timer does not start until the setup steps are complete. CodeSignal states that proctoring has no impact on the score, that identification and proctoring data is reviewed by CodeSignal only, is not shared with the company that requested the result, and is stored and deleted within 15 days.

Two rules surprise people. During the GCA you may search the web for syntax, such as how to take a substring in Python, but not for the logic of a solution, and the rules page says AI is not allowed even for syntax. And retakes are limited by cooldown periods. CodeSignal lists three cooldown categories that vary by assessment; its worked examples for the GCA follow the one that allows at most three attempts in a 180-day window with no more than two in 30 days. You get one attempt per invitation, a new attempt needs a new request from a company, and during a cooldown you share a previous score instead of retaking. Rules differ between CodeSignal's assessments, so read the ones shown before your session.

• CodeSignal: What should I expect when I take the General Coding Assessment (GCA)?
• CodeSignal: General Coding Assessment (GCA) Rules and Setup
• CodeSignal: What is proctoring and how does it work?
• CodeSignal: Understanding Assessment Score
• CodeSignal: What is a cooldown period?
• CodeSignal: How do I prepare for this coding assessment? Am I allowed to use Google?

HackerRank vs CodeSignal: platform comparison

The two platforms differ most in who controls the test. On HackerRank the hiring company assembles and configures nearly everything, so two HackerRank tests can feel unrelated. CodeSignal's certified assessments such as the GCA are standardized, with published rules and a score that can be shared with more than one employer. The table compares the documented defaults as of November 14, 2026; your invitation overrides all of it.

• HackerRank support: HackerRank Test Integrity
• CodeSignal: General Coding Assessment (GCA) Rules and Setup

Integrity rules and AI tools: what the official pages say

Policies on outside help are set per company and per test, and they are not uniform. Amazon's page for student and graduate roles says that during the coding assessment you may use publicly accessible online resources such as language documentation, but not sites that require a login or private repositories; it adds that browser usage is logged, that using print screen ends the session, and that you should avoid copying and pasting because the code is expected to be your own. Microsoft's candidate code of conduct asks for your own skills without outside assistance unless explicitly permitted. Google's interview tips say Google Search and AI are not permitted during interviews.

Some tests now include an AI assistant on purpose. HackerRank's candidate guide for the Amazon coding challenge describes two sections: single-file coding questions, where generative AI is not permitted, and a multi-file code repository question that has an embedded AI Assistant when the test setter enables it. The guide says you are not penalized for using that assistant, that it gives guidance rather than full solutions, and that your conversation with it is recorded and visible to the evaluator. The practical rule: the tools inside the test window are the allowed tools, and anything else needs a written yes in the instructions or from the recruiter.

• Read the rules screen and tick boxes slowly; on CodeSignal you must acknowledge each rule before the timer starts.
• If a rule is unclear, email the recruiter before starting, not after.
• Write the code yourself in the test editor. On HackerRank pasted content appears in the report by default, and Amazon tells candidates to avoid copying and pasting.
• Stay in the test window unless the rules allow a documentation lookup. On HackerRank the number and length of window exits are reported by default.
• Take the test under your own account and identity; CodeSignal's cooldown page says using a different account to bypass a cooldown is not permitted.

• Amazon Jobs: Online assessment prep for SDE roles (students and graduates)
• HackerRank candidate support: Preparing for your Amazon OA
• Google Careers: Interviewing at Google, best practices, advice, and tips
• Microsoft Careers: How we hire

A two-week preparation plan

OAs reward fluency more than brilliance: reading a statement quickly, choosing a known pattern, and producing exact output without an IDE's help. Amazon's prep pages recommend practicing in the language you will use and coding outside an IDE, and both platforms offer a practice environment. Two weeks is enough to remove the avoidable losses.

Split the time between untimed pattern review and timed sets. A spaced-repetition app such as RecallDeck can keep complexity facts and pattern triggers fresh between sessions, but the timed sets are what prepare you for the clock.

• Days 1-2: take the platform's sample or practice test to learn the editor, input format and submit buttons.
• Days 3-7: one topic a day (arrays and hashing, two pointers and sliding window, binary search, trees and graphs, dynamic programming), three or four problems each, written without autocomplete.
• Days 8-11: timed sets that mirror your invitation, for example two problems in 90 minutes or four in 70, in the real practice environment.
• Day 12: review every failed test case and write down the edge case behind it: empty input, one element, duplicates, negative numbers, maximum size.
• Day 13: one full dress rehearsal at the time of day you plan to take the test, with camera and screen sharing on if your test is proctored.
• Day 14: light review only; check the deadline in the invitation and your equipment.

• The best coding practice platforms for interview preparation
• Data structures and algorithms interview questions
• Big O notation explained, with a cheat sheet
• Blind 75 vs NeetCode 150 vs LeetCode 75
• Backend interview track

Test-day checklist

Most of this list comes straight from the platforms' own setup pages. Go through it an hour before you start, because the timer does not pause for a missing webcam driver, and on HackerRank it does not pause for a dropped connection either.

• Use a laptop or desktop, not a phone or tablet, with the latest version of a browser the platform lists; HackerRank's candidate FAQ says its tests are best supported on Chrome and Firefox.
• Plug in power and use the most stable connection you have.
• If the test is proctored, test the webcam and microphone, and have a valid government-issued photo ID ready for CodeSignal.
• Close unrelated tabs, windows and applications; disable browser extensions if the instructions ask for it.
• Pick a quiet place and block more time than the timer: Amazon suggests two hours for its OAs.
• Read every problem before coding and start with the one you are surest of.
• Check constraints to choose the complexity, then test empty, single-element and maximum-size inputs.
• Remove debug prints before submitting; output is compared as exact text.
• Submit a working partial solution before optimizing, and leave five minutes to resubmit your best version. On CodeSignal, submit before you switch tasks, because unsubmitted code is not saved.
• Wait for the confirmation page, and complete any required survey: Amazon says that not completing the feedback survey in its student OA delays results.

• The day-before technical interview checklist
• Technical phone screen interview: format and plan

Quick answers

Frequently asked questions