> You can also have an in-depth technical interview that’s just a conversation instead of a pass/go asynchronous take-home exercise. Just a conversation is wha

> You can also have an in-depth technical interview that’s just a conversation instead of a pass/go asynchronous take-home exercise. Just a conversation is what I've always found worked. Just two people in the same business discussing some technical topic. What do you like about Rust? Why would you write this system in Java? Blah blah, and if the person doesn't actually know much they will run out of things to say. Sprinkle in some references to ordinary tools like git or gcc, and you can't avoid using industry jargon that will function like a shibboleth. If they know how to do stuff they will know the words you throw at them and throw back some of their own. If they read around their area they will know what the adjacent areas are and they'll have opinions and more keywords. It's not actually simple to make this up, for instance how would you pretend to be a surgeon or a pilot? There'd be a bunch of things you'd have to have heard of, and there isn't going to be a shortcut to knowing what they meant. If they're a bullshitter and they somehow manage to blag themselves a job, they will get found out pretty quickly anyway, definitely before the probation period ends. If they're someone who understands stuff, they'll appreciate talking to a technical peer and that will be part of the draw of working with me.