CodeSignal is a technical assessment platform that employers use to screen software candidates, and if a recruiter has sent you a CodeSignal link, it is most likely the General Coding Assessment (GCA): four coding questions in 70 minutes, scored from 200 to 600, and sometimes proctored over your webcam. Everything about the test in this guide comes from CodeSignal's own help center and its published framework for the test, read on 18 October 2026, so you get the format, the time each question is designed to take, how the score is built, what the camera records, and the retake rules in CodeSignal's own words. At the end is a two-week prep plan built around those numbers.
The short version
| Question | Answer, per CodeSignal | Source |
|---|---|---|
| How many questions? | 4, "of varying difficulty" | GCA structure |
| How long? | 70 minutes, "unless a different duration has been configured by the company" | GCA rules |
| Score range | 200 to 600 | Understanding Assessment Score |
| Languages | The GCA list includes Python 3, Java, C++, JavaScript, Go and more than 30 others | Languages per assessment |
| Can you Google? | Syntax only. No AI. | GCA rules |
| Proctored? | Some tests are. Camera, microphone, screen and photo ID. | Proctoring |
| Retakes | Only on a new invitation, within cooldown limits | Cooldown periods |
What CodeSignal is, and who uses it
CodeSignal sells hiring assessments, live coding interviews and training. Its "certified assessments" are tests it builds and maintains itself, and the General Coding Assessment is the one most candidates meet. CodeSignal describes it as "ideal for screening early career and new grad candidates at the top of the recruiting funnel" and says it "includes over 628,000 variations to minimize cheating". There is a separate Industry Coding Assessment (ICA) for mid to senior engineers, covered briefly below.
CodeSignal's customer stories page names Instacart, Greenhouse, Asana, Brex, Dropbox, Klaviyo, UnitedHealth Group, Ramp, Zillow, Handshake and the U.S. Office of Personnel Management, among others. Those are CodeSignal's own case studies, and some describe its interview or AI interviewer products rather than the GCA, so treat the list as "companies that buy CodeSignal", not "companies that send the GCA".
The link usually arrives after you apply, because CodeSignal plugs into the employer's applicant tracking system. Its help center has setup guides for sending assessments from Greenhouse, Lever, SmartRecruiters, Workday and Oracle HCM. If you want to know how that pipeline works on the employer's side, our guide to applicant tracking systems covers it.
It is a real filter. Ashby, another tracking system, reports in its 2026 recruiter productivity report that "in 2021, approximately 7-8% of applications resulted in an interview. Today that figure sits between 3.6% and 4.7% depending on role type", based on "over 109M applications and 247K jobs from January 2021 through March 2026". An assessment invite means you are already past the stage most applications never clear.
The assessment formats
General Coding Assessment. Four questions, all visible from the start, which you can answer in any order. CodeSignal's technical brief for the framework behind the GCA describes each module, including how long an average candidate is expected to take:
| Module | What it tests | Expected code | Expected time |
|---|---|---|---|
| 1. Basic Coding | Numbers, strings, arrays; "generally be solvable using a single loop" | 5 to 10 lines | 10 minutes |
| 2. Data Manipulation | Combining 3 to 5 basic operations; "1 to 2 nested loops" | 10 to 20 lines | 15 minutes |
| 3. Implementation Efficiency | Multidimensional arrays, hashmaps, splitting a task into functions, staying within time limits | 25 to 40 lines | 20 minutes |
| 4. Problem Solving | Common algorithms such as greedy, divide and conquer and two pointers | 25 to 35 lines | 30 minutes |
The brief also says what the test leaves out. Modules 1 and 2 exclude questions that need "noticing or proving patterns" or basic algorithms. Module 3 excludes graphs, number theory and dynamic programming. Module 4 excludes "specialized or advanced algorithms, such as Dijkstra, Kruskal, or Fast Fourier transform" and brain teasers. That is a narrower syllabus than most interview prep lists.
The time math. Add up CodeSignal's own expected times: 10 + 15 + 20 + 30 = 75 minutes, against a 70-minute limit. An average candidate working at the expected pace runs five minutes short before any debugging. So the plan has to bank time early. If you finish module 1 in 6 minutes and module 2 in 11, you have 53 minutes left for the two hard questions, three more than their combined 50-minute estimate.
Industry Coding Assessment. For experienced engineers, CodeSignal's ICA rules describe "1 domain-agnostic, project-based question with 4 progressive levels" with a maximum of 90 minutes, where "candidates must reuse, encapsulate, and refactor earlier code to maintain backward compatibility." It allows two attempts within a 180-day rolling window.
Custom assessments. Employers can also build their own tests on CodeSignal, with "a custom time limit set by the administrator", per CodeSignal's guide to taking an assessment. The invitation page tells you the duration and question count before you start.
How scoring works, in CodeSignal's own words
The score runs from 200 to 600. CodeSignal explains that the range was picked to avoid looking like an SAT, GRE or 0 to 100 percentage, so the numbers have "no inherent significance".
It is built in two tiers per module:
- Base points for test cases passed. "As a test-taker successfully completes more questions within a module, they can earn up to the module's base point value."
- Bonus points only for a complete solve. "Test-takers only earn bonus points for a module if they successfully solve 100% of the questions within the module," and harder, more discriminating modules carry more bonus.
The GCA page adds that responses are scored "based on correctness, speed, implementation, and your problem solving ability", and the rules page has two lines worth memorizing: "You are allowed to submit solutions as many times as needed" and "Our system will always use your highest-scoring submission as your final, graded submission for the question."
What the numbers mean in practice comes from CodeSignal's guide to setting cut scores, dated April 2024 and written for employers:
| Score | Questions solved | CodeSignal's description |
|---|---|---|
| 200 to 279 | None | "can write simple code to do some operations" |
| 296 | 1 | "familiar with programming" |
| 396 | 1 and 2 | "good implementation skills... Most tech companies require only these skills for the job." |
| 496 | 1, 2 and 3 | "good problem-solving skills, is familiar with algorithms" |
| 500 | 1, 2 and 4 | "great algorithmic, problem-solving, and implementation skills" |
| 600 | All four | "excellent algorithmic, problem-solving as well as implementation skills" |
CodeSignal labels these "estimated thresholds". Each employer chooses its own cut score, so no one outside the company can tell you the pass mark for a specific job.
Old scores on Reddit. Threads asking how people get "800+" use the old scale, which topped out at 850. CodeSignal moved every certified test to the new scale (it calls it Coding Score 2023), converted old scores automatically, and published a conversion table based on test-takers from 2021 and 2022. A few rows, where "Population %" is the share who scored at or below that level:
| Old Coding Score | New Assessment Score | Population % |
|---|---|---|
| 700 | 389 | 34% |
| 750 | 481 | 73% |
| 800 | 532 | 86% |
| 850 | 600 | 100% |
So an old "800+" target is about 532 or higher today. CodeSignal says the table is meant for converting employers' cut scores, not individual results.
Proctoring and what is recorded
You will see whether a test is proctored in your Assessments section before you start. For a proctored test, CodeSignal's proctoring article says you will:
- share your camera, microphone and screen for the whole session;
- close unrelated tabs, windows and applications;
- take a photo of your face and of a government-issued photo ID. The ID must show a clear photo, your full name and the expiration date, and "you may redact all remaining information on the ID card".
After the test, CodeSignal's verification team checks that the camera, microphone and screen were shared throughout, that the ID is valid, and that you followed the rules. On data, the same article says identification and proctoring data "is reviewed by CodeSignal only and is stored and deleted within 15 days" and "will not be shared with the company who requested your coding report." Proctoring "has no impact on the score you receive".
Two practical notes. Proctored tests do not work on phones or tablets, so use a laptop or desktop, per CodeSignal's browser and device page. And the timer "does not begin until you complete all the setup steps", so do not rush the setup.
What is allowed. On the GCA you may search for syntax, for example a reference page listing the methods of a C++ queue. You may not look up how to implement the thing the question asks for. The rules add: "This also means that the use of AI is not allowed, including syntax search." Outside IDEs are not permitted. Some employers switch on CodeSignal's own assistant, Cosmo, which CodeSignal says will not give the solution and whose conversation is logged in your report for the employer to read.
A two-week prep plan
This plan is ours, built from CodeSignal's module specifications and time targets above. It assumes about an hour a day and a working knowledge of one language. Pick that language on day 1 and do not switch.
| Days | Focus | What to do |
|---|---|---|
| 1 | Setup | Open CodeSignal's practice area, set the IDE theme and font, and run one practice question in your chosen language. Read your invitation's rules. |
| 2 to 3 | Module 1 | Ten single-loop array and string problems. Target: each in under 7 minutes. |
| 4 to 5 | Module 2 | Ten problems that chain string splits, comparisons and nested loops. Target: under 12 minutes. |
| 6 | Mock | Timed 30 minutes: one module 1 and one module 2 problem back to back. Note which mistakes cost time. |
| 7 to 9 | Module 3 | 2D arrays (transpose, rotate, walk in a set order), hashmap counting, simulations. Write helper functions. Target: under 20 minutes. |
| 10 to 12 | Module 4 | Greedy, two pointers, sorting with a custom comparator, prefix sums. Target: under 30 minutes. Go light on graphs and dynamic programming: the brief excludes them from module 3, and excludes advanced algorithms such as Dijkstra from module 4. |
| 13 | Full mock | 70 minutes, four problems, one of each module type. Do them in order 1, 2, then whichever of 3 or 4 you read faster. |
| 14 | Rest | Check camera, microphone, ID and browser. Charge the laptop. Clear the desk. |
Three rules for the day itself, each from CodeSignal's own documents:
- Submit early and often. Only your highest-scoring submission counts, so a partial solution submitted at minute 40 is safe to improve.
- Finish a module completely when you can. Bonus points only come with a 100% solve, so getting module 3 fully right is usually worth more than half-solving both 3 and 4.
- Bank time on the first two questions. The expected times add up to 75 minutes in a 70-minute test.
One limitation of CodeSignal's practice area: its practice FAQ says it "contains only one question for each question type". The same page says companies "will not see your activity or performance" there. Use it to learn the editor, then practise on any problem set that matches the module table. For the non-coding rounds that follow, our interview prep guide has a timed plan of its own.
Retakes and sharing scores
The retake rules surprise people, so here they are exactly.
You cannot retake on demand. CodeSignal's cooldown article says "you cannot make multiple attempts per invitation; you can only reattempt upon receiving a new request for results." Its worked example for the GCA allows at most 2 attempts in 30 days and 3 in 180 days: attempts on 1 January and 8 January mean the next is possible on 1 February, and a third on 1 February means waiting until 1 July. Using a second account to dodge the limit "is not permitted."
A new invitation gives you a choice. You can share an existing result or retake. But if you retake and score lower, "the company requesting the assessment will only receive your new result", per CodeSignal's sharing article. A company that already has your earlier result keeps it.
Sometimes sharing is not offered. CodeSignal lists two reasons: the company set an age limit on results, or it requires proctoring and your earlier result was not proctored. The cooldown article says both cases grant a new attempt regardless of cooldown, and that attempts cut short by technical issues "do not count against any assessment attempt limits."
A simple rule: if you scored well recently, share it. If you scored poorly and have prepared since, retake, knowing the new number replaces the old one for that employer.
If the link expired or something broke
- Expired invitation. CodeSignal says "the hiring company makes the decision on whether to re-administer an assessment", so write to your recruiter.
- "Assessment not Found" after you started. The clock keeps running if you leave, and the test times out. Contact support@codesignal.com if you see this the first time you open the link.
- Accommodations. CodeSignal's prep article says to ask the recruiter or the company that sent the invitation.
Other employers use video screens instead of, or as well as, coding tests; our HireVue guide covers that format.
Where ApplyEze fits
ApplyEze does not take assessments for anyone. A CodeSignal link arrives only after an application goes in, and the application is the part ApplyEze handles: it completes applications on 12 platforms, including Greenhouse, Lever and Ashby, with a resume and cover letter written for each posting. The 70 minutes are yours.