I understand your point, but I disagree with it. Just like there are different versions of "good" leaders and "good" workers in any given field, there are diff

I understand your point, but I disagree with it. Just like there are different versions of "good" leaders and "good" workers in any given field, there are different types of "good" in sports. Similarly, sports has a much more straight-forward rewards system; score a point, prevent the opponent from scoring, immediate result and reward. For anything technology related, the action => reward system tends to be far more delayed and requires a different approach and type of patience. Whether it's Devops, Programming, Administration, or Support, even if you do everything right, the reward might be delayed or sullied by negative rewards. (e.g., network is never fast enough for users, it's still too complex to use your program, the solution is just not desired by the user) Again I do understand the premise of your statement, and for some situations I can agree there is crossover, but my experience in hiring for technical positions is that sports participation has been a non-factor at best. Too often, it's been a negative one because the rewards for technology related challenges tend to be very delayed or difficult for the participant to recognize. Success in Technology is very personal and goes beyond the tangible result, and instead is a victory of the self as you grow intellectually and better understand something. This does happen in sports also (you train yourself to recognize openings that maybe didn't exist for you before or you couldn't act on due to physical limitations), but there are other rewards that make sports more compelling.