> For the complete documentation index, see [llms.txt](https://help.quickappflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quickappflow.com/product-guides/recruitment-and-ats/job-tracker/recruiter-can-perform-different-action/create-technical-test.md).

# Create technical test

Recruiter can performs the **'Create technical test’** action, a popup should appear.

<figure><img src="/files/rAMg3ur347rsmlDPQ7iD" alt=""><figcaption></figcaption></figure>

If a recruiter selects a **single candidate** to schedule a technical test, they need to choose the interview mode, meeting URL, scheduled time, contact person, and interviewer, and then click on **'Yes.**'

<figure><img src="/files/Po1oG0sodiO6A3M85NkE" alt=""><figcaption></figcaption></figure>

If a recruiter selects **multiple candidates** to schedule a technical test based on the next availability date, they need to choose the interview mode, meeting URL, contact person, and interviewer. Afterward, click on **'Yes'**.

<figure><img src="/files/M7Y37py0pRhrI1LkzRzK" alt=""><figcaption></figcaption></figure>

When the technical test round is scheduled, the system sends email notifications to the candidate, sends an action-performed email to the recruiter, updates the status in the tracker as '**Technical test scheduled,**' and adds an activity as '**Scheduled technical interview'**.

![](/files/gkBcqzs4RqKQIDJbACIR)

After scheduling the technical test, the request is assigned to the interviewer and a notification is sent to the interviewer.

![](/files/5VYuRUmzRoc9h0lkjCTr)

If the interviewer **selects** the candidate for this round and approves the request, the status changes to **'Technical test - passed'** in the tracker, The system sends email notifications to the recruiter and the candidate, and a task activity is added as a **'Technical round passed'.**

![](/files/AG7CJShwsks0LmKlsqJG)

If the interviewer **rejects** the candidate for this round and approves the request, the status changes to **‘Technical test- failed’** in the tracker, The system sends email notifications to the recruiter and the candidate, and a task activity is added as a **'Technical round failed'.**

![](/files/wRDEJI47Kp5EiLwxJ8op)

If the interviewer **holds** the candidate for this round and approves the request, the status changes to **‘Technical test- hold’** in the tracker, sent email notification to the recruiter and a activity is added as a '**Candidate is on hold for technical round'.**

<figure><img src="/files/dtTmrRnCxfN7DePwqa7J" alt=""><figcaption></figcaption></figure>

Recruiter can see the technical test history from view history, click on action (3 dots) and click on view history.

![](/files/Ng8NGAoonEoBm0gg620N)

Go to **‘Technical Test’** grid.

![](/files/UOlXX6U9A8JAYGwIYAkJ)


---

# 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://help.quickappflow.com/product-guides/recruitment-and-ats/job-tracker/recruiter-can-perform-different-action/create-technical-test.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.
