Pads
Last updated on • Available in French
✅ If you’re looking for the quickstart guide for live Interview pads, you can find that here. You can find the quickstart guide for Take-Home pads here.
A “pad” is the collaborative interview session where the candidate will write and run code. It consists of a code editor on the left side and output on the right side. You should make a new pad for each interview.
✅ The right window will also contain test case results, private interviewer notes, and candidate instructions depending on the type of pad you create and the role of the user.
Execute the code
In order to run code in any language, simply hit on the Run button in the top left hand corner of a pad.
We also give a handy keyboard shortcut if you don’t want to take your hands off the keyboard.
Program Output
As soon as you click on the Run button, your code will be executed and showcase the program output in a REPL window. If there are any errors in the code that is executed, the errors will also show in the output window.
To clear the output of the REPL at any time, simply click on the Reset button, located in the top right hand corner of a pad. This will not reset any code in the left hand pane, it will simply clear the output within the REPL.
For some languages (Ruby, Python, Javascript) – the REPL carries over variables from the left pane, and are available in the REPL. For other languages (Clojure, Erlang, OCaml, Perl, R, MySQL, PostgreSQL) the REPL is “disconnected” from the left pane.
Any code written into the REPL isn’t saved/visible in playback.
Reviewing interview results
A record of everything the candidate types in the pad will be permanently saved for your team to review and share afterwards.
Pad status
In the Pads List in your dashboard you’ll notice that each pad is assigned a Status:
The pad status flow is as follows:
| Live interview pads | Take-home pads |
|---|---|
| Not started: Pad created and there has been little-to-no participant action. | Not started: Pad created with no candidate action. |
| Opened: A candidate has opened the pad. | |
| Started: At least two pad participants have joined the pad at some point AND at least two detectable actions have been performed (e.g., typing code + running code). | Started: At least five minutes must have passed AND at least two detectable actions have been performed (e.g., typing code + running code). |
| Ready for Review: Either the candidate has submitted the pad or the time limit has been reached and the pad was automatically submitted. | |
| Ended: The End Interview button has been clicked OR the pad has been auto-ended due to account settings. | Reviewed: The Finish Review button has been clicked on the playback review page. |