> For the complete documentation index, see [llms.txt](https://docs.onlydust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlydust.com/overview/team-and-jobs.md).

# Team & Jobs

#### The Gang

We are a team of 7. There is the growth, finance, and the tech team, along with our two co-founders. 

The tech team has back-end & front-end devs. All with their very own talents and specialties. They are the ones who help build the product that you see today. And debug in under 30 minutes. Yep, they are that reactive :wink:

The finance team speaks for itself! This is where the team makes sure that we're not financing weird stuff and that those who use our platform are legit users. 

The growth team is probably the most "visible". They're the ones who are contacting you daily and making sure everything is going well.  \
\
We are based in San Francisco. \
\
Every month, we gather together during our team off-site, because we like each other :). <br>

#### Jobs

Currently, we do not have any job openings! \
\
But hey, if we do, we will be sure to communicate on it.&#x20;


---

# 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://docs.onlydust.com/overview/team-and-jobs.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.