WhoBuilt

Breaking Down HackerRank's Survey of 40,000 Developers

Mar 30, 2018· 54 min· 8.8K views·Watch on YouTube

Speaker

Vivek Ravisankar, co-founder and CEO of HackerRank, discusses the company’s developer skills survey and hiring practices with a Y Combinator host.

From mock interviews to skills-based hiring

HackerRank aims to match developers with jobs based on demonstrated skills rather than resumes. Ravisankar traces the idea back to Interviewstreet, a paid mock interview service in India, and a later service helping students apply to graduate programs. Both struggled to grow, leading the founders to focus on selling to companies and building coding challenges for hiring.

What the developer survey found

HackerRank surveyed a million members of its community and received nearly 40,000 completed responses to a 40-question survey. Respondents came from several regions, with more than 40% in Asia-Pacific. Findings included that one in four developers learned to code before learning to drive, and that developers valued work-life balance and opportunities for continuous learning.

How developers learn and get hired

Hiring managers had mixed views of boot camps, which Ravisankar said may depend on their quality. The survey pointed to problem-solving as a priority across company sizes, while startups also valued experience with their specific technology stack and project contributions. Ravisankar said many developers learn through YouTube and practice sites, so employers should assess skills rather than rely on degrees, schools, or past employers as proxies.

What candidates and early hires need

Ravisankar said candidates evaluate employers too, including their interview process, peers, and the relevance of technical questions. He encouraged companies to discuss product and business strategy with developers and said brain teasers can be replaced by more relevant ways to assess problem-solving. For HackerRank’s first engineering hires, he emphasized motivation, learning ability, connection to the company’s mission, and looking beyond traditional credentials.

Takeaways

  • Use work samples and relevant coding challenges to assess skills instead of treating resumes or degrees as proof.
  • Focus an early product on a narrow group of users and make it valuable to them before expanding.
  • When selling to a new audience, check whether they have the money and ability to pay.
  • Show developers how their work connects to the product and business strategy.
  • Look for early hires with drive and learning ability, including candidates without conventional credentials.

Mentioned in this talk

Search inside this talk

What was claimed 12

Show all 12 facts

Related talks