How we hire developers
One route in for everyone: a short profile, one assessment and a decision from a developer who has read your work. Here is each step in detail.
About two hours of your time, in total
You do not have to do it in one sitting. Every step saves your progress, and you can pick up on any device by signing in.
- No CV, cover letter or interview
- No fee at any stage
- A decision within 3 business days of submitting
- Open to developers in every country
-
Create your account
Enter your name, email address, phone number and country, choose a password and accept our Terms of Service. One account per person.
-
Confirm your email address
We send you a link to make sure we can reach you with your decision. It opens your developer profile straight away.
-
Complete your developer profile
Five short sections: about you (with LinkedIn, and optionally GitHub, a portfolio and your CV), optional demographic questions, your programming experience and languages, your education and employment, and your availability. Nothing here is scored.
-
Read the briefing and take the Programming Assessment
Before the questions open, a briefing explains the three parts and the rules, and you confirm that every answer will be your own work. There is no timer, and your answers save as you type.
-
A developer reviews your submission
Multiple-choice questions are marked automatically. A reviewer then reads every written answer and runs your code. Your dashboard shows the date your decision is due.
-
Get your decision and start work
If you are hired, you add a payout account, receive your first project with its guidelines and rate, and start working whenever suits you.
What the Programming Assessment covers
It mirrors the tasks trainers do on real projects, so it is also the most honest preview of the job you will get.
Part 1: Code analysis
Three questions on programming best practice, time and space efficiency, and ordering the steps of an algorithm. Each choice is followed by a few sentences explaining your reasoning.
Part 2: Response comparisons
Two pairs of AI responses to real developer requests. Choose the better response and name the specific bug, risk or omission in the weaker one.
Part 3: Coding exercise
Write a function that fetches a published document, parses the data in it and prints the hidden message it draws. Then explain how your code works and report the message.
Your own work only. You may look up language documentation, but you may not use AI assistants, code generators, or help from anyone else. Submissions that show AI-generated or copied work are declined. Read the Candidate Integrity Policy before you start.
What reviewers look for
Every submission is read by a developer, who scores it on the same five criteria.
Correctness
Your code runs, handles the published document correctly and produces the right message.
Code quality
Clear names, sensible structure and idiomatic use of the language you chose.
Technical reasoning
Explanations that say why an answer is right, not just which one it is.
Judging AI responses
You pick the stronger response and name the concrete problem in the weaker one.
Written communication
Clear, concise English another developer could act on without guessing.
Tips for a strong submission
- Run your code against the test document before you submit
- Be specific: name the line, the input and the failure
- Write complete sentences, not notes
- Reread every answer once before submitting
Stopping part-way
Close the tab whenever you need to. Your answers save a couple of seconds after you stop typing, and they are waiting exactly where you left them next time you sign in, on any device.
If you are not selected
You can retake the assessment 6 months after your decision, with the same account. Your decision email gives the exact date.
Ready to show how you review code?
Create your account now and take the assessment whenever you are ready.