One of the repeating motifs of recruiting in the software industry are mantras of “talent”: “We recruit the best talent”, “talent attracts talent”, “we value talent” and so on. Some companies have so called “head of talent”, “talent acquisition”, “talent development” professionals on their payroll - basically a re-branding of HR. With the amount of conversations, conference talks and hype going on around talent, you would expect people will have an answer to the question “what is talent?”. You’d expect, and you’d be wrong: “it’s like porn, you know it when you see it” is the answer I usually get - and as with porn, this only conveys that the word is merely an unhelpful judgemental label. If you cannot give some attributes of “talent”, how are you going to find it, develop it, keep it? Also, it’s not as if the subject of talent hasn’t been researched - quite the contrary! Although research is far from being exhaustive of the subject (or anything related to intelligence for that matter), there is plenty we do know. As it turns out, most of what we hear about “talent” in the software industry is just plain wrong and based on naive and deprecated models if not outright self delusions. For example, Joel Spolsky has observed years ago that almost all companies are somehow convinced they hire only the top 1% of developers - a clear case of selection bias. When people tell me they want to hire the top 1% of developers, I laugh. First because as Joel Spolsky noted everyone says that. Second, it implies we have some measurement of developers abilities - if we had that, why are we working so hard on interviews? Third, do they mean “top 1% of the population” of developers or the developers with top 1% of the skill scale? they are not the same. Fourth, it assumes that skill is static and when they hire a top 1% developer she will remain a top 1% developer - in other words that performance is dependent only on the identity of the developer.