mcpField
J
job-description-analyzer

job-description-analyzer

github.com/paramchoudhary生产力2.9k11.0k 次安装19 周前更新
代码仓库

关于 job-description-analyzer

面向求职者的职位描述分析技能,帮助判断是否申请以及如何准备。它会分类要求、估算匹配度,并指出差距和招聘信息中的风险信号。

主要功能

  1. 01区分必备与优先要求
  2. 02计算经历与职位匹配度
  3. 03识别优势与技能差距
  4. 04检测招聘信息风险信号
  5. 05规划简历与求职信内容

适用场景

  1. 01申请前评估职位匹配度
  2. 02筛选值得申请的职位
  3. 03找出申请材料需弥补的差距
  4. 04规划简历和求职信修改

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/paramchoudhary/resumeskills --skill job-description-analyzer

安装后在 Claude Code 中输入/job-description-analyzer确认已加载。

详细介绍

职位描述分析器

何时使用此技能

在以下情况下使用此技能:

  • 用户想分析职位招聘信息
  • 用户询问“我该申请这个职位吗?”
  • 用户想了解自己与某个职位的匹配百分比
  • 用户需要帮助理解职位要求
  • 用户想针对特定职位调整简历
  • 用户提到:“分析这个职位”“我符合资格吗”“匹配评分”“我该申请吗”

在调整简历之前使用此技能,确保投入精力是值得的。

核心能力

  • 提取并分类职位要求(必备与加分项)
  • 计算用户经验与职位要求之间的匹配评分
  • 识别技能差距和优势
  • 检测招聘信息中的危险信号
  • 确定应重点突出的经验
  • 制定简历调整策略
  • 创建求职信要点
  • 评估公司文化契合度指标

策略问题

大多数求职者在以下方面浪费时间:

  • 申请自身资历不足的职位(匹配度 <60%)
  • 申请自身资历过高的职位(可能很快离职)
  • 申请存在危险信号的职位(高离职率、有毒文化)
  • 盲目申请 50 多个职位,希望能碰上机会

更好的做法:

  • 有策略地申请 10-15 个职位
  • 以匹配度为 70-90% 的职位为目标
  • 针对每个职位深入定制
  • 获得更高的回复率,减少倦怠

分析流程

第 1 步:提取要求

将职位描述划分为以下类别:

必备要求

  • 学历要求
  • 工作年限
  • 特定技术技能
  • 认证/执照
  • 行业经验

优先条件(加分项)

  • “加分”技能
  • 高级认证
  • 领域专业知识
  • 特定工具使用经验

软技能/文化

  • 沟通风格
  • 工作环境
  • 团队结构
  • 公司价值观
第 2 步:提取关键词

识别三种类型:

硬技能(技术能力)

  • 工具:Salesforce、Python、AWS、Excel
  • 方法:Agile、Six Sigma、SDLC
  • 认证:PMP、CPA、AWS Certified

软技能(人际交往能力)

  • 领导力、协作能力、沟通能力
  • 解决问题的能力、批判性思维
  • 适应能力、主动性

行业/领域知识

  • B2B SaaS、医疗保健、金融科技
  • 企业级与 SMB
  • 法规知识(HIPAA、SOX、GDPR)
第 3 步:计算匹配评分
MATCH CALCULATION:

Required Skills:
- User has 8 out of 10 required = 80%

Preferred Skills:
- User has 3 out of 5 preferred = 60%

Overall Match:
- Weight required 70%, preferred 30%
- (80% × 0.7) + (60% × 0.3) = 74%

INTERPRETATION:
90-100% = Overqualified (may be flight risk)
75-89% = Excellent fit (apply immediately)
60-74% = Good fit (apply with strong cover letter)
50-59% = Stretch role (apply if passionate)
<50% = Under-qualified (skip unless dream job)
第 4 步:差距分析

针对每项缺失的要求:

  • 关键差距:一票否决项(不要申请)
  • 重大差距:影响显著但可以弥补(在求职信中提及)
  • 轻微差距:容易学会(淡化该差距或强调相关技能)
第 5 步:检测危险信号

扫描警示信息:

工作量危险信号:

  • “身兼多职”
  • “快节奏的环境”
  • “能够迅速上手”
  • “能在模糊的情况下主动开展工作”

文化危险信号:

  • “明星/忍者/专家”
  • “努力工作,尽情玩乐”
  • “无限休假”
  • “像一家人”

薪酬危险信号:

  • “有竞争力的薪酬”(不愿告知薪酬范围)
  • “股权占比高”(现金薪酬低)
  • “基于佣金”(没有底薪)
  • “视经验而定”,但未提供范围

匹配评分输出格式

# JOB ANALYSIS REPORT

**Position:** Senior Product Manager
**Company:** TechCorp Inc.
**Location:** San Francisco, CA (Hybrid)
**Salary Range:** $140K-$180K + equity

═══════════════════════════════════════════

## OVERALL MATCH SCORE: 78% ✅

