一键导入
apply
Research-backed job application workflow emphasizing relationship-building over mass applications
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Research-backed job application workflow emphasizing relationship-building over mass applications
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Process a batch of job applications - discover roles, prepare materials, pre-fill forms. Use when ready to apply to multiple positions.
Style guide for writing that doesn't sound AI-generated. Use when drafting cover letters, emails, or any professional communication.
Analyze resume against job description for ATS optimization and keyword gaps
Generate tailored interview questions and practice with STAR method feedback
Search for jobs across multiple boards and company career pages. Use when looking for new positions to apply to.
| name | apply |
| description | Research-backed job application workflow emphasizing relationship-building over mass applications |
This workflow is grounded in career development research:
The online application is a formality. The real work is relationship-building.
Traditional approach: 100 applications → 2 interviews → maybe 1 offer
Relationship approach: 10 targeted companies → 5-7 conversations → 3+ interviews → multiple offers
The difference: You're not competing with 600 applicants. You're having conversations before jobs are posted.
NOT: "Who is hiring for roles I want?" YES: "Whose work do I find genuinely interesting?"
This is the key difference. You're not working backwards from a job posting to find someone to spam.
Claude does:
User does:
The test: Could you email this person even if they had no job openings?
Before reaching out, know:
Three rules for networking emails:
Template:
Hi [Name],
My name is [Your Name] and I came across your [specific work]
while [how you found it].
Your [specific thing] really stood out to me — [why it interested you].
I'd love to learn more about [specific aspect].
I know you're busy. If you have 15-20 minutes, I'd be grateful.
If not, totally understand.
Best,
[Your Name]
Subject lines that work:
Goal: Learn about their work. NOT to pitch yourself.
Questions to ask:
Key: Ask about THEIR experience. Don't pitch yourself.
After the call: Thank-you email within 24 hours. Include something valuable if possible.
For roles you really want, create a deliverable that proves you understand their problems.
What it is: A deck, analysis, or prototype showing how you'd approach their challenges.
Structure:
When to use: Only for top targets. This is high-effort.
Only after:
Now fill out the form. This is the formality, not the strategy.
Don't lead with "I applied for your job"
Don't send the same template to everyone
Don't pitch yourself in first contact
Don't ask for a job
Track every outreach for appropriate follow-up timing.
| Action | Follow-Up Window | What to Do |
|---|---|---|
| Cold email sent | 5-7 days | Brief "bumping this up" |
| Informational call | 24-48 hours | Thank you + value-add |
| Application submitted | 14-21 days | Check in on status |
| Second follow-up | 7-14 days later | Final gentle check-in |
| No response after 2 | Move on | Don't spam |
After cold email (no response):
Hi [Name], just bumping this up. [Original ask]. No worries if timing doesn't work.
After application (14+ days):
Hi [Name], I applied for [role] a couple weeks ago. Still interested in [specific thing]. Anything else I can provide?
After informational call:
Thank you for the conversation. [Specific learning]. Found [resource] related to [what they mentioned].
{
"company": "Company Name",
"role": "Role Title",
"applied_date": "2024-01-15",
"outreach": [
{
"type": "cold_email",
"recipient": "Jane Smith",
"sent_date": "2024-01-10",
"response_date": null,
"next_follow_up": "2024-01-17"
}
],
"status": "applied",
"next_action": "follow_up",
"next_action_date": "2024-01-29"
}