Mitchell Hashimoto Portfolio
mitchellh.com documents his path from building the initial engineering behind Vagrant, Packer, Consul, Terraform, Vault, Nomad, and Waypoint at HashiCorp to his current open-source terminal emulator, Ghostty, with a dedicated Writing section explaining the technical decisions behind each.
What makes it work
A breakdown of the choices that make this portfolio stand out.
A portfolio built entirely from tools other engineers depend on daily
Terraform and Vagrant aren't side projects — they are foundational infrastructure-as-code tools running in production at a huge share of companies with a DevOps practice. Listing them plainly is enough; the tools' own adoption does the persuading.
Moving to a new, unrelated project (Ghostty) after leaving HashiCorp
Rather than resting on the Terraform/Vagrant legacy, the site foregrounds a brand-new systems project. That signals ongoing hands-on engineering rather than a founder coasting on past credit.
A Writing section that explains engineering tradeoffs, not just announcements
The essays go into why a design decision was made, not just that a feature shipped — for infrastructure work, that reasoning is far more useful than a changelog.
What DevOps Engineers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Let widely-adopted tools speak for themselves — you don't need marketing language when usage numbers make the case.
Keep building something new and technical even after a big past success; a portfolio frozen at your last major project reads as stalled.
When you write about a project, explain the tradeoff you chose and why, not just what shipped.
More DevOps Engineer portfolios
Ready to build your portfolio?
Follow the DevOps Engineer roadmap — skills, projects, and timeline to get hired.