Moishe Lettvin - What I Learned Doing 250 Interviews at Google
Channel:Etsy Eng (Etsy Engineering) · Length:1:00:24 · Published:2014-05-21 · Views:713206
Summary
Moishe Lettvin, a former Google engineer, shares lessons from 250 interviews and his time on the hiring committee. He tells how the committee given anonymized packets, including its own, would hire almost none of them.
Why HN recommends it
Linked often in hiring-process threads for the anecdote about Google's committee refusing to hire itself, as evidence interviews are noisy.
The one I found very enlightening is from Moishe Lettvin given at Etsy — HN, 2016
Software practice, open source & careers · Management, leadership & organizations
Subtitles (excerpt)
hello I'm Oishi I'm here to talk about 25 things or more or less that I learned in more or less 250 interviews that I conducted at Google so let me just introduce myself real quick I've been at Etsy for about four months now before that it was at Google for about seven years before that it was at Microsoft and then some random startup and then Microsoft again and then a small time and billing company in Massachusetts I actually occurred to me when I was writing up 25 things I've learned about interviewing that I've actually been in the South for industry for 25 years now which blows my mind and makes me feel kind of old so in terms of my experience interviewing which is what I'm going to talk about while I was at Google I did about 250 interviews as the interviewer I was on hiring committee so a little bit of background about how Google's hiring process works if you don't know basically there's there's a slate of interviewers just like here at Etsy like four or five on-site interviewers each interviewer writes up written feedback that gets collated into a packet which is sent to a committee of people who review the packet and make a hire no hire decision the people in that committee
On Hacker News
As someone who interviews and hires engineers I'm not even remotely convinced live code exercises lead to better hiring than any other signal such as a CS degree. I remember when the the coding horror fizz buzz article came out and honestly things have just gotten worse since then. I always like to link the talk where the speaker mentions google hiring committee refused to hire themselves [0]. I … — gregors, 2024-07
I think this is half the problem when people interview at FAANGs -- they think it's like preparing for olympics and you truly have to be in the top 1%. It's really not. There's thousands and thousands of engineers, from mediocre to truly great. With the right preparation, a lot of it just comes down to getting lucky with who interviews, how they're feeling that day, etc -- luck. You might find th… — iooi, 2021-07
I like this video: [VIDEO] The speaker formerly worked at Google, and around 8:55 in the video relates the story of being on a hiring committee that was known for being tough on candidates. And a recruiter once forwarded a set of interview packets to them, and they voted "no hire" on all of them. The recruiter then revealed to the committee that they'd been given their own packets, slightly anony… — ubernostrum, 2018-09
Like with any BigCo, there are always bad apples (recruiters) and things slip through cracks. But compared to other similar sized companies, Google is quite focused on improving their interview processes. You can find lots of resources online from Google employees explaining it. The one I found very enlightening is from Moishe Lettvin given at Etsy: [VIDEO] My own personal experience couple of ye… — umbs, 2016-10
I've been doing this awhile, and I've seen hiring work really well without the LeetCode grilling. And I've almost always seen the LeetCode grilling be administered by someone who doesn't know what they're doing (and often also tainted with ego, despite the strange claim of some that a LeetCode grilling is objective). That said, if you're sourcing random people, good luck, it's a flood of LeetCode… — neilv, 2025-11
Related videos
- ElixirConf 2023 - José Valim - The foundations of the Elixir type system · ElixirConf · 1:11:41
- Rich Harris - Rethinking reactivity · You Gotta Love Frontend · 36:45
- Stroads are Ugly, Expensive, and Dangerous (and they're everywhere) [ST05] · Not Just Bikes · 18:13
- The Soul of Erlang and Elixir • Sasa Juric • GOTO 2019 · GOTO Conferences · 42:02
- British Airways Boeing 747-400 in D-Check · JDProductions INC. · 58:59
- Try to Rule Fairly and You'll Be Overthrown · CGP Grey · 18:13
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor The Future of Programming · Joey Reid · 32:55
- Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems" · O'Reilly · 19:09
- Ed Catmull, Pixar: Keep Your Crises Small · Stanford Graduate School of Business · 54:11
- "Uncle" Bob Martin - "The Future of Programming" · Paul Stringer's Mobile Tech · 1:18:21
- Tim Ewald - Clojure: Programming with Hand Tools · ClojureTV · 58:39
- RSA ANIMATE: Drive: The surprising truth about what motivates us · Royal Society of Arts · 10:48
- The Only Unbreakable Law · Molly Rocket · 53:25
- Using Python to Code by Voice · Next Day Video · 28:17
- Transforming Code into Beautiful, Idiomatic Python · Next Day Video · 48:51