The live CodeSignal GCA is four coding tasks in 70 minutes, scored 200–600. Forum threads that still quote 300–850 are describing a retired scale. The IDE only keeps a task if you hit Submit before you leave it, and it grades your highest-scoring submit even if the last one is a syntax error.
Search still returns codesignal gca, codesignal gca score, and codesignal gca 70 minutes as live queries. The first hit is CodeSignal's own knowledge base: the structure article (19 Aug 2026) and the rules and setup article (25 Jul 2026). Read those two pages before another LeetCode hard.
What is the live GCA, not the 2022 one?
CodeSignal's structure article is short: four questions of varying difficulty, you split the 70 minutes however you want, all questions are visible. The rules article adds the caveat most roundups skip: 70 minutes unless the company configured a different duration. If the invite says 90, believe the invite, not a Reddit recap of Capital One's default.
Scoring is a single Assessment Score from 200 to 600. CodeSignal documented the conversion off the old 300–850 "Coding Score" in 2023 and still publishes the 200–600 range on Understanding Assessment Score (updated 24 Aug 2026). A screenshot of an 800 from 2022 is not a 2026 cutoff.
Certified setup happens before the timer. Face photo, then photo ID, then a checkbox list of rules. The timer does not start until those steps finish. There is a Practice button on that same screen if you have never used the in-browser IDE.
Does the editor autosave when you jump to Q4?
No. The rules page is explicit: you can move between tasks, but you must submit before leaving a task or the code does not save. People lose a working Q2 because they tab over to peek at Q4, change one loop, and come back to a blank or stale editor.
Submit is cheap. The same article says you may submit as many times as you need. Do that before you touch another tab.
Which submit actually gets scored?
The highest-scoring submission for that question, not the last one. CodeSignal's wording: even if the last submit has a syntax error, the higher score is kept.
That changes the last eight minutes. A common panic move is to "just try one more rewrite" on Q3, introduce a missing colon, and assume the whole task is now zero. It is not, if an earlier submit already passed tests. The rewrite only hurts you if you never banked a green run.
What it does not do: recover work you never submitted. Highest-of-submits is not an autosave.
Practical order that matches the scoring contract:
- Get a correct, slow solution on Q1 and Q2. Submit. Do not polish.
- Same for Q3. Submit as soon as visible tests pass.
- Only then open Q4. If you get a partial, submit the partial. Leave Q3 alone unless you still have a passing copy in the bank.
Q4 is supposed to be hard. Community writeups (including the 600/600 Medium post people still link) treat a clean Q1–Q3 plus a partial Q4 as a strong outcome. Chasing Q4 by unsaving Q3 is how a 575-shaped attempt becomes a 500-shaped attempt.
Is Cosmo or ChatGPT allowed on a certified GCA?
On the certified GCA, no. The rules FAQ is narrower than most blogs. Syntax search is allowed so you do not have to memorize every STL method. AI is not allowed, including as a syntax search. Their own examples:
- Allowed: open the C++
queuereference to see which methods exist. - Not allowed: open a tutorial on how to implement a deque, because that page is helping you with the solution.
If the company sent you an AI-assisted CodeSignal assessment instead, that is a different product. The GCA rules page does not apply to that transcript. Mixing the two is the same failure mode as treating every HackerRank panel as Copilot: the invite and the in-IDE banner are the source of truth, not the brand name on the calendar invite.
aceround.app — AI interview assistant — keeps a longer GCA prep map (topic mix, score bands, what happens after you pass) at the AceRound CodeSignal GCA guide. The same desktop client also covers OA-style timed tests and the live round after. This article stays on the contract the knowledge base actually states.
What fails hidden tests after the samples pass?
Not a leaked GCA item. A stand-in for the Q2 ticket that shows up in every "I passed the examples and still timed out" thread: count index pairs i < j where a[j] - a[i] == k. Visible tests are n ≤ 200. Hidden tests go to n = 10^5.
The nested loop is correct. It is also O(n²). On the hidden file it is a timeout, not a wrong answer, which is why people screenshot green samples and still drop the task.
from collections import Counter
def count_diff_pairs_slow(a: list[int], k: int) -> int:
# Correct. Dies at n = 1e5.
n = len(a)
total = 0
for i in range(n):
for j in range(i + 1, n):
if a[j] - a[i] == k:
total += 1
return total
def count_diff_pairs(a: list[int], k: int) -> int:
seen: Counter[int] = Counter()
total = 0
for x in a:
total += seen[x - k]
seen[x] += 1
return total
assert count_diff_pairs([1, 3, 2, 4], 1) == 2
assert count_diff_pairs([5, 5, 5], 0) == 3
The linear version walks once, asks "how many earlier values equal x - k?", and banks that count. Same answers on the samples. Different wall clock on the hidden file.
GCA-shaped prep is this ticket, not another Hard on a whiteboard: constraints first, then a solution that survives n = 10^5, then Submit, then leave the task. If the nested loop is all you have with four minutes left, submit it anyway. A timeout on hidden tests still beats an empty editor.
Time box that matches the four-task layout:
| Task | What "done" means | Budget |
|---|---|---|
| Q1 | Samples + obvious edges, submitted | 5–8 min |
| Q2 | Linear or n log n, submitted |
8–15 min |
| Q3 | Working solution in the bank before you open Q4 | 15–25 min |
| Q4 | Partial is a valid submit | leftover |
Those buckets are community pattern, not CodeSignal SLAs. The official page only promises "varying difficulty." The budget is there so Q3 gets a submit while it still compiles.
FAQ
Does a 560 always move you forward?
No. Companies set their own cut scores. CodeSignal publishes a guide for employers on setting those thresholds. Public forums will quote Capital One / HubSpot numbers that are a year old. Treat 550 / 575 / 595 as folklore until the recruiter states a number.
Can I retake?
CodeSignal limits how often a certified GCA can be retaken inside a window. The 2024 framework writeup still circulating says three attempts in 180 days. Confirm on the account page the day you sit it; do not burn an attempt to "see the IDE." Use the Practice button on the setup screen for that.
Does tab-switching to docs.python.org fail certification?
The published example of an allowed lookup is a language reference page for methods. A how-to for the algorithm is not. If the in-IDE rule list is stricter than that FAQ, the in-IDE list wins.
Should I paste a finished answer in one shot?
Do not. Independent of whether it is allowed: you want incremental submits so a later syntax error does not leave you with nothing banked. Type it. Submit when tests go green.
What to do in the 24 hours before the invite expires
- Open CodeSignal's two GCA articles, not a 2022 score conversion chart.
- Run one session in their practice IDE, in the browser, with the language you will actually use.
- Drill one
n = 10^5timeout ticket like the pair-count above until the linear version is muscle memory. - Decide the submit rule in advance: nothing leaves a tab without a submit, Q4 never unsaves Q3.
If a company GCA used a duration other than 70 minutes for you, drop the number in the comments. The rules page says that configuration exists. The public threads still pretend every invite is the default.
Drafting was AI-assisted. Facts in this piece were checked against CodeSignal's public knowledge base (GCA structure, 19 Aug 2026; GCA rules and setup, 25 Jul 2026; Assessment Score range, 24 Aug 2026). It is not an official CodeSignal guide and it is not a leaked question set.
Top comments (0)