<http://schema.org/articleBody>
"Vivek Ravisankar is the co-founder of Y Combinator alumnus,\u00A0HackerRank,\u00A0a platform for coding contests used by programmers to hone their skills and a tool for companies to streamline their own recruiting process.\r\n\r\n\r\n\r\nThe hiring process for technical talent is broken. Across the board, the number one problem for any company is hiring programmers. Whether it\u2019s a series A-funded startup or a large multinational corporation, hiring technical talent takes up a lot of time, energy, and money - and doesn\u2019t always result in the best hires.\r\n\r\nEven if you have many resources devoted to hiring, the number one pain point remains the same. There\u2019s something fundamentally wrong in the evolution of the process.\r\n\r\nFor a long time, hiring technical talent was something just for software companies and startups, but this is no longer the case. To put it bluntly,\u00A0software is eating the world and everyone needs coders.\r\n\r\nHere are\u00A0four\u00A0hacks that\u00A0every\u00A0company can apply to their recruiting process to help efficiently and effective find great programming talent, and save time.\r\n1. Learn to look past a resume\r\nA trap that many companies fall into is relying too heavily on a candidate\u2019s resume.\r\n\r\nDon\u2019t get me wrong - resumes are a great indicator of a candidate\u2019s previous experience, and can give you terrific insight into their work ethic and skill set developed through previous employers. Some companies move fast and break things, and others have a completely different environment. Where you\u2019ve worked can be very telling of your programming philosophy and what camp you fall into.\r\n\r\nMost companies look for two things: a great school, and previous experience at a great product company. For some companies, this is all they initially look for. However, putting a resume on a pedestal like this is a seriously flawed approach.\r\n\r\nBy doing so, you are competing for the same, very small, pool of talent with hundreds of other companies. There are amazing talent\u00A0across other planes\u00A0than this; candidates that, for whatever reason, didn\u2019t get an opportunity to go to a great school, or maybe even skipped school to be able to keep hacking.\r\n\r\nIf a candidate does not have a great resume, it doesn\u2019t necessarily mean they are a bad candidate. Ironically - and this is the case more than you would think - it could be that they have spent their entire life learning their craft and put school second.\r\n\r\nLook for those diamonds in the rough \u2013 those that may not have a shining resume but do have the programming skills you are seeking.\r\n2. Create a consistent bar for your application process\r\nEvery company has different values, processes, and cultures. But when hiring, the interview should be designed with objective measurement standards in mind that will clearly indicate whether or not the bar has been cleared.\r\n\r\nProgramming is a science, not an art, and the hiring process should be the same\u00A0way. So many interviewers, whether consciously or subconsciously, try to prove their intelligence by asking hard questions \u2013 often with the intention of finding people exactly like themselves. They\u2019ll try to trick candidates to see if they fall into a trap; if they do, it\u2019s a fail. If they don\u2019t, it\u2019s a hire.\r\n\r\nHere is a great example: a friend of mine, who happens to be a brilliant developer, is in the interview process right now. He\u2019s interviewing with a number of top companies. Each of these companies obviously operate in different\u00A0ways, but he has NO clue what to expect in each interview. What will they ask? What specific skills might come up? How do you know which specific skillset are they interested in?\r\n\r\nCatching the candidate off guard to see how they respond is an unfruitful tactic used by too many companies. There is absolutely nothing wrong with preparing a candidate for an interview - this is actually a great sign that they are truly interested in the company, and are willing to do the work ahead of time, be ready for your questions, and be immersed in the company as quickly as possible.\r\n\r\nRemember to ensure that your interviewers are prepared. Every interviewer in the panel should know what is expected from the candidate, know what questions to ask, and what specific skills and talents the company is seeking. With this in mind, a company can make an informed and completely objective decision.\r\n3. Fine tune your recruiting process with data\r\nThe most streamlined processes in any business are data driven, and that is no exception for the recruiting process. How can you objectively evaluate and select a candidate without data (which is, by definition, objective)? And more importantly, how can you expect to improve your hiring process if you have no understanding of its previous effectiveness?\r\n\r\nPlain and simple: recruiting should generate a lot of usable data. You should be able to quantify a programming candidate\u2019s skills, but you should also be able to do the same with your interviewers. You want to be able to identify which interviewer is doing a great job, which questions have led to successful hires, and which questions led to busts - and use this to mold your recruiting process moving forward.\r\n\r\nIt\u2019s important to identify these questions and interviewers by percentages of interviews held that went on to be hired.\r\n\r\nAlthough most technical interviewers will be developers, that doesn\u2019t mean that the best developer will be the best interviewer. This requires an entirely different skill set, and is one that needs to be recognized, and more importantly, tapped into. It\u2019s important to not make these decisions just by gut feeling, but with supporting data.\r\n4. Recruiting can\u2019t be outbound: The future lies with inbounds\r\nDespite the natural inclination to reach out, the process of constantly pinging programmers with recruiting inquiries isn\u2019t sustainable anymore. This has always been the logical method for recruiters, but it does not guarantee a good response in today\u2019s market. The key is to generate\u00A0inbound\u00A0interest.\r\n\r\nWhen was the last time you bought something because you got a cold call about it? Or saw an ad for it? Everything we buy is either because we are naturally attracted (inbound) or hear great reviews from a friend (referral).\r\n\r\nThis same line of thinking can be applied to recruiting: a programmer is naturally attracted to a company\u2019s approach to business, or has heard great things about the company from a friend.\r\n\r\nA number of companies have started hosting\u00A0contests\u00A0to attract thousands of programmers to solve a particular challenge. The last security challenge conducted by the payment company\u00A0Stripe\u00A0attracted 16,000 security enthusiasts, and the AI\u00A0challenge\u00A0by Netflix attracted 100,000 programmers!\r\n\r\nDevelopers are a different breed \u2013 they love to try and solve problems and will even do it for free when challenged.\r\n\r\nTell the world what you\u2019re working on - not through a fancy job description, but in a fun and engaging\u00A0way. Every company claims they are the fastest growing company on the planet with 40 percent month-over-month of some parameter, funded by top-tier investors, etc. It\u2019s nearly impossible to stand out this\u00A0way. Instead, make people\u00A0want\u00A0to come to\u00A0you\u00A0by getting creative.\r\n\r\nWhat do you think about the technical hiring process? Do you think it\u2019s broken? If so, how would you fix it? The technical interview process is due for some big changes, and I\u2019d love to hear your thoughts in the comment section below."^^<http://www.w3.org/2001/XMLSchema#string>
<http://thenextweb.com/entrepreneur/2014/03/11/technical-recruiting-broken-4-ways-hire-better/>