News for hackers. Stuff that matters.
Re:How to Crack the Toughest Coding Interviews by DannyBee on Friday October 26, 2012 @04:31PM (#4704136)
Google does not have just one hiring committee, and anyone can be on hiring committees if they want to and one of the committees has a need of new members (IE it's not invite only).

So this is like saying "ex-Python-dev mailing list member".

Re:How to Crack the Toughest Coding Interviews by glaak on Friday October 26, 2012 @05:35PM (#4704377)
Actually, it was invite-only when I was there. But that's sort of besides the point. It's irrelevant whether or not it's an "honor" to be on the hiring committee. The point is that being on the hiring committee does give you some insight as to why people tend to get rejected. Without being on the hiring committee, you really only see why you're rejecting people -- smaller sample size, biased, less diversity of questions, etc. But, for hiring committee members, you see the results of many people's interviews.
Re:How to Crack the Toughest Coding Interviews by DannyBee on Friday October 26, 2012 @05:44PM (#4704410)
I'm on 3 of our hiring committees, and i've been at google for over 6 years. It hasn't been invite only for as long i've been here, AFAIK. Either that, or I was secretly invited!

It is irrelevant whether it's an honor, but as to whether it gives you insight, you are generally right but you did miss an important point:

The vast majority of people who are "members" of a given hiring committee often don't show up every week. A lot, in fact, show up never, but are still members. (for example, they were part of it years ago and nobody removed them, they got asked, said yes, never actually did anything, etc)

So while you are correct that it does give you some insight if you actively participated, simply being a "member" of a hiring committee is a necessary but not sufficient condition to say that you have that insight.

Re:How to Crack the Toughest Coding Interviews by incision on Friday October 26, 2012 @06:03PM (#4704479)
That doesn't seem to be a point missed so much as one that's obvious and generally unnecessary to state fully qualified descriptions of everything in casual conversation.
Re:How to Crack the Toughest Coding Interviews by DannyBee on Friday October 26, 2012 @07:42PM (#4704745)
Except that when you are using it as marketing in a book, there are very important distinctions.

Lies of omission and all that.

Re:How to Crack the Toughest Coding Interviews by glaak on Saturday October 27, 2012 @01:52PM (#4706721)
A lie of omission would apply if you state a selection of true facts and ignore other ones so as to make yourself look better than you are.

In this case, I'm stating that I was a hiring committee member and not saying that I attended regularly, when I in fact did. This is not a lie of omission. At worst, you could accuse me of not offering additional qualifications.

Re:How to Crack the Toughest Coding Interviews by glaak on Friday October 26, 2012 @05:49PM (#4704423)
I was in Seattle / Kirkland, and it was invite only there. I showed up every week (as did the vast majority of the Kirkland HC).

But, yes, I could have been more extensive in my credentials. Unfortunately, "How to Crack the Toughest Coding Interviews by ex-Google engineer, ex-Google hiring committee member who showed up every week, ex-Apple dev, ex-Microsoft dev, author of Cracking the Coding Interview, and author of The Google Resume" was a bit too long :).

Re:How to Crack the Toughest Coding Interviews by DannyBee on Friday October 26, 2012 @05:58PM (#4704462)
Fair :) I'm just used to MTV HC's, where you may have 75 HC members, and 10 active ones.

I expect the "newer" offices (relatively, of course) may not have this issue.