Hacker News new | past | comments | ask | show | jobs | submit login

As an interviewer, I've been on the receiving end of most of those questions (or some variation of them). It's a pretty reasonable list.

One thing though is that most interviewers don't leave a whole lot of room for a barrage of questions so you really need to pick the two or three that you really want the answers to. For example, you probably don't want to waste time asking explicitly about version control at a company that you know does open source on github. Open ended questions about engineering culture will give you a much better picture (e.g. what's the story w/ tests or deployments or design autonomy or whatever).

Or, what you can do in addition is ask the recruiter (or whoever the first point of contact is) if you could spend 30 mins to talk to someone on the team, outside of the interview window, just to have a casual chat. Some companies have this arrangement setup as an official transparency program, others are more than happy to arrange it informally.




Pre-covid, we’d take the person to lunch for a 1:1 or 1:N for this purpose. Those were often very informative. They were meant to be casual, though one candidate (out of hundreds) managed to fail based on the lunch interview alone. If it’s possible, people will find a way, I guess!




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

Search: