Programmers are confessing their sins to protest a broken job interview process
11–20 of 238 posts
Re: Programmers are confessing their sins to protest a broken job interview process
#12Re: Programmers are confessing their sins to protest a broken job interview process
#13Re: Programmers are confessing their sins to protest a broken job interview process
#14Asking developers to program in front of strangers is primarily testing for ability to perform in front of strangers and developer skills secondarily (if at all.) I never ask people to code in front of me. I ask them questions to get a feel for where their areas of expertise are, and to get to know them. I wrote a post about my feelings on it last year: https://medium.com/@ebbv/my-case-against-coding-tests-6b15c1...
why not have them write code, not in front of people.
give them a laptop and some time alone?
Re: Programmers are confessing their sins to protest a broken job interview process
#15Re: Programmers are confessing their sins to protest a broken job interview process
#16Being able to understand a problem enough to successfully google an answer is the most valuable skill for a programmer.
Re: Programmers are confessing their sins to protest a broken job interview process
#17Wasn't this in reaction to the story that Homeland Security had asked the question to a programmer entering the US? I don't know how this was extrapolated to a broken job interview process.
Re: Programmers are confessing their sins to protest a broken job interview process
#18Whiteboard interviewing based on these things isn't useful unless the candidate is being considered for a position in which knowing these things is fundamentally necessary (e.g. they'll be responsible for developing new algorithms or squeezing out the last 10% of optimization available).
On the other hand, substituting requirements for having public code profiles, and the assortment of take-home projects, in-office projects, pair programming to solve a problem the company is facing (especially if unpaid) is just as bad, for different reasons.
And certainly not asking technical questions is problematic.
I just don't know what the solution is. It's one of those things where I know a bad interview when I see it.
Re: Programmers are confessing their sins to protest a broken job interview process
#19"Cut and paste fragments from {SO,Github,Gist,.etc} and edit to taste"