DevOps Engineer

Charity Majors Portfolio

charity.wtf is her Substack, with over 6,000 subscribers, where she writes about observability, on-call culture, and engineering management, drawing directly on running production infrastructure and co-founding Honeycomb.io.

ObservabilitySREIncident ResponseEngineering Leadership

What makes it work

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

1

Opinions tied to a company she actually runs

Every observability argument on the blog is backed by Honeycomb, the company she co-founded to build the tooling she's advocating for. Readers can check the claim against a real product instead of taking a consultant's word for it.

2

Writing that names failure modes plainly

Her posts on on-call and incident response don't soften the reality of production ownership — they describe what actually goes wrong and why most teams' processes make it worse. That's more useful to a hiring manager evaluating SRE judgment than polished success stories.

3

A newsletter format instead of a portfolio site

Choosing Substack over a designed personal site keeps the focus entirely on writing cadence and subscriber relationship — appropriate for a role where the deliverable is judgment and communication, not visual craft.

What DevOps Engineers can take from this

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

  • If your expertise is operational judgment, a regular newsletter of real opinions beats a static "about me" page.

  • Back up your advice with a product or system you actually run — it's the difference between a claim and a demonstrated result.

  • Write about what goes wrong in production, specifically. Vague reliability platitudes convince no one who has been on call.

Ready to build your portfolio?

Follow the DevOps Engineer roadmap — skills, projects, and timeline to get hired.

DevOps Engineer Roadmap