Hey, I'm Lindsay Brunner, a writer, editor, and DevRel-shaped content person in the San Francisco Bay Area.

I’m a content-and-DevRel hybrid who has built a career translating scary-sounding tech into copy that normal humans, and skeptical CXOs, can trust. These days, I freelance with teams that need clearer strategy, sharper technical content, better launch messaging, or a sane way to use AI without turning the whole content operation into beige soup.

I live in the San Francisco Bay Area with my husband Alex, our son Lucas, and four cats (Piper, Sophie, Sunny, and Tucker) who routinely audition for the role of remote-work sabotage specialists. I also maintain an industrial-sized stash of dot grid notebooks “just in case,” and (deeply) rely on my custom agentic AI assistant, GUPPI, to remind me that lunch is not optional and yes, I should take my meds.

If you need someone who can ship fast, make deep tech sound refreshingly human, and slip a dry joke into an enterprise brief without anyone noticing, you’ve found your person.

Lindsay Brunner

Here's the timeline version

  1. Jan 2022-present: Consultant + Advisor at lindsaybrunner.com.
  2. Apr 2025-Jan 2026: Head of Content at Builder.io.
  3. Mar-Aug 2025: Advisor at Braze.
  4. Aug 2023-Jan 2025: Head of Content and Developer Relations at ngrok.
  5. Jan 2022-Jul 2023: Head of Marketing at Architect.io.
  6. Mar 2020-Jan 2022: Director, Content + Advocacy at Split.
  7. Nov 2020-May 2021: Advisor at Architect.io.
  8. Before 2020: Stormpath and Okta developer content programs.

A freelance practice for technical content, developer marketing, and AI-era editorial systems.

  • Helping teams turn ideas into content people actually read and use.
  • Helping companies explain complex products without flattening the interesting parts.
  • Working at the intersection of developer tools, AI, DevRel, and content strategy.

Went deep on AI, content strategy, and the new shape of technical storytelling.

  • Led content for an AI-native developer product company.
  • Worked close to product, engineering, and executive strategy.
  • Turned fast-moving technical ideas into clear, useful editorial and launch work.

Advised on technical content and developer-facing messaging.

  • Helped sharpen content for a sophisticated technical audience.
  • Brought developer marketing judgment to strategy, messaging, and editorial work.
  • Kept the work useful, credible, and allergic to empty marketing fog.

Owned the messy middle where content, DevRel, product, and go-to-market meet.

  • Led content and developer relations for a developer-focused infrastructure company.
  • Built messaging, launch content, technical explainers, and editorial systems.
  • Managed teams and protected the quality bar when the work got complicated.

Ran marketing for an early-stage developer tooling company.

  • Turned product direction into positioning, launch work, and developer-facing content.
  • Worked across product, engineering, founder strategy, and go-to-market execution.
  • Kept the story legible while the company and category were still taking shape.

Led content and advocacy work for feature delivery and experimentation.

  • Built content systems for a technical B2B audience.
  • Connected product storytelling, developer education, and market-facing strategy.
  • Helped make complex software delivery concepts easier to understand and trust.

Advised an early developer tooling team before later joining full-time.

  • Helped shape technical story, audience fit, and developer-facing content direction.
  • Brought content and DevRel pattern recognition into a young product motion.
  • Started the working relationship that later became the Head of Marketing role.

Built the foundation in developer content, technical editing, and audience trust.

  • Scaled developer content programs across identity, auth, and SaaS infrastructure.
  • Edited and coordinated technical articles, contractor programs, and special projects.
  • Learned that developer attention is earned by being useful first.

Bring Me Your Weird Content Problem

Useful product, messy story, skeptical technical audience, content system held together with vibes and one heroic spreadsheet? Perfect. Let's talk.

Start the conversation Read my blog