|
| 1 | +.. post:: February 1, 2019 |
| 2 | + :tags: advertising, sustainability, hiring |
| 3 | + :author: David |
| 4 | + :location: SAN |
| 5 | + |
| 6 | + |
| 7 | +Lessons From and For Hiring Managers |
| 8 | +==================================== |
| 9 | + |
| 10 | +Over the last four weeks, Eric Holscher and I did dozens of customer development interviews with engineering hiring managers. |
| 11 | +We wanted to learn more about hiring processes at various companies |
| 12 | +with the ultimate goal of building a product to help companies find developers. |
| 13 | +We talked to people looking for talent at five person companies all the way up to the biggest names in tech. |
| 14 | +In this post, I am going to cover some of the common things we heard from hiring managers |
| 15 | +and **share some ways for hiring managers to improve their company's process**. |
| 16 | +In a week or two, I will write the second part to this blog with actionable tips |
| 17 | +for job seekers based on the same interviews. |
| 18 | + |
| 19 | + |
| 20 | +Why is Read the Docs tackling hiring? Hasn't that been done? |
| 21 | +------------------------------------------------------------ |
| 22 | + |
| 23 | +While we didn't initially think about Read the Docs ads for recruiting, |
| 24 | +based on some :doc:`unexpected past successes <hiring-developers-with-readthedocs>`, |
| 25 | +we decided to position promoted jobs as one of our main verticals within our advertising. |
| 26 | +Rather than dash forward and create a product, however, we started by just talking to hiring managers |
| 27 | +to understand the hiring process better so we can best meet their needs with something we create. |
| 28 | + |
| 29 | +One of the questions we asked in our interviews was how long it took to hire their most recent developer? |
| 30 | +Specifically, we asked hiring managers to consider how much time they and their team spent sourcing candidates, |
| 31 | +filtering resumes, preparing for and doing phone and onsite interviews, and anything else. |
| 32 | +Internal recruiters' time is valuable too, but we figured the hiring manager |
| 33 | +would probably underestimate how much time the recruiter spent since they didn't directly observe it. |
| 34 | +While answers were all over the place, the range with the most overlap was **50-100 hours of engineering time to make a hire**. |
| 35 | +No huge revelation here, but companies make a massive investment in hiring. |
| 36 | + |
| 37 | +From my days being an interviewer at Qualcomm and Amazon as well as a smaller startup, |
| 38 | +I'd say fifty hours is on the low side for big company but about right for a smaller company. |
| 39 | +When something costs 50+ engineering hours to do, |
| 40 | +any improvement is worth a lot of time and money |
| 41 | +and at Read the Docs we believe we can help significantly here. |
| 42 | + |
| 43 | + |
| 44 | +Top hiring channels |
| 45 | +------------------- |
| 46 | + |
| 47 | +It was no big surprise to hear that **referrals were the top hiring channel**. |
| 48 | +The second best channel was a bit of a surprise with local meetups and local communities being very high in multiple interviews |
| 49 | +although this was less true among the largest companies we talked to. |
| 50 | +Companies also had some success with recruiting at conferences, using various job sites, and proactive outreach. |
| 51 | +I'll address recruiters in a separate section. |
| 52 | + |
| 53 | +Hiring managers shared strategies with us that they used to increase the number of referral and community candidates they got. |
| 54 | +Two different companies we talked to hosted multiple local meetups at their offices and one of those hiring managers said |
| 55 | +"being plugged into the community" was their main channel for hiring. |
| 56 | + |
| 57 | +Another hiring manager who focused a lot on developers with security experience talked about having "LinkedIn parties" |
| 58 | +where either a hiring manager or internal recruiter sat with engineers on their team one-on-one to go through their LinkedIn network. |
| 59 | +Even when he heard a person "is great, but they'll never change jobs", that was a good candidate to target. |
| 60 | +Security is such a high demand field, he said, that very few great people are actively looking for a job. |
| 61 | + |
| 62 | + |
| 63 | +.. figure:: img/2019-job-seeker-timeline.png |
| 64 | + :alt: Job seeker timeline |
| 65 | + :width: 100% |
| 66 | + |
| 67 | + |
| 68 | +Reaching people who aren't looking is critical |
| 69 | +---------------------------------------------- |
| 70 | + |
| 71 | +One of our biggest takeaways at Read the Docs was that companies wanted to reach candidates before they started actively looking. |
| 72 | +Most of the hiring managers we talked to stressed the importance of getting in front of passive candidates. |
| 73 | +Certainly fewer people are actively looking for developer jobs than those who are just open to a change. |
| 74 | +A few different reasons were given but I actually think `Joel Spolsky had it right`_ when he said |
| 75 | +top developers "barely ever apply for jobs at all. That's because they already have jobs." |
| 76 | + |
| 77 | +This quote isn't necessarily a slight against people who apply actively to jobs. |
| 78 | +Virtually everyone I know in tech started their career applying to a job. |
| 79 | +Rather, the implication here is that as a developer becomes a mid-level developer |
| 80 | +and then becomes a senior developer, they are more likely to rely on their network |
| 81 | +to somewhat passively job seek rather than going through the front door |
| 82 | +and simply applying on a company website. |
| 83 | + |
| 84 | +Reaching people who aren't actively looking is one area where Read the Docs can really help. |
| 85 | +Companies want to reach them when they are just thinking about a new job or perhaps passively seeking. |
| 86 | +Developers who come to our site are actively building software, not job-seeking. |
| 87 | +Many of them are content at their current position. |
| 88 | +For those that aren't, this is a perfect place to showcase great companies |
| 89 | +and help Read the Docs' visitors to find their next job. |
| 90 | + |
| 91 | +.. _Joel Spolsky had it right: https://www.inc.com/magazine/20070501/column-guest.html |
| 92 | + |
| 93 | + |
| 94 | +Recruiters can be worth it |
| 95 | +-------------------------- |
| 96 | + |
| 97 | +In each interview, we asked whether the company used recruiters or recruiting related services (eg. Hired, Triplebyte). |
| 98 | +Universally, hiring managers brought up how expensive recruiters are, |
| 99 | +but most of the people we talked to who had actually used recruiters in the past had a positive impression overall. |
| 100 | +Hiring takes a ton of time and typically takes it from senior folks at the company. |
| 101 | +At smaller startups, that's frequently the CEO or CTO. |
| 102 | +Even though the price is high, recruiters who help speed that process along are worth it. |
| 103 | + |
| 104 | +I think the quote that really summed it up was from a VP of engineering at a startup that just raised a Series B. |
| 105 | +He's trying to grow his team by 10 developers this year (about a 50% increase). |
| 106 | +His experience hiring his first couple developers through a 2-person boutique recruiting firm was great and |
| 107 | +he would use them for hiring everyone "if hiring 10 people didn't mean $100k+" in fees alone. |
| 108 | + |
| 109 | +Full disclosure: Triplebyte is an advertiser on Read the Docs. |
| 110 | + |
| 111 | + |
| 112 | +Filtering resumes isn't a real problem |
| 113 | +-------------------------------------- |
| 114 | + |
| 115 | +Every single hiring manager we talked to complained about the time they spent filtering resumes from applicants. |
| 116 | +Some choice quotes I heard included "95% of applicants weren't a fit" even after only reviewing the resume |
| 117 | +and a hiring manager who posted to a very popular remote-only job board told me he got "literally one thousand applications". |
| 118 | +While I believe this is a legitimate complaint, |
| 119 | +I think `Aline Lerner said it best`_ when she said "Engineering hiring isn't a filtering problem. It's a sourcing problem." |
| 120 | +Filtering is just a time-consuming task that hiring managers directly deal with. |
| 121 | + |
| 122 | +The real problem here is that **the number of applicants to a job post is a vanity metric**. |
| 123 | +What hiring managers are looking for is qualified applicants, which is harder to gauge without some additional work. |
| 124 | +One of the problems here is that a lot of jobs sites make it really easy for candidates to apply to lots of jobs. |
| 125 | +This is understandable from their perspective as more applicants makes it look like their platform is more valuable. |
| 126 | +I'm not trying to talk trash on these platforms as there's no reason for them to erect artificial barriers to the application funnel, |
| 127 | +but hiring managers told us they want candidates who want to work for their company |
| 128 | +not somebody who is applying to every single job out there. More on that in a future post. |
| 129 | + |
| 130 | +Instead of building product here, I think hiring managers just need a few tweaks |
| 131 | +to get more of a signal of candidate quality and intent in their applications. |
| 132 | +A few of the hiring managers we talked to described how they did this. |
| 133 | +Multiple hiring managers mentioned how they required a cover letter that answered specific questions ("why us" was the most popular). |
| 134 | +Another hiring manager described how his hiring system just asked a few short questions of candidates |
| 135 | +-- for example, "what is the software project you're most proud of" -- when they applied. |
| 136 | +When a candidate didn't do a cover letter or didn't answer the questions, they weren't considered. |
| 137 | +I think the latter solution is best as it solves the one-click apply problem without being too much of a barrier. |
| 138 | + |
| 139 | +.. _Aline Lerner said it best: http://blog.alinelerner.com/building-a-product-in-the-technical-recruiting-space-read-this-first/ |
| 140 | + |
| 141 | + |
| 142 | +TLDR |
| 143 | +---- |
| 144 | + |
| 145 | +Every company we talked to said that hiring talent and especially senior developers was hard, expensive, and time-consuming. |
| 146 | +At the same time, many of the hiring managers we talked to had tactics they used to improve the process and you can use these strategies too. |
| 147 | + |
| 148 | +* **Have a strategy for getting more referrals** whether that is actively asking employees or having an overly generous referral bonus. |
| 149 | + Referrals are probably your top source of candidates so figuring out how to get more will save you time and money in the end. |
| 150 | + The same goes for any of your other best recruiting channels. |
| 151 | +* **Reach passive candidates**. There are a lot more passive candidates than active ones so have a plan to reach them. |
| 152 | + Great developers (especially senior ones) probably aren't actively looking for a new job and it's a job-seekers market. |
| 153 | + Even if somebody isn't considering a new job at all, the next time they do, you want them to think of your company. |
| 154 | +* **Get more signal in your application process** by adding a step such as a cover letter, quiz, |
| 155 | + or simply add a couple questions folks have to answer. |
| 156 | + Making candidates spend even one extra minute on their application can save you hours filtering resumes. |
| 157 | + |
| 158 | +Check back soon for our next post which covers tips for candidates based on the same interviews! |
| 159 | + |
| 160 | + |
| 161 | +.. admonition:: Ready to hire your next developer, fast! |
| 162 | + |
| 163 | + `Get in front of passive candidates already using your tech`_ by promoting your job openings with Read the Docs. |
| 164 | + |
| 165 | + .. _Get in front of passive candidates already using your tech: https://readthedocs.org/sustainability/advertising/recruiting/?utm_medium=referral&utm_source=readthedocs-blog&utm_campaign=hiring-manager-interviews-i |
0 commit comments