OctiAI

Categories

Hiring-ready Job Description & Interview Scorecard Prompt

Convert role goals, hire rationale, and messy notes into a publishable JD, objective interview loop, and scoring rubric — ready for ATS and interviewers.

What You'll Get

How to Use

Provide crisp, labeled inputs and constraints up front

Include concrete role goals (3-5 outcomes), the hire rationale (why now, business impact), raw notes limited to the most relevant bullets or a 10-15 minute transcript excerpt, reporting line, and any location/visa/budget constraints — the more precise the inputs, the fewer clarifying questions and the tighter the JD and rubric.

Works Best With

Use this prompt pack when you need structured, auditable hiring artifacts from messy inputs

Prompt Template


## Goal
- Produce a hiring-ready job description and structured interview scorecard that can be used to post the role, screen candidates, run interviews, and make a hiring decision.

## Inputs
- Required inputs the prompt expects in plain text: Role goals, Hire rationale, Raw role notes (bullet list or transcript excerpt), Team/context (who the hire reports to and key stakeholders), Level/title (seniority and suggested title), Desired tone for JD (e.g., direct, friendly, technical), Hiring constraints (remote/on-site, timezone, visa, budget/comp band), and Desired timeline (target offer date).
- If any of these inputs are missing the assistant must ask concise clarifying questions before producing the deliverable.

## Prompt
You are a senior Talent Partner + hiring-practices expert. I will paste the required inputs below under exact labeled sections. First, check that each required input is present. If anything is missing or ambiguous, ask up to three concise clarifying questions and wait for answers. Only after all required inputs are provided, produce the deliverable.

When producing the deliverable, follow these exact stepwise instructions and output structure. Output must be in Markdown and use clear headings and bullet lists. Use measurable, specific language; avoid vague phrases like "works on projects." Do not invent facts about compensation, team size, or hiring approvals — instead mark them as assumptions if they were not supplied.

Deliverable requirements (produce all items exactly as listed):
1. Job title suggestion and one-line positioning summary (single sentence).
2. Short hiring rationale (2-4 bullets tying role goals to business outcomes).
3. Full job description:
   - Pager-style Purpose (2-3 lines).
   - Core responsibilities (10-14 concise bullet points, each a single sentence starting with an action verb).
   - Must-have skills (5-8 bullets; technical/behavioral; each testable).
   - Nice-to-have skills (3-6 bullets).
   - Reporting line, team size, and key cross-functional stakeholders (single bullet each; if unknown, state "Not provided").
4. Success metrics (present 4-6 measurable success metrics with time windows: 30/60/90 days and 6 months; format: metric → target → how measured).
5. Interview loop plan (stages numbered, owner for each stage, duration, core purpose, and pass/fail criteria per stage).
6. Structured interview guide:
   - For each interview stage, provide 4-6 targeted questions mapped to specific rubric criteria.
   - For each question include a one-line ideal answer signature and one-line red-flag indicators.
7. Scoring rubric / screening matrix:
   - List 6-8 evaluation criteria (skills, culture fit, problem solving, communication, role-specific).
   - For each criterion provide a 4-point scale: 4 = Excellent, 3 = Strong, 2 = Borderline, 1 = Poor. Give a one-line descriptor for each score level.
   - Define the pass threshold (e.g., average ≥3.0 and no critical criterion below 2).
   - Include an example scoring table row for a sample candidate.
8. Take-home or technical exercise spec (if role is technical), or a short case prompt for non-technical roles. Include deliverable expectations, time budget, and evaluation checklist.
9. Posting blurb (200-300 words, ready to publish on job boards) and a 2-line recruiter outreach message for passive candidates.
10. Manager's quick decision checklist to convert candidate scores into Hire / No-hire / Hold recommendations (include final approvers and required documentation).
11. Assumptions vs facts section: list explicitly what was taken from the inputs (facts) and what was inferred (assumptions). Flag any risks or unclear constraints that must be resolved before interviewing.
12. Next steps and timeline: 5 concrete actions with owners and ISO-format dates (if date inputs missing, use placeholders like "TBD by Hiring Manager").

Formatting rules for the assistant when generating the deliverable:
- Use headings and subheadings; bold owners and dates where specified.
- For scoring matrix use a compact table-like Markdown list (no external files).
- Provide at least 6 sample interview questions across stages, with mapping to rubric items.
- Do not include any discriminatory language. Ensure all questions comply with standard hiring legal/EEO practices.
- Keep the JD section concise enough for a job post while the interview guide and rubric should be sufficiently detailed for interviewers to execute without further clarification.

