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

# Our Team

The robustness of our strategies is backed by our expertise in research and growing knowledge of the financial markets and quant skills. Our backgrounds make us the perfect architects of this adventure!

We are a team made of finance quants, with backgrounds in Computer Science, AI, Physics, Finance and graduates from the prestigious [UC Berkeley Master in Financial Engineering](https://mfe.haas.berkeley.edu/) program. We have the ideal background to bring cutting edge quant strategies to everyone through DeFi. Our research skills and work experience at the largest banks in our regions (BNP, Credicorp), hedge funds (WorldQuant) and FinTechs (Ripple), have allowed us to hone the necessary skills to understand the markets and bring value from DeFi to users.

With our growing experience, deep curiosity in DeFi and expertise as quants, we are confident that YieldForge will redefine the boundaries of performance in the DeFi arena.

<br>


---

# 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://yieldforge-1.gitbook.io/yieldforge-protocol/features/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.