Programmer, Founder, Author, Consultant, Speaker
Focus on Tech Hiring & Interviews
PALO ALTO, CA
gayle at gayle.com
Founder
I'm the founder / CEO of CareerCup, which is a company that does lots of things around tech interviews. This includes books, consulting, a website/forum, videos, speaking, and writing.
Author
I'm the author of Cracking the Coding Interview, Cracking the PM Interview (Product Manager) and Cracking the Tech Career. They've been translated to a bunch of other languages too.
Programmer
Deep tech background. I have a BSE/MSE in Computer Science and I've worked for Google, Microsoft, and Apple as a software engineer.
Still code most days.
Consultant
Speaker
Other Stuff
I do some other stuff too, like guest writing for various publications. I play around with some random side projects for fun. I mentor and advise some people and groups. A little bit of this, a little bit of that.
Featured Blog Posts
If you want an A+ career in technology, you should move to the San Francisco Bay Area. The same argument can probably be made of finance and New York. It’s not that you can’t do it in another city, but your odds are just much better in your industry’s hub. So if you want an A+ career and your industry has a clear hub, go there.
The best programming interview book just got better.
Cracking the Coding Interview: The Sixth Edition -- now with 70% more content.
This is a huge expansion. You know that thing that many professors do, where they create a new "edition" that's not substantially different but forces you to buy a new version? I don't believe in doing that. This is actually a huge change (as was the 4th->5th edition).
Cracking the Tech Career is the job seeker's guide to landing a coveted position at one of the top tech firms. A follow-up to The Google Resume, this book provides new information on what these companies want, and how to show them you have what it takes to succeed in the role. Early planners will learn what to study, and established professionals will discover how to make their skillset and experience set them apart from the crowd. Author Gayle Laakmann McDowell worked in engineering at Google, and interviewed over 120 candidates as a member of the hiring committee – in this book, she shares her perspectives on what works and what doesn't, what makes you desirable, and what gets your resume round-filed.
I'll get to the fifteen pieces of advice. But first, let me explain what awesome careers look like.
They don't look like nice linear graphs, where you're moving up a little bit each month. (Heck, even so-so careers don't look like that. You don't move up every month. You get a bit better at your career every month, but you move up in big steps.)
After coaching hundreds of people through coding, behavioral, and product manager interviews, I’ve distilled some of my core advice into some handy prep sheets.
Study these sheets before your interview. Really understand them. Email me questions if you have any.
As you prepare for interviews, use these sheets. Walk through your next coding problem closely following the procedure below. It’ll help you — I promise.
Getting acquired by a big tech company is a dream for many start-ups. That dream comes with caveats. The acquiring firm may love your product but they still want to assess the skill of your technical team. As a result, they will often interview them just as they would “normal” candidates applying to software engineering and PM roles. For the last year, I've been semi-secretly offering a new service -- what I call "acquisition consulting". People found out about me from word of mouth mostly, and word spread. Now that I've got quite a few successes behind me, it's time to announce publicly what I've been doing.
There’s a trend among start-ups (and some larger companies) that worries me: giving candidates “homework” assignments. Homework assignments lead to candidate abuse. Knock it off (or at least be reasonable). I’ve seen many friends and clients go through this. As a pre-screening round before an onsite interview, a company gives them a “homework” assignment.
Another day, another overly-hyped article on Google’s “crazy” interview questions. This one though gives hope to aspiring Googlers; Google has finally seen the light and realized that brainteasers aren’t useful! Not exactly.
Nothing has changed.
Although I have, quite literally, made a career in the technical interviewing space, I have mixed feelings on them. They offer a lot of value and most people's issues with them ("trick questions!" "no relationship to real world coding!" "in the real world you'd just look up stuff like this!") are easily refuted. However, they're far from a perfect science. On Dice.com, I discuss why technical interviews work, and why they don't. Click to read more.
In an ideal world, I’d respond to all the questions I get from people asking for advice. I like helping people; this is why I do what I do!
In the real, time-limited world, I can only respond to about 25% of the questions I get from people. If your goal is to get a response from me, then you’re shooting to “outperform” 75% of people. Here’s how you can maximize your odds of getting a response from me and other experts.
You know those creative resumes. The ones with pretty graphics, splashy designs, and beautiful layouts. Often they adapt the design of Facebook or Google and make it into their resume. Journalists lovewriting articles about these "amazingly cool resumes." There are even companies you can buy these resumes from (ick!). But do employers love them? Not so much.

FizzBuzz might be a "classic" coding question, but it doesn't make it a good one.