3 ms·
After I initially overreacted about it's simplicity, I saw the point more clearly. In fact, the more I think about it the more I loved it. (from your business's
by jayphelps 16y ago
After I initially overreacted about it's simplicity, I saw the point more clearly. In fact, the more I think about it the more I loved it. (from your business's standpoint)
Whenever I've been apart of interviewing candidates, ≈70% of the time was wasted on applicants who fluffed their resumé, got an interview, and were obviously not what they claimed to be. This would probably significantly reduce that overhead and at the same time attract people who enjoy coding vs. do it just to pay the bills.
- ericwaller 16y agoThat was roughly our thought process (I'm another seatgeeker btw). We wanted to come up with something that would be pretty quick to solve if you know what you're doing, but at the same time, demonstrates that you've got a pretty good understanding of a bunch of the moving parts of web development.
- pavel_lishin 16y agoI interviewed with a pretty big company awhile back, and they told me that 50% of the people they talked to couldn't pass a basic phone screen - the technical portion of which basically consisted of making sure I knew what the modulo operator was, what it did, and some practical applications thereof. How were y'all's percentages in that regard? How many applicants flat-out couldn't write code to save their life?