Chris Petrilliif you want to get actual value out of a coding “interview”, trash your “leet code” dick measuring contest and give me code to refactor, debug, or even… write docs or tests for.
we all know that “write a dijkstra shortest path algorithm” test (looking at you google) is more of an indication of your inability to understand people and jobs, as well as some way for you to feel better about yourself.
cliffle@petrillic to be fair, it's also a great way to filter out people who didn't get CS degrees from particular schools!
...
@cliffle which, if we're honest, is pretty much the main use case.
which is how you get every company building its own build system and thinking _that_ is where time should be spent.
I used to shadow interviews at Google from time to time. Between that and hiring committee I saw some stuff.
One interview, the interviewer noticed that he and the candidate (also a he) both played lacrosse in college. No technical questions asked, hire recommended.
Anyway, I'm agreeing with you in a roundabout fashion.