James Hamilton Portfolio
AWS distinguished engineer whose "Perspectives" blog publishes detailed technical writeups on datacenter network design, custom silicon (Graviton), and the infrastructure engineering decisions behind running cloud services at planetary scale.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Hardware-level detail most cloud architects never publish
Writing about custom silicon design and datacenter network topology goes a level below typical "architecture" content, which usually stops at service design — it shows the infrastructure reasoning underneath the services architects actually use.
Historical framing tied to real service milestones
Pieces marking milestones like "EC2's 15-year history" connect specific engineering decisions to a known public timeline, letting readers cross-reference the claims against publicly documented AWS history.
A stated engineering philosophy ("constraint-driven innovation")
Naming the recurring theme across posts gives scattered technical writeups a coherent throughline, turning years of individual posts into a single, identifiable point of view on infrastructure design.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you have visibility into a lower layer of the stack than most people in your field discuss, write about that layer specifically — it differentiates you from generic architecture commentary.
Tie technical writeups to real, checkable milestones or dates so readers can verify the claims against public history.
Name the recurring theme or philosophy behind your work explicitly — it turns a scattered archive into a single, memorable point of view.
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.