job-requirement-analysis

name	job-requirement-analysis
description	Guides recruiters through structured job requirement analysis covering 18 dimensions (technical stack, seniority, culture fit, compensation, hiring process, and more). Use when the user says "analyze this requirement", "intake call", "new role to fill", shares raw notes from a hiring manager, or wants to break down a job before sourcing.

Job Requirement Analysis

Quick Start

Paste your job description, hiring manager notes, or just say "I have a new role to fill" and this skill will walk you through a comprehensive requirement analysis.

Before You Begin

1. Check my-examples/ for past requirement analyses. If found, match the depth, format, and structure the recruiter prefers.
2. Check resources/ for PDF guides or mind maps on requirement analysis. Reference relevant insights.
3. Check ../playbooks/ for a playbook matching this role type. If found, incorporate role-specific intake patterns and mention it: "I found a playbook for [role type] — using it to guide this analysis."

How This Works

Walk the recruiter through each of the 18 dimensions below. For each dimension:

• If the user's input covers it: extract and structure the information
• If the user's input does NOT cover it: mark it as "TO ASK" with a suggested question for the hiring manager
• Never skip a dimension — completeness is the whole point

Analysis Dimensions

1. Technical Stack

• Interesting technologies used? (AI, VR, BigData, Cloud, etc.)
• Must-know technologies: programming languages, frameworks, libraries
• Platform: web (backend/frontend), mobile (native/cross-platform), desktop
• Specific versions required? (e.g., Angular 9, Python 3.11)

2. Core Competences

• Software development? (Backend / Frontend / Full-stack)
• Software architecture?
• Automated testing?
• Analysis, data science, DevOps, other?

3. Seniority

• Overall level: Trainee/Intern, Junior, Mid, Senior, Principal, Tech Lead, Manager
• Years of experience with specific technologies

4. Job Fulfillment

• Remote, hybrid, or on-site only?
• Flexible schedule or fixed hours?

5. Specific Background / Industry Experience

• Domain expertise needed? (e.g., frontend + SEO, CTO + FinTech, backend + no framework preference)

6. Certifications Required

• Any required certs? (AZ-104, CCNA, PMP, AWS Solutions Architect, etc.)

7. Sourcing Locations

• If on-site: where is the office?
• If remote: which destinations are OK?
• Where NOT to source from?

8. Personality & Culture Fit

• Crafter/maker or generalist/specialist?
• Builder or maintainer?
• How will they recognize who is a good fit beyond hard skills?

9. Hiring Process

• Who will screen new candidates?
• Who will organize technical assessment?
• How many interview rounds are expected?

10. Administration

• Recruitment contract signed?

11. Screening Questions

• Define 3-6 screening questions for initial candidate contact
• Suggest questions based on the role if none are provided

12. Relocation

• Is relocation OK?
• Are visas sponsored?
• Any relocation package?

13. Contract

• Part-time or full-time?
• Employment or freelance contract?
• Expected start date?
• Signed directly with the candidate or through Deel/Remote/Join.com?
• Paid holidays? How many days?
• Other benefits?

14. Compensation

• Salary range
• Monthly / daily / hourly rate?

15. The Position

• "Who is this a dream job for?"
• Red flags to watch for? (e.g., freelancers yes/no)
• Excluded companies? (no-poaching agreements)

16. Project

• What's interesting about it?
• Who uses the product?
• Interesting technologies or challenges ahead?
• Nature: build from scratch / maintenance / ongoing development / R&D / quick MVP?
• Milestones: short-term and long-term

17. Team

• Team size?
• Why do they like working at this company?
• Seniority of team members? Any superstars?
• Tools used? Work methodology? Best practices adopted?

18. Company

• The pitch: how would you introduce it?
• Company type: startup, agency, corporation, product company?

Output Format

Present the analysis as a structured document with all 18 dimensions. Use this format:

# Requirement Analysis: [Job Title]

## 1. Technical Stack
[Extracted info or "TO ASK: What technologies does the team use?"]

## 2. Core Competences
[...]

... (all 18 dimensions)

---

## Open Questions for Hiring Manager
1. [Question from dimension marked TO ASK]
2. [...]

What's Next

After completing the analysis, suggest: "Ready to build a scoring rubric? Use the ICP Builder skill with this requirement analysis."