Ask HN: Do you like code pairing interviews? I hate them

Would it be easier if you had half an hour to chat with the person before you jumped into writing code?

A lot of companies prefer pair programming so they can talk through problems with a candidate, both to get a feel for how they approach their work, and to make sure they aren't blocked on anything, given the limited amount of time. Was your interviewer talking with you while you paired?

I like them a lot. It tests a lot of things.

A more common complaint is about whiteboard coding. Having a laptop connected to a projector is exactly what many people say they would prefer.

What you are describing is a pretty poor pairing interview process. I did a bunch of really frustrating whiteboard type interviews and sudo pairing interviews like you describe before interviewing for my current position [1].

The screen is a one hour onsite pairing session followed by a final round that is a day of pairing using a proper workstation: One computer, two monitors and two sets of mice/keyboards. You pair with one person in the morning and another in the afternoon. It's very relaxed (you take turns "driving") and it gives you and the interviewers a lot more information about each other and your potential place of work. It also gives you enough time to adjust to the process if you are nervous. I don't think I'd do it any other way going forward.

[1] http://pivotal.io/careers

It's definitely a new skill on top of sitting alone and writing code. You can practice by doing some pair programming at your current workplace, with a friend, or at a coding meetup.

Edit: it may also mean the company you are interviewing at does pair programming. If you don't like pair programming, the interview is a good time to bring it up!

This sounds better than whiteboarding, but I think you're right. There's a big Heisenberg effect going on that's going to cause a lot of false positives

After searching for developers this year, I can say that pair programming during an interview is hard on the interviewee and could also be frustrating for the interviewer.

That said, our best hire was the one person who rose to the occasion and solved the problem we were asking. For that reason, I would do it again.

What made it frustrating is that I am the type of person who likes to have my dev environment setup for coding, I also work in linux and not on a mac. I am also a quiet type of guy who codes best when I am sitting on my own. I do work with my team very well but I feel weird when people are watching over my shoulder. The funny thing is that I went to a second interview at a company that is doing interesting things with biometrics and large scale problems and their approach was to ask me lots of interesting questions about how i handled scaling, how to debug performance, optimzing queries, log analysis. I am a senior engineer with years of experience and these guys were very smart, at the end of the interview their HR person came and said the team loved me and would like to extend an offer. My jaw dropped. I came from a really bad interview to a place where they are doing more advanced stuff and I got the job. I thank them so much because I felt they gave me a fair chance to get to know me. :)

It would be cool if there was some kind of service to simulate these interviews, where you can code while being watched in real time and then receive good quality feedback. Does anything like this exist?

This is simply a skill worth learning if you are not good at it already

It's sort of like assigning a watcher to you while you using a bathroom.

Usually companies who engage in these practices have tendencies to micromanage their personnel down the road.

Red flag.