Getting Started: Interviewers
This document is for technical interviewers who want to detailed instructions about how to run
interviews on CoderPad. If you are joining an interview as a candidate, please check out our
getting started guide for candidates.
CoderPad is a collaborative platform for conducting technical interviews in the browser (like
Collabedit), with one major difference: we let you and your candidates run the code as you write it.
Registering an account
If you haven’t done so already, you should sign up for an account. An account lets you create new
interviews, keep track of interviews you’ve participated in, and grants you administrative powers
(like being able to lock the document or disable code execution) during interviews.
To sign up for an account, Register with your company email and a password. This will
ensure your account is associated with your company’s organization-wide plan or trial with CoderPad
Preparing before interviews
First things first: if you’re new to using CoderPad, we recommend you start by playing around with
the editor in our Sandbox. This will let you get comfortable with the interface and
customize your settings without using up any of your interview quota.
Next, head over to the Question Library. This is where you can save your favorite
interview questions ahead of time, for easy one-click insertion into an interview once it goes live.
Click “Write New Question”, fill in any starting code or instructions, and save. If you like to let
candidates choose which language they’d like to code in, we suggest you write and save your
questions in plaintext.
To see which languages CoderPad currently supports and to get detailed information on language
runtimes as well as various libraries that are included/can be imported, check out our
If you’re working with your company’s recruiting team, you’ll probably receive an emailed link in
coderpad.io/DKHC4J77.This link will always be associated with this particular
interview - before, during, and afterwards. Both you and the candidate will join the interview by
clicking on this link.
If you’re setting up an interview yourself, start at your Dashboard and click “Create Pad”.
Once you click on the link/create a “pad”, you’ll be in the collaborative interview session (as seen
below). The pad will retain all code written and run by both you and the candidate, which you can
review and share at a later date. The left pane is the code editor, and the right pane contains the
terminal-style output plus the REPL for languages that support such.
If you received a link from your recruiter, wait for your candidate to also join the session. If
you’re setting up the interview, we recommend you copy the link from the URL bar and email it to the
candidate ahead of time.
If you find yourself in an interview and the candidate has not joined, you can use the Invite
button in the bottom left corner to have CoderPad email them the link. There’s also a shortlink in
the Invite menu for phone use, but beware - it only persists for an hour.
Once your candidate has joined the interview, you can help them get more comfortable if you point
out the ability to adjust various editor preferences under the Settings button.
Some useful buttons…
Both you and the candidate will be able to edit code in the left pane, and see the output/access the
REPL for supported languages in the right pane. The Run button executes the code in the right
pane in a fresh context each time.
The Reset button clears the terminal-esque pane on the right, but it won’t clear or otherwise
affect the code written in the left pane.
Use the Language dropdown to choose a programming language.
Use the Questions dropdown to insert questions from the Question Library into the interview. You
can also use questions in your interviews that your teammates have added to the library. “Append to
pad” will add a new question below the code already in the left pane, “Replace pad” will wipe the
left pane clean and insert the next question. That’s ok, though! All that code is permanently saved
and you’ll see it again in playback mode after the interview. When inserting questions, the editor
will automatically switch to whatever language the question was written/saved in.
Settings accesses your editor settings, including auto-close brackets, code autocomplete (only
available in some languages), tab size, and key bindings. As the interviewer you can also toggle
on/off for pad privacy and code execution. The candidate can modify their own editor settings
The Start Call button launches a Skype-style video call with your candidate, within the same
After the interview and reviewing pads
CoderPad stores everything typed into the pad plus all executed code output for playback at a later
time. Once you’ve completed the interview, click the End Interview button. This closes the
session for further editing, makes it inaccessible to your candidate, and launches playback mode.
You can hit the play button in the bottom left to auto-play the interview, or drag the slider to
As the interviewer, you can access any pad or share it with other folks within your company by
sharing its original URL (in our example,
coderpad.io/DKHC4J77). For sharing to work, anyone who
wants to view the pad needs to be signed in to your company’s CoderPad account.
You can access all previously created interviews from your Pads page. Pads that are still open for
further editing will appear on the top half of the page. If you forgot to click the End Interview
button at the end of an interview, you can do that here. Completed interviews will appear in the
bottom half of the page - click the “Playback” button to view them again. If you need to delete a
pad you can do that here - but keep in mind that once it’s gone, you can’t get it back.
Additionally, 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
firstname.lastname@example.org - we’re happy to help!