**Recommendation:** STRONG FIT - Apply within 48 hours

**Application Priority:** HIGH
**Estimated Competition:** Medium (Posted 2 days ago)
**Time to Tailor Resume:** 30-45 minutes

═══════════════════════════════════════════

## REQUIREMENTS BREAKDOWN

### Required Skills - 8/10 ✅

✅ 5+ years product management (You have: 6 years)
✅ B2B SaaS experience (You have: 4 years)
✅ Agile/Scrum (You have: 5 years)
✅ Cross-functional leadership (You have: Strong experience)
✅ Data-driven decision making (You have: 3 years analytics)
✅ API products (You have: 2 years)
✅ Roadmap planning (You have: Extensive)
✅ User research (You have: 2 years)
❌ SQL/data analysis (You have: Basic Excel only) ⚠️
❌ Mobile product experience (You don't have) ⚠️

### Preferred Skills - 4/6 ✅

✅ MBA or equivalent (You have: MBA from UC Berkeley)
✅ Developer tools experience (You have: 2 years)
✅ Payment systems (You have: 1 year)
✅ International markets (You have: Worked with EU teams)
❌ E-commerce background (You don't have)
❌ Machine learning products (You don't have)

### Soft Skills - 5/5 ✅

✅ Stakeholder management (Strong mentions in your resume)
✅ Communication (You present regularly)
✅ Strategic thinking (MBA + senior experience)
✅ Influence without authority (You've done this)
✅ Customer empathy (User research experience)

═══════════════════════════════════════════

## STRENGTHS TO EMPHASIZE

**Your Top 3 Selling Points:**

1. **B2B SaaS PM Experience**
   - 4 years in SaaS, exactly what they want
   - Lead with this in resume summary

2. **API Product Background**
   - Your developer tools experience is highly relevant
   - This differentiates you from other candidates

3. **Data-Driven Approach**
   - Your analytics background addresses their need
   - Emphasize metrics and data in every bullet

═══════════════════════════════════════════

## GAPS TO ADDRESS

**Critical Gaps:** None ✅

**Major Gaps:**
⚠️ **SQL/Data Analysis**
- They mention this 5x in job description
- They want PM who can query data independently

**Strategy:**
- Don't avoid this gap
- Address in cover letter: "While my primary analytics work has been in Excel and BI tools, I'm actively learning SQL through DataCamp and can currently write basic queries"
- Emphasize your data-driven mindset and collaboration with data team

**Minor Gaps:**
- Mobile product experience (mentioned 2x)
- Not a dealbreaker - they want "any product," mobile just a plus

**Strategy:**
- Don't mention this gap
- If asked in interview, pivot to "transferable product skills"

═══════════════════════════════════════════

## RESUME CUSTOMIZATION STRATEGY

### Priority 1: Lead with Most Relevant Experience

**Current Resume Order:**
1. Company ABC - General PM work
2. Company XYZ - Your developer tools role
3. Company 123 - Early career

**Recommended Order:**
1. Company XYZ - Developer tools role (MOST RELEVANT)
2. Company ABC - B2B SaaS work
3. Company 123 - Only if space allows

### Priority 2: Keyword Integration

**Add These Exact Phrases:**
- "SQL and data analysis" (mentioned 5x in JD)
- "API product management" (mentioned 4x)
- "Developer-focused products" (mentioned 3x)
- "Stakeholder alignment" (mentioned 3x)

**Where to Add:**
- Professional Summary: Mention "API products" and "data-driven"
- Skills Section: Add "SQL (basic), Data Analysis, API Design"
- Experience: Weave into existing bullets

### Priority 3: Quantify Everything

They mention "metrics" and "KPIs" 7 times total.

**Enhance These Bullets:**

Current: "Led product roadmap"
Better: "Defined product roadmap based on analysis of 50+ customer interviews and usage data from 100K+ users"

Current: "Launched new features"
Better: "Launched 8 features in 12 months, increasing user engagement by 35% and reducing churn by 20%"

═══════════════════════════════════════════

## COVER LETTER TALKING POINTS

### Opening Hook (Choose One):

**Option 1 - Specific Company Knowledge:**
"I noticed TechCorp recently launched your API marketplace - I've spent the last 2 years as PM for a developer tools platform, and I'm excited about the opportunity to bring that experience to your growing API ecosystem."

**Option 2 - Mutual Connection:**
"[Name] on your product team mentioned you're looking for a PM to lead the API product line - my 2 years in developer tools and B2B SaaS background would be a strong fit."

**Option 3 - Problem-Solver:**
"Your JD mentions challenges in stakeholder alignment across technical teams - I've navigated this exact challenge at my current role, aligning engineering, design, and sales teams across 6 concurrent product initiatives."

### Body - Address the Match:
- "Your requirement for B2B SaaS experience: I have 4 years with..." 
- "Your focus on data-driven decisions: In my current role, I..."
- "Your need for API product expertise: At [Company], I..."

### Addressing SQL Gap (Optional):
"While my data analysis has primarily been in Excel and Tableau, I'm expanding my SQL skills and can currently write basic queries. More importantly, I've built strong partnerships with data teams and consistently use data to inform product decisions."

═══════════════════════════════════════════

## RED FLAGS ANALYSIS

### Potential Concerns: ⚠️ MINOR

**Flag 1:** "Fast-paced environment"
- Appears 2x in description
- Interpretation: Likely startup or high-growth
- May mean: Long hours, ambiguity, rapid changes

**Flag 2:** Salary range is wide ($140K-$180K)
- 29% spread
- May indicate: Experience range is flexible, or negotiation room

### Positive Signals: ✅

**Signal 1:** Detailed job description
- Shows company knows what they want
- Well-organized role

**Signal 2:** Mentions specific tools (JIRA, Amplitude)
- Shows operational maturity

**Signal 3:** Hybrid flexibility mentioned
- Modern workplace practices

### Company Research Needed:

Before applying, check:
- Glassdoor reviews (look for patterns in 1-2 star reviews)
- Recent funding/news (layoffs? growth?)
- LinkedIn: Check how long people stay (high turnover?)
- Levels.fyi: Verify salary range is accurate

═══════════════════════════════════════════

## APPLICATION TIMELINE

**✅ Day 1 (Today):**
- Customize resume (30-45 minutes)
- Write cover letter (30 minutes)

**✅ Day 1-2:**
- Submit application
- Connect with 2-3 current employees on LinkedIn
- Research company more deeply

**✅ Week 1:**
- Follow up if no response after 7 days

**📊 Expected Response Time:** 1-2 weeks

**📊 Interview Process (from job posting):**
1. Recruiter screen (30 min)
2. Hiring manager (1 hour)
3. Product case study (take-home)
4. Team interviews (3-4 hours)
5. Executive interview (1 hour)

═══════════════════════════════════════════

## DECISION FACTORS

### Reasons to Apply ✅

1. Strong match (78%) - You meet most requirements
2. Role aligns with career goals
3. Salary range is appropriate for your experience
4. Company stage fits your preferences
5. You have unique relevant experience (developer tools)

### Reasons to Hesitate ⚠️

1. SQL gap is real - prepare to address this
2. "Fast-paced" may mean high pressure
3. Need to research company culture more

### Overall Recommendation:

**APPLY - This is a strong opportunity**

You meet 80% of required skills and 67% of preferred skills. Your developer tools and B2B SaaS experience makes you a differentiated candidate. The SQL gap is addressable with honesty and emphasis on your analytical skills. Apply within 48 hours while posting is fresh.

要求分类指南

如何区分“必备要求”和“加分项”

表示必需的措辞:

  • “必须具备……”
  • “要求:……年……经验”
  • “你具备……”
  • “基本资格”
  • 列在“要求”一栏下
  • 在描述中提及 3 次以上

表示优先条件的措辞:

  • “有……更好”
  • “具备……可加分”
  • “优先资格”
  • “理想情况下,你应具备……”
  • “具备……将是加分项”
  • 仅提及 1-2 次
淘汰条件检测

绝对淘汰条件(不要申请):

  • 要求持有你没有的执照(医疗、法律、CPA)
  • 要求具备你无法获得的安全许可
  • 要求的经验年限比你多出 50% 或以上
  • 要求持有你没有的学位(明确写为“必需”时)
  • 有你无法满足的地点要求

不构成淘汰的条件(仍可申请):

  • 经验年限略低(例如,对方要求 5 年,你有 3 年)
  • 没有对方“优先考虑”的学位
  • 可以学习的锦上添花型工具/技能
  • 你拥有可迁移技能,但缺少相关行业经验

实施清单

分析职位时:

  1. ✅ 提取所有要求(必需与优先考虑)
  2. ✅ 识别所有关键词(硬技能、软技能、行业术语)
  3. ✅ 计算匹配度评分
  4. ✅ 找出需要重点突出的优势
  5. ✅ 找出差距并制定应对策略
  6. ✅ 检测危险信号
  7. ✅ 制定简历定制方案
  8. ✅ 生成求职信要点
  9. ✅ 调研公司
  10. ✅ 提供申请建议和时间安排

特殊情况

职位描述含糊
  • 标记为潜在危险信号
  • 尽可能提取关键词
  • 建议在申请前联系对方澄清
  • 以行业标准要求作为基准
一份 JD 包含多个职位
  • 区分核心职位与“其他职责”
  • 主要依据核心职责计算匹配度评分
  • 标记职责范围不断扩大的隐忧
内部招聘(已在该公司工作)
  • 采用不同策略,突出内部知识
  • 强调跨团队关系
  • 提及公司的具体计划
重新发布的职位
  • 可能意味着:之前的录用人选表现不佳、职位职责扩大,或首次招聘未成功
  • 值得申请,但应调查重新发布的原因
  • 查看要求是否与最初发布时有所变化

评论

支持 Markdown