Using CoderPad for take home assignments

This document is for companies who want detailed instructions for setting up take home assignments on CoderPad.

CoderPad is a platform for conducting remote technical assessments in the browser.

Our interface is very similar to a programmer’s everyday tools and allows code to be run as it’s written. This makes for a comfortable candidate experience and allows the candidate to fully demonstrate their technical skills. CoderPad’s #1 use case is live, interactive interviews, where both the candidate and the interviewer join a shared session at the same time. However if time or scheduling does not permit such, you can also send candidates take home assignments.

Setting up Questions

Decide what questions you will ask candidates, and save the take home assignments in the question library. It’s helpful to give these assignments titles associated with the position candidates are applying for, like “Take home assignment for Senior Java developer”. If the whole assignment will be in one language, select that language when setting up the assignment. If you’d prefer to allow the candidate to choose their language or if multiple languages will be tested, we recommend writing your questions in plaintext.

Creating a new pad

A pad is the session where the candidate will write and run code. You should make a new pad for each candidate. A record of everything the candidate types in the pad will be permanently saved for your team to review and share afterwards. Go to your dashboard, and on the left side, click the “Create Pad” button. This creates a new pad, as seen below:

We recommend renaming the pad so you can keep track of it in future. You can rename by clicking on the title in the bottom right corner of the pad and typing a new title. The new title will then be visible in your dashboard (but not displayed to candidate), like this:

Setting up the take home assignment

While in the new pad, click the “Questions” menu and select the appropriate assignment from the list of previously saved questions. Click “Replace pad” to replace any existing text with the contents of your assignment.

Sending participants the assignment

Copy the URL of the pad and send it to the candidate (the URL will always look similar to​). Let the candidate know the time/date they should have completed the assessment by, how long you’d like them to spend working, and let them know that timestamps will record how much time they actually take.

After the test and reviewing pads

After the assignment is completed, the recruiting team or reviewer should click the “End Interview” button next to this interview in the list on your pads page. This closes the session for further editing and launches playback mode with timestamps. CoderPad permanently stores all data including code written and execution output. You can click the “Playback” button next to a pad to review the full interview at any time. You (and members of your organization who are signed in to a CoderPad account) can access or share any pad or its playback using its original URL (in our example,​, even if you have renamed it.

Final tips

Each pad you create counts against your quota. However, if you have created a pad but didn’t send it to a candidate, you can rename it and use it for a different assignment.

You can delete pads but once they’re gone, they’re gone for good, so be careful with this feature! Deleted pads still count against your interview quota.

If you have any questions or concerns about how things work in CoderPad, feel free to email us at​- we’re happy to help!