3 ms·
> * How big is the team I would be working with? In particular, you'd want to distinguish between the people you directly collaborate with on a daily basis and
by JoshTriplett 12y ago
> * How big is the team I would be working with?
In particular, you'd want to distinguish between the people you directly collaborate with on a daily basis and the broader organization working on the same or similar technologies.
> * Do team members socialise out of hours?
Depending on your preferences, that can be a good question or a critical one. If you want to socialize out of hours, it's good to know if the team likes to do so. On the other hand, it can be critical to know that you're getting into a company where you have to socialize out of hours to fit in. Don't work somewhere where you're going to be utterly at odds with the company culture.
> * What is the average age of team members?
That's a very strange question; why do you think that matters, or that it's reasonable to ask? As an interviewer, I'd find that question extremely offputting.
> * How long has the longest member of the team been there?
Now that's an interesting question. Good to know the turnover of the team. Goes along with "how long has the team been around?".
> * Does the company have a "no arseholes" rule (or "no brilliant jerks")?
As much as I think this is a very critical item for a good work environment, do you think an interviewer is likely to answer that question any differently whether they do or not? Sure, if they come right out and say that they're willing to tolerate such behavior, run away fast. But otherwise, they either do have such a policy, or they'd like to think they do but they really don't in practice, or they'd like you to think they do.
> * How old is the company?
You should know that before you ever go to the interview.
> * Does the company release any software as open source?
If you can't find that out before going to the interview, the company isn't doing very well at it.
- pgl 12y ago> That's a very strange question; why do you think that matters, or that it's reasonable to ask? It's just to find out more about who I might be working with. It didn't feel weird to ask - but perhaps you're right. Often it's been explained before as part of the "how sociable is the team" question. ("Well, we're all family people, so...", or "Most of the team are in their early 20s so often out on a Friday night" etc.) > As much as I think this is a very critical item for a good work environment, do you think an interviewer is likely to answer that question any differently whether they do or not? This question is generally one I would ask someone who I would be working with as part of the team, and while you might not get a direct answer, you can tell a lot from how they answer. If it's a bit vague, then they probably don't have anything specific in place. But I've also had very enthusiastic replies along the lines of "Yes we do! In fact that's very important to us!" This can make a difference if there's multiple offers on the table and you're trying to figure out which offer to take. The other questions are, yes, obvious, but they're basically leading questions. Asking about the company history can often give you some insights into recent events that might not be obvious from their website (and other sources), and replies to the question about open source are useful to see whether they're aware of open source practices inside the company (depending on the size of the company, there might be different things going on).