4 ms·

This is blatantly false. Source: I work for Google. Our daily schedule is packed with meetings and we try to be as on time as possible, interviews (which are

by Morgawr 10y ago

This is blatantly false. Source: I work for Google. Our daily schedule is packed with meetings and we try to be as on time as possible, interviews (which are something that everybody should be doing) work exactly the same, we don't try to screw people over with bad timing just to "test" them. Sometimes it happens that people miss interviews and somebody else has to show up, this is unfortunately a problem and it shouldn't happen but sometimes it does (accidents and unforeseen things happen). It's not done on purpose.

civilian 10y ago
I remember reading an article that this is how they interview for product managers? Not for engineers, but product managers are people who maybe need to deal with more craziness.
- Morgawr 10y ago
  I admit I am not familiar with the interviewing process for the non-engineering sides of the org, but I'd still find this very unlikely and weird. We are very very strict in our meeting and timing policies as our meeting rooms are usually packed with people all the time so we really need to be in and out at the given time. It's counter-intuitive that somebody would delay a meeting on purpose...
- jpatokal 10y ago
  I interviewed for product manager at Google. It was tough, but no craziness involved: flew in, had a day of interviews, flew back.
wpietri 10y ago
I know you don't set up the system, so I'm not blaming you here. But this is the problem: > Our daily schedule is packed with meetings and we try to be as on time as possible If Google's goal were to respect the candidate's time, interviewers wouldn't have daily schedules packed with meetings. The less slack in a system, the worse the failures are. That employees try to be "as on time as possible" is a sign that everybody understands the scheduling is unrealistic. This isn't unusual, by the way. Most hiring processes don't optimize for candidate experience. Or even for good hiring decisions. Indeed, if you take a POSIWID view of typical hiring processes, the point is to make interviewers feel powerful and selecting for people people willing to put up with inefficiency and suspicious power dynamics.

by Morgawr 10y ago

civilian 10y ago

I remember reading an article that this is how they interview for product managers? Not for engineers, but product managers are people who maybe need to deal with more craziness.

Morgawr 10y ago
I admit I am not familiar with the interviewing process for the non-engineering sides of the org, but I'd still find this very unlikely and weird. We are very very strict in our meeting and timing policies as our meeting rooms are usually packed with people all the time so we really need to be in and out at the given time. It's counter-intuitive that somebody would delay a meeting on purpose...
jpatokal 10y ago
I interviewed for product manager at Google. It was tough, but no craziness involved: flew in, had a day of interviews, flew back.

wpietri 10y ago

I know you don't set up the system, so I'm not blaming you here. But this is the problem: > Our daily schedule is packed with meetings and we try to be as on time as possible If Google's goal were to respect the candidate's time, interviewers wouldn't have daily schedules packed with meetings. The less slack in a system, the worse the failures are. That employees try to be "as on time as possible" is a sign that everybody understands the scheduling is unrealistic. This isn't unusual, by the way. Most hiring processes don't optimize for candidate experience. Or even for good hiring decisions. Indeed, if you take a POSIWID view of typical hiring processes, the point is to make interviewers feel powerful and selecting for people people willing to put up with inefficiency and suspicious power dynamics.