Liz Rice Portfolio
lizrice.com centers on her two technical books — "Container Security" and "Learning eBPF" — her role as Chief Open Source Officer at Isovalent (part of Cisco) and co-creator of the Cilium networking project, and a body of live-coding conference talks explaining how containers work at the kernel level.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Books as the primary portfolio artifact, not slide decks
A published, technically-reviewed book on container security is a much higher bar than a blog series — it has to be complete, correct, and coherent end to end.
Live-coding as the talk format
Building a container from scratch in a few lines of Go, live, on stage, is a riskier and more convincing demonstration than a slide walkthrough — if she's wrong, the terminal shows it immediately.
Governance work listed alongside technical work
CNCF Governing Board membership and a former Technical Oversight Committee chair role sit next to the coding and writing credentials, showing a career spanning both engineering and open-source governance.
What DevOps Engineers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
A completed book or long-form technical publication is one of the strongest portfolio artifacts available.
If you speak at conferences, consider live-coding a small piece instead of only using slides.
Include governance or maintainer roles (a foundation board) alongside technical work — it shows a complementary kind of seniority.
More DevOps Engineer portfolios
Ready to build your portfolio?
Follow the DevOps Engineer roadmap — skills, projects, and timeline to get hired.