Member-only story
Here’s What’s Wrong With How You Hire Software Developers
Your interviewing process is a waste of time
What’s the number one reason you’re hiring software developers?
Is it to write code?
Maybe you’re one of those companies who conduct computer scientist-like interviews. Your interview process includes questions about Big-Oh notation. Or you quiz people on the nuances of a specific language.
If an interviewee passes, you hire them for their “technical chops.” But once your new hires land the job, they’ll invest their time creating user interfaces and CRUD APIs.
We live in the age of frameworks and auto-generated code. We spend more time settings things up than we do coding. Most of us button click our way through building infrastructures.
Still, we design esoteric, hard-to-pass interviews. Untrained interviewers lick their chops, hoping to stump candidates.
We expect people to prove themselves. Write code on the board so we may judge thee. We look at our cheat sheet while the candidate struggles with a whiteboard marker in hand. We can’t wait to see another version of the Fibonacci sequence as sweat trickles down their brows.
Why do we do this?
