Ask for each interviewer's pasted profile before searching, since LinkedIn rarely renders for a fetch

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Opus 5.5 committed 2026-10-03 23:32:41 +02:00
1 parent 7149cfd902
commit 59db5b292b
2 files changed
+3 -3

No files matched your search

@@ -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