# Technical Writer

Responsibilities&#x20;

* Structure, write and update conceptual content, tutorials, guides, API/SDK developer documentation Synthesize and translate complex technical information effectively across the organization&#x20;
* Write high-quality SEO-friendly content, and continuously improve user experience, traffic, and retention.&#x20;
* Continuously improve the user and developer experience by creating and iterating on the user interface, landing page, technical content, and marketing materials&#x20;
* 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&#x20;

* Strong skills in writing, planning, and editing.&#x20;
* Native English speaker and writer&#x20;
* Creative and able to produce unique ideas and cognition&#x20;
* Strong sense of responsibility, logical, rigorous and meticulous, self-motivated, and values strong teamwork&#x20;
* 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.** <https://forms.gle/U7pXpxCyk2q3TPzDA>&#x20;


---

# Agent Instructions: 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:

```
GET https://peardao.gitbook.io/docs/team/pear-members/technical-writer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
