RECREWD FIELD GUIDE · 8 MIN READ
How to prepare a profile for a hiring-manager introduction
Turn career history into a concise, evidence-led profile a hiring manager can understand quickly.
- For
- Experienced professionals preparing for networking or introductions
- Published
- Updated
SHORT ANSWER
The practical answer
A useful introduction profile answers five questions quickly: what role you want, where and how you can work, what problems you have solved, what evidence supports those claims and what conversation you want next. Keep it specific enough to route to the right person and broad enough to describe your real transferable value.
Start with the destination
Write down one primary role family, one adjacent option, preferred locations or remote arrangements and any firm constraints. “Open to anything” makes routing harder; a narrow title with no adjacent skills can hide good options.
Use language a hiring team would recognise. If your internal title is unusual, pair it with a widely understood function without misrepresenting your seniority.
Choose evidence, not adjectives
Replace claims such as “strategic” or “results-driven” with a short description of the situation, your responsibility, the action you took and the observed result. Keep the boundary of your contribution clear when work was shared.
Good evidence can be a measured business result, a delivered system, a change in cycle time, a portfolio item, a promotion, or responsibility for a defined scope. If a number is confidential, describe the direction and scale without inventing precision.
Worked example
Weak: “Innovative product leader with a proven track record.”
Stronger: “Product lead for a B2B workflow platform, responsible for discovery through launch across a six-person product and engineering group. Led a redesign that reduced median customer setup time from nine days to four, based on the company’s internal onboarding report.”
The stronger version identifies the function, scope, action, outcome and source of the number. It can be checked and discussed.
Build the introduction packet
A practical packet is short enough to review before a conversation and detailed enough to verify.
- One-sentence target: role family, industry or problem space and work location.
- Three evidence-backed achievements relevant to that target.
- A current CV selected for the role family.
- Constraints that affect fit, such as location or work arrangement.
- A clear request: exploratory conversation, feedback or consideration for a relevant opening.
Final accuracy check
Confirm every title, date, number and credential. Remove sensitive personal data that is not needed for the conversation. Ask whether a reader could mistakenly infer sole ownership, a larger scope or a guaranteed outcome from any sentence.
PUT IT INTO PRACTICE
A complete introduction packet
This fictional product-lead packet builds on the example above. The numbers, employer context and candidate preferences are illustrative. Replace them with the actual candidate’s verified facts and approval before sharing a real packet.
Target and adjacent option
Primary target: product lead in a B2B workflow business, owning discovery through launch. Adjacent option: senior product manager with comparable scope.
Preferred arrangement in this exercise: hybrid work in Vienna. Work authorization, notice period and compensation preferences remain questions for the actual candidate; this example does not assume them.
Introduction summary
Product lead for a B2B workflow platform, responsible for discovery through launch across a six-person product and engineering group. Led an onboarding redesign that reduced median customer setup time from nine days to four in the scenario’s internal onboarding report. Interested in teams where customer workflow complexity is a core product problem.
“Across a six-person group” does not imply six direct reports or sole responsibility for every implementation task.
Evidence one: the onboarding redesign
Attach a one-page case study covering the baseline, candidate decisions, collaborators, implementation and the nine-to-four-day result.
For a real packet, confirm the cohort, measurement window, exceptions and attribution before using the number. If those records are unavailable, describe the verified work without that precise result.
Evidence two and three: ownership and judgement
Use a redacted decision log to show discovery-to-launch ownership and distinguish decisions held by engineering or leadership. Confidential customer names are unnecessary.
Add a short explanation of how the candidate would investigate a similar workflow problem in a new organization. Label future hypotheses as proposals, separate from past achievements.
CV version and sharing preferences
Name the specific current CV version approved for this role family. List locations, constraints and any companies the candidate wants excluded.
Record what the candidate permits to be shared, the intended scope and how preferences can be changed. These are working-packet fields, not a claim that every product provides identical controls.
Conversation request and final check
“I would welcome a conversation about product roles involving complex customer onboarding or workflow design. I can share a redacted case study and explain the tradeoffs behind the redesign.”
Confirm the target, contribution boundaries, evidence, CV version and sharing permission. The request does not imply a vacancy, an existing relationship or a guaranteed introduction.
Make your own working copy
Download the plain-text template or open it below to copy into your preferred notes editor. Your working copy stays with you.
Download blank template (.txt)View and copy the blank template
Recrewd — A complete introduction packet Blank working template Use your own facts. Leave unknowns explicit. Do not include private or confidential material. Target role and adjacent option: [Complete here] Problem space and relevant employer types: [Complete here] Preferred location and working arrangement: [Complete here] Constraints and eligibility questions to confirm: [Complete here] Introduction summary: [Complete here] Evidence item one, source and contribution: [Complete here] Evidence item two, source and contribution: [Complete here] Evidence item three, source and contribution: [Complete here] Selected CV version: [Complete here] Sharing scope and company exclusions: [Complete here] Conversation request: [Complete here] Candidate approval, review date and next update: [Complete here]
Put this into practice
Use your introduction packet to explain your direction clearly. See how Recrewd uses a selected profile with your permission.
Sources and scope
This guide provides general educational information. It does not promise that a particular search, CV, introduction or hiring method will produce an interview or hire.