This document is for candidates who are going to be interviewed on CoderPad.
CoderPad is a platform for doing technical phone screens or remote interviews in the browser.
A pad is similar to common Integrated Development Environments (IDEs). You write code in the left-hand pane, run code with the ‘Run’ button, and view output in the right-hand pane. The right pane also includes an interactive Read–Evaluate–Print Loop (REPL) for some languages.
The Reset button clears the output in the right pane, while the code you’ve written in the left pane remains intact.
✅Preparation Protip: One of the best ways to prepare for a CoderPad interview or take-home test is to use the sandbox environment, which you can access here.
Table of contents:
- Interview types
- Customizing code editor (i.e. “pad”) settings
- Programming languages and testing
- Drawing mode
- Prepare for your interview with the CoderPad sandbox environment
- Final tips
CoderPad supports two types of assessments, live interviews and asynchronous take-home projects.
You will receive a CoderPad link prior to your interview. At the scheduled time, open the link, input your name, and join the interview. Your interviewer may have you connect via a video call, which you can do by selecting the Start Call button in the bottom left corner of the pad.
You will receive a CoderPad link to the project. Click on the link to see detailed instructions about the task, including the amount of time you have to complete it.
The project starts once you enter the CoderPad environment. You can start coding immediately. The amount of time you have left appears in the bottom left-hand corner.
When you are ready, submit your code by clicking the Submit Take Home button at the bottom right-hand corner of the screen. If you don’t complete the challenge within the allotted time, your code will be submitted when the time runs out.
Customizing editor settings
Click the Settings button in the lower-right corner to customize settings, such as auto-close brackets for supported languages, bracket auto-closure, unique tab size, larger font size, lighter color theme, and to change your key bindings from normal to Vim or Emacs.
Most settings are disabled by default. Changing your settings does not affect your interviewer’s settings.
Programming languages and testing
We support most programming languages, many with autocomplete functions. We also have unit testing suites and other packages and libraries. See our languages page for more details.
For the languages that support autocomplete, you may need to toggle autocomplete to “Disabled” from the Settings menu during your interview if you want to turn it off.
To add a language, simply click on the Languages button on the left side of the screen, and then select Add Environment (if it’s not already selected) to choose your language of choice.
For more information on a particular language, you can either view the
Readme.md file in the case of frameworks or the Language Info tab that pops up when you click on the three vertical dots next to the language.
Change the default language
You may have a question presented to you in a default language. Some questions will allow you to switch languages to a language you may be more comfortable with.
To change languages, simply click on the vertical ellipses (three dots) next to the question, and then select your desired language from the list:
Interviewers may enable Drawing Mode in a pad to describe a system or diagram an architecture. For more detailed instructions on using Drawing Mode check out our user guide.
Try it out ahead of time!
You can try out CoderPad in this embedded sandbox:
✅ CoderPad supports common IDE keyboard shortcuts. The full list can be found here.
Each company creates their own interview questions, so there are no practice questions on our site.
We do encourage you to try out the sandbox environment which gives you a CoderPad session that is nearly identical to a real CoderPad interview – minus the multi-user functions and the ability to save the session.
- CoderPad is here to make your life easier. If you get stuck in the interview, don’t worry, just run the code and use the output for debugging.
If you have any questions or concerns about how things work in CoderPad, feel free to email us at [email protected] – we’re happy to help!
Table of Contents