Yes, Google’s founders used a curious interview technique: they asked candidates to explain something complex in a way that revealed their thought process, often starting with a seemingly simple or odd question. This approach, popularized in the company’s early years, was designed to test problem-solving ability, creativity, and cultural fit rather than just technical knowledge.
The Origins of the Technique
In the late 1990s and early 2000s, Google was growing rapidly and needed to hire engineers who could think on their feet. Larry Page and Sergey Brin, along with early employees, developed an interview style that broke from traditional corporate recruiting. Instead of relying solely on resumes and standard behavioral questions, they used puzzles and open-ended problems. The goal was to see how a candidate approached an unfamiliar challenge, not whether they already knew the answer.
One famous example involves asking candidates to explain a complex concept (like how a search engine works) to a child, or to estimate the number of gas stations in the United States. These questions had no single correct answer; the interviewer was watching the candidate’s reasoning, assumptions, and communication skills.
How the Technique Worked
The technique typically followed a pattern:
- Start with an open-ended question that sounds deceptively simple (e.g., “How many golf balls fit in a school bus?”).
- Encourage the candidate to think aloud, explaining each step of their reasoning.
- Probe with follow-up questions to test flexibility and depth (e.g., “What if the bus is empty? What if the balls are deflated?”).
- Observe how the candidate handles uncertainty—do they ask clarifying questions, make reasonable assumptions, or panic?
The interviewer was not looking for a correct number but for a logical, structured approach. A candidate who said “I don’t know” and stopped was usually rejected, while one who broke the problem into parts and estimated each one was more likely to pass.
Why It Was Effective (and Controversial)
This approach helped Google identify candidates who were:
- Curious and creative—willing to explore unconventional solutions.
- Comfortable with ambiguity—able to work without clear instructions.
- Strong communicators—could explain complex ideas simply.
However, it also drew criticism. Many argued that puzzle questions were poor predictors of job performance and could disadvantage candidates from non-traditional backgrounds who hadn’t practiced them. By the mid-2010s, Google’s own internal studies (led by their people analytics team) found that these “brainteasers” had little correlation with success at the company. As a result, Google phased them out in favor of structured behavioral and situational interviews.
Common Problems with the Technique
Several issues emerged in practice:
- False negatives—highly qualified engineers who were introverted or nervous might fail a puzzle interview despite being excellent coders.
- Cultural bias—candidates from certain educational systems (e.g., those that emphasize rote learning) were less familiar with this style.
- Lack of standardization—different interviewers might score the same answer differently, leading to inconsistent hiring decisions.
These problems contributed to the technique’s eventual decline.
Comparisons to Other Interview Methods
Google’s old technique is often compared to:
- Traditional technical interviews—which focus on coding challenges and algorithms, testing hard skills directly.
- Behavioral interviews—which ask about past experiences (e.g., “Tell me about a time you failed”) to predict future behavior.
- Work-sample tests—which simulate actual job tasks (e.g., writing a piece of code) and are considered the most valid predictor of performance.
Google’s current process combines structured interviews with work-sample tests and behavioral questions, reflecting lessons learned from the puzzle era.
How to Choose Your Own Interview Approach
If you’re designing an interview process, consider:
- What skills are truly needed? For a role requiring creative problem-solving, a well-designed case study may be more relevant than a brainteaser.
- Fairness—ensure all candidates have equal opportunity to prepare and succeed.
- Validation—track whether interview scores correlate with on-the-job performance.
Google’s experience shows that even the most innovative techniques must be tested and refined.
Frequently Asked Questions
Why did Google stop using brainteasers?
Internal research found that brainteasers had little predictive validity for job performance. The company’s people analytics team, led by Laszlo Bock, reported that these questions were a waste of time and could unfairly penalize capable candidates.
What replaced the puzzle questions?
Google moved to structured interviews with consistent questions, behavioral interviews, and work-sample tests like coding challenges. They also emphasize “cognitive ability” questions that measure learning agility rather than trivia.
Are brainteasers still used at any company?
Some startups and tech firms still use them, but they are increasingly rare. Most modern hiring experts recommend avoiding them in favor of more reliable methods.
How can I prepare for a puzzle-style interview?
Practice breaking down problems into smaller parts, making reasonable assumptions, and verbalizing your thinking. Books like “Cracking the Coding Interview” include such practice problems.
Did the founders personally conduct these interviews?
In the early days, Larry Page and Sergey Brin were involved in interviewing early employees, and their influence shaped the company’s hiring philosophy. However, as Google grew, professional recruiters and engineers took over.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- How to Choose an Amplifier for Magico A3 Speakers
- How to Ban a Player from Your FiveM Server
- Pokemon Go Friend Codes: How to Add & Use Them33.33 XP/day
- Google Algorithm Change: Original Reporting Boost
- Create Folder for Selected Item on Mac: Full Guide
- Data Center Location Questions for AI Workloads