You’re probably reading this because you have an upcoming interview on CoderPad and you want to make sure you understand how things work. We’ll keep it short and sweet.
CoderPad is a platform for doing technical phone screens or remote interviews in the browser, like Collabedit or Google Docs, with one major difference: we let you run the code as you write it.
Here’s what a CoderPad session looks like:
It’s pretty simple. You write code in the left pane, and when you hit Run the output is displayed in the right pane. For certain languages, the right pane also includes an interactive REPL. The Reset button clears the output in the right pane, but leaves the code you’ve written in the left pane intact.
CoderPad also supports built in video calling. You will have the opportunity to select your webcam and audio inputs before the call starts.
You will be in one of two types of interviews. A live coding interview or a take-home interview.
For Live Interviews, you will be sent a CoderPad link prior to your interview. When you open the link, you will be asked to input your name. Once you have entered your name you will join the interview with the interviewer.
For Take-Homes, you will also be sent a CoderPad link. Once you have opened the link, there will be detailed instructions with the amount of time you have to complete the challenge.
Once you have entered the interview, you can start writing code as soon as you’d like. The amount of time you have left to complete the challenge will appear in the bottom left hand corner.
When you feel like you have sufficiently completed the challenge, you can submit your code by pressing on the “Submit Challenge” button. If you have not been able to complete the given challenge within the allotted time, the code you have written will be submitted once the timer has reached its limit.
If you hit the Settings button in the lower-right corner, you can turn on/off a variety of settings. By default, most settings are disabled, so if you want code autocompletion for supported languages, bracket auto-closure, a unique tab size, larger font size, a lighter color theme, or to change your keybindings from normal “sublime-esque” to Vim or Emacs, you will need to click the Settings button during your interview.
Don’t worry about messing up your interviewer’s view, either! They can adjust their own settings from their side.
We support many of the most commonly used programming languages. We also have autocomplete, unit testing suites and other libraries for many of them (like Java). Check out the available languages here.
For the languages that support autocomplete, you may need to toggle autocomplete to “Enabled” from the Settings menu during your interview if you want it.
If you’re curious about the details or want to know if we offer your favorite testing framework or library, please check it out on the languages page!
Language information will also be available to you during your interview. To access it, all you have to do is click the Info button next to the language name at the top of your pad.
Interviewers may enable Drawing Mode in a pad to describe a system or diagram an architecture. When you are in plaintext the drawing will appear as a full screen. When you are in execution mode the drawing will appear on the right side of your screen. For more detailed instructions on using Drawing Mode check out our user guide.
Each company creates their own unique interview questions, so you won’t find any practice questions on our site.
However, we encourage you to click on over to the Sandbox.
The Sandbox gives you a session that’s identical to a real CoderPad interview - the only things it doesn’t have are multiple users and saving the session.
Remember, don’t sweat it during the interview - CoderPad is here to make your life easier. You can run your code at any time, and use the output to get yourself unstuck.
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!