Technical Writer

This role is on-site in San Francisco in the Dogpatch neighborhood.

Giga has recently raised a $61M Series A and is working with Fortune 500 customers to deploy the next generation of customer experience - real-time AI agents that can understand emotion, resolve issues instantly, and scale across the world's largest enterprises.

Industry leaders like DoorDash trust Giga with their most complex support and operations workflows across voice, chat, and email, in high-stakes regulated environments where accuracy and compliance matter. We're at an exciting inflection point.

While we've found real commercial success, our ambitions are larger: to become the go-to AI platform for all enterprise automation, powered by our voice superintelligence. The work affects millions of people every day, and our team has the autonomy to make true impact - with brilliant founders, a clear path forward, and the kind of momentum that defines generational companies.

If being part of that resonates with you, we'd love to hear from you!

• Voice AI startup Giga raises $61M Series A

• DoorDash and Giga Partnership

Giga ships product fast. What we don't ship fast enough is the writing that makes builders understand why it matters. We're hiring a Founding Technical Writer to own our engineering voice externally — technical blog posts, teardowns, and narratives published on a weekly cadence. Marketing owns distribution. You own craft.

The quality bar: Anthropic's engineering blog (their multi-agent research posts, Claude Code best practices) and Ramp's Builders blog (Forward Deployed Engineering, Abstraction Engineering). If those are publications you read and have opinions about, we should talk.

• 2 flagship technical posts per month (1,500–3,000 words, interview-driven, your byline) — the kind of posts engineers share with their teams

• 2 shorter pieces per month — tactical teardowns, customer engineering stories, technical POV pieces

• Source material and editorial for major product launches — working directly with engineering to shape the narrative

• A technical publishing rhythm the engineering team is proud to share and candidates cite in interviews

You've interviewed technical people and turned what they said into writing people actually read. You understand agents, LLMs, and production systems well enough to ask the second and third question — not just the softball. You can hold your own with senior engineers because you translate across, not down. You write with a point of view, not just a style guide. You ship on cadence without sacrificing craft.

Technical PMM, ex-DevRel, engineers who pivoted to writing, tech journalists who went in-house, serious AI/agents Substack writers. We don't care about your title. We care about your writing.

Send 3 writing samples and a paragraph on which post from Anthropic's engineering blog or Ramp's Builders blog you'd write differently, and how.