Hacker News Reader

I think pairing during an interview is a great idea, and I'm surprised that it's not a more common practice. Solving a code problem before the interview is one way to get a codebase on which you can pair during the interview that both the candidate and the interviewer are familiar with. (In theory you could also pair on solving a new problem).

View on HN

Pairing is a common practice at companies that pair, and not a common practice at those that do not. Pairing is stil not a widely adopted practice industry-wide.

People who were taught to manage using industrial revolution management practices look ta pairing a producing half the output as could be produced by two people at two machines working in parallel.

Regardless of how companies feel about pairing during regular development, it's hard to imagine what they would have against pairing during an interview.

I'm saying that you'll typically not find pairing as part of an interview process at an organization that does not value pairing. Furthermore, due to the low adoption of pairing, you'll find a lot of candidates that have never paired before, and if there's one thing we know about people, it is that they fear the unknown.

Reply on news.ycombinator.com