Documentation Engineer

Braintrust is the AI observability platform. By connecting evals and observability in one workflow, Braintrust gives builders the visibility to understand how AI behaves in production and the tools to improve it.

Teams at Notion, Stripe, Zapier, Vercel, and Ramp use Braintrust to compare models, test prompts, and catch regressions — turning production data into better AI with every release.

At Braintrust, documentation is a core part of the product experience. Our customers - developers and product managers shipping AI features - deserve docs that help them learn, onboard, and succeed with our product.

This role is for someone comfortable operating in ambiguity, who moves quickly without sacrificing quality, and takes ownership from understanding the product hands-on to shipping documentation that meaningfully reduces friction for users.

• →

  Ship high-quality documentation at speed - guides, tutorials, API references, SDK documentation, code samples, and more.

• →

  Translate ambiguous goals into structured plans. Proactively unblock yourself through hands-on product testing, sharp questions, and cross-functional collaboration.

• →

  Produce clear, correct, and complete docs that allow customers to onboard and use Braintrust with minimal support.

• →

  Test the product hands-on. Build fluency in core Braintrust workflows, anticipate where users may struggle, and surface UX or DX issues early. Write code examples, call APIs, build with SDKs, and verify that everything works as expected.

• →

  Use AI tools to accelerate your work - drafting, researching, reviewing, and iterating. We're an AI company, and we use AI to increase velocity and improve quality.

• →

  Improve information architecture, clarity, and user flows.

• →

  Engage early and often with partners. Communicate progress, risks, and insights proactively, and provide thoughtful feedback that improves both the product and how it’s documented.

• →

  Follow existing conventions while helping improve templates, content patterns, and workflows to increase clarity, consistency, and team velocity.

• →

  Contribute beyond long-form docs - error messages, in-product copy, onboarding flows, changelog entries, CLI help text.

• Proven experience writing high-quality product and developer documentation.

• Strong ability to operate independently in fast-moving, ambiguous environments.

• A hands-on, product-first mindset - you learn by using the product, not just reading specs.

• Excellent written communication and attention to detail.

• Familiarity with developer tooling - REST APIs, SDKs, CLIs, and at least one programming language. You can follow a codebase, run scripts, test API calls, and write clear code samples.

• Fluent in docs-as-code: Markdown, Git, pull requests, CI-based publishing.

• Experience using AI tools to accelerate writing, research, and review.

• Comfort collaborating cross-functionally and giving constructive product feedback.

• Bias toward action, iteration, and continuous improvement.

• Data-informed. You use analytics, search logs, and support signals to guide what you write.

Please include writing samples of developer-facing documentation with your application. We are looking for examples that demonstrate your ability to produce clear, effective documentation across different types of content, such as:

• Instructional content: quickstarts, how-to guides, or tutorials.

• Explanatory content: conceptual or architectural explanations that help users understand how a system works and why.

• Reference content: API documentation, SDK references, CLI docs, or other technical reference material.

Samples can be links to published documentation, GitHub repositories, or documents you authored. If possible, include work that reflects how you approach clarity, structure, and developer usability.

Braintrust is an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran or disability status.