A recommendation-first note that helps a hiring manager decide quickly

Introducing a Candidate to a hiring manager is a short, high-stakes note. The manager is busy, the candidate is waiting, and the introduction has to establish fit without overselling. Lead with the reason this person is worth a conversation, not with a chronological resume. Choose two strengths that map directly to the role, and support each with one concrete proof point. Say what the candidate has done, where, and why it matters for this team. Then state the process step you are proposing. The note should read like a recommendation from someone who knows both sides, not like a forwarded profile with a greeting attached.
Pick strengths the role actually needs. If the team is rebuilding its onboarding flow, a candidate who has run onboarding experiments is more relevant than a candidate with a longer list of unrelated achievements. Read the role description before you write, and choose evidence that answers its hardest requirement. Two relevant strengths are enough; four dilute the message. Avoid adjectives that cannot be checked, such as 'rock star' or 'perfect fit'. A hiring manager trusts a specific example more than a strong opinion, and a specific example gives them a question to ask in the interview. That question is the beginning of a useful conversation.
Use one proof point per strength. 'Led a three-person team through a migration that cut release time' is a proof point; 'strong technical leader' is a label. The proof point should be short enough to fit in a sentence and specific enough to invite a follow-up question. If the candidate's work is not public, describe the scope and the result without revealing details that are not yours to share. The manager needs enough to decide whether to talk, not a full case study. Precision builds credibility, and credibility is what makes a short introduction work. It also gives the manager something to repeat when they discuss the candidate with colleagues.
Avoid superlatives and comparisons. 'The best engineer I have worked with' is hard to verify and can make a manager skeptical. 'Shipped the billing rewrite on a team of four' is easier to trust because it is bounded. If you want to convey enthusiasm, do it through the specificity of the example and the clarity of your recommendation. One sentence of genuine endorsement is enough: 'I would put her in front of your team tomorrow.' The rest of the note should give the manager reasons, not adjectives. A calm, concrete recommendation is more persuasive than a loud one. Enthusiasm is strongest when it is supported by a fact.
A hiring manager needs three facts before agreeing to a conversation: what the candidate does now, what they have done that matches the role, and whether they are genuinely interested. Put those three facts in the first paragraph. Current scope tells the manager how to calibrate the conversation. The relevant achievement tells them why this candidate is worth time. Expressed interest tells them the introduction is not a speculative fishing trip. Availability, notice period, and location can follow in a short line. The order matters because the manager is deciding whether to keep reading, and the first paragraph is where that decision is made.
Include the role context from the manager's side. Name the team, the problem it is hiring for, and the stage of the process. A candidate introduction that does not mention the role forces the manager to search for context. If the role is not public yet, describe the scope instead of the title. If the team is growing quickly, say what that means for the first six months. The manager should be able to see why this candidate, at this moment, for this team. Context turns a generic recommendation into a targeted one, and targeted notes get replies. A manager who has to search for the role will postpone the introduction.
Say why now. A hiring manager receives many introductions; the ones that get attention explain the timing. Maybe the candidate is interviewing elsewhere, maybe the team's next project starts in a month, or maybe the candidate's current contract ends soon. Timing is not pressure; it is context. State it plainly and without exaggeration. If there is no urgency, do not invent one. A calm 'there is no rush, but I wanted you to see this profile before the role closes' is more credible than a manufactured deadline, and it respects the manager's judgment. Timing is a reason to act, not a substitute for fit.
Keep the candidate's interest explicit. Say that you have spoken with the candidate, that they are interested in the role, and what they want to learn. Do not imply consent you do not have, and do not share details beyond what the candidate agreed to. A short line such as 'Priya has agreed to be introduced and is interested in the platform scope' is enough. The manager then knows the conversation is welcome. Explicit interest protects both sides, makes the next step easier to propose, and gives the candidate a clear expectation of what happens next. That expectation is part of a respectful introduction.
State the process step you are proposing. Is this a first exploratory call, a portfolio review, or a formal interview? The manager should not have to guess. Name the step, the duration, and who will arrange it. If the candidate is at a different stage, say so; a manager who expects an interview and receives a casual chat will feel misled. A clear step also helps the candidate prepare. The introduction is not the hiring process, but it should hand the process a clean starting point that both sides can act on. A clean starting point is the best thing an introducer can give a busy manager.
Name the contact owner. Say whether the manager or the recruiter will reach out, and through which channel. If the candidate should contact the manager first, say that too. Ambiguous ownership is a common reason candidate introductions stall, because each side waits for the other. A single sentence, such as 'I will ask Priya to send two times tomorrow, and you can pick one', removes the ambiguity. The owner should be a person, not a team or an inbox, and the sentence should say what that person will do first. The first move should be as clear as the first name on the note.
Keep documents minimal. Attach a role brief or a short candidate summary only if it helps the manager decide. A long resume, three references, and a portfolio link in the first note create work before interest exists. Offer the materials and say what they contain; the manager can ask for more. If a document is essential, name the one page that matters. The goal of the introduction is a conversation, not a complete application. Minimal materials also reduce the chance that a busy manager postpones the note until they have time to read everything. A small attachment with a clear purpose beats a large one with no owner.
End with the next action and an easy way to pause. 'If you are open to a 20-minute call, I will connect you; if the timing is wrong, tell me and I will hold the profile for the next opening.' This gives the manager a clear choice without pressure. It also tells the candidate what to expect. A candidate introduction that ends with an open question often produces a polite maybe and no movement. A specific next action with a clean pause gives both sides a decision they can make quickly, and it keeps the relationship intact for later.
Dictate the candidate introduction in blocks: the recommendation, the two strengths with proof, the role context, and the next step. Voiskey inserts each block at the insertion point and removes filler, stutters, and false starts, so the note reads as a considered recommendation rather than a spoken ramble. Keep the first block short; the manager should hear the recommendation before the evidence. Between blocks, check that you have not repeated a point. A candidate note is strongest when every sentence adds a reason to talk, and a block-by-block draft makes that easier to see. That structure also makes the spoken draft easier to review.
Set a factual, warm tone. Before you speak, say 'write this as a concise recommendation to a hiring manager' or 'keep this professional and specific'. Voiskey adapts punctuation, formatting, tone, and word choice to what you are trying to do. It also learns names, jargon, acronyms, and spelling preferences, which matters for candidate names, team names, and role titles. Say those once, check how they render, and correct any misspelling by voice. A consistent tone signals that the recommendation comes from a person who knows both sides, not from a form. The manager should hear a person who knows the candidate, not a performance.
Verify every factual detail by voice. Read the candidate's current role, the proof points, the process step, and the proposed time aloud, then correct any mismatch at the insertion point. Voiskey polishes the replacement in place, so the note stays in one field. If the candidate's title is unusual, spell it once. If the role has a specific internal name, use it. A single wrong detail can undermine an otherwise strong recommendation, so treat this pass as part of the writing, not an optional extra that someone else will catch. A short factual check is part of the recommendation, not an afterthought.
For cross-border hiring, dictate in the language you know best and request a translation, then compare both versions for the role, the proof points, and the next step. Voiskey supports more than one hundred languages and translation, and it learns names and terms you use often. Keep the subject line consistent across versions. When the note is ready, download Voiskey so the same block order is available on your other device, and use it for the next candidate introduction. Consistency in structure is what makes a recommendation easy to trust at a glance. The reader should feel the same confidence in either language.
After the introduction, check whether the manager engaged. Look for a reply that names a next step, not just an acknowledgement. If the manager asks a question, answer it in the same thread and restate the proposed action. If the manager is silent, wait a few business days, then send one short nudge that repeats the recommendation and the step. Do not forward the candidate's materials again or add new claims. The candidate is waiting, so a clear outcome matters even when the answer is not yet yes, and a calm nudge usually gets one. A specific step is easier to nudge than a vague hope.
Update the candidate with the same discipline. Tell them who has the note, what step is proposed, and when they should expect contact. Do not promise an interview you cannot guarantee. If the manager asks for more information, say what and by when. A candidate who knows the timeline is less likely to chase you and more likely to prepare well. The introduction is part of the candidate experience, and a clear update is part of a professional process. Silence from the introducer is often worse than a slow answer. A clear update is a small courtesy with a large effect on trust.
Debrief with the manager after the first conversation if you are looped in. Ask what was useful in the introduction and what was missing. That feedback improves the next candidate note more than any template. If the manager says the proof points were too general, make the next note more specific. If the role context was wrong, fix it before the next introduction. Record the pattern in a short note for the team, and keep the pattern short enough to reuse. A debrief turns one introduction into a better routine. Small corrections to the pattern are easier to keep than a full rewrite.
Review the candidate introduction routine every quarter. Check how many notes produced a conversation, which strengths were asked about, and where the process stalled. Update the block order and the proof-point style. Share the improved pattern with anyone who introduces candidates for the team. Download Voiskey on each work device, keep the recommendation-first order, and let the routine carry the quality. A good candidate introduction is not a single polished note; it is a repeatable way of connecting strong people to the right conversations, and the review is what keeps it sharp. That is how a single good introduction becomes a reliable practice.
Dictate in four blocks: the recommendation, two relevant strengths with proof, the role context, and the next step. Voiskey inserts polished text at the insertion point and removes filler, so the note reads as a concise recommendation. Then check names, titles, and dates by voice before sending.
Emphasize fit rather than a full history: what the candidate does now, one achievement that matches the role, and expressed interest. Add the proposed process step and who will contact whom. Speak the recommendation first so the note opens with it, then check the draft before sending.
Yes. Voiskey learns names, jargon, acronyms, and spelling preferences. Say unusual names and internal role titles once, check how they appear in the draft, and correct any misspelling by voice. Those details stay consistent across the note, which matters when a recommendation carries a person's professional reputation.
Check for a reply that names a next step, not a polite acknowledgement. If there is none, send one short nudge that repeats the recommendation and the proposed action. Update the candidate with the same timeline. Voiskey can polish that nudge in the existing thread, keeping the tone calm and specific.

Download Voiskey for Mac and Windows and turn a rough spoken draft into a clear, reply-ready note.
Use it across macOS, Windows, iOS, and Android