Noogler 100: So you accepted Google's offer; what now?
Open resources that could help a not-yet-onboard Noogler getting an advanced start at Google.
A Noogler hat.
Congratulations on accepting the job offer from Google! You've got a few weeks (or months) of time before actually starting to work at Google, and you feel like to get prepared in advance. What can you do?
This list is assembled by Mingyang Li to help you familiarize yourself with Google's tech stacks and environments. Disclaimer:
- This is NOT an official Google product/article. Always refer to your true Noogler onboarding trainings for accuracy.
- Everything listed are public information. In other words, I have not leaked sensitive or confidential information.
Now the actual content.
- At Google, all source code need to be peer-reviewed. How to prepare for a smooth review, and how to actually give out reviews? This official guide can be handy.
- I wish the site above could have provided more information about engineering practices at Google. For now, I found this article to be of great help.
- When proposing a new product/feature/etc., Google requires design docs. Here is a design doc template from the Chromium project, and it resembles much of Google's internal requirements for DDs.
- You might have a few personal projects at hand, or you may be anticipating contributing to some GitHub repos after joining Google. If so, you definitely want to consult the open-source contribution guidelines and policies first.
- What are some open-source/non-Google alternatives to each of many Google-internal technologies? This lookup table (that was meant for those who quit Google to survive in the wild) answers just that.
- Google has, by far, developed 3 container-management systems. What are they, and how do they compare? Check out this article.
- What is my level? How long does it usually take for one to level up? Am I paid well at my level? How does level system compare across tech companies? There is a website for that.