6 ms·
For the lazy: javascript:$('div.code.plain').last().html('<form action=#>name:<input name="name"><br />email:<input name="email"><br />about:<input name="a
by Cushman 15y ago
For the lazy:
javascript:$('div.code.plain').last().html('<form action=#>name:<input name="name"><br />email:<input name="email"><br />about:<input name="about"><br />urls:<input name="urls"><br /><p id="status"></p><button>submit</button></form>').find('button').click(function(){var f,o={};for (var k in f=$('form').serializeArray()) {o[f[k].name] = f[k].value};o.urls = o.urls.split(',');$.ajax({url:'/jobs/apply',type:"POST",data:JSON.stringify(o),contentType:"application/json; charset=utf-8",dataType:"json",error: function(d,s){$('#status').text(d.status)}});return false;})
Or is that unsporting somehow? Downvotes suggest yes, but on the other hand it'd be pretty silly for someone to expose an API intending people not to write tools that use it.
- butayni 15y agoAnother one for the lazy: curl https://www.parse.com/jobs/apply https://www.parse.com/jobs/apply -d '{"name":"somebody", "email": "me@hotmail.com", "about": "some blurb about me", "urls": ["url1","url2"]}' -H "Content-Type:application/json" Enjoy
- X-Istence 15y agoIs this really so hard that it sets the bar higher to the point that it really works as a filter?
- vandahm 15y agoI know software developers who wouldn't be able to figure it out.
- michaelcampbell 15y agoSadly "yes". That said, it's not "so hard" in absolute terms, but that is precisely why it works so well as a zero'th order filter. You wouldn't want to hire based on passing that, but you certainly want to NOT hire based on failing. (Depending on what you're hiring for, of course; I can't see not taking a sales guy to do sales if he couldn't do it.)
- neurotech1 15y agoActually if there business is cloud services, and APIs, then it might be a good idea NOT to hire a sales guy if they can't understand the basics.
- angstrom 15y agoThat was my thought. I curl requests like this all the time. This is like a tire obstacle course, not a high jump bar.
- bitops 15y agoIt is unsporting. The whole point of the exercise is for job seekers to show their chops and that, for some basic problems, that they can solve it without using Google. For fun, I posted my info using curl, vi and not one Google search. A web developer with 2-3yrs of experience should reasonably be expected to be able to do this challenge.
- Cushman 15y agoMaybe, but personally I'd be pretty weirded out if someone who could figure out the significance and use of the string I posted could not figure out curl. Is that just me?
- bitops 15y agoBased on personal experience, I'd respectfully say it's just you. I do see your point, though. I've met plenty of people who could code up a simple web UI but weren't very familiar with the underlying HTTP protocol. I guess my point is that knowledge of the protocol and web infrastructure is more valuable (sometimes) than just being a person who knows how to slap something together. YMMV.
- ams6110 15y agoA lot of devs who only know Visual Studio have never even heard of curl and other unixy utilities.
- mkopinsky 15y agoCurl?? Real men use Telnet...
- nitrogen 15y agoTelnet is not the best thing to use when talking to non-telnet servers since it's not a raw protocol that just passes data back and forth. For example, telnet appends an ASCII NUL to any CR in the stream. Netcat gives a truly raw socket.
- jedberg 15y agoYeah, that wasn't very nice of you. Now you've basically ruined their low bar filter and made the bar even lower, completely defeating the purpose.
- Cushman 15y agoI'm not immune to that concern, but 'ruined' seems like a strong word... it's not like I've injected that code into their page. Really, I just thought it was a funny little hack worth sharing with the community. I doubt anyone from Parse sees it as hugely threatening to their recruitment strategy.
- DanielRibeiro 15y agoThe sad part is that most people who see this are also able to pass such test.
- jedberg 15y agoWell, from a personal point of view, when we did the reddit hiring, it really annoyed us when someone posted their solution to one of the problems, because there were clearly people who were copying the solution to get their cover letter to us. So then we had to read those letter to determine that no, this person isn't actually qualified, and now we wasted our time (and theirs). So that is where I was saying the harm comes from. It's not hugely threatening, it's just annoying.
- shin_lao 15y agoThat just means that posting public problem to hire people isn't a good idea.
- mvanveen 15y agoDon't you think that's throwing the baby out with the bath water a little bit? I agree that it's a problem that people can easily dupe an interview by copying a readymade result, but that doesn't imply that public problems are unilaterally a bad idea. In fact, I'd liken this to a public announcement of a security exploit. Someone has found an insecurity within the social algorithm of public problem interviews.