2 ms·
It's not about "failing" or "passing" the question, it's about understanding the company. For example, the "agile" question... You might answer "yes, we do agil
by gjulianm 4y ago
It's not about "failing" or "passing" the question, it's about understanding the company. For example, the "agile" question... You might answer "yes, we do agile" and that might be a good thing for some developers and bad for others (and even that might depend on the position).
- ChrisMarshallNY 4y agoIf the question was standalone, I'd agree. However, in the context of all the other questions, I'm not so sure.
- gjulianm 4y agoWell, the list says at the beginning that the point is to choose the questions that matter to you. On time alone, you probably can only ask 3-4 per interview. I've asked similar questions on interviews and the truth is that they reveal a lot of information about the company. For example, asking about work on week-ends, I don't only want the answer but the way they answer is interesting: "we work some week-ends, lately quite a bit due to X, but rest assured all those hours are counted as overtime and compensated accordingly" is far different than "if we need to work week-ends we work week-ends", one tells me they know they're stretched thin but they don't want that to remain permanent, the other tells me I'm going to get fired soon for refusing to work a week-end on short notice.
- ChrisMarshallNY 4y agoFair point.