From 59db5b292bc81db8e1c1d7eb03a62130af3f5ace Mon Sep 17 00:00:00 2001 From: Wolf Date: Sat, 3 Oct 2026 23:32:41 +0200 Subject: [PATCH] Ask for each interviewer's pasted profile before searching, since LinkedIn rarely renders for a fetch Co-Authored-By: Claude Opus 5.5 --- claude-skills/interview-prep/SKILL.md | 2 +- claude-skills/interview-prep/references/company-research.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/claude-skills/interview-prep/SKILL.md b/claude-skills/interview-prep/SKILL.md index 6699771..bf4446e 100644 --- a/claude-skills/interview-prep/SKILL.md +++ b/claude-skills/interview-prep/SKILL.md @@ -19,7 +19,7 @@ The application optimised what the company reads; this skill optimises what it h If any of the first four is missing, ask for it and stop. Do not reconstruct a posting or a CV from memory or from the web; a posting the owner cannot find again is stated as missing, and the pack is built without it only if he says so. -Then ask, in one message, for whatever the inputs do not already state: stage (screen, hiring manager, technical, case, panel, final), date, format (phone, video, onsite, take-home), interviewers (names and titles), and anything said in earlier rounds. +Then ask, in one message, for whatever the inputs do not already state: stage (screen, hiring manager, technical, case, panel, final), date, format (phone, video, onsite, take-home), interviewers (names and titles, and for each a pasted profile or its link: LinkedIn rarely renders for a fetch, so the owner's copy of the profile is the best source), and anything said in earlier rounds. ## Flow diff --git a/claude-skills/interview-prep/references/company-research.md b/claude-skills/interview-prep/references/company-research.md index b5a0071..c0dd032 100644 --- a/claude-skills/interview-prep/references/company-research.md +++ b/claude-skills/interview-prep/references/company-research.md @@ -17,7 +17,7 @@ Work through these, skipping what the inputs already answer: - [ ] Team or product area the role sits in: engineering blog, product pages, talks, open-source repos. - [ ] Media coverage: growth, funding, acquisitions, restructuring, layoffs, workplace issues. - [ ] Review sites (Glassdoor, Kununu, similar): recurring themes only, labelled as opinion. -- [ ] Each named interviewer: public professional profile (company page, LinkedIn as far as it renders, conference talks, published articles, public repos). +- [ ] Each named interviewer: first the profile the owner pasted or linked (ask for it when missing; LinkedIn rarely renders for a fetch), then public professional sources (company page, conference talks, published articles, public repos). A pasted profile counts as a source; note it as "pasted by the owner". ## Verify before use @@ -48,7 +48,7 @@ Stay within public professional information. No private social media, no family, ## Conversation hooks -Pick 2-3 recent, verified specifics (a product launch, a stated priority, a talk the interviewer gave) that the owner can mention naturally in "why this company" and in his questions. Each hook names its source. A hook the owner cannot comfortably talk about for a minute is not a hook; cut it. +Pick 2-3 recent, verified specifics (a product launch, a stated priority, a talk the interviewer gave) that the owner can mention naturally in "why this company" and in their questions. Each hook names its source. A hook the owner cannot comfortably talk about for a minute is not a hook; cut it. ## Call before applying