> For the complete documentation index, see [llms.txt](https://peardao.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peardao.gitbook.io/docs/team/pear-members/technical-writer.md). # Technical Writer Responsibilities * Structure, write and update conceptual content, tutorials, guides, API/SDK developer documentation Synthesize and translate complex technical information effectively across the organization * Write high-quality SEO-friendly content, and continuously improve user experience, traffic, and retention. * Continuously improve the user and developer experience by creating and iterating on the user interface, landing page, technical content, and marketing materials * Support proofreading and rewrites of portions of complex industry topics to ensure that the substantive facts, issues, conclusions, and recommendations are included and presented appropriately Requirements and Skills * Strong skills in writing, planning, and editing. * Native English speaker and writer * Creative and able to produce unique ideas and cognition * Strong sense of responsibility, logical, rigorous and meticulous, self-motivated, and values strong teamwork * Bachelor's degree or above in education, journalism, psychology, media, marketing, etc. is preferred. **Fill in this form, so we could get to know you better.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://peardao.gitbook.io/docs/team/pear-members/technical-writer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.