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

Location

Coordinates unknown. Vibes: international.

Skills

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.

Case studies

The newsletter is the front door, but the evidence behind it is a company and two O'Reilly books. Charity Majors argues for observability, then points at the product she co-founded to build it and the books that spell out how.

Case StudyadvancedSecond edition out in 2026

Observability Engineering (O'Reilly, 2nd edition)

OpenTelemetrySLOsDistributed tracingInstrumentation

An O'Reilly book on building and running software using observability, co-written with Liz Fong-Jones and George Miranda. The second edition was almost entirely rewritten, adds instrumentation guidance for AI agents and nondeterministic workloads, and adds a new section on observability governance for CTOs, VPs and staff+ engineers.

Rewriting a book around what changed (OpenTelemetry adoption, telemetry cost, AI-written code) shows someone who revises their own framework when the ground moves, and can explain SLOs to both engineers and executives.

  • 27 net-new chapters in the second edition

  • New governance section aimed at CTOs, VPs, directors and staff+ engineers

  • Covers instrumenting nondeterministic AI workloads in production

Case StudyintermediatePublished October 2017

Database Reliability Engineering

Site reliability engineeringDatabasesReplicationInfrastructure as codeRelease management

A 294-page O'Reilly book, co-written with Laine Campbell, applying site reliability engineering to database architecture and operations. It is aimed at developers, sysadmins and junior to mid-level DBAs, and moves from service-level and risk management through infrastructure engineering to storage, indexing and replication.

It turns the DBA role into an engineering discipline with SLOs, risk budgets and automation. That is the operating model teams now expect from anyone who owns stateful infrastructure.

  • Co-authored with Laine Campbell; 294 pages

  • Service-level and risk management applied to datastores

  • Covers replication, indexing and data-driven architectures

Projects

SaaS ProductadvancedFounded about 10 years ago (per Honeycomb's About page); ongoing

Honeycomb

ObservabilityDistributed tracingOpenTelemetrySLOsColumnar storage

An observability platform built, in Honeycomb's words, by 'an ops engineer and a developer who had the same problem and couldn't agree on whose fault it was.' It gives dev, ops, SRE and now AI agents one shared view of what code is doing in production.

It shows the difference between writing about production and running it. The operational ideas in her essays had to hold up as a commercial product that engineering teams pay for.

  • Founded by an ops engineer and a developer; she is CTO

  • Built for dev, ops, SRE and AI agents to share one view of production

  • Contributed a tail-sampling processor to the OpenTelemetry Collector

Ready to build your portfolio?

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

DevOps Engineer Roadmap