> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/become-a-chef/data-analyst.md).

# Data Analyst

#### Responsibilities

* Collect, analyze, and interpret large datasets from on-chain transactions, including betting volumes, market resolutions, odds fluctuations, open interest and user participation in prediction events.
* Partner with product and engineering teams to design analytics solutions that transform raw blockchain data into insights on protocol health, liquidity trends, and market efficiency.
* Build and maintain data dashboards (using tools like Dune Analytics, Tableau, datawind or similar) to monitor key metrics such as Total Value Locked (TVL), user engagement, prediction accuracy rates, and event outcomes.
* Lead analytical support for on-chain campaigns, such as token airdrops, staking incentives, or market promotions, including tracking eligibility, rewards distribution, and ROI analysis.
* Query public blockchain data to uncover trends in user behavior, such as betting patterns, oracle integrations for event resolutions, and potential market manipulations.
* Communicate complex insights through visualizations and reports, translating blockchain data into actionable recommendations for stakeholders.
* Stay updated on blockchain advancements, prediction market protocols, and regulatory changes to inform data-driven strategies.
* Collaborate in a fast-paced environment where time-to-insight is critical for market competitiveness.

#### Requirements

* Bachelor's degree in a quantitative field such as Computer Science, Statistics, Mathematics, Economics, or a related discipline.
* 3+ years of experience in data analysis, preferably in blockchain, crypto, or fintech environments.
* Deep understanding of blockchain fundamentals, including EVM-based chains (e.g. Ethereum, BNB Chain), smart contracts, transaction structures, and event logs.
* Proficiency in SQL for querying blockchain data (e.g., via Dune Analytics, BigQuery) and at least one programming language (e.g., Python, R) for data processing and scripting.
* Experience with data visualization tools like Tableau, Power BI, or Matplotlib.
* Familiarity with on-chain metrics in DeFi or prediction markets, such as liquiditypools, oracle data feeds, and resolution mechanisms.
* Strong analytical mindset with the ability to handle large, unstructured datasets and derive meaningful insights.
* Excellent communication skills to present findings to non-technical teams.

#### Preferred Qualifications

* Experience working with prediction market platforms (e.g., Polymarket, Augur, or similar) or analyzing on-chain gaming/betting data.
* Knowledge of advanced analytics techniques, including machine learning for predictive modeling of market outcomes.
* Proficiency in additional tools like Nansen, Glassnode, or GraphQL for blockchain querying.
* Understanding of non-EVM chains (e.g., Solana) is a plus.
* Prior experience in Web3 startups or decentralized organizations.


---

# 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.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/become-a-chef/data-analyst.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.