> For the complete documentation index, see [llms.txt](https://hello.kodadot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello.kodadot.xyz/be-part-of-kodadot/join-as-a-developer/why-should-you-contribute.md).
# Why Should You Contribute?
## Bounty Rewards
We offer bounties starting from **$50** up to **$1200 USD**, with our most popular issues being **$100 USD**. The more complex the issue is, the more you'll get rewarded.
You can feel free to take a peek at our [current bounties](https://github.com/kodadot/nft-gallery/labels) in our GitHub to get started!
## Flexibility
Don't have time for a second job? We got you. Everyone has a side hustle nowadays and with the **gig economy**, this is how we can operate more efficiently. Here at KodaDot, **we don't hold anyone full-time, nor do we track hours.** Come and go whenever you want.
## Challenging Puzzles
Our challenging issues will push you to think deeply about solutions and force you to learn a thing or two along the way. Mental stimulation is something you won't get on your day-to-day office jobs, so this is where we come in.
Sense of Community
Collaboration is an important part of contributing. Your name becomes known throughout the community when you make pull requests, ask questions, or even hop on a call for a minute or two. Everyone who contributes to KodaDot becomes a member of the family. You'll find others who are working on challenges similar to yours, as well as those that are struggling. This is where you enter the picture. We're all here for each other, and we want to see each other succeed. KodaDot will become synonymous with a sense of belonging.
## Contribution to Open Source
**Public proof of contribution** is arguably one of the most important things when trying to land your first tech job. Focusing on a person's GitHub is more telling of one's skillset than reading a PDF. Rather than blindly trusting resumes, you can judge what a person has contributed publicly.
---
# 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://hello.kodadot.xyz/be-part-of-kodadot/join-as-a-developer/why-should-you-contribute.md?ask=&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.