What this template is for
Hiring scorecards exist to make interview signal comparable across candidates and interviewers. They fail when scorecards are submitted as free-form prose with no rubric, when interviewers wait a week to write them up, or when the recommendation is hidden inside a paragraph.
This template enforces a competency rubric, a 24-hour SLA on submission, and an explicit four-point hire / no-hire recommendation per scorecard.
When to use it
Use this template for every panel interview in a structured hiring process. Skip it for informal screens or referral conversations that have not yet formally entered the funnel.
How to set it up in Jira
Create a hiring-program project. Add the custom fields above to the Create Issue screen. Use Custom Fields for the Recommendation select list with the four named values. Build a per-candidate Epic that links every scorecard issue for that candidate so the debrief panel has one consolidated view.
Sub-task breakdown
- Confirm interview kit and rubric ensures the interviewer is using the right competencies.
- Run the interview is the interview itself.
- Score and document within 24 hours is the SLA that keeps signal fresh.
- Submit recommendation is the explicit hire / no-hire call.
- Participate in debrief is the calibration step.
Use STM Issue Templates to auto-create scorecard issues for every interview slot booked in the ATS via an integration, then apply the sub-task list with an Executor.
Fields to add to your Jira create screen
These are the fields a project admin should make sure exist on the Create Issue screen for this issue type (Project settings → Screens). Without these on the screen, reporters can't provide the information triage needs - and STM can't reference them either.
| Field | Example value | Required |
|---|---|---|
Summary | Scorecard - Senior backend engineer - J. Patel | Yes |
Candidate Name (custom) | Jamie Patel | Yes |
Role / Requisition (custom) | Senior Backend Engineer (REQ-204) | Yes |
Hiring Manager (custom) | Engineering manager name | No |
Interview Date (custom) | 2026-05-21 | No |
Competencies Assessed (custom) | System design, code quality, collaboration | No |
Competency Ratings (custom) | 1-4 per competency, with evidence | No |
Evidence / Examples (custom) | Verbatim examples per competency | No |
Strengths (custom) | Bulleted list with evidence | No |
Concerns (custom) | Bulleted list with evidence | No |
Recommendation (custom) | Strong hire / Hire / No hire / Strong no hire | Yes |
Component/s | hiring, scorecards | No |
Labels | req-204, senior-backend | No |
Attachments | Take-home assessment, recording, notes | No |
Note on custom fields. STM currently supports up to 5 custom fields per template. You can add as many custom fields as you like to your Jira Create Issue screen - the 5-field limit only applies if you want STM to set or update those custom fields itself.
Sub-tasks STM creates automatically
Build an STM sub-task template containing the items below, then wire it to an On Create Issue Executor scoped to this issue type. Whenever a new issue of this type is created in the project, STM creates the full sub-task set in one step - with assignee, due date, and components inherited from the parent unless you override them.
- Confirm interview kit and rubric
- Run the interview
- Score and document evidence within 24 hours
- Submit recommendation to hiring manager
- Participate in the debrief
Common questions
What is a Jira hiring scorecard template?
It is a Jira task that captures a single interviewer's structured assessment of one candidate against a role's competencies. It records competency ratings, evidence, strengths, concerns, and an explicit hire / no-hire recommendation. One issue per interviewer per candidate gives the debrief panel auditable, comparable inputs.
How do you build a hiring scorecard in Jira?
Create a hiring project. Use this template to file one issue per scorecard - per interviewer, per candidate. Populate the competency rubric in the role's job-kickoff issue and reuse it across every scorecard. Use the recommendation sub-task to enforce a 24-hour SLA on submission. Link all scorecards for a candidate to a parent candidate ticket.
Should hiring scorecards live in an ATS or in Jira?
The ATS (Greenhouse, Lever, Ashby) is the authoritative system of record for candidate status and offer workflow. Jira complements that with cross-team work tracking, hiring program management, and integration into engineering workflows. Many teams use Jira for hiring-program tasks (open req tracking, debrief scheduling) and the ATS for the candidate funnel itself.
What custom fields belong on a hiring scorecard?
Candidate name, role, hiring manager, interview date, competency ratings, evidence, strengths, concerns, and recommendation. Configure Recommendation via Custom Fields as a four-point select list (Strong hire / Hire / No hire / Strong no hire) to avoid wobbly 'maybe' answers. Required-on-create for recommendation so no scorecard is submitted without an explicit call.
Automate the sub-tasks with STM
STM Issue Templates saves the sub-task list above as a reusable template and creates them on every new issue of this type - via an Executor on issue creation, on status transition, or triggered manually from the issue's "Create bulk sub-tasks" menu. STM does not change the parent issue's create screen (that's a Jira project-settings job) but it removes the manual work of creating the sub-tasks every time.
Try STM on the Atlassian Marketplace ↗ See how STM templates are built →