Never done any recruiting, but here something I have noticed in recruitment efforts. Figure out what you really need and how "good" is defined. Good is contex

Never done any recruiting, but here something I have noticed in recruitment efforts. Figure out what you really need and how "good" is defined. Good is contextual. My past company spent a lot of time on system design interviewing. Here is the problem. We didn't build anything close to a complex system. We created demos to show off to clients as MVPs. So we left positions open for months until we found the perfect person and they didn't want to join/did not stay as they wouldn't actually use those skills. Said past company also wanted "product minded people", something in my own background. Devs had no influence on the product there. Yet they waited for people like myself to come along. A job before that leetcoded. Nobody currently there could pass the leetcode. The dev doing the interview had never even seen a tree in production at any company. We certainly didn't care internally as the database was so small and it was a Scrum team focused on shipping tickets. But we kept reposting the job and then had to eventually just take a candidate (if you could solve a tree leetcode, you would not work at this place).