> ...are doing so because they don't know how to hire engineers I agree with this. I think teams no longer know how to actually select and filter good enginee

> ...are doing so because they don't know how to hire engineers I agree with this. I think teams no longer know how to actually select and filter good engineers so they spend multiple weeks filtering candidates using take homes, live assessments, followups, panel interviews, and so on because it's what everyone else does. Instead, this approach tends to yield the "least worst" candidate; the ones that have the time to waste going through a 3 week interview process. The take home is the most egregious. I think that the solution is rather simple: what would knock your socks off if you saw it in a submission to a take home? Could you design 2-3 questions that would get right to that scenario and test for that output? It seems like it would be a far more efficient use of time. I wrote a followup blog post on this: https://chrlschn.dev/blog/2023/10/your-interview-process-is-too-damn-long/ https://chrlschn.dev/blog/2023/10/your-interview-process-is-...