call-summary.md

name	interview-summary
description	Convert a hiring interview transcript into a concise, scannable bullet-point summary written for an internal hiring audience (e.g. a teammate or co-founder). Use when the user pastes a call transcript and asks to summarise, recap, or write up an interview/candidate call.

Interview Summary

Turn a raw interview transcript into bullet points an internal stakeholder can read at a glance to decide on next steps.

Audience

Written for someone else at the company (hiring manager, co-founder, teammate). They already know the role and the company — do not restate role details, comp ranges quoted by the interviewer, company background, or process steps the reader already knows. Focus on what's new about the candidate.

Output format

• Pure bullet list. No headings, no preamble, no closing summary.
• Bold the key phrase in each bullet (the noun or fact a skimmer's eye should land on) — not whole sentences.
• One fact per bullet. Keep each bullet to 1–2 lines.
• 8–14 bullets typical. Stop when you run out of signal; don't pad.
• End with a Next step: bullet if one was agreed.

What to include

Prioritise in roughly this order:

1. Location / basic context (where they are, current situation)
2. Background — what they do now, how long, relevant prior experience
3. Motivation — why they're interested, what they're moving away from
4. Strengths / fit signals — concrete evidence (audience size, tools, prior shipped work)
5. Concerns or gaps — comp mismatch, conflicts, availability, things flagged for follow-up
6. Quality of their questions — were they sharp, prepared, strategic? This is signal.
7. Logistics they raised — side work, existing clients, conflicts of interest
8. Workflow / working style — how they operate, batch vs. continuous, tools
9. Next step — what was agreed

What to leave out

• Role details the reader already knows (cadence, format, metrics, tooling policy, meeting structure)
• Comp ranges the interviewer quoted — only mention comp if the candidate's number is the news (e.g. mismatch, expectation gap)
• Pleasantries, weather, scheduling friction, tangents
• The interviewer's own commentary unless it materially shaped the conversation

Tone

• Direct and evaluative, not transcriptive. "He asked sharp questions about X" beats "He asked about X, Y, and Z."
• Quote the candidate sparingly — only when the exact phrase is revealing ("occupies my mind far more than consulting").
• Flag concerns honestly. If there's a comp gap, conflict, or red flag, name it as such — don't bury it.

Example bullet shapes

• Matt is **UK-based** and runs his own **DevOps YouTube channel**, started ~1 year ago.
• Salary expectation is a potential gap: my ~£120k ceiling sits **below his £130–140k consulting income**. Stock may help bridge.
• He asked **sharp, well-prepared questions** about scope, tooling, cadence, and funding.
• **Next step:** test video brief out today; if it lands, intro to Veronica.

Process

1. Read the full transcript before writing anything.
2. Extract candidate-specific facts; discard interviewer monologue about the role.
3. Group by theme (background → motivation → fit → concerns → logistics → next step).
4. Bold the scannable phrase in each bullet.
5. Re-read as the recipient: would removing this bullet lose signal? If no, cut it.