100 Things I’ve Learned as a Software Engineer at Google

It’s amazing to look back over the past seven years. When I first stared this blog, I was a CS student at UT. 99 blog posts later, I’m a software engineer and tech lead at Google. I don’t have everything figured out, but I love showing people earlier in their career how to advance even farther.

Since this is my 100th blog post, here are 100 things I’ve learned while working as a software engineer at Google.

Doing Interviews

  1. No one has the exact set of skills listed in the job posting. The hiring manager is forced to go with the best candidate that shows up.
  2. The interviewer wants you to do well.
  3. The worst interviews are when the candidate struggles hard and can’t make progress.
  4. The best interviews are when the candidate performs exceptionally well.
  5. The hardest interviews are when the candidate is a borderline case, and you lean towards rejecting them.
  6. Structured interviews are necessary, but not sufficient, to remove bias from the process.
  7. Crafting good interview questions is hard.


  1. Code reviews are magic. I’ve learned so much from my code being reviewed.
  2. Small code changes are better than large ones.
  3. Lines of code written is not a good metric. You might as well judge an airplane by how much it weighs.
  4. Dependency injection is magical. Sometimes it is scary.
  5. Everything takes longer than you expect it to.
  6. If you have two dashboards for the same metric, at least one of them must be wrong. Probably both. You’ll try to deprecate one and end up creating a third dashboard.
  7. Don’t look at a dashboard unless you have to. You’ll likely find a “false positive” and waste time trying to debug it.
  8. Nothing is more permanent than a temporary solution (e.g. legacy code).
  9. Infrastructure teams exist so that they can transform O(n) units of work into O(1).
  10. Get an ergonomic keyboard and mouse to avoid wrist problems later.
  11. Programs function in strange ways. Sometimes they do not function in strange ways.
  12. Testing is more important than most people realize.
  13. At the same time, test flakiness is the bane of your existence.
  14. It’s better to prevent a bug at compile time, than runtime, than presubmit, than postsubmit, than in production.
  15. In system design, there is no right answer. This is completely unlike a unit test, which either passes or fails without ambiguity.
  16. Your job is to solve problems, not to write code.
  17. Sometimes a solution that involves no coding is the best solution.

Working at Google

  1. Everything at Google is medium-hard. Impossible tasks become possible, and trivial tasks become difficult. Want to change the color of a button? Medium hard. Want to launch to 1 billion users? Medium hard.
  2. Your experience at Google will heavily depend on what team you are on.
  3. Google’s systems interact in very weird ways.
  4. I do not envy the people who work on Android. They’re caught in a confusing network of partner teams, OEMs, and legal restrictions.
  5. Google has some of the most amazing software tools in the world.
  6. Google takes user data really seriously. Sometimes I have to wait weeks for access to anonymized logs, with all the personal data redacted. And all I wanted to do is was find common events that lead to application crashes…
  7. (Almost) all code lives in the same repository, known as “google3”. This has to be the largest code base in the world.
  8. The repo also is full of mysterious, unowned, untouchable pieces of code known as “haunted graveyards”.
  9. No one gets promoted for fixing haunted graveyards.
  10. UX is usually underfunded at Google. Meanwhile at Apple, people understand its importance and put their money where their mouth is.
  11. It’s hard to make a good UX design.
  12. iOS teams often have no UX designer, so they have to use Android mocks.
  13. (Almost) everyone at Google is highly competent.
  14. Everything must be measured.
  15. It is difficult to prove the value of your work if it cannot be measured. This discourages people from doing unmeasurable but necessary work.
  16. Most Googlers would like to help you, but their busy completing their OKRs. For the rest the quarter. And next quarter, too.
  17. Sundar Pichai is a complicated man. He seems extremely calm for someone at the helm of one the world’s largest companies.
One of Google’s food trucks.

