CodeSignal Pre-Screen vs GCA: Questions, Scoring, and What Employers See

A CodeSignal Pre-Screen invitation can contain the General Coding Assessment (GCA). These are not necessarily two competing tests. GCA identifies a particular assessment; “pre-screen” can describe the hiring stage or integration that sends it. For example, RippleMatch's own integration documentation describes a CodeSignal Pre-Screen request that delivers the GCA.

Before choosing practice, check the assessment name in the invitation.

Which rules actually follow from the label?

Invitation wording	What it establishes	What it does not establish
General Coding Assessment / GCA	The named assessment's published format applies	The employer's hiring cutoff
Pre-Screen, without an assessment name	A screening request exists	Four questions, a 70-minute timer, or a particular scoring scale
A different named or custom assessment	Read that assessment's instructions	GCA rules merely because CodeSignal hosts it

The practical mistake is rehearsing GCA pacing for an invitation that never names the GCA. An ATS stage name is not a test specification. If the email only says Pre-Screen, inspect the pre-start details without beginning the timed attempt; ask the recruiter for the exact assessment name if it remains unclear.

GCA questions and timing

CodeSignal's GCA format guide specifies four coding questions in 70 minutes. Candidates can access all four throughout the assessment and choose their order. That guide also prohibits outside IDEs. The rules displayed for the actual attempt still matter, especially permitted resources and proctoring.

As a preparation exercise, try a four-problem session with one shared 70-minute budget. Afterward, separate time spent misunderstanding a requirement from time spent implementing or debugging it. That diagnosis is more useful than assigning a fixed difficulty label to question three or four. This exercise is editorial advice, not a prediction of the questions CodeSignal will serve.

The current GCA Assessment Score is 200–600

CodeSignal calls the current measure an Assessment Score, with a 200–600 scale. Its scoring explanation describes weighted skill modules. Do not treat the score as a simple percentage of four questions solved, or import an older Coding Score screenshot into the current scale.

A score of 500 is not “500 out of 600 questions,” a percentile, or a universal pass. A hiring decision requires the employer's threshold and other criteria. Likewise, a score on an unnamed Pre-Screen cannot be interpreted using GCA rules until the underlying assessment is identified.

What employers see, and what CodeSignal verifies

The Assessments quick-start guide describes employer reports with scores, skill and question detail, and code-replay controls. That report is distinct from the raw recordings used to verify a proctored session.

CodeSignal's proctoring explanation says identification and proctoring data are reviewed by CodeSignal and are not shared with the requesting company. An employer's ability to replay code does not mean it receives the webcam video or ID image. For the separate question of previously shared scores, use the sharing rules rather than the Pre-Screen label.

Resolve the invitation before you start

Use this short message when the invitation is ambiguous:

My invitation calls this a CodeSignal Pre-Screen. Could you confirm the assessment name, duration, permitted languages, and whether an existing eligible result can be shared? I want to prepare for the correct format before starting the timer.

Once the format is clear, use the platform's familiarization flow to learn navigation and submission. A practice resource cannot establish your employer's deadline or sharing settings.

Sources and Further Reading

Documentation checked: September 6, 2026.

• RippleMatch's own integration documentation
• GCA format guide
• scoring explanation
• Assessments quick-start guide
• proctoring explanation