# Hiring process

> "It doesn't make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do." Steve Jobs

Here’s what is most important to us in our hiring process:

* It needs to be efficient, and could be done within a couple of days.
* It needs to remove any unconscious bias we might have.

Here is what the process looks like for a **non-dev role**:

* A first call with one of our founders or team, focusing mostly on aptitude for the role and your alignment with our values and culture.
* Depending on the role, there will be 1 or 2 additional interviews with team members 

Here is how the process goes for **a dev role**: 

* A first call with one of our founders or team, focusing on two key areas:
  * Ensuring you will be a great cultural fit
  * Aptitude for the role
* A "take home" assignment to be done within a week. (Depending on the role)
* A call to discuss your "take home" assignment and ask you various technical questions. This can include some small "live coding". 

Once all of this is done, we will discuss the process internally and get back to you quickly with a positive or negative answer. In case of negative answer, we will call you and give you a detailed feedback on the reasons we decided not to move forward with you.

We recognize that interviewing is a two-way street where we both mutually learn about each other. During each step in the process, we will always reserve time to discuss anything you’re curious about and answer any questions you have about Astrafy and our team.


---

# Agent Instructions: 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:

```
GET https://docs.astrafy.io/handbook/its-all-about-people/hiring-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.