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).
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.
We recommend creating pads before the interview time. Go to your dashboard, and on the left side,
click the “Create Pad” button. This creates a new pad, which looks like:
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 to the interviewer (but not the candidate), as seen below:
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
coderpad.io/DKHC4J77). 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. This closes the session for further editing, makes it no longer accessible to your candidate,
and launches playback mode.
You can also end interviews on your pads page by clicking the “End Now” button next to any
interview that is listed as “In Progress”. Pads that are still available for use in upcoming interviews
will be listed as “Unused”.
CoderPad stores all interview data for playback at a later time. Click the “Playback” button next to
a pad to review the full interview. 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
coderpad.io/DKHC4J77), even if you have renamed it.
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 rename it and use it for a different interview.
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 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
email@example.com - we’re happy to help!