Guide · Open source
How to use backend-challenges: practice real take-home coding tests
Updated · written with AI from the project's own documentation and checked against our catalogue data
backend-challenges is a public, MIT-licensed list of open-source backend coding tests that companies around the world have used in their hiring processes. It is a set of links rather than a program, so there is nothing to install. This guide explains how to read the list, pick tests that match your stack, and use them to practise before interviews.
Backend ChallengesCollabCodeTech/backend-challenges · ★ 10k · MIT Install options & downloads Quick start
- 1Read the README. Open the backend-challenges repository and read the introduction to understand that the list contains links to open-source tests.
- 2Clone the repository. Run git clone https://github.com/CollabCodeTech/backend-challenges to keep a local copy of the list.
- 3Pick your stack. Scan the Stack column for the language or framework you want to practise.
- 4Open a challenge. Follow the Code link on a row to reach the test's own repository and its instructions.
- 5Solve it under time pressure. Build the solution in your own environment as you would for a take-home assignment, and note how long it takes.
- 6Compare approaches. Look at a second test from a different company to see how their requirements differ.
What backend-challenges is and what it is not
Each row of the list names a company, the stack its test uses (for example Java, Node.js, Ruby or Go), and a link to the test's code repository. The README describes it as a way to test your knowledge using real jobs challenges.
It is a list of links, not a software tool. The README does not list any prerequisites, and it does not say how often links are checked, so some entries may be out of date.
- Good for: backend developers preparing for technical interviews
- Good for: developers who want practice in a specific language or framework
- Good for: students who want real-world style exercises
- Not for: anyone looking for frontend or mobile challenges, since the list is centred on backend stacks
Browse the list and filter by stack
Scan the Stack column for the language or framework you use. Many rows name several options, such as "Java or Scala" or "Node.js, Typescript & Koa, Express or Fastify", so a test may fit more than one of your skills. Rows marked "Any Language & Any Framework" are open to whatever stack you choose.
Some companies have more than one test, numbered in the Company column (for example Addison Global - 1 and Addison Global - 2). Compare them to see different problem types and stacks.
- Look for the exact language you want to practise in
- Check whether the test asks for a REST API, a database or Docker
- Open the Code link to read the problem statement in the test's own repository
Get a local copy of the list
You can read the list online, but the README gives a command to clone the repository so you have a local copy. Cloning needs Git installed on your machine.
Run the following command in a terminal:
git clone https://github.com/CollabCodeTech/backend-challengesWork through a challenge like a take-home test
Open the Code link for a row and read the instructions in that repository. Treat each one as a take-home assignment: set up the project in your own environment, solve the problem in the stack the row names, and keep track of how long it takes.
Because each test comes from a different company, the requirements vary. Some ask for a REST API, some for a specific framework, and some leave the language open. Follow the instructions in the linked repository, since this list does not describe the tasks itself.
- Read the full problem statement before writing code
- Use the stack named in the row when the test specifies one
- Time yourself to build a sense of how long a take-home test takes
Contribute new challenges
The README invites contributions and asks that only open-source challenges be added. If you know a public test that is missing, you can add it following the project's contribution process. The README excerpt does not describe that process in detail, so check the repository for guidance.
What people use it for
- Practising a Node.js take-home test before a backend interview
- Finding a Java or Spring Boot REST API exercise to prepare for a specific role
- Studying how different companies structure their take-home tests
- Finding an open-source Go or Ruby challenge when you want practice outside your usual stack
Frequently asked questions
Is backend-challenges free to use?
The project is released under the MIT licence, so you can use the list freely. The linked tests belong to their respective companies and repositories, so check each repository's own terms before reusing its code.
Do I need to install anything to use backend-challenges?
No. It is a list of links, and the README does not list any prerequisites. You can read it online or clone the repository with git clone https://github.com/CollabCodeTech/backend-challenges if you want a local copy.
Which programming languages are covered?
The list includes tests that name stacks such as Java, Scala, Node.js, Ruby, Go, C++, PHP, C#, Python and Elixir. Many rows say Any Language, so the list is not limited to one language, and it is centred on backend stacks.
Are the links in backend-challenges up to date?
The README does not say how often entries are checked, so some links may be broken or out of date. If a link fails, the test may have been moved or removed.
Is there a frontend or mobile version of this list?
The list is focused on backend challenges. The README does not mention frontend or mobile lists, so it is not the right place to look for those.
Are there alternatives to backend-challenges?
The analysis for this item lists no comparable projects. For other practice material, you would need to search separately, since this guide does not cover alternatives.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
backend-challenges is a good choice for backend developers and students who want realistic take-home problems in specific stacks, and who are comfortable with a list of links. It is a poor fit if you want a tool to install, frontend or mobile practice, or links you can trust to be current.
Install options & downloads