What I learned getting acquired by Google
Summary
Shreyans argues that succeeding at Google requires navigating a complex web of shifting goals and process debt by proactively aligning projects with the interests of influential leaders and research teams.
Google's scale mandates custom infrastructure.
The company rarely uses external software, forcing Socratic to abandon its existing codebase and rebuild all ML systems to meet Search standards.
Just about every piece of software and infrastructure used at Google was built at Google
Manual data inspection drives AI.
Despite high-level algorithms, engineers improve Search by performing repetitive, non-scalable tasks like side-by-side spreadsheet comparisons and hand-labeling data.
great AI researchers are willing to manually inspect lots of data
Process debt slows feature releases.
Layers of legal checks, reviews, and document templates accumulate over years, creating a gauntlet that can stall ready features for months.
Layers accumulate over the years until you end up unable to release a new feature
Top-heavy teams cause gridlock.
Combining many veterans and co-founders can hinder unified product development unless there is a clear leader and more doers than thinkers.
Alignment determines project viability.
Success depends on finding VPs or research teams whose charters match your vision; without this, re-orgs or competing team goals can kill projects.
Navigating this mess of interests is half of a PM’s job.
Read the original ↗Save to your Sponge
Summarized with Sponge. Quotes are the author’s own words.