That is because over last few years it became extremely prevalent industry to make everything about "teams": projects are responsibility of teams, failures are

That is because over last few years it became extremely prevalent industry to make everything about "teams": projects are responsibility of teams, failures are attributed to teams, etc. It used to be that code won arguments. Now it is not ruffling feathers that wins arguments. If I'm not hiring the entire team, how do I know who in that team actually can code based on the result? What does it all mean? It means exactly what it meant in a high school/college group assignments - one or two people carried the group project but everyone took credit. I have seen hundreds of resumes where people claimed that they have done XYZ where through some side channels I know they just happened to be on that team but their contribution was limited to tweaking spelling. I see coding tests as one of the two ways to evaluate that someone can code[1]. I trust it. [1] The other way is that I know this person and I'm already aware what they can do.