Getting Started: Interview Coordinators & Recruiters

This document is for interview coordinators and recruiters who want to know more about creating, scheduling, and managing interviews on CoderPad.

CoderPad is a platform for conducting remote interviews with programmers, in any 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.

Registering an account

If you haven’t done so already, start by signing up for an account. Register on our main page and enter your company email and a password. This will ensure your account is associated with your company’s organization-wide plan or trial with CoderPad (if applicable).

Creating Interviews

A “pad” is the collaborative interview session where the candidate will write and run code. You should make a new pad for each interview. A record of everything the candidate types in the pad will be permanently saved for your team to review and share afterwards.

You can create one of two types of pads for your interviews. A live interview, available to all plans, or a take-home project, available to our Business and Enterprise customers.

To create a live interview, simply go to your dashboard and click on the “Create Pad” button, and you are all set. We recommend creating live interview pads before the interview time. Once created, your new pad will look like this:

Renaming the pad at this stage will help you 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 to the interviewer (but not the candidate), as seen below:

To set up a take-home project, click on the “Create Pad” button, and hit the settings button in the bottom right hand corner. In the right hand column of settings, enable the take-home option under Pad Type, select the amount of time the interview should last, and the pad is now set up to be sent to the candidate.

For live interviews, you have the option to attach a question to the pad. For take-home projects, you can attach a challenge. You can create your questions and challenges using the following links: Questions | Challenges.

Inviting participants to interviews

Copy the URL of the pad and send it to both the candidate and the interviewer (the URL will always look similar to You can paste the URL into a calendar invite or email it. The candidate and interviewer will click on the link at the scheduled time, which brings them into the shared interview session.

After the interview and reviewing pads

At the end of the interview, the interviewer should click the End Interview button at bottom right. You can also end interviews from the Pads tab in your dashboard by clicking the End Now button next to any interview that is listed as “In Progress”. Ending an interview closes the session for further editing, makes it no longer accessible to the candidate, and launches playback mode.

Click the Playback button next to any pad listed as “Ended” to review the full interview, including any notes the interviewer made.

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.

Pads that are still available for use in upcoming interviews will be listed as “Unused” in your dashboard.

Final tips

Each pad you create counts against your quota. However, if you have created a pad but didn’t use it in an interview, you can use it for a different interview by clicking the Start button next to its name in the Pads view of your dashboard, then updating the title in the bottom right. (This will not actually start the interview without a candidate joining).

You can also 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 unless they are deleted within 28 days of when they were created.

If you have engineers who are new to CoderPad, we strongly recommend you have them get started by writing some code in our Sandbox. This will let them get familiar with the CoderPad interface without using any of 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!