Skip to main content

Create and Train an Interview

Learn how to create an interview from a job description, set up questions, define your ideal candidate, and configure interview settings.

Are you connected to an ATS?

You can import a job directly from your ATS instead. See Import an Interview for step-by-step instructions.

Steps overview​

Training Ezra is a 9-step process:

  1. Upload job — Add your job description
  2. Role details — Review and edit the extracted role information
  3. Interview questions — Set up the questions Ezra will ask
  4. The perfect candidate — Describe what you're looking for
  5. Interview settings — Configure expiry, team access, and analysis features
  6. Additional context — Give Ezra the information it needs to answer candidate questions
  7. Test interview — Preview how Ezra will conduct the interview and answer questions
  8. Notifications — Set up email and Slack alerts
  9. Welcome screen — Customize the landing page candidates see before starting

Step 1: Upload a job description​

Drag and drop or browse for a PDF, DOCX, or DOC file. Ezra extracts the job title, location, salary, and description automatically.

Already connected to an ATS?

You can skip this step by importing a job directly. See Import a Job Posting from ATS.

Step 2: Review role details​

Ezra auto-populates the role title, location, pay, description, core duties, and requirements from your job description. Click the edit icon on any field to make changes.

Step 3: Set up interview questions​

You can either generate example questions from the job description or write your own from scratch. Each question has four configurable sections:

  • Question — The question Ezra will ask the candidate.
  • Ideal answers — A rubric defining what Great, Good, OK, and Poor answers look like for this question. These benchmarks are how Ezra evaluates each candidate's response. You can write them yourself or click Generate benchmarks to have Ezra draft them.
  • What should Ezra listen for? — Key themes, keywords, and nuances. Ezra uses this to ask intelligent follow-up questions during the interview, digging deeper when a candidate's answer touches on (or misses) these points.
  • Importance — A weight from 1–5 that controls how much this question impacts the candidate's overall score.

Drag questions to reorder them.

Step 4: Define the perfect candidate​

Describe your ideal candidate traits in the text editor, or have a voice conversation with Ezra about what you're looking for.

After writing or speaking with Ezra, you can click Generate question — Ezra will create an interview question tailored to the perfect candidate traits you described.

You can also invite hiring managers to contribute their own perspective on the ideal candidate.

Step 5: Configure interview settings​

  • Interview expiry — Select a date after which the interview link will expire.
  • Team members — Control who on your team has access to this interview and its candidates. Search for existing team members by email, or type a new email address to add someone who isn't on the team yet. Members added here can view this interview's candidates and results. Admins always have access to all interviews and cannot be removed.
  • Communication analysis weight — Adjust how much communication quality affects the overall interview score for this role. Toggle this on to set how much weight Ezra's communication analysis carries in the candidate's overall score (0–20%).
Danger zone

The Reset button at the bottom of this step erases all current interview settings and starts the setup process from scratch. This action is irreversible. Candidates who have not yet taken the interview will no longer be able to access it.

Step 6: Add additional context​

During an interview, candidates will often ask questions about the role, the team, benefits, day-to-day expectations, and more. Context documents are how you give Ezra the information it needs to answer those questions accurately.

Without context documents, Ezra can only draw on what's in the job description. With them, Ezra can speak knowledgeably about anything you've documented — team structure, tech stack, growth plans, perks, on-call expectations, or whatever else matters for this role.

Ezra will never guess or fabricate information. If a candidate asks a question that isn't covered by the job description or your uploaded documents, Ezra will let them know the recruiting team hasn't provided that information yet. The more relevant context you provide, the more questions Ezra can answer confidently.

How to add a document​

Upload a PDF, DOCX, or DOC file (up to 10 MB). For each document, add:

  • Description — A short summary of what the document contains. This helps Ezra understand what kind of information is in the file.
  • Importance — Why this document matters for the interview. For example: "This outlines the on-call rotation, which is a common candidate concern for this role."

Ezra reads the full text of each document you upload, so there's no need to highlight or extract specific sections — just upload the original file.

What makes a good context document?​

Think about the questions candidates are most likely to ask about this specific role, and upload documents that answer them. Good examples include:

  • Role-specific details not in the job description (team structure, reporting lines, day-to-day responsibilities)
  • Technical information (tech stack, development process, tools used)
  • Compensation and benefits details
  • Growth paths and promotion criteria
  • On-call schedules, travel expectations, or remote work policies specific to this role
Company-wide vs. interview-specific documents

Documents uploaded here apply only to this interview. If you have documents that should apply across all interviews (like company values, a benefits summary, or an employee handbook), upload them as Company Documents instead. Ezra references both company documents and interview-specific documents together when answering candidate questions.

Consistency check​

After uploading documents, you can run a consistency check. This analyzes everything Ezra knows about the role — the job description, role details, your uploaded documents, any company documents, and FAQ answers — and flags contradictions between them. For example, it might catch that the job description says "fully remote" while an uploaded team guide mentions a required office presence, or that two documents list different reporting managers.

Each flagged contradiction includes a clarifying question. You can resolve it by providing an answer, and Ezra will use your resolution as the source of truth going forward.

Candidate questions​

This section comes pre-populated with commonly asked candidate questions. As candidates complete interviews, Ezra identifies the most frequent questions they ask and automatically surfaces them here for you to answer.

Add answers to any question so Ezra can respond accurately in future interviews. Ezra will only answer candidate questions when it has defined information to draw from. It will not guess or make up answers.

Step 7: Take a test interview​

The test interview lets you have a live conversation with Ezra to preview how it will conduct the interview. Ezra has access to everything you've set up so far including your interview questions, benchmarks, context documents, company documents, and FAQ answers. You can test how it asks questions, follows up on answers, and responds when candidates ask their own questions.

This is a good opportunity to check whether Ezra has enough context to answer the kinds of questions candidates are likely to ask. If Ezra can't answer something, consider adding a context document or FAQ answer to cover it.

Not a simulated candidate interview

The test interview is a preview tool, not a replica of the candidate experience. The interface and flow are different from what candidates see. Nothing from the test interview is recorded, stored, or analyzed. It's purely for you to evaluate how Ezra will engage.

Step 8: Set up notifications​

Configure email and Slack notifications so your team is alerted when candidates complete their interviews.

  • Email notifications — Add email addresses to receive alerts when candidates complete their interviews. You can search for existing team members or add new ones.
  • Slack notifications — Connect a Slack workspace and select which channel should receive interview completion alerts.

Step 9: Customize the welcome screen​

The welcome screen is the landing page candidates see before they start the interview. By default, Ezra generates this page from your job description — it includes sections like "About this role," "Key responsibilities," "Requirements," and "About the company."

You can replace the default content with your own using the rich text editor, which supports formatted text, links, images, and embedded videos. This is a good place to set expectations about the interview format, share a welcome message, or highlight what makes the role or company appealing.

Click Reset to default at any time to revert to the auto-generated content from your job description.

Next steps​