Your first CodeSignal General Coding Assessment attempt is rarely for one company. CodeSignal lets you share an existing score with any company that later asks for the same assessment. It also limits retakes. Some certified assessments allow three attempts in 180 days, with at most two in 30 days. Say you take it cold for a company you barely care about. That score may be the one your target company sees. A retake doesn’t fix that cleanly either. If you retake and score lower, the company that asked gets only the new result. The tactic is to treat the GCA as one exam for your whole search. Take it once, prepared, on your own date. Practice in CodeSignal’s own editor, because outside IDEs aren’t permitted. And finish questions completely, since the score pays a bonus only for a fully solved module. Below is one Android engineer with two invites, worked through to a plan.
One CodeSignal score can travel to every company that asks for it
Here’s the running example. You’re an Android engineer with five years of Kotlin. A mid-size company you’re lukewarm about sends a GCA invite on Monday. It’s due Friday. Your target company says its own GCA invite will come next week. You haven’t solved a timed algorithm problem in a year.
The obvious move is to take Friday’s test as a warm-up. CodeSignal’s own help pages explain why that’s risky. Its page on sharing results with employers gives you two options for each new invite. You can share an existing eligible result. Or you can retake, if you’re outside the cooldown period. CodeSignal describes its own product here, so read these pages as the vendor’s account.
The cooldown period page sets the limits. They vary by certified assessment. The strictest allows one attempt in 180 days. The loosest allows three in 180 days, with at most two in any 30 days. The page doesn’t say which limit applies to the GCA. Its worked example uses the GCA, though. That example follows the three-in-180 rule.
Now apply that to the example. Friday’s warm-up is attempt one. The target company’s invite arrives the following week. You can share Friday’s score or spend attempt two. Either way, the warm-up has already shaped what the target company can see.
A retake replaces what the next company sees, even when it’s lower
Suppose Friday goes badly. You plan to retake for the target company. The sharing page covers this case directly. If you retake and score lower, the requesting company receives only the new result. That holds whether the new score is higher or lower than the old one.
The same page adds a second detail. A company that already received a result keeps access to it. So if the lukewarm company invites you again later, it still sees Friday’s score. A retake can’t hide an old result from a company that has it.
The cooldown page’s own example shows how fast the window closes. Two attempts a week apart in January block a third until February. A third attempt on February 1 blocks a fourth until July 1. In our example, a bad warm-up plus a nervous retake uses two attempts. That could leave one for the next six months. That matters if a third company invites you in November.
The exceptions are narrow. CodeSignal grants a new attempt after a technical failure its team identifies. It also does so when a company needs a proctored result and you only have unproctored ones. And it does so when your old score is older than the company’s age limit. None of these help with a bad day.
The CodeSignal General Coding Assessment rewards a finished question more than half-done ones
Before you plan the attempt, know what earns points. CodeSignal’s Understanding Assessment Score page says the final score runs from 200 to 600. Questions are grouped into modules. Base points grow as you complete more questions in a module. Bonus points come only when you solve 100% of the questions in a module. Harder modules that better separate test-takers carry more bonus.
The GCA structure page gives the format. There are four questions of varying difficulty in 70 minutes. You can split the time however you like. It also lists speed among the things your responses are scored on. The scoring page doesn’t explain how speed enters the number. So spend your minutes where they finish a question.
In practice, a question that passes every test earns its bonus. A question that passes most tests doesn’t. Take the running example. A full solve on question three earns a bonus. Partial credit on both three and four earns no bonus at all. So the plan below gives question three a fixed block of time to finish it.
Two rules make finishing cheaper. The GCA rules page says you can submit as many times as you need. The system keeps your highest-scoring submission, even if a later one has a syntax error. So submit a working version early, then improve it. But you must submit before leaving a task, or the code isn’t saved.
Kotlin is allowed, but Android Studio isn’t
CodeSignal’s language list includes Kotlin for the GCA. So you don’t need to switch to Python. But the structure page says you code in the assessment itself. Outside IDEs aren’t permitted.
That rule catches Android engineers in particular. Our daily work happens in Android Studio, with autocomplete and instant error highlighting. The reflex is to draft in the IDE and paste the result into the browser. CodeSignal’s Suspicion Score page tells hiring teams how such pastes look. It tells reviewers to check the size and number of paste events. Larger and more frequent pastes count as more suspicious. Pasting after a stretch of no activity is called a common cheating pattern. Copying the question text is tracked too.
The same page says a high Suspicion Score isn’t proof of cheating. It leaves the call to the hiring team. You still don’t want a reviewer reading a replay of your session to decide. The rules page also says AI use isn’t allowed, even for syntax search. Plain syntax lookups on documentation sites are allowed. CodeSignal’s syntax search page draws that line. It was last updated about a year ago.
The fix is to know the standard library well enough to type it without help. Most GCA-style tasks lean on a small set of collection calls. Here’s a drill to type from memory in a plain editor until it compiles first time.
fun main() {
val words = listOf("pay", "card", "pay", "wallet", "card", "pay")
val counts = words.groupingBy { it }.eachCount()
println(counts) // {pay=3, card=2, wallet=1}
val ranked = counts.entries.sortedWith(
compareByDescending<Map.Entry<String, Int>> { it.value }.thenBy { it.key }
)
println(ranked.map { it.key }) // [pay, card, wallet]
val queue = ArrayDeque<Int>()
queue.addLast(1); queue.addLast(2); queue.addFirst(0)
println(queue.removeFirst()) // 0
println(listOf(3, 1, 4, 1, 5).windowed(2).map { (a, b) -> b - a }) // [-2, 3, -3, 4]
}
The comparator line is the easiest one to get wrong without autocomplete. On its own, compareByDescending infers the entry type. Chain thenBy onto it and inference fails. Then you have to write the type argument out. That’s the kind of error that costs five minutes in a browser editor.
A sample plan for two invites and one attempt
Back to the example. The goal is one prepared attempt that both companies can see. Start with a message to the lukewarm company’s recruiter on Monday.
Hi Dana, thanks for sending the CodeSignal assessment. I’m interested in the role. I’d like to take the assessment on the 20th instead of this Friday. That lets me give it a proper block of time. Would that date work for your timeline? If it doesn’t, please tell me the latest date that does.
Then use the time before the 20th like this.
Days 1-3 CodeSignal's practice assessment, in its own editor, Kotlin selected
Days 4-8 one timed 4-question set every other day; no IDE open at all
type the stdlib drill from memory before each set
Days 9-10 rest; check webcam, ID photo and a quiet room for proctoring
Attempt first 25 min: questions 1 and 2, submit each as soon as tests pass
next 30 min: question 3 until every test passes
last 15 min: question 4, or more edge cases on 3 if it isn't full
After share this score with the target company; don't retake unless
the result is clearly below what you scored in practice
The message asks only for a date. It also gives the recruiter an easy fallback answer. A recruiter may say no. Then you decide with the real deadline in hand.
The run sheet follows the scoring rules above. Practicing in CodeSignal’s editor removes the urge to paste from Android Studio. Early submits protect your best score, since the highest submission is kept. The 30-minute block on question three chases a full solve and its bonus. The minute splits are our own suggestion, so adjust them to your pace. The last line reflects the retake rule. A retake only makes sense when you expect it to beat the score you’d share.
If the target company follows the assessment with a live coding interview, the habits carry over. Our post on what the algorithm round tests in Android interviews covers practicing in Kotlin. It also covers talking through a problem out loud.