Technical Hiring: A Survival Guide for the Slightly Unhinged

As a seasoned technical manager, let me tell you – building a top-notch team of tech wizards is its own kind of adventure. Think of it like a high-stakes puzzle where the pieces have minds of their own. Some fit perfectly, others need a little coaxing, and a few are shaped so bizarrely you’re convinced they came from a different box entirely.

In our last episode, we conquered the MVP Framework to strike a balance among the various tech deities within our realm. Today, my friends, we embark on the quest to fill those skill gaps – to find the diamonds in the rough, the geniuses who speak in code. Buckle up, it’s gonna be a bumpy ride.

The “Butts in Seats” Mentality: Sometimes Getting Started is the Hardest Part

We’ve all been there, paralyzed by the quest for the perfect candidate. Endless interviews, countless revisions of the job description, and a growing sense of dread as the workload piles up. Here’s the thing: while thoroughness is important, sometimes you gotta embrace the “good enough is good enough” mentality, especially in a fast-paced tech environment.

Here’s where those two simple questions save the day:

• Can They Do the Job? We’re not talking about coding savant status here. Can they demonstrate the fundamental knowledge and problem-solving skills needed to get the job done? Would they, given reasonable supports (and one’s you have or can afford) get to the level you need them to be, in a reasonable timeframe?

• Would They Make the Team Fall Behind? Are we talking about a complete newbie who’ll need hand-holding for months, or someone who can hit the ground running with minimal disruption?

If your answers are a tentative “yes” and a confident “no”, it’s time to take the calculated risk. Why?

• Onboarding and Training: Interviews are just a snapshot. Getting someone in the door allows you to see how they learn, adapt, and collaborate with the team. Often, that’s the true indicator of potential. Plus, they can put into action all the cool training material you’ve thrown together for the team (and if you don’t have anything, they can help be the guinea pigs to create some for the next round of victims).

• The Cost of Inaction: Projects stalled, deadlines missed, your team burning out – these are the consequences of an eternally open position. Sometimes, bringing on a slightly imperfect candidate gets things moving.

• Mentorship Matters: A strong team culture prioritizes knowledge sharing and upskilling. That promising but slightly green candidate might thrive with the right guidance.

Important Caveat!

This isn’t about hiring just anyone to fill a chair. Due diligence in the interview process is still crucial. But, once you’ve established a baseline level of competence, remember that progress is often better than perfection (so don’t drag out the hiring process any longer than necessary).

The Technical Hiring Gauntlet

To even get to the point of having someone to interview, you’ve got to come up with a strategy to find these elusive development resources (more than just a quick post to ZipRecruiter will provide). The hiring battlefield is littered with jargon and cryptic job descriptions that could give the Rosetta Stone a headache. Here’s where the fun begins.

Helpful Hints for Crafting a Positive Job Description

Your job description is like a digital billboard for awesome talent. If it’s vague, riddled with buzzwords, or longer than a terms-of-service agreement, you’re gonna see crickets instead of coding superstars. Here’s how to make it truly shine:

• Ditch the Jargon Tsunami: Yes, your team might be fluent in acronyms and obscure frameworks, but your ideal candidate may not be. Focus on describing the impact of the role and the real-world problems you’re solving.

• Sell the Sizzle: Don’t just list tasks, highlight the cool stuff! Are you building cutting-edge tech? Working with massive datasets? Let candidates envision themselves being part of something exciting.

• Be Honest About Expectations: No one likes surprises, especially when it comes to work hours, on-call rotations, and most importantly salary. Be upfront about it, and you’ll filter out candidates who wouldn’t be a good fit anyway.

• Degree or No Degree? That Is the Question. The eternal debate rages! Is that shiny CS degree essential, or is real-world experience the true treasure? My stance? I care more about whether they can build a killer app than recite Big O notation. Give me the scrappy hacker who builds robots in their garage over the textbook ace any day. However, to be successful, they can’t just be a code monkey who copy and paste things they dug up on StackExchange – but rather, someone who can understand algorithmic principles (having a degree is one way of demonstrating this).

• The Keyword Tango: A delicate dance. Include relevant keywords so search engines and algorithms put you in front of the right people, but don’t overdo it to the point where your description reads like robot gibberish.

• Proofread, for the Love of Code: Typos and sloppy grammar scream unprofessionalism. Even the most brilliant developer might be hesitant to join a team that can’t get the basics right.

Building a Better Interview Process

• Decoding the Interview: Mind Games or Medieval Torture? We’ve all been there – the dreaded whiteboard interrogation, where you’re asked to reverse a linked list while solving differential equations in Klingon…blindfolded. Sure, it’s fun to see how they crack under pressure, but let’s be real, when was the last time you needed to calculate projectile trajectories on the fly?

• The HR Machine: Think outside the box. One of my key considerations for any technical role, is their ability to think algorithmically. Luckily there is a Steam game available that does just that. Give the candidate a fixed time and have them progress through the game as far as possible to watch how they approach analytic thinking. It’s not a make-or-break component, but it ensures that those who pass through the grinder have the appropriate mindset necessary for high-level engineering success.

• A Note for My Fellow Managers: When it comes to the interview process, let’s cut the fluff and get to the good stuff. Can they code? Do they play well with others? Would your team rather have root canal than work alongside this person? These are the real questions. Now, when HR gets involved…well, bless their hearts, bless their little algorithmic hearts. Just be ready to translate everything.

A Few Words of Wisdom (Before I Lose My Sanity)

The search for technical talent is an ongoing dance, a constant quest for those elusive code unicorns that perfectly fit your team’s puzzle. There will be days of frustration, whiteboard drawings will be erased, and job descriptions will be rewritten more times than you care to admit.

But in the end, when you’ve assembled a team so powerful it could probably hack the Pentagon (not that we condone that sort of thing…), the thrill of victory will make it all worthwhile. So, chin up, battle-hardened tech managers. May your code be bug-free, your budgets overflowing, and your team stocked with the most brilliant, caffeinated minds in the land.