I think that is a fair point, but it seems akin to requiring a physics degree for the job of mechanic. Generally, the people doing the hiring decidedly know no more about mechanical work than they do about software development, so I do not think this is a unique issue.
Now, I am sure it would be useful for a mechanic to understand all of the properties of the materials to manually derive the torque setting needed for a wheel bolt and all, but in reality, you just follow the book. The science behind the application is not particularly useful within this context.
Hiring is hard, but I think this goes back to the original submission: If all you look for is a physicist, you're going to miss the master mechanic. You might even end up with someone who has no interest in tearing down engines at all. Is that really the better member for your team?
Now, I am sure it would be useful for a mechanic to understand all of the properties of the materials to manually derive the torque setting needed for a wheel bolt and all, but in reality, you just follow the book. The science behind the application is not particularly useful within this context.
Hiring is hard, but I think this goes back to the original submission: If all you look for is a physicist, you're going to miss the master mechanic. You might even end up with someone who has no interest in tearing down engines at all. Is that really the better member for your team?