why<\/em> they started learning in a specific language. In a short time, your exposure to the natural conversation on the topic should help you build a natural intuition on the subject. Just keep in mind that junior recruits might have a much narrower perspective on these types of questions.<\/p>\nWin 2: Get Tough Questions Answered Fast<\/h2>\n
I won\u2019t pretend to understand the ins and outs of talent acquisition. I do understand optimization problems though, which are most certainly aligned with recruiting. When looking for ways to optimize your recruitment process, the most obvious step is to re-use the connections you build rather than relying only on new contacts. Surely, you’re already doing this to some degree. The thing about optimizing is that you can keep making things even better!<\/p>\n
In developing a network of technical professionals, many connections are likely suitable to help answer technical questions. Engineers can help you audit job descriptions for nonsense, help you better realize where to look for new talent, and even help field tech-specific questions that aren\u2019t easily Google-able. Don\u2019t let those hard-earned connections fall by the wayside after the initial position is filled \u2013 even if your recruit<\/em> filled it! This means nurturing these connections and doing more, in the initial steps for recruits, to better understand their backgrounds, develop a report, and make a meaningful connection. It might sound like more work, but it is the kind of effort that continues working\u00a0for<\/em> you.<\/p>\nFor example, let\u2019s say you\u2019re hiring a team that\u2019s looking for new talent to build their payment processing infrastructure. You know they\u2019re \u201cFinTech\u201d but so is everything else that deals with money, right? A member of your technical network can help you better understand that recruiting candidates from a Crypto-based<\/em> FinTech might not be what your traditional payments processing client is looking for. To be fair, there\u2019s likely to be some<\/em> overlap these days \u2013 but that\u2019s something your technical network would help you sort out!<\/p>\nWin 3: Make Your Network \u201cWork\u201d For You<\/h2>\n
Engineers know other engineers and<\/em> what they\u2019re good at. In the time it takes you to fully absorb the technical details of a new position, comb your network of contacts, and draft a new posting to LinkedIn, a member of your technical network could come up with a shortlist of candidates with a first-hand opinion for each. Chances are, they could even vouch for that person’s fluency in any number of requirements for a position.<\/p>\nNow, this comes with some caveats. Namely, what incentives do these engineers have to offer you referrals? On the softer side of motivation, they get to help a friend find a job. Let’s put that one aside for the moment, filed away with things like helping make the world a better place<\/em>.\u00a0 If you want practical immediate action you need to consider practical immediate incentives. Spoiler alert: engineers like money just like everyone else<\/em>. What if you could send a single email to a network of engineers and have them all respond with a list of people they know would be qualified for a position? What would that be worth to you? What size of\u00a0investment<\/em> would you consider warranted for that type of return?<\/p>\nThere\u2019s no one-size-fits-all approach here, but the mechanics are universal: send and receive<\/b>. In a common model, the referral model, you send compensation (or a chance of compensation) and receive leads. There\u2019s no need to deep dive into the implantation here \u2013 just look at any major referral marketing program out there and you can discover the mechanics.<\/p>\n
Every recruit is a possible referral machine for you, with their ears to the ground, making all the connections that could benefit you, day in and day out. How would you incentivize them to respond to emails with referrals? Effective incentives could range from a percentage share of the placement value or be as simple as a $100 Amazon gift card. When you have an email list of relevant connections, even a small incentive can produce tremendous results.<\/p>\n
Final Thoughts<\/h2>\n
These are three easy ways to leverage the effort you put into recruiting to help ensure those efforts can continue to benefit you. Think of it like compound interest: initially, the size of the win will be minimal. However, over time the results will be exponential! By recognizing the value your recruits can offer you, your retained value from your recruitment efforts can begin compounding just like your savings might if you invested them wisely. Whether you\u2019re in-house for a FAANG-level company or hustling as a private contract, these easy wins are accessible to you and can help supercharge your impact. The only thing you need is an email client, a spreadsheet editor, and some focused determination.<\/p>\n","protected":false},"excerpt":{"rendered":"
Software Engineering is a competitive field and subject to aggressive recruiting. I have heard both engineers and recruiters express frustration resulting from working with each other. Engineers deal with recruiters not adequately briefed on technical details and recruiters deal with our very interesting personality types. Both sides have been through a lot, and a better […]<\/p>\n","protected":false},"author":2,"featured_media":3569,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[186],"tags":[754,753],"acf":[],"_links":{"self":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/3568"}],"collection":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/comments?post=3568"}],"version-history":[{"count":4,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/3568\/revisions"}],"predecessor-version":[{"id":3573,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/3568\/revisions\/3573"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media\/3569"}],"wp:attachment":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media?parent=3568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/categories?post=3568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/tags?post=3568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}