Earlier quoted context omitted.
Yeah it's pretty easy to tell where a senior engineer is at if you're in the same domain as them. Just discussing projects really provides much more insight than leetcoding them to death. It's shocking to me how many places are leetcoding senior engineers before talking to them about their past work or discussing design. Is it because we want to have hiring automated? Is it because of discrimination? Why is the leetc…
Behavioral, system design, coding, and problem solving interviews are AND gated. It's not a question of one being more important, but which ordering optimizes the funnel and employee time. There are many more calendar slots belonging to tech ICs than to hiring managers; you can run a higher velocity pipeline if you start with a technical phone screen. The coding interview itself is an immune system against the surpri…
You're trying to measure how they'll perform on your work before you hire them? That sounds like you're trying to get free work from them. (Just a note.. this is on the words you used)
> recognize smart people who will do well with whatever they're given,
How does a take home coding test that is limited on time, and their own time + stress indicate that they are in that category?