Scale up your impact by working for a company with billions of users, a culture that is focused on the right things, and brilliant coworkers.
Changing a system with billions of users is harder than changing smaller systems. Google today is cautious, deliberative, and process-heavy. Much of what makes an engineer successful at Google today is their ability to navigate the hierarchy, build consensus, and document everything. If you want to crank out code, iterate quickly, or focus on technical tasks, Google is not the place for you.
Be more forthright with employees. A mea culpa is always preferred over corp-speak.
Basic phone screen, On-site interview since I'm local. Blackboard coding, Requirements/analysis brainstorming.
I'm graduating college soon, so I went through the university graduate application process. I submitted my initial application, which contained my resume and transcript. Pretty soon after that, about one to two weeks later, I received an invitation
I received a phone call that included an IQ test and some recursion problems. The interviewer presented a problem and asked me to solve it. I believe I solved it correctly, and my solution was as efficient as possible.
Basic phone screen, On-site interview since I'm local. Blackboard coding, Requirements/analysis brainstorming.
I'm graduating college soon, so I went through the university graduate application process. I submitted my initial application, which contained my resume and transcript. Pretty soon after that, about one to two weeks later, I received an invitation
I received a phone call that included an IQ test and some recursion problems. The interviewer presented a problem and asked me to solve it. I believe I solved it correctly, and my solution was as efficient as possible.