[andrewflnr]

Perhaps "teamwork" is not the best term, if it invites such a narrow interpretation. But even for mere "cooperation" as you put it, empathy is needed. In your cloud service example, if a client ever needs tech support, at least the support person is trying to read the client's mind, or they're not doing their job. Even in the case of holding up heavy objects, don't underestimate the value of sensitivity to the other person's needs; I've been on both sides of screwups in that area.

GP asked about hiring at companies, so solo projects are either not germane, or an illusion. Are you the only dev on a project that serves larger business goals? You're on a team! You need to understand how your work fits in with others' efforts, and either adjust or explain how others should adjust instead, most likely both. Oh, and don't forget to document everything, another empathy-heavy task. I think we all know this; it's just another way of discovering the meme that devs who understand the business go farther.

Part of the point I was trying to make is that those "large projects" you were talking about are going to become more common and more important, out-competing smaller teams that are almost by definition less capable in terms of feature output. If a solo dev outcompetes a team, it's because they were better at empathizing with customers. If that's not exactly teamwork, it doesn't avoid the problem, either.