About Build With Her

About Build With Her Magazine

The publication the industry needed. The engineers building the cloud, AI, and platform infrastructure that powers the modern internet are doing some of the most consequential technical work of our time. Build With Her documents it. Specifically, the women doing that work, whose names belong in the record.

Why We Exist

The beats that cover technology almost never go deep enough to find the people doing the underlying work. Build With Her is built on one conviction: the engineering decisions that matter most are made by people whose names aren't in the announcement. We cover those decisions, and the people who made them.

We do not explain what we are documenting. We document it.

Who We Serve

Our readers build and operate production systems at scale. They already know what a container is. We write for engineers who are more interested in why a decision was made than what the decision was.

We also write for the women in this industry who are tired of being covered as a diversity metric. Our subjects are the architects and decision-makers they are.

Our founding principle
"We were never the quiet ones. We were just doing the load bearing work."
From "The Quiet Revolution Rewiring the Cloud" · Issue 01
What We Believe
·

The best technical stories are human stories. Infrastructure decisions are made by people under specific conditions, with incomplete information, and real consequences. We cover the conditions, not just the output.

·

Vulnerability is credibility. A writer who admits what they got wrong earns more trust than one who only reports their successes. We actively commission the harder version.

·

Specificity is the standard. A story about a specific system, a specific failure, a specific number is more valuable than a story about a pattern. We push for the number, the quarter, the latency, the cost.

·

Unresolved questions are honest. Not every story needs a lesson. Some of the most important things that happen in engineering are still being understood by the people they happened to. We publish the uncertainty.

·

Recognition is political. Choosing whose name appears in a byline is a form of documentation. We take that seriously.

What We Cover
Cloud & Infrastructure

Architecture decisions, regional strategy, outage postmortems, and the engineers who keep the backbone running.

Artificial Intelligence

Production AI systems, training runs, deployment war stories, and the people building models in conditions that don't make the paper.

DevOps & SRE

Reliability, on-call culture, deployment pipelines, and the systems that separate "running" from "working."

Cybersecurity

Threat intelligence, incident response, zero trust implementation, and the security engineers who make trust a product feature.

Platform Engineering

Internal developer platforms, toolchains, and the infrastructure teams building the substrate that makes everyone else faster.

Engineering Leadership

Org design, team building, and the unglamorous work of running engineering at scale.

Contribute

We publish the stories the industry is living but not writing.

We accept original technical stories, career journeys, architectural retrospectives, and industry perspectives from women building in the areas we cover. We edit for clarity and voice, not for positioning or brand safety.

Submit a Story
What Makes a Strong Pitch
  • Specificity: A real system, a real tradeoff, a real outcome. Not a framework or a philosophy.
  • Stakes: Why did this matter? What broke, what held, what changed?
  • Expertise: You were there. You built it, broke it, or fixed it. That's the credential.
  • Voice: Technical precision and editorial voice are not in conflict. We want both.