How to pass a CodinGame test: the preparation guide
CodinGame is one of the most common screening tests in European tech hiring. Here is what the exam looks like, where candidates lose points, and a concrete plan to walk in ready.
A CodinGame hiring test usually lasts 30 to 90 minutes and mixes multiple-choice questions (language, algorithms, SQL) with one or more coding exercises graded by hidden test cases. You don't pass it by memorising solutions; you pass it by recognising the problem type quickly, managing the clock, and checking edge cases before you submit.
What a CodinGame recruitment test looks like
The recruiter sets up a campaign in CodinGame for Work (now CoderPad Screen) and you receive an email link that stays valid for a few days. You take it alone, at home, in the browser, with a timer per question.
There are three formats. Multiple-choice questions cover a specific language (Java, Python, JavaScript, C#, SQL…) or general topics: complexity, data structures, HTTP, Git. Short coding exercises ask you to complete a function that must pass a set of hidden tests. Puzzles, which are longer, follow the logic of the public puzzles: read an input, compute, print an exact output.
The final score combines the number of tests passed, the time used and, in some campaigns, code quality. A half-passed exercise still earns points, so a partial submission always beats an empty editor.
The question types that come up most
On coding exercises the themes are remarkably stable from one campaign to the next: string manipulation (parsing, splitting, counting), arrays and sorting, linear or binary search, maps and sets, grid traversal, and a little recursion. The easy public puzzles (Temperatures, The Descent, Power of Thor, ASCII Art, Chuck Norris) cover exactly these ideas.
On language MCQs the classic traps are variable scope, reference versus value equality, operator behaviour on mixed types, uncaught exceptions, and predicting the output of a short program.
General MCQs mostly test complexity (which algorithm runs in O(n log n)?), data structures (stack, queue, hash table, tree) and some SQL basics: joins, GROUP BY, indexes.
The mistakes that cost the most points
Reading the statement too fast. CodinGame expects an exact output: an extra space, a missing newline or a different rounding fails the test even when the algorithm is right.
Forgetting edge cases. Empty list, single value, negative numbers, duplicates, ties. Half of the hidden tests target these.
Getting stuck on one question. The clock runs per question or for the whole test; ten minutes on a 2-point MCQ leaves two for the 20-point exercise.
Not running the visible tests. The editor lets you run them: do it after every change, not only at the end.
A 7-day preparation plan
Days 1–2: the language. Pick the language you know best, not the one in the job ad if you are not fluent in it. Review reading standard input, conversions, sorting with a comparator, maps and output formatting.
Days 3–5: puzzles. Solve 3 or 4 easy puzzles a day, timed. After each one, read an explained solution and compare the approach, not just the code: that is how you learn to recognise a problem type.
Day 6: MCQs. Run through question sets on your language and on complexity. Write down every mistake and why you made it.
Day 7: a mock test in real conditions: 60 minutes, no break, with a time budget per question.
How Coding Solutions helps you practise
The Coding Solutions Chrome extension reads the exercise or MCQ on screen and explains the solution step by step: the approach, the complexity, commented code in 29 languages and the edge cases to check. Used on practice puzzles, it replaces hours spent hunting for a reliable correction on forums.
You can also work without the extension using our 39 explained CodinGame solutions, sorted by difficulty, or the French versions.
Frequently asked questions
How long is a CodinGame test?
Usually between 30 and 90 minutes. Each question has its own time limit, shown before you start, and the total appears on the test's welcome page.
Which language should I pick?
The one you practise most. The score does not depend on the language, but hesitating over syntax costs minutes. Python and Java are the most used on hiring tests.
Can I retake a CodinGame test?
No, a campaign link can only be used once. If something went wrong technically, contact the recruiter, who can send a new invitation.
What score do I need to pass?
It depends on the recruiter, who sets the threshold. Most shortlist candidates above 60–70% and mainly compare scores within the same campaign.
Are the public puzzles the same as the test ones?
No, recruitment exercises are private. But they rely on the same concepts, and the easy and medium public puzzles remain the best practice material.