Technical Writer

We're looking for a technical writer to join our Tech Writing team — someone who thinks in systems as naturally as they think in sentences. At Braze, documentation is infrastructure: a connected, structured body of knowledge that both developers and machines read from, not a collection of individual pages. You'll spend as much time shaping how that knowledge is organized and generated as you will writing it.

Our documentation practice is already well established, with a mature style guide, writers who own specific product domains, and a workflow where AI-assisted drafting sits alongside traditional technical writing. Your job is to push it forward on two fronts. The first is architectural: defining the metadata, taxonomy, and context our tooling relies on to produce useful first drafts. The second is editorial: becoming a genuine expert on Braze's platform and bringing the kind of scrutiny that turns a plausible draft into documentation our customers can actually trust — accurate, well-structured, and consistent in voice with every other Braze experience.

WHAT YOU’LL DO

• Define and maintain the metadata (YAML front matter), taxonomy, and contextual guidelines that our AI-assisted drafting workflows depend on
• Review and verify machine-generated prose and code samples line by line, checking technical accuracy, edge-case behavior, and voice before anything ships
• Write and revise API references, integration guides, and conceptual documentation in our docs-as-code environment, owning feature updates end to end
• Become an expert on the Braze platform, distilling complex functionality into approachable, user-centric language
• Help oversee and maintain the documentation GitHub repository
• Work closely with Product Management, Engineering, Support, Customer Success, Marketing, and Implementation teams to pin down how the platform actually behaves and to validate real customer integration paths
• Organize content so it serves a developer mid-integration and a system retrieving context — the same structure has to work for both
• Ensure documentation applies voice, style, and branding consistent with other client experiences
• Keep improving our documentation and client education experience through feedback-gathering, research, experimentation, and data-driven decisions
• Promote and foster knowledge exchange across teams

WHO YOU ARE

• 3+ years writing documentation for genuinely technical audiences — APIs, SDKs, or developer platforms — with writing samples that show both range and precision
• Fluent in information architecture and knowledge management
• A rigorous editor with a sharp instinct for the draft that reads well but says something subtly wrong
• Comfortable with Git, Markdown, YAML, and docs-as-code workflows
• An active, practical user of LLMs and AI tooling in your own work — you've figured out where they help and where they don't
• Able to explain technical concepts to engineers and to non-technical readers, and to know which one you're writing for
• Curious by default: you want to understand why something works the way it does before you document it, and you'll say so when a plan doesn't hold up
• Steady across many stakeholders and comfortable when priorities shift
• Excellent interpersonal skills, a user-centric team-player attitude, and confidence presenting your work and your reasoning
• A relentless advocate for the user experience

For candidates based in the United States, the pay range for this position at the start of employment is expected to be between $73,000 and $109,000/year with an expected On Target Earnings (OTE) between $81,000 and $121,000/year (including bonus or commission). Your exact offer may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. In addition to cash compensation, this role qualifies for a comprehensive Total Rewards package that includes equity grants of restricted stock (RSUs) so that you will own a piece of our company.