Documentation Engineer

Summary

Arize AI is an AI observability and evaluation platform that helps AI engineers build and deploy reliable models and agents. The Documentation Engineer will own product documentation, develop AI-driven systems to maintain and test documentation, create tutorials and examples, and support developers through onboarding and community engagement.

Responsibilities

• Own the health of Arize's product documentation: keep it accurate as we ship, and rewrite the parts that have stopped making sense
• Build automated systems that monitor documentation quality, detect drift between docs and code, test that code samples still work, and draft updates for human review
• Make our documentation work for coding agents as well as humans: structured content, machine-readable indexes, and real measurement of whether an agent can complete a task using our docs alone
• Write and refresh tutorials, cookbooks and open-source demonstration repositories that take a developer from introduction to value quickly
• Get Arize documented accurately outside our own site, working with integration partners, framework maintainers, and course and curriculum authors
• Create a stellar onboarding experience for new users, judged by whether they get to their first working eval unassisted
• Take feedback from the community and turn it into actionable product insights that shape our open source and commercial product roadmaps
• Assist our marketing team by providing source material for field marketing, SEO and answer-engine-focused website copy
• Interact with our developer community at conferences, trade shows and local meetups, as well as online through our community Slack and other channels
• Be the first point of contact for community members with product questions, directing them to the appropriate teams and channels
• Collaborate with the Product team to prototype "spikes" for new features and product directions

Skills

• * 3+ years in technical writing, documentation engineering, developer relations, or an engineering role with a lot of writing in it
• * Excellent technical communication skills, demonstrated by public-facing documentation, blog posts or videos you can point us to
• * Up-to-date engineering skills. You'll be writing code that maintains documentation, not only prose, so docs-as-code workflows, CI and general comfort working in a repo are assumed
• * Working knowledge of LLM-based app development e.g. agents, RAG, orchestration frameworks. You do not need to be specifically familiar with Arize
• * Genuine interest in how agents read and use documentation, and in building the tooling that makes that work
• * A curious and self-motivated continuous learner, comfortable with the ambiguities and rapid iteration of a startup environment
• * Willing to attend occasional evening and weekend events in-person either local to your location or (less frequently) within a few hours' travel time
• Note: Arize is a remote-first company but Developer Relations roles often appear at in-person events. The nature of this role requires candidates to be based in the San Francisco Bay metro area, though there isn't an in-office requirement
• * Familiarity with the evaluations and observability space including products like Arize
• * Experience building automation around documentation: link checking, snippet testing, style linting, LLM-assisted review
• * Opinions about llms.txt, documentation MCP servers, and the other current attempts at machine-readable docs
• * Highly engaged in technical communities on forums like X, Reddit, Slack, Discord, Dev.to etc
• * Existing experience running or contributing to open-source projects like Arize Phoenix

Qualifications

Must Haves

• * 3+ years in technical writing, documentation engineering, developer relations, or an engineering role with a lot of writing in it
• * Excellent technical communication skills, demonstrated by public-facing documentation, blog posts or videos you can point us to
• * Up-to-date engineering skills. You'll be writing code that maintains documentation, not only prose, so docs-as-code workflows, CI and general comfort working in a repo are assumed
• * Working knowledge of LLM-based app development e.g. agents, RAG, orchestration frameworks. You do not need to be specifically familiar with Arize
• * Genuine interest in how agents read and use documentation, and in building the tooling that makes that work
• * A curious and self-motivated continuous learner, comfortable with the ambiguities and rapid iteration of a startup environment
• * Willing to attend occasional evening and weekend events in-person either local to your location or (less frequently) within a few hours' travel time
• Note: Arize is a remote-first company but Developer Relations roles often appear at in-person events. The nature of this role requires candidates to be based in the San Francisco Bay metro area, though there isn't an in-office requirement

Nice to Haves

• * Familiarity with the evaluations and observability space including products like Arize
• * Experience building automation around documentation: link checking, snippet testing, style linting, LLM-assisted review
• * Opinions about llms.txt, documentation MCP servers, and the other current attempts at machine-readable docs
• * Highly engaged in technical communities on forums like X, Reddit, Slack, Discord, Dev.to etc
• * Existing experience running or contributing to open-source projects like Arize Phoenix

Benefits

• Competitive equity package
• Medical, dental, vision, 401(k) plan, unlimited paid time off, generous parental leave plan, and others for mental and wellness support
• WFH monthly stipend to pay for co-working spaces
• Regularly have chats with industry experts, researchers, and ethicists across the ecosystem to advance the use of responsible AI
• Culturally conscious events such as LGBTQ trivia during pride month
• We have an active Lady Arizers subgroup