Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem here isn't the interviewee; it's the interviewer.

This is exactly why we do phone screenings and brief initial interviews. If something like location, development technique, interior design or dress code isn't going to work out for someone, you should be able to flush some of that out in a 15-minute phone screen, and the rest in a 30-60 minute initial interview.

By the time you're bringing someone in for a full day, the interviewer should be at well over 75% sure the person is a do-hire. Don't waste your team's time or effort on someone you're not going to go with (unless you're stress-testing your interview process...).

As far as walking out: there's so much data here. For the company, they've either got a dysfunctional interview process or some seriously difficult fellow developers. Both those problems need to be addressed.

For the interviewee, there's the information on how the team responds. If there's a problem, and they want to solve it, they need to be more pro-active about it. "Can we break now and continue later?" Also, "Can we get a post-mortem from you?" At the very least, it's a good time to break for coffee or beers around the corner.



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: