What this template is for
Interview feedback is the raw observation layer of a hiring process. Teams confuse it with the scorecard - the rating - and end up with feedback that is just a single sentence (“seemed great, hire”). This template separates the two: feedback captures what happened, the scorecard captures what it means.
It is designed for teams running structured interview loops who want to make hiring decisions defensible to the candidate, the manager, and the panel.
When to use it
Use this template for every structured interview slot in a hiring loop. Combine it with the hiring scorecard for senior or panel-based roles where evidence and rating need to be separated.
How to set it up in Jira
Add the custom fields above to your hiring project’s Create Issue screen. Use Custom Fields for Interview Type as a select list so dashboards can report on feedback completion by interview stage. Link each feedback issue to both the candidate Epic and the corresponding hiring-scorecard issue.
Sub-task breakdown
- Confirm questions ensures the interviewer enters the slot with a plan.
- Conduct the interview is the slot itself.
- Capture notes during the interview preserves freshness.
- Write up within 24 hours is the SLA gate.
- File and link to scorecard closes the audit trail.
Use STM Issue Templates to ensure these five sub-tasks appear on every interview-feedback issue automatically - see /stm-overview/.
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 | Interview feedback - System design - J. Patel | Yes |
Candidate Name (custom) | Jamie Patel | Yes |
Role / Requisition (custom) | Senior Backend Engineer (REQ-204) | Yes |
Interview Type (custom) | Phone screen / System design / Coding / Behavioural / Onsite | Yes |
Interviewer (custom) | Interviewer name | No |
Interview Date (custom) | 2026-05-21 | No |
Questions Asked (custom) | List of questions used | No |
Candidate Responses (custom) | Summary of what was said | No |
Observations (custom) | Behaviours noticed, signals collected | No |
Calibration Notes (custom) | How this candidate compares to recent hires at level | No |
Component/s | hiring, interviews | No |
Labels | req-204, system-design | No |
Attachments | Whiteboard photo, code sample, recording | 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 questions for the interview slot
- Conduct the interview
- Capture notes during the interview
- Write up feedback within 24 hours
- File feedback in the ATS and link to the scorecard
Common questions
What is a Jira interview feedback template?
It is a Jira task that captures the structured feedback from a single interview slot - the questions asked, candidate responses, observations, and calibration notes. It sits one level below the hiring scorecard: feedback is the raw observation, the scorecard is the rated synthesis. Both together give the debrief panel a defensible decision artefact.
How do you give interview feedback in Jira?
Create one Jira issue per interview slot using this template. Capture notes during the interview, then complete the writeup within 24 hours. Link the feedback to the candidate's parent issue and to the corresponding hiring scorecard. Use sub-tasks to enforce the 24-hour SLA and the ATS-filing step.
Should interview feedback and hiring scorecards be the same Jira issue?
They can be combined for lightweight hiring processes but separating them is better for senior or panel-based roles. Feedback is the raw observation - long, detailed, possibly free-form. The scorecard is the calibrated rating with an explicit recommendation. Separating them prevents the panel from anchoring on the rating before reading the evidence.
What custom fields belong on a Jira interview feedback issue?
Candidate, role, interview type, interviewer, interview date, questions asked, candidate responses, observations, and calibration notes. Configure Interview Type via Custom Fields as a select list (Phone screen / System design / Coding / Behavioural / Onsite). Required-on-create for interview type and interviewer.
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 →