I really wish there was more work done in changing the terrible interview culture in software, instead of doubling-down on bad practices with low signal-to-noise ratios.
It's clear that whiteboarding and impromptu coding have little-to-nothing to do with real-life coding capability (let alone with generating real business value), while actual signals (e.g.: GitHub projects, OSS contributions, StackOverflow, take-homes, etc.) are ignored by interviewers. I've interviewed dozens of engineers and it's always been a miserable experience because my hiring manager (or other senior engineers on my team) always insisted on using these kinds of "grilling" methods which were never good signals to begin with.
It's a shame how our industry is the only highly-paid professional industry where this kind of sophomoric "intellectual hazing" is not only accepted, but also encouraged. I mean, hell, I have like three books on my bookshelf not about how to write good code, or scalable code, or performant code, but merely about how to pass interviews. Yuck.
It's clear that whiteboarding and impromptu coding have little-to-nothing to do with real-life coding capability (let alone with generating real business value), while actual signals (e.g.: GitHub projects, OSS contributions, StackOverflow, take-homes, etc.) are ignored by interviewers. I've interviewed dozens of engineers and it's always been a miserable experience because my hiring manager (or other senior engineers on my team) always insisted on using these kinds of "grilling" methods which were never good signals to begin with.
It's a shame how our industry is the only highly-paid professional industry where this kind of sophomoric "intellectual hazing" is not only accepted, but also encouraged. I mean, hell, I have like three books on my bookshelf not about how to write good code, or scalable code, or performant code, but merely about how to pass interviews. Yuck.