Cloud Architect

Kelsey Hightower Portfolio

Former Google Cloud Distinguished Engineer whose "kubernetes-the-hard-way" repository (over 50,000 GitHub stars) teaches Kubernetes cluster architecture by building one manually, without scripts or managed abstractions, to force real understanding of the underlying infrastructure.

KubernetesGCPInfrastructure as CodeOpen Source

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Teaching architecture by building it manually, without shortcuts

"kubernetes-the-hard-way" deliberately strips out managed tooling so the reader has to provision every component of a cluster by hand — the constraint itself is the teaching method.

2

A GitHub profile as the primary portfolio, not a personal website

The work lives where it is used — as runnable, forkable repositories with real star and fork counts — rather than as descriptions of work on a separate marketing page.

3

Restraint in repository scope

Each project solves one narrow infrastructure problem (cluster bootstrapping, config templating, cert management) instead of bundling many concerns into one framework, which keeps each one legible on its own.

What Cloud Architects can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • If your best portfolio evidence is code, let your GitHub profile be the portfolio instead of duplicating it on a separate site.

  • Teach a hard concept by stripping away the tooling that normally hides it — walking through the manual process is often more instructive than the abstraction built on top of it.

  • Keep each open-source project scoped to one problem; a focused, well-used tool is a stronger credential than a sprawling framework nobody adopts.

Ready to build your portfolio?

Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.

Cloud Architect Roadmap