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

# Hiring

VecomLab is a dynamic IT company focused on software development, marketing, e-commerce, and web3 technologies.

Our mission is to develop cutting-edge digital solutions and to advance new technologies.

Would you like to be part of our team? Although we don't have any open positions at the moment, we always welcome talented professionals!

### What do we offer our employees? <a href="#what" id="what"></a>

* **Professional Growth**: Continuous training and development in advanced IT areas.
* **Flexible Terms**: Remote work and a flexible schedule.
* **Future Technologies**: Participation in projects in the fields of web3 and e-commerce.
* **Friendly Team**: Mutual support and collaboration towards common goals.

### How do I propose my candidacy? <a href="#how" id="how"></a>

If you are ready to contribute to our projects, please send your resume to [**help@vecomlab.com**](mailto:help@vecomlab.com). We will carefully consider your application and contact you when a suitable position becomes available.


---

# 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://team.vecomlab.com/hiring.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.