Werner Vogels Portfolio
Amazon CTO who has run the "All Things Distributed" blog since 2006, publishing detailed technical breakdowns of how AWS services like Lambda and S3 are architected internally, alongside broader distributed-systems design principles.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Nearly two decades of continuous publication under one identity
Running the same blog since 2006 under a real name and title gives the archive a rare quality: you can trace how his thinking on distributed systems evolved alongside the infrastructure he was building.
Internal engineering writeups made public
Posts on "the invisible engineering behind Lambda's network" translate what would normally stay an internal design doc into a public technical narrative, which is a different and harder skill than announcing a feature.
Architecture principles stated as durable rules, not trend commentary
The writing favors general distributed-systems principles over reacting to industry news, which is why older posts remain useful years after the specific service they describe has changed.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you have access to how a system was actually built, write about the engineering decisions behind it, not just the feature announcement — that is the harder and more valuable piece to produce.
Sustain one blog under one identity for years rather than starting over on a new platform — continuity is itself part of the credibility.
State the general principle behind a specific design choice so the writing stays useful after the specific technology it describes has moved on.
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.