Resource
API Request Variable Builder
Turns a reusable API request prompt into a clean variable set covering endpoint, method, auth, payload, response format, and error handling.
Job Description Variable Builder
Documents variables in job description prompt templates — role title, seniority, responsibilities, required skills, benefits, location, and hiring process.
Overview
Job description templates get reused heavily across roles and teams. When the same base template is adapted by different recruiting managers, {{responsibilities}} and {{duties}}, or {{requiredSkills}} and {{skills}}, appear as separate names for the same field across different versions. Beyond naming drift, the format expectations often differ too: responsibilities filled as bullet points in one copy, numbered steps in another. Documenting the variable set — names and format — before the template is shared prevents mismatched job posts across every hire.
How to use this resource
-
Open in Prompt Variable Builder
Load the job description template. The tool detects all eleven variables.
-
Check for similar variable names
If your team has used {{skills}}, {{requiredSkills}}, and {{skillsRequired}} in different versions of the same template, the similarity check will flag them. Rename to one consistent form before the template is shared.
-
Set types and add format descriptions
Responsibilities and requiredSkills are best typed as list. Add a description specifying whether bullet points, numbered steps, or plain prose is expected.
-
Export for recruiting tools
Use the JSON schema in the ATS integration. Use Markdown or CSV as the template reference for hiring managers.
Why This Works
- {{responsibilities}} and {{duties}}, or {{requiredSkills}} and {{skills}}, are the naming pairs most likely to appear across different recruiting team versions of the same template — consolidating them prevents substitution failures in ATS integrations
- Responsibilities is the variable most often filled in different formats across copies — a documented format expectation prevents bullet points in some posts and prose in others
- A variable schema shared with an ATS integration team prevents format mismatches before the automation is built
Best for
- Recruiting teams that generate job descriptions from a shared template across multiple roles
- Companies integrating job description prompts into an ATS or HR automation tool
- Hiring managers unfamiliar with the template format who need a clear variable reference
Not for
- One-off job posts written by hand for a single hire
- Roles with a completely custom description format that doesn't follow a standard structure
Use cases
- Standardising the job description template shared across a recruiting team — catching {{responsibilities}} and {{duties}}, or {{requiredSkills}} and {{skills}}, before they fork
- Documenting variable format expectations so recruiters fill in responsibilities as bullet lists, not paragraphs
- Generating a variable schema for an ATS integration that automates job description generation
- Exporting a CSV to divide responsibility for filling in each section across the hiring team
FAQ
How does this catch the same field showing up under different variable names?
The builder's similarity check flags near-duplicate names. Across recruiting-team copies the same field drifts into pairs like {{responsibilities}} and {{duties}}, or {{requiredSkills}} and {{skills}}, and the tool surfaces those so you rename to one form before the template is shared — preventing substitution failures when it feeds an ATS integration. It documents variables; it doesn't write the job posts or make any hiring decision.
Why document a format expectation for responsibilities and required skills?
Because those are the fields most often filled inconsistently. Step 3 types responsibilities and requiredSkills as list and has you add a description saying whether bullet points, numbered steps, or plain prose is expected — so one recruiter's post isn't bullets while another's is a paragraph. The prompt-variable-builder detects all eleven variables in the template for you to annotate.
What can I export to hand this off to an ATS or hiring managers?
Three formats for two audiences. Step 4 uses the JSON schema for an ATS integration and Markdown or CSV as the template reference for hiring managers — the CSV also lets you split responsibility for filling each section across the team. This is a documented variable set the tool derives; it neither generates descriptions nor makes any hiring decision.
More resources from Prompt Variable Builder
Resource
Landing Page Variable Builder
Cleans up variables in landing page prompt templates — headline, audience, pain point, offer, social proof, CTA, and objections.
Resource
User Story Variable Builder
Documents and exports variables from user story and acceptance criteria prompt templates — persona, goal, outcome, constraints, and definition of done.
Resources that pair well
Resource
Agent Task Template
A reusable AI agent task template with variables for objective, context, available tools, constraints, success criteria, failure handling, and output format.
Resource
Agent Instruction Prompt Formatter
Formats fuzzy agent instructions into a structured prompt with objective, available tools, constraints, success criteria, and failure handling.
Related tools
Tool
Prompt Variable Builder
Turn any plain prompt into a reusable, variable-based template — auto-detect values and export.
Projects that use this resource
Project
Build an Applicant Tracking System with AI
The full path to an applicant tracking system — model jobs, candidates, and hiring stages, generate job descriptions and screening prompts, parse résumés into structured data, design the hiring API, set roles, review security, then ship.
Workflows that use this resource
Workflow
AI Hiring Workflow
Run hiring the same way for every role — build a reusable job-description template, lay out a consistent screening sequence, and extract structured data from resumes instead of eyeballing each one.