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.
Workflow
-
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