So far, I’ve launched 2 LinkedIn sourcing challenges – Ruby and X-Ray Location False Positives.
The former had very strong participation as it was a little on the easier side (for some!). The latter had fewer participants, perhaps because it was more technical – but those who did participate did so heavily.
For my 3rd Linkedin Sourcing Challenge, I think I have one that is universally appealing because it requires no technical or advanced sourcing experience to participate, nor to win the challenge!
I was extremely pleased to receive many responses/solutions to the Ruby LinkedIn Sourcing Challenge I posted recently, including some from well-known online sourcing heavyweights, as well as a number from other talented folks who came out of the Internet ether from several continents to show off their skills and take a crack at solving the challenge.
Kudos to those who successfully found people on LinkedIn who have experience with Ruby but do not make explicit mention of it on their profile!
I sincerely hope everyone appreciated seeing the various approaches and methods people utilized to solve the first LinkedIn Sourcing Challenge – that was my primary motivator in posting it.
One thing I noticed from some of the responses is that for a few people, the challenge seemed too easy.
So – if you’re up for another LinkedIn Sourcing Challenge, take a crack at this one – it’s at least a degree more difficult than the last. :-) Continue reading
During my SourceCon NYC session, I gave an example of a sourcing challenge that can verify one’s “capacity to think logically and solve problems in novel situations, independent of acquired knowledge. It is the ability to analyze novel problems, identify patterns and relationships that underpin these problems and the extrapolation of these using logic.”
This capacity is otherwise know as fluid intelligence or fluid reasoning .
The LinkedIn Sourcing Challenge
If you and/or your team are up for a test of your fluid reasoning and sourcing capability, try solving this challenge:
- Find a LinkedIn profile of someone who has Ruby on Rails experience, but does not mention Ruby, Ruby on Rails, Rails, or RoR in their profile, and show with a link or other evidence exactly how you are certain they have Ruby experience.
There is no single correct answer – there are many different approaches to solving this challenge.
I’m going to recognize Jeremy Langhans once again for being able to solve that challenge in about 15 minutes before I even finished my presentation, using only his iPhone. To this date, no one else has even tried to take a crack at it.
The gauntlet has been thrown down. I hope at least a few people are up to the challenge! Continue reading