I kind of agrees with the above.
What If Cars Were Rented Like We Hire Programmers?
21–30 of 177 posts
Re: What If Cars Were Rented Like We Hire Programmers?
#22I agree with parts of it, but I disagree with the basic premise that hiring programmers is like renting cars. When you hire a programmer, it is like hiring a car mechanic, not a car driver. Some of the questions do seem appropriate to ask to a car mechanic.
If you see a programming language as a tool like photoshop you certainly can see the renting car point. I don't think every Java Coder would be able to tell how the internal mechanics of Java work. They aren't Java mechanics, they're just driving Java.
Car Mechanics dont build the car parts or research into how to build the most efficient engine, but do need to know how to apply the knowledge of those parts. The best car mechanics can apply the science but may not be the best car researchers. Thats why in my opinion, some questions do make sense for a car mechanic.
If you were using the photoshop analogy, then I think to interview someone, you need to ask them how different features of Photoshop work, not how Photoshop was built but also not how they draw in general, IMO. You may be a great artist, but if you can't understand Photoshop features and what they mean you will fail to create a great digital painting.
Re: What If Cars Were Rented Like We Hire Programmers?
#23While this seems "spot on" at first glance, I can tell you that when I interviewed at Google and Amazon (two years ago), it wasn't anywhere near this bad. Both places asked what might seem like contrived technical questions, but the thing is, you have to pick something that can be tested in an hour (or less). That, and it's not the answer that matters, but more your process of working a problem. They didn't seem to c…
My experience with Amazon was similar but at the end I was led to ask: "if the 1hr filter process isn't efficient at finding the best candidates, why do they do it?" I think in the end its a balance of basic filtering vs. HR requirements. The process has to be objective and quantifiable so they're covered in the event of anyone calling foul play. Everyone gets the same treatment and there is a paper trail of reasons…
The process only has to look objective and quantifiable. Everyone doesn't get the same treatment, but it's not actionable if the differences are all deniable and have rationalizations like 'culture fit'. People can and do still hire who they want for whatever reason, they just claim some objective reason for it.
Re: What If Cars Were Rented Like We Hire Programmers?
#24This analogy is backwards... Hiring a programmer is an exchange of company money (or equity, benefits, etc) for a service (programming skills). Renting a car is an exchange of one's own money for a service (use of the car).
In this case, the person renting the car would be "interviewing" the car rental company to determine if their service is worth their money.
Re: What If Cars Were Rented Like We Hire Programmers?
#25Maybe applicants need insurance. If they don't work out, their insurance company refunds the employer their salary and the opportunity cost of their bad commits. This way, applicants get muscled out of the job market gradually by high insurance rates, rather than with a brick wall filter.
Re: What If Cars Were Rented Like We Hire Programmers?
#26hehe, yeah, I've been through this several times.
I think it's funny when the recruiters try and lie at the beginning by saying a later interviewer may or may not be out sick and there is the possibility for some interviews to be cancelled and the day cut short. We all know they want to send you home if you screw up in the beginning. It's not a secret.
Re: What If Cars Were Rented Like We Hire Programmers?
#27My own personal, small sample size experience has shown that if I start questioning things early on in the interview, I can predict fairly well whether or not the company will be a good fit or not. I try not to jump to conclusions but even initial emails and phone calls can make for pretty strong clues.
If I sense during an interview that things aren't going to be a good fit, I still try and finish the interview graciously. There is no use burning any bridge, even if it's one you're 100% certain you'll never use. One trick I do to keep myself from seeming aloof or displeased is to start asking questions about the industry. At this point, I know I don't want the job and probably don't care about the culture, but learning something about an industry you may not know much about could be useful down the line.
Re: What If Cars Were Rented Like We Hire Programmers?
#28Maybe it's because I just made the egregious mistake of getting drawn into a gun-control debate with a friend and his friends on Facebook, but hyperbolic arguments by analogy feel really silly, cheap, and disingenuous to me right now...
that'll teach you
Re: What If Cars Were Rented Like We Hire Programmers?
#29The poor interview process is one thing, but what irks me most is that almost nobody offers you a chance to meet the team, even when they make you an offer. That's been my general experience so far anyway. It sucks, because your only exposure to anyone was the hiring manager, and maybe a lead, and all they did was ask questions about what you memorized about whatever language(s).
Re: What If Cars Were Rented Like We Hire Programmers?
#30This analogy is backwards... Hiring a programmer is an exchange of company money (or equity, benefits, etc) for a service (programming skills). Renting a car is an exchange of one's own money for a service (use of the car). In this case, the person renting the car would be "interviewing" the car rental company to determine if their service is worth their money.
Thanks, exactly what I thought when I read the article.