Build interesting software infrastructure in a company that values engineering.
Work with really bright co-workers and build atop an awesome codebase.
Projects in Google can become very big, very fast, as they should. But running very small, experimental projects has become more difficult, as the risk/reward equation has shifted more towards the huge expense of uncertainty, given Google's large revenues.
Management already understands very well how the increasing size has created a much more cautious culture than the early Google. There are experiments like Google-X and others, but there isn't a decentralized Google-X, which is why I am now doing my own X-Google startup.
The standard Google interview process, which started with a recruiter reaching out on LinkedIn, followed by: * Data Structures and Algorithms round * System Design round * Hiring Manager round * Culture Fitment round * Bar Raiser round
Top process. Interviewer knows a lot. Location and time were good. I like to go to interviews late at night after a disco. The process consisted of 7 rounds. Doing the same LeetCode challenge.
Applied online and through the company website. A recruiter/sourcer reached out via email. The recruiter/sourcer was courteous and professional. However, the hiring manager/team had already filled the position with another candidate who was in the
The standard Google interview process, which started with a recruiter reaching out on LinkedIn, followed by: * Data Structures and Algorithms round * System Design round * Hiring Manager round * Culture Fitment round * Bar Raiser round
Top process. Interviewer knows a lot. Location and time were good. I like to go to interviews late at night after a disco. The process consisted of 7 rounds. Doing the same LeetCode challenge.
Applied online and through the company website. A recruiter/sourcer reached out via email. The recruiter/sourcer was courteous and professional. However, the hiring manager/team had already filled the position with another candidate who was in the