# Executive Team

The Pineapple team brings together expertise across blockchain, finance, product, design, engineering, and AI.

Ali Abood — CEO\
Founder of Pineapple and the driving force behind the ecosystem's strategy and vision. Ali is also the Founder and Executive Director of Poolify, a Web3 agency dedicated to accelerating blockchain projects. With over a decade of experience across technology and finance, he manages a portfolio of 30 high-net-worth individuals and is known for translating bold ideas into operational reality across the DeFi space.

Kevin M — CTO\
Chief Technology Officer overseeing the technical direction and architecture of the Pineapple ecosystem, specifically Express and Staking.

Zed L — Lead Full-Stack Developer\
Lead developer responsible for the exchange, smart contracts, and core product infrastructure. Currently leading the P2P trading development and fiat feature improvements.

Arjun Aghera — Lead Product Designer\
Responsible for the product design and UX across the DEX, including the Fresh and Juiced mode interfaces.

Samir Baxter — Head of Community and Operations\
Oversees community management and operational delivery across the Pineapple ecosystem, including the Pineapple Mansion and community channels.

Veronika Volkonovska — Marketing Manager\
Leads marketing strategy and execution. Owns the Pineapple Academy content programme and newsletter, and drives external communications across X, Telegram, and other channels.


---

# 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://pineappledex.gitbook.io/litepaper/executive-team.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.
