Comment by sbaidon94
Spent 5 years there, I definitely know the experience varies wildly between teams and orgs so take all of this as just my personal opinion.
I was part of the Amazon Luna team and Devices org.
Yes oncall is super rough, yes people are very demanding. Internal documentation sucked.
But overall I had a really great experience, there was a strong sense of “ownership” on the stuff we built due to how teams are expected to be run. We owned all the infrastructure ourselves, costs, QA, deployments, technical decisions, you name it.
As long as you could justify the customer value managers and execs were pretty open to experimentation and trying out new approaches.
I also was lucky enough to have a very technical oriented manager, he had a great long term vision of where he thought we needed to go and the technical chops to guide us there.
The approach is definitely not for everybody nor the only one that can work in a company like Amazon but I think it did fit with my own values (if that makes any sense).
Some other random things I miss not in any particular order:
- Strong document oriented culture, it is expected of you to dive deep into certain areas while at the same time communicating them effectively
- smithy
- While CDK started out clunky pretty amazing high level constructs were available later.
- Full access to AWS, pretty easy for you to experiment and prototype.
- Both internal FF tooling and the AWS options were quite good.
> But overall I had a really great experience, there was a strong sense of “ownership” on the stuff we built due to how teams are expected to be run. We owned all the infrastructure ourselves, costs, QA, deployments, technical decisions, you name it.
This is one of those terms that drive me nuts, because actual ownership implies revenue/profit sharing, decision making, and property rights.
Sounds like you're getting all the responsibilities of ownership, but none of the tangible benefits.