Google’s Culture

  1. Getting a massage at work is pretty cool. I should probably fix my sitting posture.
  2. You stop being a Noogler when you start complaining about the free food in Google’s cafes.
  3. Google has changed in the past six years. Every year, there’s more bureaucracy.
  4. The quality of food at Google’s cafes has also declined over time.
  5. In my opinion, Google hired too quickly in 2020-2022. There wasn’t enough time for all the new hires to absorb Google’s culture.
  6. Memegen is one of the things that makes Google unique. It’s an internal website where employees post memes. If you post enough funny memes you will be invited into the secret Memeacademy.
  7. Google is slowly losing that magical feeling of Googliness present in its early days.
  8. When you have a company of over 170,000 people, just one idiot can make the rest of the employees look bad. Now HR has to institute new rules.
  9. No one understands everything at Google. Not even Jeff Dean.
  10. Jeff Dean is a genius, but even he makes mistakes (e.g. his conflict with Dr. Timnit Gebru)
  11. Dr. Timnit Gebru and Tanja Gupta did not deserve to be fired.
  12. Alphabet has a union.
  13. Peer bonuses are cool. You can give up to 5 to other employees each quarter to reward them for good work. The recipient gets $150.
  14. The perks really are great.
Google’s new Bay View building.


  1. I used to think that technical skills alone are good enough to advance your career. I was wrong.
  2. Start thinking about promotion early. Ask your manager what you need to do. Then do it.
  3. 1:1s are an opportunity to advance your career. Use them to your advantage.
  4. Every job level is another layer of abstraction.
  5. At L3, you write code with help.
  6. At L4, you write code independently.
  7. At L5, you write design docs.
  8. At L6, you have meetings about design docs.
  9. At L7, you have meetings about meetings.
  10. At Google, you’re promoted based on your leadership, impact, and solving difficult problems. It is difficult to get promoted if your contributions are not measurable.
  11. Most of Google’s product problems can be traced to performance reviews (GRAD) and promo.

Management and Leadership

  1. You don’t have to be a manager to be a leader.
  2. Management is different from leadership. Management is about using resources efficiently. Leadership is about having a vision and followers.
  3. Being a good TL is hard. Being a good manager is also hard.
  4. Before starting a project, make sure all stakeholders are on board.
  5. Sometimes the best way to serve customers/clients/users is to make them do no work it all.
  6. Sometimes projects get canceled. It’s nothing personal.
  7. Managers want to see you succeed.
  8. Managers want to unblock you and move the project along.
  9. If a team looks like a well-oiled machine, it’s only by comparison.
  10. One of my favorite parts of my job is mentoring younger engineers.
  11. Crafting a good plan is hard.
  12. Also, nothing goes exactly according to plan.

Working with Others

  1. Scheduling a meeting is a great way to get someone to respond to your e-mail.
  2. Everyone needs to do their part to account for unconscious bias.
  3. I used to overvalue technical skills and disdain talk about team culture. I was wrong.
  4. You probably care more about your work than they do.
  5. A good program manager drives projects forward, proactively resolves dependencies, and and is a true leader.
  6. A mediocre program manager does little more than update spreadsheets.
  7. People (users, colleagues, stakeholders, etc.) will always complain.
  8. The type of complaint you get can tell you whether you’re doing good job. When your manager says the margins should be 4 pixels instead of 2 pixels, you’re doing great. When they complain that “the page is empty”, you have a serious bug to fix.
  9. Listening is an underutilized skill.
  10. Some people oppose DEI. I can understand not caring about it, but I do not understand actively opposing it.
  11. Antisocial programmers really need to improve their communication skills.
  12. Fortunately, you can Dale Carnegie your way through a lot of situations.
  13. Ask questions even when you feel embarrassed about asking. People are usually happy to explain the stuff they work on.
  14. It is important to give feedback regularly. You have to be humble enough to accept feedback, too.
  15. Googlers value feedback. They really want it.


  1. We might be at or past “peak software”.
  2. Silicon Valley simultaneously understands very much and very little about its users.
  3. There’s a lot of money sloshing around in the world.
  4. Small is beautiful.
  5. Sometimes you have to slow down to go faster.
  6. It’s better to put out an MVP quickly than to delay a perfect launch forever.
  7. It is possible for a tiny group to drive huge changes. The path is often difficult and the chance of success usually low. But it is possible.
This entry was posted in Software and tagged , , , , , , , , , , , . Bookmark the permalink.

2 Responses to 100 Things I’ve Learned as a Software Engineer at Google

  1. Pingback: How to NOT worry about layoffs | Sheldon's Software

  2. Pingback: Get the top rating in your next performance review with this one weird trick | Sheldon's Software

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s