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

# Contributors

You will find here the internal structure of the mDAO and its team members.

## Contributors

You will find here how Marinade is organised and how to join.

### Team Structure

Marinade's contributors are organised into teams rather than the two mDAO-era workgroups the DAO started with. The current teams are:

1. **Engineering:** Protocol and product engineering, DevOps, data and security. Owns the on-chain programs, the app, the APIs and the infrastructure behind them.
2. **Product:** Product direction and design across Marinade Native, Marinade Liquid, Select, Recipes, Borrow and the USDC vault.
3. **Partnerships:** Integrations, institutional and custodian relationships, technical sales and user support.
4. **BizOps:** Finance, legal, compliance, HR and operations.
5. **Marketing:** Brand, content and communications.
6. **Management:** Company direction and coordination across the teams above.

Governance sits with MNDE holders rather than with any of these teams. See MNDE Governance for how proposals are discussed, voted and executed, and for the split of powers between MNDE holders and the Marinade Council.

***

## Become a contributor

If you think you can contribute to Marinade, you can use [this form](https://tally.so/r/wkg9Zw) to reach out. If an open position fits with your skills, you'll be contacted for an interview. If there are no open positions matching your profile, we'll keep your application and may contact you in the future.

In the meantime, we strongly recommend that you read our entire documentation, join our [Discord](https://discord.gg/yTdH8YkYKg) and introduce yourself to the kitchen.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.marinade.finance/marinade-dao/contributors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.