Corey Quinn Portfolio
Publishes the "Last Week in AWS" newsletter and blog as self-titled "Chief Cloud Economist," dissecting AWS service announcements, pricing changes, and architecture tradeoffs with a consistent focus on cloud cost optimization.
What makes it work
A breakdown of the choices that make this portfolio stand out.
A clearly stated, narrow specialty
Rather than a generic "cloud consultant" title, the self-given title "Chief Cloud Economist" stakes out one specific lens — cost — and every piece of content reinforces it. Visitors know exactly what problem he solves within one sentence.
Long-running, dated newsletter archive
Years of consistent output on the same beat builds a searchable body of analysis that a one-off blog post never could — it demonstrates sustained expertise, not a single take.
Commentary that names real AWS tradeoffs by name
Analysis references specific services, pricing tiers, and announcements rather than speaking about "the cloud" in the abstract, which is what makes the writing useful to working architects.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Pick one narrow specialty inside a broad field and let your title say it explicitly — a specific title tells a hiring manager more in three words than a generic one does in a paragraph.
Publish on a fixed cadence for years, not a burst of posts followed by silence — the archive itself becomes evidence of expertise.
Name the specific services, prices, and tradeoffs you're analyzing instead of writing generically about "the cloud" — specificity is what makes technical writing useful to other practitioners.
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.