5 ms·
> I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned enough about the job and
by minimaxir 9y ago
> I would never do a homework project as the first step in an application process. I would do one as the last step, after I had learned enough about the job and the company to decide that I really wanted it, and they had narrowed down the field to me and a handful of other candidates.
When I was job hunting last year, the steps typically went like this.
1) 30 min phone call
2) Homework
3) Algorithm Exam
4) Onsite
I typically got rejected at #3 which means the homework meant nothing.
- TheGRS 9y agoMaybe to your experience, but it likely is a filter for others.
- minimaxir 9y agoI have no issues with doing homework as a filter, but a homework plus an algorithm exam for filtering is annoying, especially since the homework is more related to on-job performance and the algorithm exam isn't. (and in my experience, it's never a weighted average of doing well on the HW and doing less-well on the algorithms: it's always pass/fail).
- rhapsodic 9y ago>I typically got rejected at #3 which means the homework meant nothing. It got you to step #3, but if I were applying to that company, I would not have done the homework. When they told me of the homework assignment, I would have asked, "assuming I do it, what comes next?" And when they replied "an algorithm exam, followed by an onsite interview", my reply would have been, "homework is the last step, or no thank you." Then again, I have almost two decades of experience and a well-established track record of accomplishments. And I currently have a solid, well-paying job. If I were fresh out of school, trying to land my first programming job, I would probably be more flexible.
- minimaxir 9y agoIn disclosure, all the companies were upfront about the full interview process. That said, in this job market, there isn't much leverage to say no to a prospective job or to make demands of the interview process unless you're already a rockstar.
- rhapsodic 9y ago>That said, in this job market, there isn't much leverage to say no to a prospective job or to make demands of the interview process unless you're already a rockstar. I don't consider myself a rockstar, or even a prima donna type who would make "demands" of the interview process. But I'm confident I could find a job fairly quickly without jumping through ridiculous hoops just to get an initial response from a company. From my perspective, the software developer market is still a seller's market. YMMV, of course. Maybe you're in an area where there are more qualified developers than available jobs, and employers have the upper hand to the extent they can pull off bullshit like this.
- deleted 9y ago[deleted]
- ryandrake 9y agoThis is a great point that gets lost because of the widely held “shortage of engineers” myth. The hiring market is strongly an employer’s market. There is far more talent out there seeking relatively few jobs, so employers can dictate terms pretty much absolutely. If they require a 5 day homework, then it’s “homework or GTFO”. If they require whiteboard hazing, it’s “whiteboard or GTFO”. The last real employee’s-market we had was in the late 90’s!
- markbnj 9y ago> The hiring market is strongly an employer’s market. There is far more talent out there seeking relatively few jobs, so employers can dictate terms pretty much absolutely. Wow, are you in the U.S.? This is pretty much the exact opposite of my experience and perception. I'm sure it must vary somewhat based on your specialty and what kind of work you do.