This is also true for PhD students and research labs. Like if you are a C.S. PhD student interviewing at Microsoft Research or in an academic position, no one is going to ask you code up insertion sort. They look at your papers and evaluate you. I sometimes regret not doing a PhD for this very reason.
> Here's an idea: hire smart people. Even if they don't know your particular stack.
What the fuck does smart even mean anyway? How do you find out in the space of 5 one hour interviews if a person is smart or not?
1. If smart means problem solving ability, the way we test it now is a huge crock of shit because it is hard to abstract out domain specific elements from pure problem solving. I mean if you take any Math olympiad book, there are no pure problems beyond the puzzle level, most of them have a few tools of the trade that you can use. I remember someone posting here that IQ tests are illegal and probably not very good.
2. If smart means suave, sophisticated or looks like me (the accepted buzzword is "cultural fit"), it is going to not scale very well.
this has not been my experience, lab / academic jobs are a day of interviews which probably will not have any programming questions because you're hiring a scientist, not a staff programmer, but you will talk about research, ideas, and be expected to think and produce insights on the spot, and you as a candidate will give an hourlong talk. the decision is not made before you show up and the desires of the hiring body are very fickle.
Then we need to solve that problem, not bury our heads in the sand and pretend it doesn't exist. When you post a job ad for a software development position, you should receive absolutely no applications from people incapable of fizzbuzz. Yet we the majority of applications we receive are from such people. That problem won't go away if we just say "well, you had a job before, so that's good enough for me!" and hire them.
However, it would take a developer 5 minutes to realize they can't code shit. They are good at other stuff ... sure ... and they shouldn't be applying for programmer jobs.
I think startups are trying to emulate the Google way of hiring and that is to their detriment. There used to be a time where Microsoft hired an MD/PhD to become a coder ... because he had raw intellectual horse power and a desire to learn. I know quite a few PhDs who would love to work for a startup. Most of them have gotten dejected after the interview process. The common complaint I hear is "interview made me think I'm going to be a code monkey. F that. I'll keep my cushy research job with a door on my office".
In tech, it feels that one's education and work experience is what gets you the interview. Then, it doesn't matter. I'm tired of hearing the old "developer with 10 years of work experience who can't do fizbuzz". Rather than a lack of competence, the issues are:
1) Most humans can only hold so much information in their head at a given time
2) Tech/dev tool updates move ridiculously fast. It seems they are moving faster as time goes on.
Here's an idea: hire smart people. Even if they don't know your particular stack. Here's another idea that will never happen: lets all agree to be tested for interviews in one tech platform (that'll happen when pigs fly). We dismiss these issues now because we are young and hip. Eventually, many of us will have kids who we want to spend with. That's when we'll be on the other side of the table and have our oh-shit moment. I guess I shouldn't complain about the inevitable.