Candidate Decline Feedback

Template Overview

Maintaining a respectful, rigorous hiring process requires documenting clear, objective justifications when declining candidates. The Candidate Decline Feedback Log structures interview committee evaluations, drafts constructive feedback for the candidate, and identifies high-potential talent for future re-engagement.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Decline Log: [Candidate Name]"
date: [YYYY-MM-DD]
hiring_manager: "[[Engineering Manager]]"
recruiter: "[[Lead Recruiter]]"
candidate_name: "[Candidate Name]"
target_role: "Senior Systems Engineer"
interview_stage_reached: "Final Round Architecture Debrief"
decline_reason: "Technical Leveling Mismatch / Systems Concurrency Depth"
future_reengagement: "Yes / Re-evaluate in 12 Months"
tags: [hiring, decline-log, feedback, candidate-experience, talent]
---

# Candidate Decline Feedback Log — [Candidate Name]

## 1. Interview Stage & Committee Consensus
- **Stages Completed:** Recruiter Screen, Technical Coding Pairing, System Design Architecture, Values Alignment.
- **Committee Decision:** **Decline for Current Senior Level**.
- **Consensus Rationale:** The candidate demonstrated strong high-level product design intuition but struggled with low-level concurrency primitives, memory management, and CoreAudio buffer lock mechanics required for our macOS engine.

## 2. Specific Interview Observations by Dimension
| Interview Stage | Evaluator | Rating | Key Objective Observation |
|---|---|---|---|
| **Technical Coding** | [[Alex Chen]] | 4.0 / 5.0 | Clean algorithm implementation; good code structure |
| **System Architecture**| [[Devin Zhao]]| 2.5 / 5.0 | Relied on cloud managed services; struggled with local threading |
| **Values Alignment** | [[Claire Evans]]| 4.5 / 5.0 | Excellent team player; strong intellectual humility |

## 3. Constructive Feedback Draft for Candidate
> [!TIP] Constructive Feedback Call Script (Recruiter)
> "The team was deeply impressed by your collaborative demeanor and clean TypeScript craftsmanship. However, for this specific Senior Systems role, we require deeper production experience with low-level multithreading, lock-free queues, and memory buffer management on macOS. We would love to stay in touch as our frontend product team expands next year."

## 4. Future Re-Engagement Profile
- **Candidate Strengths:** Rapid prototyping, exceptional empathy, clean API design.
- **Future Role Match:** Full-Stack Product UI Engineer (scheduled for Q2 2027 headcount).
- **Scheduled Outreach:** Add to recruiter talent pipeline for check-in in **9 months**.

## 5. Process Closure
- [x] Candidate notified via phone call with constructive technical feedback delivered.
- [x] Application archived cleanly in applicant tracking system.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Decline Log: Travis Miller"
date: 2026-10-06
hiring_manager: "[[Marcus Vance]]"
recruiter: "[[Rachel Adams]]"
candidate_name: "Travis Miller"
future_reengagement: "Yes"
tags: [hiring, decline-log]
---

# Decline Log: Travis Miller

## 1. Summary
Marcus Vance and Rachel Adams logged the decline rationale for Travis Miller. While Travis lacked low-level C++ experience needed for CoreAudio, his product instincts were stellar. Rachel will reconnect in 6 months for a product engineering opening.

When to Use and When to Avoid

When to Use

• Use immediately following hiring committee decisions to decline a candidate.
• Use to compose compassionate, actionable feedback for candidate phone calls.
• Use to build a high-quality talent re-engagement pipeline for future quarters.

When to Avoid

• Avoid using to document subjective personal impressions unrelated to job criteria.
• Avoid using before all committee interviewers have submitted independent rubrics.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the hiring committee decline discussion recording:
1. Summarize the objective technical and behavioral reasons why the committee decided to decline.
2. Draft constructive, respectful feedback points that can be delivered to the candidate by the recruiter.
3. Record future re-engagement suitability and follow-up timelines into structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.