Role Intake Strategy Session

Template Overview

Sourcing the wrong candidates wastes dozens of engineering hours. The Role Intake Strategy Session template aligns hiring managers and recruiting leads before a job is posted, defining precise evaluation rubrics, target talent pools, non-negotiable competencies, and interview stage ownership.

Markdown Template Structure

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

---
title: "Role Intake: [Job Title / Requisition ID]"
date: [YYYY-MM-DD]
hiring_manager: "[[Engineering Director]]"
lead_recruiter: "[[Lead Technical Recruiter]]"
job_requisition_id: "REQ-2026-ENG-14"
target_role_title: "Staff Audio Systems Engineer"
approved_compensation_band: "$185,000 - $215,000 + Equity"
target_hire_date: "[YYYY-MM-DD]"
tags: [intake, recruiting, headcount, hiring, job-spec]
---

# Role Intake Strategy Session — [Job Title / Requisition ID]

## 1. Business Justification & Mission Impact
- **Why this role exists now:** Expanding our on-device audio pipeline to support multi-channel audio loopback and ScreenCaptureKit device switching.
- **Success in 12 Months:** The engineer has eliminated 100% of audio buffer underruns and benchmarked local Whisper models across macOS Sequoia.
- **Reporting Hierarchy:** Reports directly to [[Head of Systems Architecture]].

## 2. Candidate Profile & Competency Breakdown
| Competency Dimension | Absolute Must-Haves (P0) | Nice-to-Haves (P1) | Anti-Profiles (Disqualifiers) |
|---|---|---|---|
| **Core Systems Programming** | 5+ yrs Swift/Objective-C/C++ | Rust memory experience | Exclusive web frontend JS developers |
| **macOS Audio Frameworks** | Deep CoreAudio & ScreenCaptureKit | AudioUnit plugin authoring | Engineers reliant only on cloud APIs |
| **Local-First Philosophy** | Passion for user data privacy | Personal Obsidian vault user | Advocates for multi-tenant cloud storage |

## 3. Target Sourcing Pools & Companies
- **Target Organizations:** Companies with desktop macOS client depth (e.g. Rogue Amoeba, Panic, Ableton, Apple, Algoriddim).
- **Communities:** macOS developer forums, audio DSP discords, SwiftLang open-source contributors.

## 4. Structured Interview Loop Architecture
1. **Recruiter Screen (30m):** [[Lead Recruiter]] — Background, motivation, comp alignment.
2. **Technical Pairing (60m):** [[Staff Engineer 1]] — Real-time audio buffer ring queue coding.
3. **Architecture Review (60m):** [[Principal Architect]] — ScreenCaptureKit pipeline design.
4. **Peer Panel (45m):** [[Cross-Functional Peers]] — Empathy, PR reviews, teamwork.
5. **Bar Raiser (45m):** [[Independent Bar Raiser]] — Long-term principles and craft.

## 5. Recruiter Sourcing Commitments
- [ ] Recruiter to deliver initial calibration batch of 5 candidate profiles by Friday.
- [ ] Hiring manager to review calibration batch within 24 hours to tune sourcing filters.

Filled Real-World Example

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

---
title: "Intake: Staff Documentation Architect"
date: 2026-10-06
hiring_manager: "[[Elena Rostova]]"
lead_recruiter: "[[Rachel Adams]]"
job_requisition_id: "REQ-902"
tags: [intake, recruiting]
---

# Intake: Staff Documentation Architect

## 1. Intake Summary
Elena Rostova aligned with Rachel Adams on the Staff Documentation Architect role. The candidate must possess deep experience with Markdown ASTs, CommonMark specifications, and programmatic SEO architecture.

When to Use and When to Avoid

When to Use

• Use when opening any new hiring requisition before publishing the job description.
• Use to establish agreement between hiring managers and recruiters on talent profiles.
• Use to design the structured interview loop and assign interview stage owners.

When to Avoid

• Avoid using for evaluating individual candidate interviews.
• Avoid using for routine weekly recruiter status meetings.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the role intake strategy session recording:
1. Extract must-have technical qualifications, target candidate backgrounds, and disqualifying anti-profiles.
2. Outline the agreed interview loop stages, stage durations, and assigned engineering interviewers.
3. Record compensation bands, target hire dates, and recruiter sourcing commitments into clean Markdown.

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