CoderPad
coderpad.io
coderpad.io
If anyone here has any questions about CoderPad, please feel to ask here, or if it looks like this topic's dropping off the frontpage, I'm always available at me@vincentwoo.com.
CoderPad allows you to instantly evaluate a candidate's abilities without paying for an expensive on-site interview.
It seems like he's just stating a fact.
Okay, so you say you do C++. What does that mean? Can you compile and see error messages? The editor in the demo has no line numbers - is there any hope in actually deciphering the errors and fixing the problem? Can I, the interviewer, provide or run unit tests against the code? Does the editor have things like auto-complete, code formatting, etc?
Okay, I gave up, I signed up. It's pretty cool, no, strike that, very cool. I had no idea from your front page. It wasn't clear at first that I could experiment endlessly without using my 2 pad quota, which was another thing to add friction for me to try it out. I can see that I can easily paste in some unit tests for the user to use. But, do you have boost, gtest, etc? What version of Python (and all other languages) do you support? What C++ compiler and version are you using? I tried some C++11 code, and it compiled, which is nice, but should I really need to type in test code to figure out what is supported?
Site seems very hacked together. Now that I am signed in, I have no way to get back to the start page, the FAQ, and whatever links you had on that front page. The code of my pads seems to somewhat overlay the ad links (select your plans) below. One I start editing code, there is no back button. If I use the browser's back button, sure I end up where I was - at the profile, with the new pad I just created not listed as one of my pads until I hit refresh on the browser. If I create a bunch of pads, it just creates them in a never ending expanding list - will I have ways to sort through for different candidates, times, etc? I kind of wonder what happens when you get to 50-60, as you don't seem to be storing them in a container - am I going to end up with a huge unmanageable page? Can I delete pads?
I also am not crazy about your tiers, though I recognize it is a common strategy. Small shops hire in bursts - a few months go by with few to no interviews, you get funding or a new contract, and suddenly you have 100 people to interview. Do I need to pay for a high tier so I can deal with the bursts? What if I buy the 20/month, and need 21 pads? Can I change my subscription level on a monthly basis? Is it really safe for me to just type my credit card number into your site? Why doesn't this just scale to my needs - why do I have to subscribe to tiers? Amazon doesn't make me pay for computer services I am not using, why do you?
I'm not looking for the answers to any of the above in this thread - I'm not going to recommend that my company pays for a service that cannot describe itself on it's webpage but eagerly provides me with fields with my credit card info, and whose only contact information is "me". There's not even an address - what recourse do I have if you take my data, or I have billing issues? Are you in the US, the UK, Argentina? Finally, I don't believe you can actually provide 24/7 support. I'm emailing "me@vincentwoo.com" - I doubt one person can service enterprise scale use 24/7. I don't even know what your infrastructure is - are you using AWS such that you can easily add nodes as needed, or is this run on a box in your basement that dies when the power goes out?
Awesome app, bad site.
As for the language versions, privacy policy, etc - those will be coming soon, but you can be assured I'm not NSA'ing you guys.
The tiering is because most shops favor cost predictability over scale-to-your-needs billing, which smooths out acccounting. I understand your concern here, though, and the pricing is still definitely very new (like the rest of this site).
My site is in fact on top of AWS (heroku), and I have 0 doubt about my ability to scale to enterprise usage. I've invested a fair amount in the architecture thinking up front, and I eagerly await a reason to pull the switch on my dyno counts. Unfortunately, I need an excuse to do it, but I might just spin up 20 nodes and do a load test for fun one of these days.
Anyhow, I'm glad that you at least like the product. Hopefully improvements to the landing page will be present soon. Sorry that your experience with it was so unfavorable.
I like the implementation, but if folks didn't like the NSA spying on them, they might not like this. This is wiretapping on steroids. I'm assuming the interviewer watches every keystroke. Creepy. I'm sure authors, well spoken and in full command of the English language, would get annoyed at someone staring at them to see if they can write a novel.
Tech interviewing is broken, but all solutions historically point to trying to watch a person code. I don't think that's the solution. When folks realistically work on multiple tech stacks with multiple frameworks and multiple languages, what is to be gained by zeroing in (deeply) on only one aspect of it.
This explains the need for a tech interview "study guide" posted earlier in the day. You're working on stuff contextually needed for your current job, but you'll be tested on stuff you don't use daily/monthly/yearly? That's insane.
c, c#, c++, clojure, coffeescript, haskell, java, javascript, lua, php, python, ruby, scala, scheme
As for your philosophical objection, I think the true value prop of CoderPad is a bit more nuanced than you make it seem, respectfully. The primary benefits as I see them are twofold:
1. The right kind of candidate is wowed. It is a real fish landing back in the ocean moment. "Finally, this works like I've always dreamed it should." You look really sexy administering that interview.
2. It can help you see candidates who have a firm grasp of programming but not quite a great hold on syntax do better. I would argue the former is more important, and CoderPad let's you see them experiment with syntax without having to rack their brains over whether the parameter goes before "do" in ruby.
It would obviously be ideal to have a demo for each language you support, but even if you simply highlight a bit clearer which languages you support right in the top part of the page rather than as a bullet point further down, that should really help your conversion rate.
What about using JRuby on the server-side?
(Which is the beginning of a fascinating discussion about choosing between the Scylla of wasted eng time and the Charybdis of a rigid, non-adaptive auto-screening, but that's for another comment.)
As far as the env itself goes, though, props++.
Athena is said to have emerged fully formed and fully armored from her interviewer's head, but what her peer reviewers did not see at the time was the struggle she faced in Zeus' ego. Though newly born, she yearned to wrest the tools of code to her will, yet no matter how she strained at the yoke of her keyboard, she could never quite overcome the compiler.
One day, she happened upon a memento that belonged to Metis. It was CoderPad, and it allowed her to more fully bring her will into reality. Using it, she forged herself a suit of armor - not her best work, but much better than the patchwork stuff she was making before. She banged and clamored with her shield, and eventually, the hiring manager Hephaestus was finally brought around to overrule's the stubborn Zeus' "no hire."
It appears to have been developed by/for http://repl.it/, which is education- rather than interview-oriented.
* I can set interview questions in various languages
* Candidate can write code right away, I can see everything he/she writes
* Code can be executed to see the result right away
* This even works for SQL, they have a sample schema the candidate can manipulate
* They have a fairly large library of questions you can just add to your interviews
* It's completely free as far as I can tell
No affiliation with the site, but it was very useful for me.Glad to see you took some of my copy write advice from last time :)
If you don't mind me asking, how many users do you have?
Might want to go over the "flow" of how the application will be used?
I'm guessing the interviewer will set up the "pad" and just send a URL to the interviewee?