It's not that you can BS your way through a tech interview, but that the skillset required to do well in a tech interview is different than the one you need to be good at a developer job.
I've seen way more than a few false positives from tech interviews, along with tremendous amounts of false negatives: People with backgrounds of being transformative to teams and organizations that just couldn't look good enough while solving random algorithm problems to save their lives.
It's just hard to see the kinds of things a company misses when they keep insisting in asking people about graph algorithms and implementing red black trees, because those same companies just never get to see the kind of people that you get when you do things differently.
I currently work for a company that does relatively traditional tech interviews and does 95% of sourcing from big schools and ver well known tech companies. I fail to see a major difference between my coworkers here vs my coworkers at places where your average dev went to a midwest state school and was never asked an algorithm question during interview.
I've seen way more than a few false positives from tech interviews, along with tremendous amounts of false negatives: People with backgrounds of being transformative to teams and organizations that just couldn't look good enough while solving random algorithm problems to save their lives.
It's just hard to see the kinds of things a company misses when they keep insisting in asking people about graph algorithms and implementing red black trees, because those same companies just never get to see the kind of people that you get when you do things differently.
I currently work for a company that does relatively traditional tech interviews and does 95% of sourcing from big schools and ver well known tech companies. I fail to see a major difference between my coworkers here vs my coworkers at places where your average dev went to a midwest state school and was never asked an algorithm question during interview.