CodeSignal Industry Coding Assessment: how the four levels work and how to prepare
Quick answer: the CodeSignal Industry Coding Assessment (ICA) is one project-based question with four progressive levels, a 90-minute maximum, and a 200-600 score. Each level adds features to the code you wrote for the previous one, so the test rewards code that is easy to extend, not clever one-off solutions. CodeSignal says candidates are not necessarily expected to finish every level. If you only need the side-by-side with the General Coding Assessment, see our GCA guide; this page goes deeper on the ICA itself.
What the ICA is built to measure
CodeSignal's technical brief for the Industry Coding Framework says it is designed to assess the coding skills of senior software developers and engineers, and lists the skills it targets: software design patterns, code implementation, problem solving, data structures and data processing, and maintaining a codebase through refactoring and encapsulation. Its datasheet describes the audience as mid-to-senior engineers.
Two design choices follow from that. First, the task is language-agnostic and domain-agnostic: it is a small simulated system (the brief's own example is a file hosting service), not an algorithm puzzle. Second, the brief says each level introduces new methods while "retaining the integrity of previously implemented method contracts", so you extend and refactor rather than start over.
The four levels, one by one
The brief gives an approximate size for each level. These are CodeSignal's own estimates for a typical candidate, not requirements.
| Level | Focus | What is asked | Typical time (brief) |
|---|---|---|---|
| 1 | Initial design and basic functions | 3-4 simple methods; conditions, loops, strings, 1-2D arrays, hash tables, corner cases | 10-15 min, 15-20 lines |
| 2 | Data structures and data processing | 1-2 more methods of medium difficulty; calculations, aggregation, filtering, JSON/CSV-style formats; reuse Level 1 code | 20-30 min, 30-45 lines for levels 1-2 |
| 3 | Refactoring and encapsulation | 3-5 additional methods of medium to advanced difficulty, some wrapping earlier functionality with extra logic; helper methods and classes | 30-60 min, 90-130 lines for levels 1-3 |
| 4 | Extending design and functionality | 1-2 more methods, backward compatible with the earlier design | 30-60 min, 110-160 lines for the whole project |
Add those ranges up and they exceed 90 minutes, which is consistent with CodeSignal saying you are not necessarily expected to complete everything. The brief also says "a major factor in assessing candidates' skill levels is to see how far they can progress within the given time frame."
What a real ICA task looks like
The brief includes a worked example. It is a simplified file hosting service, and it shows how the levels stack:
- Level 1:
FILE_UPLOAD,FILE_GET,FILE_COPY, with runtime exceptions for duplicates and missing sources. - Level 2:
FILE_SEARCH(prefix)returning the top 10 matches ordered by size, ties broken by file name. - Level 3: every operation gets a timestamped
_ATvariant, and uploads can carry a time to live. Search must only return files still alive. - Level 4:
ROLLBACK(timestamp)restores the storage state at an earlier time, with all TTLs recalculated.
Notice what Level 3 does: it does not ask for new ideas, it asks you to thread a timestamp through the methods you already wrote. If Level 1 copied and stored files in a way that cannot be queried by time, Level 3 hurts. The brief says as much: the more reusable your earlier methods, the easier the later levels. This is an example of the format; actual tasks are randomized and vary.
How the ICA is scored
CodeSignal's ICA rules say Coding Scores range from 200 to 600, that higher scores indicate more of the assessment completed, and that only test-takers who submit nothing receive 200. The brief's example task also says partial credit is granted for each test passed and tells candidates to press Submit often, so progress on a level counts even if you do not finish it.
What we could not confirm: we found no official table that maps ICA scores to levels solved. The question-by-question anchors in our GCA article (for example 396 or 496) come from the four-question GCA and should not be read onto the ICA. A number like 420/600 on the ICA tells you that you got part of the way; what counts as good is the employer's decision, and each company sets its own cutoff. Ask the recruiter what theirs is.
Retakes: the ICA rules page says two attempts within a rolling 180 days, and a new invitation from the company is required. CodeSignal's cooldown rules can also block a new attempt, in which case you share a previous score. Check your own invitation, since the company configures the assessment.
How to prepare for a project-style test
- Practice the format, not just problems. Take one small system (an in-memory key-value store, a bank, a file system) and extend it in four stages: basics, a query, a time dimension, then a rollback or undo. Our CodeSignal practice test guide covers the official practice environment.
- Read all levels' text early, but code them in order. The brief's own tips: read the whole question first, implement level by level, do not change existing method signatures.
- Keep Level 1 boring and extendable. Small helper methods, one place where state lives, no premature cleverness. You will wrap these methods at Level 3.
- Submit often. Partial credit per passing test means a submission at the end of each level is cheap insurance.
- Run the old tests after every change. Level 4 explicitly assesses "adjust previous functionality without regressions."
- Rehearse the clock. Aim to finish Levels 1-2 in the first 30-40 minutes so Levels 3-4 get the time that matters.
Rules, proctoring and AI tools
What is allowed during an ICA is set by CodeSignal's rules and by the employer's configuration, and both can change. CodeSignal publishes how its detection and proctoring work; we summarise it in can CodeSignal detect AI, and compare it with its rival in CodeSignal vs HackerRank. Before any assessment, read the instructions page and ask the recruiter in writing what is permitted. Breaking the rules can cost you the result or the application, and it is not worth the risk.
For practice and for live interviews where AI help is explicitly allowed, a desktop assistant such as Interview Copilot can read a coding problem from a screenshot and talk through approaches; there is a free plan to try it. Whether you may use any assistant in a given assessment is the employer's rule, not ours, so confirm it first. See also how employers are changing the format in AI-assisted coding interviews.
Sources
- CodeSignal - Industry Coding Skills Evaluation Framework, technical brief (levels, timings, 200-600, example task)
- CodeSignal - Industry Coding Framework datasheet (audience, 90 minutes, level summaries)
- CodeSignal Support - ICA rules (score range, attempts, structure)
- CodeSignal Support - converting historical coding score thresholds
- CodeSignal Support - cooldown periods
Checked 12 November 2026. CodeSignal may change the format or limits; the invitation you receive is the authority.
FAQ
What is the CodeSignal Industry Coding Assessment?
It is a certified CodeSignal assessment with one project-based question split into four progressive levels and a maximum of 90 minutes. Each level adds features to the code from the previous one. CodeSignal describes it as aimed at mid-to-senior engineers, and its score runs from 200 to 600.
How many levels does the ICA have and do I need to finish them all?
Four. CodeSignal says candidates are not necessarily expected to complete every level in 90 minutes, and that how far you progress is part of the signal. Partial credit is awarded for passing tests, so submit after each level instead of waiting until the end.
How is the ICA different from the GCA?
The GCA is four separate questions in 70 minutes by default, while the ICA is one project built up over four levels in up to 90 minutes. On the ICA you reuse and refactor your own earlier code, so there is no easy question to skip. Our GCA article has the full comparison table.
Is 420 out of 600 a good ICA score?
There is no official pass mark and we found no published table mapping ICA scores to levels solved. 420 means you got partway through the project. Each employer sets its own cutoff, so ask the recruiter what theirs is rather than comparing with GCA score anchors.
How many times can I take the ICA?
CodeSignal's ICA rules say two attempts in a rolling 180 days, and you need a new invitation from the company each time. Cooldown rules can also apply, in which case you share a previous score. Check your invitation, because the employer configures the assessment.
What is the best way to prepare for the ICA?
Practice building one small system in four stages, such as storage, a query, a time dimension and a rollback. Keep early methods small and extendable, never change method signatures, submit often, and rerun older tests after every change. Confirm with the recruiter which tools and resources are allowed.