I’m a curious person by nature. I’m not generally satisfied with what’s on the back flap of the book – I want to know what’s inside. I’ve also lost more than one laptop to this curiosity. I, like many sourcers, was one of those kids who broke their toys as a kid to see if they could figure out how to put them back together. About half the time, the answer was “yes”, I could put them back together. The other half resulted in my mother asking things like “why is there a half melted G.I. Joe figure on the light bulb?” As you’d assume, I gave a plethora of answers to these questions, but no answer I’d give would ever suffice. This carried into my professional life, and as a sourcer, this innate curiosity has served me well.
As sourcers, we’re researchers at heart when you think about it. We can come up with a thousand ways to dissect profiles, absorb trends, siphon copious amounts of data off of public (and some not-so-public) websites and apps. But many of us seem to falter in an area that, while a little left of center of our core duties, is essential to our success. We can’t speak to technology as adeptly as we should be able to. We fail frequently to glean ample insight into the technology being used by those candidates we so covet.
The argument here for some may be that they don’t interact with candidates often, or at all. And while a firm grasp of specific technology talking points may be slightly more beneficial to those who are talking with candidates each day, those of us doing pure research can also benefit as well. By understanding the landscape of the technology we’re searching for, we are able to find similar, translatable skill sets that can meet the needs of the teams you are supporting. Read More