> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Jinn for recruiters

> The role and the interview plan from the hiring manager's own words, a write-up of every interview, and finalists compared in one question.

This page sets Jinn up for hiring: every interview is on record, and you compare candidates on
what they said rather than on whose notes were more careful. Once it's set up, you get:

* A write-up of every interview — strengths, concerns, what still needs checking — read the same
  way for every candidate ([step 3](#3-get-a-write-up-after-every-interview))
* The role, the screening questions and the interview plan, written from the hiring manager's
  own words ([step 4](#4-turn-the-intake-call-into-a-role))
* Candidates compared side by side in one question, with links back to the moments that decided
  it ([step 5](#5-compare-the-candidates))

Steps 1–2 you do once per role. Steps 3–6 are what you do for every hiring round.

## 1. Make a private project for the role

A hiring loop is one [project](https://docs.jinn.so/projects/manage-projects.md): every interview for one role, where the
same questions need the same reading each time.

1. Click **New project** in the left sidebar.
2. Name it after the role: *Backend engineer — 2026*.
3. Choose **Private**. Only the people you add can open it — the hiring manager and the
   interviewers, nobody else. Search and chat don't show its interviews to anyone outside it.

## 2. Set up recording

Interviews are recorded from the Jinn desktop app. No bot joins: the audio comes from your own
machine, so the candidate sees the call they expected.

1. [Download the app](https://app.jinn.so/download) and install it.
2. Open **Settings** → **Meetings** and turn on **Enable meeting notes**.
3. Under **When meeting starts**, choose **Show a recording prompt**.

Tell the candidate you're recording before you start. See
[recording a meeting](https://docs.jinn.so/meetings/record-a-meeting.md).

## 3. Get a write-up after every interview

1. When the interview starts, click **Start** on the recording bar.
2. Under **Select project**, pick the role's project. Under **Meeting name**, type the
   candidate's name.
3. When it ends, click **Stop & Generate**.

![Jinn's recording bar floating over another window, showing the timer and the audio levels](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/record-a-meeting-bar.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=69ff0932ce76e2a1e46511ca6f60e7ad)

The recording bar, mid-interview

Every recorded meeting gets a write-up from AI [agents](https://docs.jinn.so/agents/add-an-agent.md) — each one reads
the meeting through a particular role. One of them, **Default**, is built into every project
and writes a summary on its own. For hiring you need **Recruiter**: it reads for what the role
needs and how to tell the right candidate from the wrong one.

4. On the recording, click **Add agent** at the end of the row of agents and pick
   **Recruiter**.
5. Read its write-up. If it got something wrong, fix it in place — what you write is what the
   hiring manager reads.

If **Recruiter** isn't in the list, it isn't on this project yet. Ask the person with **Full access** on the project to add it; if the
workspace doesn't have it at all, a workspace admin creates it first.

An interview recorded somewhere else comes in as a file: open the project, go to
**Recordings** and click **Upload recordings**.

## 4. Turn the intake call into a role

Record the call where the hiring manager explains who they need into the role's project, the
same way as an interview. Then:

1. Open the recording and click **Chat**. The chat reads only this call.
2. Type `/` in the message box and pick **Job description**. Ask for the description.
3. In the same chat, pick **Candidate screening** for the screening questions, and
   **Interview kit** for the interview plan.

![The / menu in Jinn's message box, with Custom skills at the top and Built-in skills below: Candidate screening, Cold outreach, Discovery call and others](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/skills/use-a-skill.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=7aa38a05e9fcea5507398259d37aaf98)

Type / to pick a skill

4. Paste what you keep into a doc in the project: **Add** → **New doc in project**. From then on
   the chat checks every interview against it.

See [skills](https://docs.jinn.so/skills/use-skills.md).

## 5. Compare the candidates

1. Open the role's project and click **Chat**. The chat reads every interview in it.

2. Ask in plain words.

   > [!TIP]
   >
   > For example: *Compare the three finalists on system design and ownership. Where did each
   > of them struggle?*

3. Open the links under the answer and listen to the moments it's based on before the debrief.

## 6. Share the decision with the hiring manager

* **A moment worth hearing.** Select the passage in the transcript, choose **Add tag**, and
  tag it — *strong*, *concern*. The tag works as a filter in [search](https://docs.jinn.so/find/search.md).
* **A question about it.** On the **Comments** tab, select the words in the write-up and ask.
  The hiring manager answers with **Reply**.
* **Your ATS.** **Copy** above the write-up puts it on your clipboard. There's no automatic
  hand-off to other tools.

## Where to go next

> [card] [Jinn for sales teams](https://docs.jinn.so/for/sales.md)
>
> Keep every customer call on record and write the follow-up from what was said.

> [card] [Jinn for QA engineers](https://docs.jinn.so/for/qa-engineers.md)
>
> Know what to retest after every meeting, and find the earlier report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.