> For the complete documentation index, see [llms.txt](https://careers.dabba.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://careers.dabba.com/help-us-build-connectivity-infrastructure/team-dabba.md).

# Team Dabba

<figure><img src="/files/ON1XDaVJEUfWmBU8RNZU" alt=""><figcaption><p>We are a happy bunch of builders!</p></figcaption></figure>

We are always on a lookout for folks who are excited to work on interesting problems, enjoy learning from and helping each other, and above all, are resilient and empathic.

At Dabba, you’ll be working on a small team with other experienced engineers and operators - people who have helped scale successful companies and understand how to get stuff done. We value honesty, passion, humour, and curiosity.&#x20;

You get to define the future of telecom infrastructure ownership and operations. We are building for the long term and just getting started. Join & help us build something amazing together for the next billion users.

#### All of the open positions are based out of our Bangalore office unless otherwise stated. We do not work in remote setup and strongly believe in-office productivity.&#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://careers.dabba.com/help-us-build-connectivity-infrastructure/team-dabba.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.