There's a way you end the feedback loop that encourages leet code, the people who endorse it. Openly commit that your focus in hiring evaluations will be on rea

There's a way you end the feedback loop that encourages leet code, the people who endorse it. Openly commit that your focus in hiring evaluations will be on real world problem solving specific to each service team and that each service team must maintain 3-4 hacking challenges that are direct representations of their work. For most of us that's "perform a code review of this junior engineers undocumented code", "add some specific functionality to this API", "add functionality to this API without breaking contracts and show me how you ensure it's not broken". That creates variety in the question bank, standardizes evaluation, and will only encourage engineers who really want to work on your stack and product combination.