Most lists of the best coding kata sites rank platforms by size or popularity, but a kata is about repetition, and only a few places actually support that. This page sorts the sites by how they train you, so you can pick one for building language fluency, one for test-driven habits, and one for interview speed. Each entry says what the site does well, where it falls short, and who should skip it. The list stays at six picks, each with a reason for being there. By the end you’ll know which two sites deserve your time and how to run a weekly routine that makes the practice stick.
The Short Answer
Codewars is the best all-round coding kata site for most developers, Exercism is the strongest for learning a new language with mentor feedback, and Cyber-Dojo is the pick for test-driven practice. Use LeetCode only when interviews are the goal, since it trains speed, not craft.
What Actually Counts as a Kata
Dave Thomas, co-author of The Pragmatic Programmer, borrowed the word from martial arts, where a form is repeated again and again with small improvements each time. Codewars’ own documentation credits Dave Thomas with coining the term and describes a code kata as an exercise that sharpens skill through practice and repetition. The word repetition carries the whole definition, and it’s the part most ranking pages quietly drop.
A proper kata is small, usually 30 to 60 minutes, and Thomas’s original set mixes coding problems with open-ended ones that are really about thinking. Supermarket Pricing and Karate Chop opened his list of 21 exercises, and neither has one correct answer worth chasing. The point is rarely the final output and mostly what you notice on your third attempt.
That definition matters when you’re choosing a site, because platforms fall into two groups. Some are built for repetition and reflection, and others are built for coverage, handing you a fresh problem every time. Both are useful, but they train different muscles, and mixing them up is how people grind for months without getting faster at real work.
The Six Sites Worth Your Time
Codewars
Codewars is the closest match to the original idea, since it literally calls its challenges kata and ranks you from 8 kyu down to 1 kyu as you earn honor. You can run your own tests, practice test-driven development, and read other users’ solutions once you’ve solved a kata, which is where most of the learning happens. The discussion thread on each kata is underused and often explains the trick faster than a tutorial would. Its weakness is that the format rewards moving on, so you have to supply the repetition yourself.
Exercism
Exercism is free, runs as a not-for-profit, and pairs its exercises with feedback from mentors who know the language you’re learning. You download an exercise through a command line tool or solve it in the browser editor, submit it, and refine it based on what a mentor suggests. That loop makes it the best choice when you’re picking up Go, Rust, or Python and want your code to look idiomatic early. The trade-off is that it teaches language features more than software design, so pair it with one of the design-focused options below.
Cyber-Dojo
Cyber-Dojo is built around test-driven development, so it fits the red, green, refactor rhythm better than the points-and-badges sites do. Because it runs in the browser, you can start a session in seconds, which removes the setup friction that kills most daily practice. It’s a strong place to repeat one small exercise until the cycle feels automatic. Gamification isn’t the point here, which suits some people and bores others.
CodeKata and the Coding Dojo Catalogue
The original CodeKata series by Dave Thomas contains 21 exercises, and the early ones are still worth doing today. The original site has been reported offline, though the descriptions survive in community copies and wikis. Pair them with the Coding Dojo Kata Catalogue, a wiki of exercises that works well for pairing sessions and group practice. Neither source grades your work automatically, so you bring your own test framework, which is arguably part of the exercise.
CodinGame
CodinGame turns problems into games, where your code controls a character or a bot and the result plays out on screen. It’s closer to a puzzle site than a kata site, but the visual feedback makes abstract logic easier to see when you’re tired of staring at assertions. Treat it as a change of pace once or twice a week instead of your main practice. The weak spot is that these problems rarely teach you anything about clean design.
LeetCode
LeetCode is the one entry here that isn’t really kata practice, and it’s on the list because so many people search for it under this keyword. It trains speed on the algorithm patterns that show up in interviews, such as two pointers, dynamic programming, and graph traversal. That’s valuable when a technical interview is on your calendar and fairly irrelevant if you want cleaner everyday code. My position is simple: use it for the final few weeks before interviews, and keep it out of the rest of your routine.
Where People Go Wrong With Kata Sites
The biggest mistake is treating a kata as a puzzle you beat once. Solve it, collect the points, move on to the next one, and you’ve done coding challenges, which is a fine hobby but not what Thomas described. The confusion comes from how the platforms are built, because ranks, honor, and streaks all reward finishing new problems instead of revisiting old ones.
A better rule is to count repetitions, not completions. After your first pass, redo the same kata a day or two later from a blank file, writing the tests first and without looking at your earlier answer. Then try a third pass with a constraint, such as no loops, no mutable variables, or a different language entirely.
Reading other people’s solutions belongs in the loop too, and Codewars makes that easy once you’ve solved a kata. The useful question isn’t who wrote fewer characters but what the other solution assumed that yours didn’t. A clever one-liner nobody could maintain isn’t an improvement, so judge every answer by how easily you’d read it in six months.
A Weekly Routine That Fits Around Real Life
Three sessions of about 30 minutes each is enough, and it sits inside the window Thomas suggested for a single kata. The structure below uses one kata per week, which sounds slow until you see how much each problem gives back.
- Session one: solve a fresh kata on Codewars or Exercism with your tests running.
- Session two: redo the same kata from a blank file, tests first, without peeking.
- Session three: solve it again with a constraint or in a new language, then read two other solutions.
That adds up to 90 minutes a week and three passes of learning from every problem. If you’re learning a new language, make Exercism your primary site and keep Codewars as a weekend extra. If you’re trying to improve design habits instead, make Cyber-Dojo or the CodeKata exercises your primary and use Codewars for variety.
Staying consistent is usually harder than choosing a site, and there are more practical write-ups on everyday topics if you want to keep reading around it. A fixed time slot beats a vague plan every time, so put the three sessions in your calendar before you close this page.
Conclusion
The best coding kata sites aren’t the biggest ones, they’re the ones that make you repeat a problem and look at your own work again. Pick one site for breadth, such as Codewars or Exercism, and one for repetition, such as Cyber-Dojo or the original CodeKata list. Choose a single exercise today, solve it, and schedule the second pass for two days from now. That second sitting is where the learning starts.
FAQ
Is Codewars too hard for a complete beginner?
Not if you start at the bottom. New users begin at 8 kyu, the easiest rank, and you can stay there as long as you like. Use the discussion thread when you’re stuck instead of jumping straight to someone’s answer.
What if a kata takes longer than an hour?
Stop and read a solution, then redo the kata from scratch the next day. A session that runs past an hour usually means the problem is too hard for now or you picked a bad approach early.
Can I practice katas offline without any website?
Yes pick an exercise from the CodeKata list, set up a test framework in your usual editor, and write the tests first. Exercism’s command line tool also lets you work locally and submit afterward.
Do coding katas help with job interviews?
They build fluency in your language and test-first habits, which helps in live coding rounds. They won’t replace practice on interview-style algorithm questions, so add LeetCode in the last few weeks if you have a date.
Should I do katas in a language I know or a new one?
Use your strongest language for the first pass so you can focus on technique. Redo the kata in a new language on the third pass, which gives you comparison without drowning in syntax errors.