Think Big Analytics CEO Ron Bodkin reveals what he looks for in candidates for Hadoop and other big data-related positions.
"Polyglot" programmers who have shown the willingness and ability to learn and work with multiple software languages as the development universe evolves.
That last one's worth some extra emphasis. Java skills are no doubt a good thing for big data professionals given that Hadoop and related technologies are based on Java. But Bodkin said it's a good sign when people know other languages as well; among other things, it shows a willingness to learn.
"We actually prefer people that don't just have experience in the Java world... they know SQL, they've probably been successful in something else like Python or R or Ruby," Bodkin said.
Don't be too quick to rule people out If you subscribe to Bodkin's strategy of emphasizing people and their potential rather than specific skills and experience, you'll likely buy in here, too. Although you might want to have your list of red flags handy when reading resumes or meeting with candidates, don't be too quick to judge.
An example: Although Java experience is certainly a major plus for Hadoop and other big data jobs, it's not always a must if a person nails your other criteria -- provided you're willing to train and be patient. When Bodkin was VP of engineering at Quantcast, the firm hired several people who lacked a Java background even though their jobs demanded Java skills, and they ultimately worked out just fine.
"They were able to learn the Java ecosystem; it just took a little longer," Bodkin. "It depends on whether you're able to nurture top talent through a longer learning curve to be successful."
Shore up software engineering fundamentals Particularly when it comes to senior-level data engineering positions, Bodkin said it's important to remember the basics of successful software engineering: "People who know the discipline and practice of testing, designing effectively, using continuous integration, designing for testability -- [look for] some of those types of skills as well."
Bodkin also sees an emerging trend linking big data -- especially Hadoop-based endeavors -- and the DevOps approach. "Having a bunch of engineering skills but also administration skills in Linux is increasingly important," he said. "We think there's a connection between big data and effective DevOps," and subsequently a growing need for talent in this arena.
Although Bodkin doesn't have a long list of red flags when it comes to identifying and vetting big data talent -- common sense and internal needs should rule -- one that does get his radar chirping: Resumes or LinkedIn profiles overloaded with big data buzzwords, without the requisite evidence of real knowledge and experience in the technologies and responsibilities behind the buzzwords.
"If you see a long list of things [and] it's unlikely that they've had that level of exposure, that's important," Bodkin. "That's certainly something that we like to get some validation of... is this person representing what they're capable of accurately? Do they know what they know and know what they don't know?"
You can use distributed databases without putting your company's crown jewels at risk. Here's how. Also in the Data Scatter issue of InformationWeek: A wild-card team member with a different skill set can help provide an outside perspective that might turn big data into business innovation. (Free registration required.)
Kevin Casey is a writer based in North Carolina who writes about technology for small and mid-size businesses. View Full Bio
Top IT Trends to Watch in Financial ServicesIT pros at banks, investment houses, insurance companies, and other financial services organizations are focused on a range of issues, from peer-to-peer lending to cybersecurity to performance, agility, and compliance. It all matters.
Join us for a roundup of the top stories on InformationWeek.com for the week of October 9, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week to get the "story behind the story."