Amazon's internal tooling has everything described here. I can't say if it's better or worse than Google, but every team uses the same internal tooling for building and testing, code reviews, deployment, issue tracking etc. All code is also searchable in one place. The tooling is generally quite good too IMO.
Used both. Amazon is worse than google but only by a bit and where they’re better they’re much better. Blaze>Brazil, but pipelines has no real comparison at G. Metric Portal/Carnaval also come to mind as having no real competition. Meanwhile AWS/CloudFormation or Apollo et al are way more annoying to work with than the much more strict and uniform G alternatives. Anything data related (company wide data query tools, etc like Plx) is something that Amazon just doesn’t have.
Amazons approach is to let each team use their own combo of tools, all centered around the Pipelines workflow, while G has one set of tools and everyone uses it the same way (comparatively).
It's changing with the push to Peru and AWS native pipelines. I left last year, but I was very excited to see Peru launch. Oh, and also for LPT to be replaced by CDK.
Overall I'd say they are above industry average, but quality is all over the place. Some of the tools are old and carry a lot of baggage. Migrations are incredibly hard and there seems to be an underinvestment in modernization and developer experience.
