Preface: This post is written less as my opinion and more as a culmination of all the feedback (use cases) some four thousand high-end technology professionals have given me over the past three plus years.
We are in one of the tightest, if not the tightest candidate markets since, well…forever. More open positions than qualified candidates and new companies sprouting up every day (like the dot com). That said, the technical community has maintained a very high bar for talent and experience to make the cut when interviewing (not so much like the dot com). Modern day job descriptions look like a good action story super hero or better yet, Mark Zuckerberg. This and the fact that many still think we are in a soft market due to lasting effects of a recession, lead to ineffective first round interviews often, so I hear.
The first round interview is a first impression of your organization, and a lasting one. With the supply-and-demand curve favoring them, candidates are more likely to just move on from a bad experience. So, is it better to cover technical strengths? Or weaknesses? Code test?
If you use this simple model while conducting first round interviews you’ll find the ability to make a good assessment while also leaving a great impression on each candidate you interview whether or not you decide to move forward with them in the process.