> Markdown version of [/jobs/ext/2306251-developer-relations-documentation-engineer](https://www.wearedevelopers.com/jobs/ext/2306251-developer-relations-documentation-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Developer Relations Documentation Engineer - **Company:** Arize AI - **Location:** San Francisco Bay Area, CA, United States (Remote available) - **Experience:** Experienced - **Salary:** $100,000.0 - $175,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Open Source Technology, Software Engineering, Large Language Models, Kubernetes, Build Tools, Code Inspection, Discord, Software Coding - **Published:** August 30, 2026 - **Apply:** https://www.dice.com/job-detail/65a4fe07-afd0-48ba-aa4c-27d314673fcc ## About the Role * 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 Bonus qualifications: * 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 ## Description Our developer relations team's mission is to provide the best possible developer experience for our flagship products, Arize AX and Arize Phoenix. This role owns the documentation half of that mission: keeping our own docs accurate as the products change, expanding our guides and cookbooks so a developer can get from first read to working code without asking anyone for help, and making sure Arize is documented correctly in other people's material too, from integration partners to online courses. Documentation now has two audiences reading it simultaneously: developers, and the coding agents working on their behalf. The same page has to be skimmable by a human and unambiguous to an agent that will act on it, and nobody in the industry has settled on how to do both well. That's an exciting problem and it will be central to this role. We are not looking for someone to hand-edit pages forever. We are heavy users of AI-driven automation and expect you to build systems that spot stale content, catch drift between the code and the docs, draft updates for review, and check that our examples still run. Good writing and editing skills are of course required for this role, but we expect you to use AI to greatly accelerate and amplify your skill. What You'll Do Primary 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 Secondary responsibilities: * 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 ## Related Videos - [Developer Marketing](https://www.wearedevelopers.com/videos/1049-developer-marketing) - [Your Docs Are Now AI Infrastructure (Treat Them Like It)](https://www.wearedevelopers.com/videos/100284-your-docs-are-now-ai-infrastructure-treat-them-like-it) - [Modern Data Architectures need Software Engineering](https://www.wearedevelopers.com/videos/1030-modern-data-architectures-need-software-engineering) - [Understanding Kubernetes in a visual way](https://www.wearedevelopers.com/videos/100085-understanding-kubernetes-in-a-visual-way) - [The ABC of DX](https://www.wearedevelopers.com/videos/727-the-abc-of-dx) - [Building a framework-independent component library](https://www.wearedevelopers.com/videos/1679-building-a-framework-independent-component-library) ## Related Articles - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Humanizing Your Documentation](https://www.wearedevelopers.com/magazine/133-humanizing-your-documentation) - [Technical Documentation For Developers](https://www.wearedevelopers.com/magazine/128-technical-documentation-for-developers) - [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters) - [The real reason we document our code](https://www.wearedevelopers.com/magazine/518-the-real-reason-we-document-our-code) - [Dev Digest 150 - The shift to AI generated code, fingerprinting and OKRs vs. doing your job](https://www.wearedevelopers.com/magazine/533-dev-digest-150-the-shift-to-ai-generated-code-fingerprinting-and-okrs-vs-doing-your-job)