| I'll take the opposite side of the comments and the body of cynical people here. It absolutely matters to care about the problem you're solving. A team of people with a skill level of X that cares about a problem will be better in both performance and in general culture and being around than a team with a skill level of 2X that consists of mercenaries. I learned it the hard way. When I was asked to set up a team of 14-16 engineers, I first went the latter way. The interviewing was difficult and the bar was higher, but the people who were there were focused on what they could get out of the role. Circumstances led to a reset, and the second time around, I built a team that optimized for caring about the problem. I started with the two people I liked working with in the initial group because they liked the problem statement. I had to lower the computer science performance bar to build the team to size. I also had a budget left over for other purposes, as we didn't need to pay for 2X performance, and the team was heavier with younger folks. We delivered the goals in three months. More importantly, working with people who have a shared purpose, rather than "getting mine," is just a better place to be. I had to spend time skilling up some people, but they did it in a month! Since then, I've always optimized for being around "mission-driven" people, rather than "mercenaries." Sometimes you need that 5X skill set, in which case a limited-time contractual helper is probably better, but the team has a soul. |