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

# Our Team

We are rethinking financial markets and their instruments in a new era of technology and decentralization. This is an exciting challenge to be at the beginning of something new that will affect the whole global economy. Learn more about our team [here](https://finchtrade.com/about-us.html). 

### [Pavel Efremov](https://www.linkedin.com/in/pavel-efremov-98a8a146/)

Head of risk and treasury 

### [Yuri Berg](https://www.linkedin.com/in/yuriberg/)

Member of the board

### [Anton Dines](https://www.linkedin.com/in/dinesanton/)

Client operations

> **We are hiring!**

We advocate a quantitative approach and promote data mining. We respect logical reasoning but believe solely in statistics. If you share the same values, you will be welcome to join our team. Visit our [Careers page](https://finchtrade.com/about-us.html#positions) to find out who we are looking for.


---

# 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://help.finchtrade.com/finchtrade/our-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.