> For the complete documentation index, see [llms.txt](https://greenpaper.games.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://greenpaper.games.gg/why-gam3s.gg/team.md).

# Team

Our team has 18 members at the moment across the content and product team, most of whom have been at the company for over 2 years. GAM3S.GG team members are predominantly present in the United Arab Emirates and Portugal, with the rest spread across the Netherlands, Thailand, United Kingdom and USA.

<figure><img src="/files/cToMTR7xFwSvmVue5KGV" alt=""><figcaption></figcaption></figure>

Collectively, our team has **20+ years of experience** working with the likes of Riot Games, Ubisoft, Epic Games, Activision, Esports.GG, Nvidia, Steelseries, Razer, and many more across multiple fields including content creation, influencer campaigns, tournament organizing, operations, product development and more.


---

# 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://greenpaper.games.gg/why-gam3s.gg/team.md?ask=<question>&goal=<endgoal>
```

`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.