Now confirm you have received the inputs. If complete, produce the deliverable. If not, ask up to three clarifying questions.

After this block, I will paste the inputs under these exact labels:
Role goals:
Hire rationale:
Raw role notes:
Team/context:
Level/title:
Desired tone:
Hiring constraints:
Desired timeline:

## Output Format
- Use the SOP-style layout below for the entire deliverable:
  - Purpose → (Job title, one-line summary, purpose)
  - Scope → (level, reporting line, team/context, stakeholders)
  - Procedure → (hiring process steps / interview loop / sample questions / take-home / posting)
  - QA checks → (scoring rubric, pass thresholds, success metrics, interview calibration notes)
  - Escalation → (who approves offers, who to escalate unclear cases to, timeline for final decision)

## Guardrails
- Separate facts vs assumptions in a dedicated section. Do not present assumptions as facts.
- Do not create compensation figures, team headcount, or approval authorities unless provided; mark these items as "Not provided" and include a required-action to confirm them.
- Ensure each action/owner pair is explicit and uses full role names (e.g., Hiring Manager, Recruiter, Tech Lead).
- Make pass/fail criteria numeric and unambiguous.
- Do not propose interview questions that solicit medical, age, religion, marital, citizenship (beyond work authorization), or other protected-class information.
- If the role requires a take-home task that takes more than 4 hours of candidate time, require recruiter approval before assigning.
- Provide one-sentence justification for each must-have skill linking it to the role goals.

## Examples
- Mini decisions/actions excerpt:
  - Decision: Proceed to on-site interviews for candidate Jane Doe.
  - Actions: Recruiter to schedule on-site with Hiring Manager and Tech Lead by 2026-02-14; Hiring Manager to prepare 60-minute technical case; Recruiter to collect work authorization documents by 2026-02-12.

Variables

Usage Notes

Not for

Do not include

Hiring-ready Job Description & Interview Scorecard Prompt

Turn labeled inputs (role goals, hire rationale, raw notes, context, constraints, timeline) into a complete hiring artifact set: JD, responsibilities, must-have/nice-to-have skills, success metrics, structured interview loop, question bank with ideal answers/red flags, 4-point scoring rubric, take-home/case spec, posting blurb, and an auditable assumptions section.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

No placeholders required for this prompt.

Rules

Canonical Examples

Input: Hiring a Senior Backend Engineer to reduce API latency, increase system reliability, and own core services. Reports to Head of Engineering; remote-US hiring; target offer date 2026-03-15; role level Senior/IC4; tone: direct. Raw notes: improve latency <100ms, own payments & auth services, mentor junior engineers, write infra-as-code, run on-call rotation, deliver feature end-to-end.

Loading result...

Failed to load output.


Job title: Senior Backend Engineer — Build and operate low-latency, highly available core services that power customer transactions.
Success metric sample: API latency → <100ms p95 for core endpoints → measured by New Relic dashboards and release ticket closure.

Why it works: This example demonstrates the full deliverable for a technical hire: a concise JD, testable must-have skills tied to role goals, measurable 30/60/90/6mo metrics, a structured interview loop with technical and behavioral stages, a take-home exercise under 4 hours, and a clear rubric for fast, auditable hiring decisions.

Input: Hiring a Product Operations Manager to standardize launch processes, create playbooks, and improve cross-functional delivery. Reports to VP of Product; hybrid in SF (PT timezone); no visa sponsorship; target offer date 2026-04-01; level Manager; tone: friendly. Raw notes: needs stakeholder mapping, RACI, OKR alignment, run quarterly launch retros, create intake form, enforce release checklist, coordinate beta programs.

Loading result...

Failed to load output.


Purpose

- Job title suggestion: Product Operations Manager
- One-line positioning summary: Standardize launch processes and operationalize product delivery so cross-functional teams ship reliably and predictably.
- Pager-style Purpose (2-3

Why it works: This non-technical example shows the prompt’s ability to generate a hiring-ready JD and operational hiring artifacts for a program-oriented role: clear responsibilities, testable must-haves (process design, stakeholder management), a case-style take-home under 4 hours, measurable success metrics with time windows, interviewer questions mapped to rubric items, and a decision checklist for managers.

Works Best With

Use this prompt pack when you need structured, auditable hiring artifacts from messy inputs