IssueRaiser

Everything you've pointed out is a legitimate criticism.

Everything you've pointed out is a legitimate criticism. That said, yeah, I think this might be better, because what we currently have is really bad. Recruiters scan resumes for buzzwords. Candidates are contacted and asked to code fizbuzz, or are given 10 java questions. If it's clear they're not a total waste of time, they're brought in for several hours at the whiteboard. They might be asked data structures and algorithms questions (the kind you get from the back of a 2nd year CS textbook), otherwise they might be quizzed on the intricacies of a programming language. If they pass the exam, the process may move toward "culture fit", more soft interviews with various managers and directors. Other variants on this involve homework assignments that can take the candidate a full work day (but reduce the amount of time a company has to spend interviewing them). All in all, I'd rather spend a couple days building a fun app than spending a day reviewing my old data structures and algorithms textbook and reading up on ruby syntax to make sure people believe that I've actually be using it as a programming language for the past few years, followed by a couple of days of technical grilling. I don't think hiring is an easy problem to solve. It's very difficult to evaluate programming talent, even if you're a programmer. None of this would be objectionable to me if employers weren't so adamant that there is a shortage of programmers (the bit about paypal was particularly hard to take - at one point, we're hearing about how desperate silicon valley companies are for programmers, next, we hear that a programmer was rejected from Paypal because he used the word "hoops").

Posted by geebee on Jan 26, 2015, 8:16 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments

ux (SaaS)

Everything you've pointed out is a legitimate criticism.

geebeeJan 26, 2015, 8:16 PM

Everything you've pointed out is a legitimate criticism. That said, yeah, I think this might be better, because what we currently have is really bad. Recruiters scan resumes for buzzwords. Candidates are contacted and asked to code fizbuzz, or are given 10 java questions. If it's clear they're not a total waste of time, they're brought in for several hours at the whiteboard. They might be asked data structures and algorithms questions (the kind you get from the back of a 2nd year CS textbook), otherwise they might be quizzed on the intricacies of a programming language. If they pass the exam, the process may move toward "culture fit", more soft interviews with various managers and directors. Other variants on this involve homework assignments that can take the candidate a full work day (but reduce the amount of time a company has to spend interviewing them). All in all, I'd rather spend a couple days building a fun app than spending a day reviewing my old data structures and algorithms textbook and reading up on ruby syntax to make sure people believe that I've actually be using it as a programming language for the past few years, followed by a couple of days of technical grilling. I don't think hiring is an easy problem to solve. It's very difficult to evaluate programming talent, even if you're a programmer. None of this would be objectionable to me if employers weren't so adamant that there is a shortage of programmers (the bit about paypal was particularly hard to take - at one point, we're hearing about how desperate silicon valley companies are for programmers, next, we hear that a programmer was rejected from Paypal because he used the word "hoops").

Comments (0)

No comments yet. Start the discussion.

Comment on this issue