Ideally, how many meetings per week would you like to have?
Ugh. When I did interview training (some years ago, now) we were coached to avoid asking candidates hypothetical questions like this. The rationale being that it just becomes a game for the interviewee to guess what would make a good answer for the interviewer, and thus ultimately of little value as a means of fairly and accurately determining whether the candidate is a good fit for the job.
My reaction was similar to yours (even the "ugh" 😊). In addition to your point, I'd add that it's a useless question because there are many kinds of meetings with many kinds of people. If anyone thinks about meetings quantitatively instead of qualitatively, they're either fresh out of college (in which case I wouldn't criticize them), or they're focusing on meaningless data, which is a bad sign.
If someone asked me this question in an interview, I'd politely point out that I don't think in terms of number of meetings but rather in terms of outcomes. If the meetings led to useful outcomes for the team/company/customer, then I'd have whatever number led to those useful outcomes. If I were pressed on this (pointless) question, it'd be a clear sign that this company is not a good fit for me. There are so many other, more meaningful questions that could be asked.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ugh. When I did interview training (some years ago, now) we were coached to avoid asking candidates hypothetical questions like this. The rationale being that it just becomes a game for the interviewee to guess what would make a good answer for the interviewer, and thus ultimately of little value as a means of fairly and accurately determining whether the candidate is a good fit for the job.
My reaction was similar to yours (even the "ugh" 😊). In addition to your point, I'd add that it's a useless question because there are many kinds of meetings with many kinds of people. If anyone thinks about meetings quantitatively instead of qualitatively, they're either fresh out of college (in which case I wouldn't criticize them), or they're focusing on meaningless data, which is a bad sign.
If someone asked me this question in an interview, I'd politely point out that I don't think in terms of number of meetings but rather in terms of outcomes. If the meetings led to useful outcomes for the team/company/customer, then I'd have whatever number led to those useful outcomes. If I were pressed on this (pointless) question, it'd be a clear sign that this company is not a good fit for me. There are so many other, more meaningful questions that could be asked.