Hiring, Fast and Slow
Hiring screening optimizes for fast thinking, but IT success depends on slow thinking.
When should you assign technical homework during an interview?
I once worked with a company that had a take-home assignment as the first stage of an interview process. Ugh. Here are my suggested alternatives.
What if we can't afford to hire an expert?
When you can't afford to hire an expert, “moneyball it”. Hire a fractional expert.
Who to hire first: A senior or junior?
For a first hire, select a candidate with seniority in line with the role's ability to destroy your business.
What are your least favorite things?
One simple question that can help separate the novices from the experts.
Are your hiring filters working?
How often would an otherwise great candidate simply not continue the application process due to your filtering criteria?
People are naturally great
For the vast majority of roles, hiring the "best" is simply a waste of recruitment time and effort.
Unsure? Browse the archive.
The hidden costs of hiring too fast
I was making really great progress at instilling a culture of quality until the pressure above from to "hire more people!"
What to look for when hiring an engineer
Just about the last thing I really care about is someone's actual ability to code.
A simple way to improve your technical onboarding
Somewhere, long ago, I learned of a technique I like to employ when onboarding new team members
A DevOps role by any other name...
Can we avoid conflating DevOps with operations in job titles?