← The Library
Recruiters lose one hour a dayto admin. These 9prompts do it all in seconds. Recruiter’s Swipe 
0 1 O F 0 9 Boolean Searches Turns a JD into search strings for LinkedIn and GitHub, plus where else to look. T H E P R O M P T Build me Boolean and platform search strings for a role I’m recruiting on. JD: [PASTE, or the company name and role title, and find the live listing] Location: [WHERE, and whether commutable or open] Surfaces: [LinkedIn Recruiter / LinkedIn basic / GitHub] Given a company and title instead of a JD, find the live listing, name which one and its date. If you can’t, say so and flag the strings as looser. Work out what identifies this person: titles held now and on the way up, tools, domain, company types, plus what nobody thinks of like old names, UK and US spellings, abbreviations, and the title a smaller company uses. Don’t show this working. Start with the first string. Cover every requirement, soft ones and bonus points included. Anything with a plausible proxy gets a string: product mindset as "product-minded", "0 to 1", "discovery"; ambiguity as founding engineer, early-stage, greenfield. Only after trying proxies does something go in the "can’t catch" list. LINKEDIN One full string for Recruiter. Then 6-9 shorter standalone strings, because basic LinkedIn and Sales Navigator silently drop terms past a certain complexity and return wrong results without erroring. Each takes a different angle (titles, core tech, secondary tech, domain, company type, seniority, soft requirements, bonus points) and must work alone. Label what each surfaces that the others won’t. Max two levels of brackets. GITHUB GitHub syntax, not Boolean: language:, location:, followers:, repos:. Separate user and code/repo searches, since they find different people. location: is free text, so give me the variants. WHERE ELSE TO LOOK Named repos, communities, Slack and Discord groups, meetups, conferences, companies with the right engineering culture, adjacent job boards. The actual ones, not the category. Every entry something I can open today. Rules: - Terms from the JD and from what appears on a real profile, not what the JD wishes were true. - Skip terms so common they add nothing. - Flag what Boolean genuinely can’t catch, after trying proxies, and what I do instead. 
0 2 O F 0 9 CV Write Up Writes the write-up that sits in front of a CV before it goes to a client. T H E P R O M P T Write the recruiter’s write-up that goes in front of a candidate’s CV before it’s sent to a client. CV: [PASTE] · Structure to follow exactly: [PASTE EXAMPLE WRITE-UP] · Role: [PASTE JD] Style: conversational, the way you'd explain the candidate to a hiring manager on a call. Full sentences, contractions fine, no bullet fragments. Open each point with years of experience in that specific thing, calculated from CV dates, so "Six years of TypeScript, across four roles" rather than "Strong TypeScript experience". Keep each point to two lines. Be specific about what they did, at what scale, and what changed. Let the evidence carry it. Never write: excellent, proven, ideal fit, perfect match, strong candidate, or a closing pitch. No em-dashes, no "not just X but Y", no "it’s worth noting", no colon-then-reveal, no scare quotes, no closing paragraph that repeats what you just said. Vary sentence length. Some short ones. Nothing in the write-up may read as a note to myself. No hedging about what the CV does or doesn’t show, no bracketed caveats, no meta-commentary. It goes to a client as it stands. Rules: - Every claim comes from the CV. Never infer skills, seniority, motivation, notice period, salary or availability. - If a skill has no datable start (it appears in a tech list with no bullet describing its use), drop the years opener and lead with what they did with it. Put the duration question in the gaps list at the end. - Gap in the structure the CV doesn’t cover: write "X - confirm with candidate" so I can fill it before sending. - Lead with the JD requirements they meet strongest, evidenced with their specific tech, metrics and scope. - Requirements the CV doesn’t evidence go at the end, not inside the write-up. Output: the write-up, then gaps and anything needing confirmation. 
0 3 O F 0 9 Interview Prep Builds prep for a specific stage, from your own prep doc and the latest feedback. T H E P R O M P T Write interview prep for a candidate going into a specific stage of a live process. House format to follow exactly: [PASTE ONE OF MY PREP DOCS] Previous prep for this role: [PASTE, or "none"] Candidate: [NAME, CV or summary] Stage and interviewers: [ROUND, WHO THEY'RE MEETING, FORMAT] New since last prep: [PASTE: feedback, client updates, anything that’s changed] Build from the previous prep. Keep what holds, cut what’s been overtaken, work the new information in where it belongs. New information wins wherever the two conflict. Every point must be specific to this candidate and this interviewer. If it can’t be tied to the CV, the JD, the previous prep or the new information, drop it. Style: written to the candidate, the way I'd brief them on the phone. Full sentences, contractions fine. No em-dashes, no "it’s worth noting", no colon-then- reveal, no closing paragraph repeating what you just said. Vary sentence length. Rules: - Never invent interviewer background, company detail, likely questions or client feedback. If it isn’t in an input, it isn’t in the doc. - Nothing about any other candidate, even if it’s in the pasted material. - This goes to the candidate as it stands. No notes to myself, no bracketed caveats, no hedging. Output: the prep doc, then what I need to chase before sending, then what changed since last version. 
0 4 O F 0 9 Write a Job Advert Researches the client and writes the advert, without naming anything confidential. T H E P R O M P T Write a job advert for a live role I’m recruiting on. JD or intake notes: [PASTE] Client: [NAME + WEBSITE] Anything I can’t name: [PASTE: client is confidential, salary not to be published, etc, or "nothing"] One of my adverts that worked: [PASTE, or "none"] Research the client yourself. Their own site, careers page, LinkedIn, Companies House, recent press. Pull what a candidate would actually want to know: what they build, stage and funding, size, offices, hybrid policy, anything they've said publicly about how they work. If the client is in the can’t- name list, still research them, but write around it and never name them or anything that identifies them. Match the voice of my example. If there’s no example, write plainly, second person, the way I'd describe the role to someone on the phone. Open with what the person will actually be doing, not a paragraph about the company. Lead with the tech, the scope, the money, the flexibility. Company context goes after that, kept short. Never write: fast-paced, dynamic, rockstar, ninja, wear many hats, hit the ground running, we’re like a family, exciting opportunity, or a closing line telling them to apply now. No em-dashes, no "it’s worth noting", no colon-then-reveal. Vary sentence length. Rules: - Everything in the advert comes from the JD or from something you found and can point to. Never fill a gap with a plausible guess. - Date anything that goes stale: funding, headcount, office moves. Old news in an advert makes me look like I don’t know the client. - If research and the JD disagree, the JD wins. Flag the conflict at the end. - Requirements come from the JD only. Don’t pad the must-haves, and don’t add years-of- experience figures the JD doesn’t give. - If the site won’t render or you can’t verify something, it goes in the confirm list, not the advert. Output: the advert, then what I need to confirm before posting, then what you found and where. 
0 5 O F 0 9 Screening Questions Technical screening questions for a role you don’t know, and what a good answer sounds like. T H E P R O M P T Build me screening questions for a technical role. Assume I’m not technical. JD: [PASTE] For each thing that actually matters in this JD, give me a question that separates good from average. Ask about decisions they made and problems they hit, not definitions or anything recitable from a tutorial. Write it in the language an engineer would use, technical terms included. For each question: - The question, word for word as I'd say it - What I just asked, in plain English - What a good answer sounds like, and what makes it good - What a weak answer sounds like, including the ones that sound impressive but aren’t - One follow-up if they're vague - A one-line answer to "what do you mean by that?" that doesn’t require me to bluff Rules: - Only what’s in the JD, weighted the way the JD weights it. - Nothing I couldn’t ask in a 20-minute phone call. - Tell me anything I can’t screen for over the phone, so I stop trying. Output: 6-8 questions, then the 3 to ask if I’m short on time, then a short explainer of what this role actually does day to day. 
0 6 O F 0 9 Redact a CV Anonymises a CV for client submission and lists everything it changed. Disclaimer: I recommend using a specialised tool for this, to protect the candidate’s data. T H E P R O M P T Redact the attached CV for anonymous client submission. Redact: full name (use "Candidate A"), phone, email, address, LinkedIn/GitHub/portfolio URLs, DOB, age, nationality, right-to-work or visa status, marital status, photo, referee details. Replace every employer name with a descriptor ("a Series B fintech, ~200 staff"), current and past. Catch names in body text, bullets, team names and award names too. Label them consistently so a reader can track which role is which. Convert every date range to duration only ("2 years 2 months"), counting inclusive of both end months. No months or years left anywhere, including education. For a role with no end date, write "(current)" and no duration, so don’t calculate one from today. Keep verbatim: tenure, tech, tools, metrics, achievements, scope, qualifications, industry descriptors. Preserve original formatting and section order. Rules: - Don’t paraphrase, improve or correct anything you keep, including typos. - Never fabricate. Every fact in the output must appear in the source CV, descriptors included. If an employer can’t be described generically without staying identifiable, say so. - Universities and schools aren’t employers, so their names stay unless I say otherwise. Output: the redacted CV, then every item removed and what replaced it, then any identifier still in there that could give the candidate away. 
0 7 O F 0 9 Pre-Call Research A two-minute briefing on a client before you get on the phone. T H E P R O M P T Pre-call research for a recruiter. Output is a briefing they'll scan in two minutes before the call. Company: [NAME + WEBSITE] · Niche: [NICHE] · Speaking to: [NAME + TITLE] · Prior history: [PASTE or "none"] Search the company’s own site, careers page, Companies House, LinkedIn and press before aggregators. Cover funding, leadership hires in the last 12 months, open roles, headcount, locations and hybrid policy, and any restructuring or exits. Weight by relevance to the niche. Output in this order: snapshot (4 lines max); hiring signals, newest first, each with a date and why it matters; open roles near the niche, with source and posted date; the person: role, tenure, prior companies, anything public on hiring; three questions, each tied to a dated fact above; then what you couldn’t find, item by item. Rules: - Date every fact and cite anything you'd hate to be wrong about. Never guess. Unknowns go in "couldn’t find". - Job listings go stale. Treat open roles as something to ask, not assert. - If the site won’t render, say so, and don’t report it as nothing found. - Name any similarly-named company crowding the search results. - Fewer than three hiring signals: give one line on what they do, one line saying there’s no public signal, the name clash, the couldn’t-find list, and stop. - Flag anything in the inputs that public sources contradict. - Leave out home addresses and dates of birth. - No advice on running the call, no summary, no filler. 
0 8 O F 0 9 LinkedIn Role Post Writes the post advertising a live role, hook first, client kept anonymous. T H E P R O M P T Write a LinkedIn post advertising a new role I’m working on. Role: [PASTE JD OR NOTES: seniority, contract/perm, package, hybrid working model, location] Client: [NAME + WEBSITE] One of my posts that worked: [PASTE, or "none"] Research their careers page and job boards for this role: stack, seniority, team shape, working model, salary. That’s research, not fact from me, so list it in the confirm section. Never use aggregator salary estimates. My notes beat research. Blank fields go in the confirm list, never guessed. Never name the client. Keep the sector, the problem, the rough stage, the city. Drop funding, investors, licences, revenue, founders, and the specific market. Two sentences on them, maximum. Structure: - Hook, under 8 words. Stops the scroll, lands the big idea, signals the client is worth working for, pulls them in, screens the wrong people out. About the market, not the vacancy. If it fits any role in any sector, rewrite it. - Blank line. - Rehook, under 8 words, moving them into the role. - The customer’s problem, pain made real. What goes wrong for them today, what this team does instead. - Who does well here, second person: the team they've worked in, domain experience that transfers, way of working that suits. This is the screen, so say what would make someone struggle. - Role details in my example’s structure: title and seniority, stack, team, location, package. - A call to action for the right person, telling them what to do and what they get. Then the line inviting everyone else to pass it on. Contact details last. Voice: match my example. Short lines, white space. Mobile truncates after two lines, so hook, blank and rehook must work alone. Never invent salary, stack, team size or working model. Never write: exciting opportunity, dream role, rockstar, hashtag walls, urgency lines. No em-dashes, no colon-then-reveal, no emoji rows, no "not just X, but Y" or "X, not Y" of any kind. One or two emojis, only if my example uses them. Output: five hook and rehook options scored against the five tests, then the post, then what to confirm and what came from research. 
0 9 O F 0 9 Market Insight Content Post Writes an engagement post about what has changed in your market, with sources. T H E P R O M P T Write a LinkedIn post about what’s happening in my market. Topic: [WHAT, e.g. TypeScript contract hiring in London, cloud rates in UK fintech] One of my posts that worked: [PASTE] My angle: [PASTE, or "none, find one"] Search what’s happened here in the last few months: funding, layoffs, hiring shifts, rate movement, new tooling, anything changing what candidates or clients want. Primary sources over roundups. Date everything. Pick a story that’s positive for my market, or negative with a contrarian angle I can argue. Never a straight negative. I’m not arming clients against my candidates or telling my own pool their market got worse. If everyone posted it last month, find the angle nobody took. Structure: - Hook, under 8 words, about the change, not about me. Stops the scroll and screens for people in this market. If it fits any market, rewrite it. - Blank line. - Rehook, under 8 words, moving them into the point. - What changed, with the specifics and dates that make it credible. - What it means for whoever I’m talking to, candidates or clients. The part they can’t get from the news itself. - A question worth answering. Not "thoughts?". Voice: match my example. Short lines, white space. Mobile truncates after two lines, so hook, blank and rehook must work alone. Never fabricate. Every number, date and trend traces to a source you found. No estimates, no rounded figures, no plausible gap-filling. If sources disagree, say so rather than picking one. Anything not in the sources is my opinion, not fact. No client names, candidate details, or salary figures from live processes. Never write: game-changer, paradigm shift, the future of work, hot take, numbered lists of lessons, urgency lines. No em-dashes, no colon-then-reveal, no emoji rows, no "not just X, but Y" or "X, not Y". Output: the post, then sources with dates, then anything to sanity-check against what I’m seeing myself. Download the PDF
Recruiters lose one hour a dayto admin. These 9prompts do it all in seconds. Recruiter’s Swipe 0 1 O F 0 9 Boolean Searches Turns a JD into search strings for LinkedIn and GitHub, plus where else to look. T H E P R O M P T Build me Boolean and platform search strings for a role I’m recruiting on. JD: [PASTE, or the company name and role title, and find the live listing] Location: [WHERE, and whether commutable or open] Surfaces: [LinkedIn Recruiter / LinkedIn basic / GitHub] Given a company and title instead of a JD, find the live listing, name which one and its date. If you can’t, say so and flag the strings as looser. Work out what identifies this person: titles held now and on the way up, tools, domain, company types, plus what nobody thinks of like old names, UK and US spellings, abbreviations, and the title a smaller company uses. Don’t show this working. Start with the first string. Cover every requirement, soft ones and bonus points included. Anything with a plausible proxy gets a string: product mindset as "product-minded", "0 to 1", "discovery"; ambiguity as founding engineer, early-stage, greenfield. Only after trying proxies does something go in the "can’t catch" list. LINKEDIN One full string for Recruiter. Then 6-9 shorter standalone strings, because basic LinkedIn and Sales Navigator silently drop terms past a certain complexity and return wrong results without erroring. Each takes a different angle (titles, core tech, secondary tech, domain, company type, seniority, soft requirements, bonus points) and must work alone. Label what each surfaces that the others won’t. Max two levels of brackets. GITHUB GitHub syntax, not Boolean: language:, location:, followers:, repos:. Separate user and code/repo searches, since they find different people. location: is free text, so give me the variants. WHERE ELSE TO LOOK Named repos, communities, Slack and Discord groups, meetups, conferences, companies with the right engineering culture, adjacent job boards. The actual ones, not the category. Every entry something I can open today. Rules: - Terms from the JD and from what appears on a real profile, not what the JD wishes were true. - Skip terms so common they add nothing. - Flag what Boolean genuinely can’t catch, after trying proxies, and what I do instead. 0 2 O F 0 9 CV Write Up Writes the write-up that sits in front of a CV before it goes to a client. T H E P R O M P T Write the recruiter’s write-up that goes in front of a candidate’s CV before it’s sent to a client. CV: [PASTE] · Structure to follow exactly: [PASTE EXAMPLE WRITE-UP] · Role: [PASTE JD] Style: conversational, the way you'd explain the candidate to a hiring manager on a call. Full sentences, contractions fine, no bullet fragments. Open each point with years of experience in that specific thing, calculated from CV dates, so "Six years of TypeScript, across four roles" rather than "Strong TypeScript experience". Keep each point to two lines. Be specific about what they did, at what scale, and what changed. Let the evidence carry it. Never write: excellent, proven, ideal fit, perfect match, strong candidate, or a closing pitch. No em-dashes, no "not just X but Y", no "it’s worth noting", no colon-then-reveal, no scare quotes, no closing paragraph that repeats what you just said. Vary sentence length. Some short ones. Nothing in the write-up may read as a note to myself. No hedging about what the CV does or doesn’t show, no bracketed caveats, no meta-commentary. It goes to a client as it stands. Rules: - Every claim comes from the CV. Never infer skills, seniority, motivation, notice period, salary or availability. - If a skill has no datable start (it appears in a tech list with no bullet describing its use), drop the years opener and lead with what they did with it. Put the duration question in the gaps list at the end. - Gap in the structure the CV doesn’t cover: write "X - confirm with candidate" so I can fill it before sending. - Lead with the JD requirements they meet strongest, evidenced with their specific tech, metrics and scope. - Requirements the CV doesn’t evidence go at the end, not inside the write-up. Output: the write-up, then gaps and anything needing confirmation. 0 3 O F 0 9 Interview Prep Builds prep for a specific stage, from your own prep doc and the latest feedback. T H E P R O M P T Write interview prep for a candidate going into a specific stage of a live process. House format to follow exactly: [PASTE ONE OF MY PREP DOCS] Previous prep for this role: [PASTE, or "none"] Candidate: [NAME, CV or summary] Stage and interviewers: [ROUND, WHO THEY'RE MEETING, FORMAT] New since last prep: [PASTE: feedback, client updates, anything that’s changed] Build from the previous prep. Keep what holds, cut what’s been overtaken, work the new information in where it belongs. New information wins wherever the two conflict. Every point must be specific to this candidate and this interviewer. If it can’t be tied to the CV, the JD, the previous prep or the new information, drop it. Style: written to the candidate, the way I'd brief them on the phone. Full sentences, contractions fine. No em-dashes, no "it’s worth noting", no colon-then- reveal, no closing paragraph repeating what you just said. Vary sentence length. Rules: - Never invent interviewer background, company detail, likely questions or client feedback. If it isn’t in an input, it isn’t in the doc. - Nothing about any other candidate, even if it’s in the pasted material. - This goes to the candidate as it stands. No notes to myself, no bracketed caveats, no hedging. Output: the prep doc, then what I need to chase before sending, then what changed since last version. 0 4 O F 0 9 Write a Job Advert Researches the client and writes the advert, without naming anything confidential. T H E P R O M P T Write a job advert for a live role I’m recruiting on. JD or intake notes: [PASTE] Client: [NAME + WEBSITE] Anything I can’t name: [PASTE: client is confidential, salary not to be published, etc, or "nothing"] One of my adverts that worked: [PASTE, or "none"] Research the client yourself. Their own site, careers page, LinkedIn, Companies House, recent press. Pull what a candidate would actually want to know: what they build, stage and funding, size, offices, hybrid policy, anything they've said publicly about how they work. If the client is in the can’t- name list, still research them, but write around it and never name them or anything that identifies them. Match the voice of my example. If there’s no example, write plainly, second person, the way I'd describe the role to someone on the phone. Open with what the person will actually be doing, not a paragraph about the company. Lead with the tech, the scope, the money, the flexibility. Company context goes after that, kept short. Never write: fast-paced, dynamic, rockstar, ninja, wear many hats, hit the ground running, we’re like a family, exciting opportunity, or a closing line telling them to apply now. No em-dashes, no "it’s worth noting", no colon-then-reveal. Vary sentence length. Rules: - Everything in the advert comes from the JD or from something you found and can point to. Never fill a gap with a plausible guess. - Date anything that goes stale: funding, headcount, office moves. Old news in an advert makes me look like I don’t know the client. - If research and the JD disagree, the JD wins. Flag the conflict at the end. - Requirements come from the JD only. Don’t pad the must-haves, and don’t add years-of- experience figures the JD doesn’t give. - If the site won’t render or you can’t verify something, it goes in the confirm list, not the advert. Output: the advert, then what I need to confirm before posting, then what you found and where. 0 5 O F 0 9 Screening Questions Technical screening questions for a role you don’t know, and what a good answer sounds like. T H E P R O M P T Build me screening questions for a technical role. Assume I’m not technical. JD: [PASTE] For each thing that actually matters in this JD, give me a question that separates good from average. Ask about decisions they made and problems they hit, not definitions or anything recitable from a tutorial. Write it in the language an engineer would use, technical terms included. For each question: - The question, word for word as I'd say it - What I just asked, in plain English - What a good answer sounds like, and what makes it good - What a weak answer sounds like, including the ones that sound impressive but aren’t - One follow-up if they're vague - A one-line answer to "what do you mean by that?" that doesn’t require me to bluff Rules: - Only what’s in the JD, weighted the way the JD weights it. - Nothing I couldn’t ask in a 20-minute phone call. - Tell me anything I can’t screen for over the phone, so I stop trying. Output: 6-8 questions, then the 3 to ask if I’m short on time, then a short explainer of what this role actually does day to day. 0 6 O F 0 9 Redact a CV Anonymises a CV for client submission and lists everything it changed. Disclaimer: I recommend using a specialised tool for this, to protect the candidate’s data. T H E P R O M P T Redact the attached CV for anonymous client submission. Redact: full name (use "Candidate A"), phone, email, address, LinkedIn/GitHub/portfolio URLs, DOB, age, nationality, right-to-work or visa status, marital status, photo, referee details. Replace every employer name with a descriptor ("a Series B fintech, ~200 staff"), current and past. Catch names in body text, bullets, team names and award names too. Label them consistently so a reader can track which role is which. Convert every date range to duration only ("2 years 2 months"), counting inclusive of both end months. No months or years left anywhere, including education. For a role with no end date, write "(current)" and no duration, so don’t calculate one from today. Keep verbatim: tenure, tech, tools, metrics, achievements, scope, qualifications, industry descriptors. Preserve original formatting and section order. Rules: - Don’t paraphrase, improve or correct anything you keep, including typos. - Never fabricate. Every fact in the output must appear in the source CV, descriptors included. If an employer can’t be described generically without staying identifiable, say so. - Universities and schools aren’t employers, so their names stay unless I say otherwise. Output: the redacted CV, then every item removed and what replaced it, then any identifier still in there that could give the candidate away. 0 7 O F 0 9 Pre-Call Research A two-minute briefing on a client before you get on the phone. T H E P R O M P T Pre-call research for a recruiter. Output is a briefing they'll scan in two minutes before the call. Company: [NAME + WEBSITE] · Niche: [NICHE] · Speaking to: [NAME + TITLE] · Prior history: [PASTE or "none"] Search the company’s own site, careers page, Companies House, LinkedIn and press before aggregators. Cover funding, leadership hires in the last 12 months, open roles, headcount, locations and hybrid policy, and any restructuring or exits. Weight by relevance to the niche. Output in this order: snapshot (4 lines max); hiring signals, newest first, each with a date and why it matters; open roles near the niche, with source and posted date; the person: role, tenure, prior companies, anything public on hiring; three questions, each tied to a dated fact above; then what you couldn’t find, item by item. Rules: - Date every fact and cite anything you'd hate to be wrong about. Never guess. Unknowns go in "couldn’t find". - Job listings go stale. Treat open roles as something to ask, not assert. - If the site won’t render, say so, and don’t report it as nothing found. - Name any similarly-named company crowding the search results. - Fewer than three hiring signals: give one line on what they do, one line saying there’s no public signal, the name clash, the couldn’t-find list, and stop. - Flag anything in the inputs that public sources contradict. - Leave out home addresses and dates of birth. - No advice on running the call, no summary, no filler. 0 8 O F 0 9 LinkedIn Role Post Writes the post advertising a live role, hook first, client kept anonymous. T H E P R O M P T Write a LinkedIn post advertising a new role I’m working on. Role: [PASTE JD OR NOTES: seniority, contract/perm, package, hybrid working model, location] Client: [NAME + WEBSITE] One of my posts that worked: [PASTE, or "none"] Research their careers page and job boards for this role: stack, seniority, team shape, working model, salary. That’s research, not fact from me, so list it in the confirm section. Never use aggregator salary estimates. My notes beat research. Blank fields go in the confirm list, never guessed. Never name the client. Keep the sector, the problem, the rough stage, the city. Drop funding, investors, licences, revenue, founders, and the specific market. Two sentences on them, maximum. Structure: - Hook, under 8 words. Stops the scroll, lands the big idea, signals the client is worth working for, pulls them in, screens the wrong people out. About the market, not the vacancy. If it fits any role in any sector, rewrite it. - Blank line. - Rehook, under 8 words, moving them into the role. - The customer’s problem, pain made real. What goes wrong for them today, what this team does instead. - Who does well here, second person: the team they've worked in, domain experience that transfers, way of working that suits. This is the screen, so say what would make someone struggle. - Role details in my example’s structure: title and seniority, stack, team, location, package. - A call to action for the right person, telling them what to do and what they get. Then the line inviting everyone else to pass it on. Contact details last. Voice: match my example. Short lines, white space. Mobile truncates after two lines, so hook, blank and rehook must work alone. Never invent salary, stack, team size or working model. Never write: exciting opportunity, dream role, rockstar, hashtag walls, urgency lines. No em-dashes, no colon-then-reveal, no emoji rows, no "not just X, but Y" or "X, not Y" of any kind. One or two emojis, only if my example uses them. Output: five hook and rehook options scored against the five tests, then the post, then what to confirm and what came from research. 0 9 O F 0 9 Market Insight Content Post Writes an engagement post about what has changed in your market, with sources. T H E P R O M P T Write a LinkedIn post about what’s happening in my market. Topic: [WHAT, e.g. TypeScript contract hiring in London, cloud rates in UK fintech] One of my posts that worked: [PASTE] My angle: [PASTE, or "none, find one"] Search what’s happened here in the last few months: funding, layoffs, hiring shifts, rate movement, new tooling, anything changing what candidates or clients want. Primary sources over roundups. Date everything. Pick a story that’s positive for my market, or negative with a contrarian angle I can argue. Never a straight negative. I’m not arming clients against my candidates or telling my own pool their market got worse. If everyone posted it last month, find the angle nobody took. Structure: - Hook, under 8 words, about the change, not about me. Stops the scroll and screens for people in this market. If it fits any market, rewrite it. - Blank line. - Rehook, under 8 words, moving them into the point. - What changed, with the specifics and dates that make it credible. - What it means for whoever I’m talking to, candidates or clients. The part they can’t get from the news itself. - A question worth answering. Not "thoughts?". Voice: match my example. Short lines, white space. Mobile truncates after two lines, so hook, blank and rehook must work alone. Never fabricate. Every number, date and trend traces to a source you found. No estimates, no rounded figures, no plausible gap-filling. If sources disagree, say so rather than picking one. Anything not in the sources is my opinion, not fact. No client names, candidate details, or salary figures from live processes. Never write: game-changer, paradigm shift, the future of work, hot take, numbered lists of lessons, urgency lines. No em-dashes, no colon-then-reveal, no emoji rows, no "not just X, but Y" or "X, not Y". Output: the post, then sources with dates, then anything to sanity-check against what I’m seeing myself.