Great Tools, Slow Promotions
Great Tools, Slow Promotions
- Opportunity to work on meaningful products with global impact.
- The company really cares about employees being happy, growing, and performing.
- You can move around to different teams, roles, and offices relatively easily to find the right fit.
- Tons of employee development programs and perks.
- Generous compensation based on performance.
- Very smart, mostly well-intentioned coworkers.
- Amazing developer tooling. I especially liked the internal code review tool; I haven't seen anything as powerful outside.
- Google will be around for a long time and continue to be a great place to work and build a career, offering stability depending on your preference.
- Impact and growth opportunities depend heavily on your team.
- When you first join, you are typically assigned to a team, so you might not be working on something you're super excited about. (You can transfer after 18 months.)
- Your equity is (probably) not going to 10x.
- The tech stack is different than the rest of the industry, though with Google Cloud Platform, they are trying to change that.
- The SF to Mountain View commute is soul-sucking.
- Not allowed to work on side projects that make money.
- Depending on the team, people are not as hungry, young, or motivated as what you might find at startups.
- Promotions are determined outside your team. It's the best system I could imagine, but it's also time-consuming and slow.
Was this helpful?
Google Interview Questions
Google Interview Experiences
Software Engineer
I applied online, and a recruiter reached out to me. The first round was a coding interview, featuring a LeetCode Hard difficulty problem involving trees. I was not able to solve it, although the interviewer was helpful. I received my rejection the s
Software Engineer
The first stage was the OA, which consisted of two questions to be answered within 90 minutes. I did not pass all the test cases on the second question before time expired, but I was still offered a technical phone interview. The second stage was th
Software Engineer
Five in-person interviews were conducted at Google headquarters, with a single break for lunch. They covered travel to and from Google and followed up promptly afterward. Subject-matter interviews went well but needed more preparation on general CS
Software Engineer
Mountain View, California, United StatesJanuary 9, 2025I applied online, and a recruiter reached out to me. The first round was a coding interview, featuring a LeetCode Hard difficulty problem involving trees. I was not able to solve it, although the interviewer was helpful. I received my rejection the s
Software Engineer
Mountain View, California, United StatesJanuary 1, 2018The first stage was the OA, which consisted of two questions to be answered within 90 minutes. I did not pass all the test cases on the second question before time expired, but I was still offered a technical phone interview. The second stage was th
Software Engineer
Mountain View, California, United StatesJune 1, 2018Five in-person interviews were conducted at Google headquarters, with a single break for lunch. They covered travel to and from Google and followed up promptly afterward. Subject-matter interviews went well but needed more preparation on general CS
