Published in


My Google Coding Interview Question

At Google I’ve done over 200 interviews and evaluated over 50 hiring packets. One thing is clear, and that interviewing is hard. Signals are all over the place. Both the interviewer and interviewee have less than one hour to do their best. Sometimes, for any number of reasons, we get false or inaccurate signals. This is the nature of human beings.




Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

DeepCode’s Top Findings #8: The ZIP Slip

Enabling Autonomous Software Teams

Air Fried Steak’s Logo

DecimalChain Developers Report

Laravel Eloquent Query | Laravel Multiple Where Condition Example

Virtual Machine (VM) vs Container

DSC Medipol Global Summit

Designing High Availability Architecture with AWS S3 & CloudFront Using AWS CLI

Basic Python Syntax — Introduction to Syntax and Operators

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
William Wen

William Wen

25 years in tech | 13 years @ Google | 9+ years Tesla Investor | |

More from Medium

My Google L4 interview experience

The Most Important Thing I Did to Become a Senior Developer

My Boss Fired a Programmer Due to 3 Weird Reasons

You Are the Average of the Five Developers You Spend the Most Time Creating Software With