How to Build a Hiring Process Based On Skill, Not Pedigree

<p>It’s true what they say, “finding a job is a full-time job.” After all, as the hiring process becomes more global and recruiters are constantly inundated with an influx of applications, on the other end of that equation are the candidates submitting those applications, who grow weary as the days go by with no response.</p><p>As with most things, processes change over time, but, with some technical exceptions, the hiring process has mostly remained the same. Until now. <a href="https://www.linkedin.com/in/vivekravisankar/">Vivek Ravisankar</a> felt called to address the pain points of hiring after speaking with a recruiter. a</p><p><i>“I remember walking up to a recruiter one day and asking, ‘Hey, can you tell me how this whole recruiting process works?’ He pulled out his Macbook and he had two folders: pass and fail. He would look at a resume for 10-15 seconds and determine which folder [the resume] was actually going to go into. I was thinking, ‘Man, you have way too much power in your hands.’ But I can also understand and empathize with them because if you're Amazon, you don’t have a better way to do it either. So that was a trigger point. This needs to be fixed.”</i></p><p>The fix came in the form of HackerRank, a platform that helps developers put skills over pedigree. On this episode of IT Visionaries, Vivek explains what that means, and how it helps developers stand out from the crowd. Plus he explains  the dangers of utilizing A.I. throughout the hiring process and why distributed workforces are great for company diversity.</p><p><strong>Main Takeaways</strong></p><ul><li><strong>Supply and Demand:</strong> As companies continue to trend towards software companies, developers currently remain one of the most sought after candidates. However, that trend is drastically changing as the number of companies that employ developers rise.</li><li><strong>A.I. Is Not A Magic Pill: </strong>When it comes to the hiring process, A.I. should be used as a way to streamline your workflow, but not as an indicator of if