Skip to content

Comment on Principles of Recruiting from Keith Raboisparent

Comments

I understand how to do a good, structured interview process for a role like engineer or tech ops. (Work sample, chronological walkthrough of history and "why did you do that vs. this" at each step, etc.; ideally aptitude tests and existing work samples as screeners.)

How do you run a structured process for roles like sales, PM, GM, etc.? I guess with sales, depending on the model, you have a much lower bar (easy to hire, easy to fire), but that's not the case for long-sales-cycle enterprise products. A bad GM/COO will almost certainly sink an an otherwise-strong company.

The best I've ever come up with is just agreeing on criteria beforehand and having people score those, and then also having people who have done the role involved in both creating criteria and evaluating candidates (e.g. having lots of engineers engineer sales = probably a waste of everyone's time).

In a large company, you can test the interview process itself by seeing how candidates who are accepted under different processes perform, but in a smaller company, a bad string of sales hires means the company is probably not going to need to worry about making more hires -- and even if you do have time to correct, hiring/firing to the point where it is obviously a high churn environment deters good candidates and may cause good current employees to leave as well.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.