3 ms·

Many spent an entire afternoon working on this thing without success. I hope they liked the challenge, but I’m also glad we didn’t have to use our internal res

Many spent an entire afternoon working on this thing without success. I hope they liked the challenge, but I’m also glad we didn’t have to use our internal resources reviewing their resume. How fucking pretentious can you get? Maybe they were busy, maybe they had kids to take care of, maybe they were documenting their steps vs. flailing around. Glad I don't work in the valley if this is the kind of attitudes "rockstar" employers have. Edit: I see they are actually located in NYC.

chc 16y ago
If they had kids to take care of at the time, I hope they did not spend an entire afternoon working on it without success. And if they took so much time documenting their steps that it made the project take so long they could not complete it, I would say that is a negative indicator. In the end, IIRC it wasn't that hard a test for the sort of person who would be good at the job, so it seems like a reasonable filter. The only good reasons for not successfully completing it were 1) You didn't have time for it, or 2) You simply aren't ready at this point in your career.
- josegonzalez 16y ago
  I'd like to note that I have yet to pass the test - my first and only attempt was a curl one-liner that I gave up on when I realized I had work to complete :D.
  - mmelin 16y ago
    Without giving away the solution I would say that a well-equipped Firefox is a better tool than curl to complete this particular challenge :)
    - deleted 16y ago
      [deleted]
fshaun 16y ago
I don't understand the outrage. Some completed this in 7-8 minutes. That's quite a difference from spending hours without a result. Add a few of these problems up (which I hope are representative of actual skills) and you're looking at minutes vs. days. Sure, the aside on resources comes off a bit flippant -- but it doesn't mean it's untrue.
- maukdaddy 16y ago
  1. Time to complete the task is a terrible metric for white-collar, knowledge work. There are myriad factors to explain the time discrepancies, especially since there wasn't first-hand observation. If this was a job for building a widget on a factory line, then time might be a reasonable metric. 2. Using time alone as a selection criteria borders on discrimination given that some users might have sight or other physical disabilities that require longer to complete the task. 3. Do you really want to work for someone that has that kind of attitude? Oh, you're worthless because you took a few hours longer than John over there. We're not even going to consider your other talents, abilities, capabilities, or creativity that you bring to the table.
  - kessler 16y ago
    To clarify - time it took to complete the challenge was never factored into the application process. We simply pulled this data because we thought it would make for an interesting metric to display in the post.
- fleitz 16y ago
  I just did it for the challenge, took me about 30 minutes, primarily because I didn't look at the cookies first and spend about 15 minutes wiring up greasemonkey to add an input field into the form. Turns out I needed this for the _csrf and cookie stuffing so it wasn't entirely a waste.

chc 16y ago

If they had kids to take care of at the time, I hope they did not spend an entire afternoon working on it without success. And if they took so much time documenting their steps that it made the project take so long they could not complete it, I would say that is a negative indicator. In the end, IIRC it wasn't that hard a test for the sort of person who would be good at the job, so it seems like a reasonable filter. The only good reasons for not successfully completing it were 1) You didn't have time for it, or 2) You simply aren't ready at this point in your career.

josegonzalez 16y ago
I'd like to note that I have yet to pass the test - my first and only attempt was a curl one-liner that I gave up on when I realized I had work to complete :D.
- mmelin 16y ago
  Without giving away the solution I would say that a well-equipped Firefox is a better tool than curl to complete this particular challenge :)
  - deleted 16y ago
    [deleted]

fshaun 16y ago

I don't understand the outrage. Some completed this in 7-8 minutes. That's quite a difference from spending hours without a result. Add a few of these problems up (which I hope are representative of actual skills) and you're looking at minutes vs. days. Sure, the aside on resources comes off a bit flippant -- but it doesn't mean it's untrue.

maukdaddy 16y ago
1. Time to complete the task is a terrible metric for white-collar, knowledge work. There are myriad factors to explain the time discrepancies, especially since there wasn't first-hand observation. If this was a job for building a widget on a factory line, then time might be a reasonable metric. 2. Using time alone as a selection criteria borders on discrimination given that some users might have sight or other physical disabilities that require longer to complete the task. 3. Do you really want to work for someone that has that kind of attitude? Oh, you're worthless because you took a few hours longer than John over there. We're not even going to consider your other talents, abilities, capabilities, or creativity that you bring to the table.
- kessler 16y ago
  To clarify - time it took to complete the challenge was never factored into the application process. We simply pulled this data because we thought it would make for an interesting metric to display in the post.
fleitz 16y ago
I just did it for the challenge, took me about 30 minutes, primarily because I didn't look at the cookies first and spend about 15 minutes wiring up greasemonkey to add an input field into the form. Turns out I needed this for the _csrf and cookie stuffing so it wasn't entirely a waste.