> For the complete documentation index, see [llms.txt](https://docs.envisioning.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.envisioning.io/envisioning/how-we-work.md).

# Work with us

We are a networked company with people in several different countries and backgrounds, which means our headquarters is the Internet, we don't have a physical office and probably never will. Our core team is divided into seven leading areas that constantly receives contributions from developers, designers, editors, reviewers and researchers with expertise according to every project. 

## Tools we use

| Tool      | Use                                    | People                            | Tutorial                                                                                          |
| --------- | -------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------- |
| Slack     | Internal communication                 | All                               | [Link to Tutorial](https://api.slack.com/tutorials)                                               |
| Flow      | Schedule and agenda                    | All                               | [Link to Tutorial](https://www.flow.help/hc/en-us/categories/360002279133-Using-Flow)             |
| Zoom      | Meetings platform                      | All                               | [Link to Tutorial](https://support.zoom.us/hc/en-us/articles/206618765-Zoom-Video-Tutorials)      |
| Grammarly | Check grammar and spelling             | Editors and Reviewers             | [Link to Tutorial](https://support.grammarly.com/hc/en-us/categories/115000018631-Tips-Tutorials) |
| Whereby   | Meetings platform                      | Envisioning core team             | [Link to Tutorial](https://whereby.helpscoutdocs.com/category/377-using-whereby)                  |
| Airtable  | Web organization database              | Head of Operations and Developers | [Link to Tutorial](https://support.airtable.com/hc/en-us/categories/360001657594-Guides)          |
| Github    | Development internal tool              | Developers                        | [Link to Tutorial](https://help.github.com/en)                                                    |
| Gitbook   | Editing and Research organization tool | Head of Research and Lead Editor  | [Link to Tutorial](https://tomcam.gitbooks.io/gitbook-tutorial/content/)                          |

## Meetings

### Onboarding

A space to welcome newbies

### Monthly Touchpoint

A monthly meeting intended to update new practices, meet coworkers and establish a more fluid and interconnected relationship of this remote workplace

## Who we are looking for?

* Researchers
* Experts
* Designers
* Developers
* Editors
* Recruiters

## Apply for a position

{% embed url="<https://airtable.com/shrlS6HRwjIENtiAD>" %}

## Best practices

{% embed url="<https://about.gitlab.com/handbook/tools-and-tips/>" %}


---

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

```
GET https://docs.envisioning.io/envisioning/how-we-work.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.