3 ms·
Ok, so why not pay devs for their time? Because you prefer to use that time as profit, no? The system encourages the default distrust of developers resumes. Th
by collyw 6y ago
Ok, so why not pay devs for their time? Because you prefer to use that time as profit, no?
The system encourages the default distrust of developers resumes. That most of them out there are lying, and we need a test to be sure that they can actually code. How many people have actually hired the mythical devloper that can talk well in an interview and not code?
- brandall10 6y agoONE MORE TIME - NO ONE IS PROFITING FROM INTERVIEW OUTPUT - THIS IS TO ASSESS ABILITY AND ONLY THAT. Forward, backward, sideways, up and down. If you're doing work that benefits the company that is another matter, but that's not what's happening here (or anywhere I've ever worked) and is ethically dubious regardless. That's not the point of an interview. I can't believe I'm having to explain this. You don't pay a dev for their time during the interview process for the same reason no one pays anyone for their time to interview in any industry. To hire straight off a resume is beyond wild. I'm in the process of hiring a dozen developers for my team, and have had 3 people who had great resumes fail a basic pairing session - they couldn't code. In the 24 years I've been in this industry, probably had at least a few dozen encounters like this. Sure, 90% of the time this isn't true, but it's true enough that it's insane to do it. "How many people have actually hired the mythical devloper that can talk well in an interview and not code?" I actually have. Twice. Earlier in my career when I believed these sorts of things. And was on hook for cleaning up the mess. Never again. The harm to the team's morale is not worth it.