Our Customer Stories & Testimonials

CoderPad is by far the best coding interview tool we’ve used. It beats the pants off of all the other “live editor” services out there – and then it lets you execute code, too!

My goal is to simulate real work as much as I can in an hour. CoderPad lets me do just that – the candidate gets to write code in a language they know, run it, write test cases, and debug. It’s so, so much better than just pseudocoding on a whiteboard.

CoderPad is the best remote phone screening tool I’ve used for two reasons: The first is that it’s very reliable. It’s very distracting to have a tool go down in the middle of an interview. The second is code execution. Being able to run code gives me a better overall picture of a candidate’s ability. This helps me decide on who should make it to the on site.

CoderPad has been a great addition to our interviewing toolkit. With it, you can watch a candidate iteratively develop their code and then actually use the compiler for debugging. This adds a whole new dimension to the process and brings it one step closer to the holy grail of natural coding in an interview.

CoderPad, compared to Google Docs, is a much better interviewing experience. My most successful interviews involved candidates running specific test cases. This wouldn’t have been possible with the other tools I’ve used.

When I’m doing phone screens, people are amazed. My favorite part of CoderPad is hearing that initial ‘a-ha’ moment that people have. After finding CoderPad, I’ll never go back.

Google Docs is what I used at Google. Candidates would often spend a lot of time organizing the code and fighting with auto text formatting. With CoderPad, the syntax highlighting goes a long way to help candidates write clean code and make corrections easily. Because of this, candidates are more comfortable in our remote interviews.

CoderPad is much better than what I was using before (Google Docs @ Google). Specifically, I like the ability to compile the code. It helps me see if candidates can actually write code or not. Also, it helps the candidates because they can tell where the errors are after running the code.

The candidate experience was our most important factor when evaluating CoderPad. All the good candidates are talking to other companies and anything we can do to set ourselves apart is important. When we talked to candidates about being interviewed with CoderPad compared to other tools, they told us it left a great impression.

CoderPad is really powerful. When we revamped our interview process for our Software Engineer role, we strove to have every single interviewer use CoderPad during phone interviewers to ensure we’re screening candidates consistently and truly assessing coding skills over the phone.

Stypi used to crash all the time, resulting in re-interviews. This annoyance was solved with the reliability of CoderPad. As a result, the relationship between the hiring managers and myself has been improved.

All the other tools I had seen before CoderPad provided multi-language support with highlighting, but no support for code execution, and that was it for me. The fact that I could execute my code simply made me feel like I had been given a little bit more control over the interview process as a candidate.

CoderPad has finally, truly, and uncompromisingly eliminated the whiteboard from interviews. It feels native, lets you write and run real code instead of pseudocode with no effort, and gives you something interactive that you can review again after.

There are lots of collaborative editing tools out there that do syntax highlighting for various languages, but CoderPad is the only one I’ve seen with “compile and run it right now!”, and that’s really cool. It adds objectivity to the interview – we’re not both guessing if the code works, we can run it and see. Doing a software interview is already such an artificial process that only vaguely maps to actual software engineering. Using CoderPad lets me better demonstrate the actual skills of being a software creator.