ChatGPT Prompts for Recruiters: Briefs and Interview Prep

The most useful ChatGPT prompts for recruiters turn approved role requirements into clearer hiring materials: a role outline, a structured interview guide, or a candidate communication template. Give the assistant the source requirements, a defined output, and instructions to flag missing facts rather than invent them.

Keep this work separate from evaluating real applicants. Tools like fenbs can hold reviewed prompts and hiring process rules without applicant details, so another recruiter can reuse the same starting point. The examples below use fictional roles and placeholders; your hiring team reviews every result before it becomes part of a live process.

What should you give ChatGPT before drafting recruiting materials?

Start with a short, approved role outline. Include the work the person will do, the skills needed to do it, the work arrangement, and the recruiting stage. Separate required qualifications from preferences. If the hiring manager has not agreed on an important detail, leave it marked as an open question.

Avoid a vague instruction such as “find us a great culture fit.” Describe observable work instead: explaining a technical problem to a customer, organizing a delivery schedule, or reviewing a design against stated requirements. The prompt should prepare a useful document, not turn a loose impression into an assessment criterion.

Help prepare recruiting materials for a fictional [role]. Use only the approved role requirements below. Do not evaluate people or infer personal characteristics. Separate facts, proposed wording, and questions for the hiring manager. Do not add qualifications, benefits, compensation, dates, or promises. Output a draft for human review.
Approved requirements: [insert nonpersonal role information]

Our work prompt examples explain the broader pattern of goal, source material, constraints, and output. Here, the extra discipline is keeping the requirements tied to the job throughout every revision.

Which prompt helps clarify a role before it is advertised?

Ask for a requirements audit before asking for persuasive copy. A polished advertisement can hide a disagreement about what the role actually involves. Have the assistant identify duplicate requirements, unexplained jargon, and qualifications whose connection to the work is unclear.

Review these approved requirements for a fictional operations coordinator. Return a table: responsibility, stated requirement, reason the requirement matters, and unanswered question. Flag requirements with no stated connection to a responsibility. Suggest clearer wording separately. Do not add credentials or change required versus preferred status.
Requirements: [insert approved text]

For example, a hiring manager might request both “excellent communication” and “ability to explain delivery delays.” Ask whether the second phrase describes the actual skill the first was meant to capture. A person decides whether to replace it; the assistant provides a question and a wording option.

Review the finished role description against the original requirements, line by line. Confirm the location, schedule, responsibilities, and contact instructions. Save the chosen requirements and the reason for meaningful changes in fenbs Decisions and rules, so the next draft does not silently restore an old preference.

How can you prepare a structured interview guide?

Prepare the questions and review standards before interviewing anyone. The Office of Personnel Management explains structured interviews↗ (opens in a new tab) as job-related questions with consistent questions and rating standards. Use that structure to ask for a draft guide that your team can review, rather than a list of clever questions.

Using the approved responsibilities below, draft four interview questions for a fictional operations coordinator. For each, identify the job skill, a neutral follow-up, and observable evidence an interviewer could listen for. Use the same core questions for every applicant. Do not create candidate scores or recommend hiring decisions. Flag questions requiring HR review.
Responsibilities: [insert approved text]

An example question could ask how someone would organize two deliveries with conflicting deadlines. The review guide should focus on the explanation: what information they would gather, how they would communicate, and how they would identify a conflict. It should not reward a preferred personality, accent, or storytelling style.

Have the hiring manager check whether each question measures a real responsibility. Then have HR review the wording and the process, including how applicants can request an accessible application or interview process. A draft that looks consistent still needs that review.

What prompts make candidate communications more consistent?

Create separate templates for an invitation, a scheduling update, and a closing message. State the purpose and allowed facts for each. Keep individual names, addresses, application records, and interview notes in the approved recruiting system; the reusable template needs placeholders.

Draft three plain-language templates: interview invitation, scheduling delay, and application closure. Use placeholders for name, role, date, contact, and approved next step. Do not invent a rejection reason, promise feedback, or guarantee future consideration. Include a clear action only where one is required. List facts a recruiter must confirm before sending.

Check practical details as carefully as tone. A friendly invitation that omits the time zone, format, expected duration, or contact route creates avoidable questions. A delay message should say what is known and what happens next, without inventing a new deadline to make the sentence sound complete.

If the task is promoting a business rather than communicating about a hiring process, use the separate marketing prompt templates. That work has a different audience and review standard.

Which recruiting tasks need tighter boundaries?

Keep these prompts focused on preparing materials. Do not paste resumes, application answers, assessment results, or interview transcripts into a general drafting session. Do not ask the assistant to rank applicants, guess a protected characteristic, or infer suitability from a name or personal history.

The EEOC guidance on hiring questions↗ (opens in a new tab) describes restrictions on pre-offer disability questions and questions about genetic information. A prompt that says “be unbiased” does not establish that your interview complies with applicable requirements. Review the actual questions and workflow with the responsible HR or legal professional.

• Check every requirement against the approved role responsibilities.
• Remove unsupported claims about benefits, selection timelines, or employment terms.
• Test message placeholders so private details cannot become part of a shared template.
• Keep hiring judgments and applicant records in the authorized recruiting process.

Ask for a final comparison of the draft with its approved sources. OpenAI’s prompting guidance↗ (opens in a new tab) recommends specifying how you will use the output and reviewing important results yourself. Our system prompt examples can help you write reusable instructions, but instructions remain something you verify in the output.

How to do this with fenbs?

Use fenbs for the reusable process: prompts, nonpersonal role criteria, human decisions, and outstanding template reviews. Keep real applicant information out of this project. The value is a clear record of which version the team should use and what remains unapproved.

1. Create a free account and add a project for recruiting templates, using a fictional role to start.
2. Save the reviewed role audit, interview guide, and message instructions in Skills and prompts. State when each template applies.
3. Record the hiring team’s approved process rules in Decisions and rules. Leave unsettled criteria as questions for a person.
4. Connect a supported assistant from Integrations, ask it to read the project context before drafting, and save progress with the remaining review steps.

fenbs is not the right fit for applicant tracking, storing resumes, or making hiring decisions. Keep those activities in your organization’s approved systems and review process.

How do you know a recruiting prompt is ready to reuse?

Try it on a fictional role with a deliberately missing fact. The result should flag the gap, preserve the approved requirements, and leave personal decisions to people. If it invents a date or turns a preference into a requirement, tighten the instruction before saving it.

Store the purpose, approved inputs, reviewer, and revision reason with each template. Review it again when the role or process changes. The AI prompts hub has more examples, but a small library your team has actually checked is the useful starting point.