4 ms·

I wouldn't expect a recruiter to even know many of these. Code review process? Version control? Meeting frequency? How much spaghetti code do you have? Recruite

I wouldn't expect a recruiter to even know many of these. Code review process? Version control? Meeting frequency? How much spaghetti code do you have? Recruiters aren't tech people and things like meetings and code review culture can vary from team to team. Honestly, it's not uncommon to have 4 interviews at a company, and each person asks "do you have any questions for me?" A list like this is a good source of questions for these stages. Obviously, you shouldn't ask every single one, but when you meet with people on your prospective team, you should have SOME questions to ask them and this list is as good a resource for that as any.

Double_a_92 4y ago
But those things should be important to any professional developper! Like I would absolutely 100% not work for a company that doesn't use proper version control.
cholantesh 4y ago
There are a lot of technical questions there, yes, but plenty of non-technical ones. That being said, yeah, a recruiter isn't always going to have great pertinent insight to offer about the organization, and they might also be coached to give a particular set of replies. OTOH, the author specifies that not all the questions are going to be suitable to the initial interview, which would be the only one held with a recruiter anyway.