> For the complete documentation index, see [llms.txt](https://playbook.functionary.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.functionary.co/welcome-to-our-playbook.md).

# Welcome to our Playbook

Learn about how we practice our craft - engineering, design, & project management. Know about the policies we follow and the benefits we offer.

At Functionary we're working hard to build an environment that is inclusive, open, and appreciative. Building a value-driven company has helped us hire the best people who not only build amazing software but are also nice to work with.

As we grow we were looking for a place to write the policies & processes we follow and what we are looking for while hiring. By no means is this playbook complete, in fact, this is ever-evolving and will continue to change as we grow. We encourage everyone to provide their feedback and suggestions. We love positive discussions as that is the only way to build an inclusive workplace.

After reading this if you feel like this is a place where you'd like to work please take a look at the open positions


---

# 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://playbook.functionary.co/welcome-to-our-playbook.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.
