How to Use CoderPad
The purpose of this guide is to get you familiar with CoderPad so you can start running your own live technical interviews or assessments quickly.
Register Your Account
If your company has an existing CoderPad account, check in with your administrator to receive an invite and/or find out if you should use SSO.
If your company does not have an existing CoderPad account, register here with your company email and a password.
If you’re interested in purchasing a paid plan, visit our Pricing page and click ‘Buy Now’.
What’s a Pad?
A pad is a session where the candidate and interviewer will write and run code – within either a live collaborative interview or Take-Home question. You should use a new pad for each interview or assessment.
A pad should feel familiar if you’ve ever used an IDE. You write code in the left-hand pane, run code with the ‘Run’ button, and view execution output in the right-hand pane.
Some key features to note:
- Languages – We support many languages (over 30!), many with attached libraries and packages.
- Run Code – Execute (and debug) code together with your candidate.
- Customizable Settings – Change IDE settings like autocomplete, auto-close brackets, light theme and Vim mode. Click the ‘Settings’ button in the lower right hand corner.
Live Interview Features
- Drawing Mode – Use the included virtual whiteboard to add a visual element to any interview.
- Audio/Video Call – Interact with candidates through CoderPad’s built-in audio/video calling.
- View Participants – Each person’s name will show in the interview pad, and distinctly colored cursors make following along easy.
- Internal Interviewer Notes – Take notes during your interview right within the pad – completely private from external candidates.
- Focus Time – Give your candidates 5 minutes of quiet time to gather their thoughts and begin work on a solution.
- Automated Test Cases – Use visible or invisible test cases to see whether the code has passed or failed the requirement of expected outputs.
- Configurable Time Limit – You can set your pad to automatically submit after either 30, 60, 90, 120, or 180 minutes. Alternatively, you can set no time limit.
Create a Question and Save it to the Question Bank
Use CoderPad’s Question Bank to create and store questions for each technical role.
- Enable your team to have a consolidated list of interview questions shared with everyone
- Alternatively, individual interviewers can have their own list of questions
- Questions specific to Live Interviews or Take-Homes are both supported – you can create either.
- Candidates can answer multiple questions as they progress through the hiring process.
- Example Questions within your Question Bank can serve as inspiration for your own questions.
Set Up a Live Interview or Take-Home Pad
Live Interview Pads
You can set up a pad for a live interview by either:
- Using the ‘Create Pad’ button on “Pads List” and adding questions to it from your Question Bank
- Creating a pad directly from your question in your Question Bank
Once the pad is created, you can send the invite to the candidate using the button in the bottom left corner of the pad
Take-Home Interview Pads
You can set up a pad for take-home interviews by:
- Using the ‘Create Take-Home’ button from your question bank
- Selecting a time limit for the candidate to complete the pad within
- Adding the names you’d like these pads to be called. You can input as many as you’d like
- Once the pads are generated, the links will display on the “View Take-Home Pads” page
- Alternatively, you will receive an email once your take-home pads have been created
End Live Interview or Submit Take-Home Pad
Ending a Live Interview
To end a live interview, click the ‘End Interview’ button on the lower right hand corner.
- This prevents candidates from returning to the pad later
- This also enables Playback Mode.
Ending a Take-Home
To submit a Take-Home question, the candidate must click the ‘Submit’ button on the lower right hand corner
- Doing so enables Playback Mode for the interviewer
Debrief and View Playback
When either you’ve ended the interview or the candidate’s submitted their pad, you’ll be able to start your technical assessment debrief. Once a pad is closed, a candidate is no longer able to access the results.
You can utilize our tools to review the interview with others on your team who were not present, recall how a candidate reached a solution, and more.
- Every keystroke typed within the code editor is saved. You can replay the entire session keystroke by keystroke.
- You can see the user’s program output throughout the interview. This helps gain insight into their debugging process.
- Take-homes also have the ability to see the results of test-cases, both the ones visible to the candidate and otherwise.
- If you utilized Drawing Mode in a live interview, the final snapshot will be captured for review as well