Before you're done you'll have built a lot of pieces of software that do different things that have complex little dependencies on each other.
Now iterate that through many generations of development, and build some other systems that tackle similar problems.
Do that and you'll discover why Google's infrastructure is complex.
As somebody external to Google, it seems to me that this approach largely does not exist at Google (or if it does, it exists only for particular isolated pieces). Is this true? Or rather? What's Google's method for containing, directing and handling this complexity if it's not a traditional EA thinking process?
I don't think I'm supposed to answer it.
However Google's answer would be part of the, "nobody would believe me" piece of neilk's top-rated comment.
What do you mean the company is complex?
It's not clear to me why solving difficult problems merits organizational or operational complexity.