Pros: - Food in the office - Work-life balance - Nice tools and environment to work (Notebooks, desks, comfortable offices) - Interesting projects and technologies to work with.

Cons: - Local management is a little bit limited, not that inspiring. - Not specialized skills in local roles. - Moments with a lot of work.

Pros: 1. Strong engineering standards Code quality, design reviews, and testing standards are high. You learn to write maintainable, scalable systems. Good exposure to distributed systems, infra, reliability, and performance. 2. Exposure to large-scale systems GCP operates at massive scale (data centers, networking, storage, ML infra). Even internal tools are built to handle high throughput and reliability. Valuable experience if you want to work on infra-heavy roles later. 3. Internal mobility Google allows internal team transfers after a period. You can move between Cloud, Search, Ads, etc., without re-interviewing externally. Useful if your initial Cloud team isn’t a great fit. 4. Documentation and tooling Internal documentation is generally detailed. Strong internal developer tools, testing frameworks, and monitoring systems. Makes onboarding and maintenance easier than many companies. 5. Stability and benefits Stable job, low risk of sudden layoffs compared to startups. Predictable working hours in most teams. Strong health benefits and leave policies.

Cons: 1. GCP is not Google's core revenue engine. Search and ads dominate company priorities. Cloud sometimes receives less urgency and fewer resources. Strategy can change based on leadership shifts. 2. Product direction can be unclear. Some teams experience shifting goals or reorgs. Projects may be deprioritized or merged without a clear long-term vision. This can reduce a sense of ownership or impact. 3. Slower career progression. Promotions require extensive documentation and peer validation. Performance reviews are conservative. High performers may still wait longer than expected to level up. 4. Limited customer exposure for many roles. Engineers often work far from end users. Product decisions are sometimes top-down. There is less hands-on customer feedback compared to smaller cloud companies. 5. GCP skills are less transferable than AWS. AWS has broader industry adoption. Some GCP-specific tools, such as BigQuery and Spanner, don't map directly to other clouds. This can slightly limit external job mobility compared to AWS-heavy resumes.

Pros: Good Food Good company culture Good projects

Cons: Hiring standards have drastically dropped over the last 1.5 years.