# Resume Generation Guide
## Configuration Requirements
- **Link format:** "https://www.linkedin.com/in/andrea-cadonna-3833451a5 https://github.com/AndreaCadonna"
- **Resume template:** Always use template number 1
- **Personal project:** Always include and last section on resume
- **Output tool:** Use MCP resume-generator tool with JSON format
- **Introduction:** Use the award property as field to write an introduction line following these strict requirements:
- MUST include "almost 5 years of experience"
- Maximum 2 sentences
- MUST include 1-2 soft skills from job requirements (exact phrases when possible)
- Focus on personal technical expertise and capabilities
- NO industry context references unless explicitly stated in experience dataset
- NO company-specific or platform-specific references not in knowledge base
- Structure: [Job Title] + experience duration + core technical focus + demonstrated soft skills
---
## MANDATORY CONSISTENCY CHECKLIST
### Pre-Generation Verification (Execute EVERY Time)
**STOP - Complete this checklist before generating any resume:**
✅ **Job Title Exact Match Check:**
- [ ] Does target job title match any compatible title group?
- [ ] Does target include "Senior" prefix? (Only use if job explicitly states it)
- [ ] Have I verified the EXACT title from job posting?
✅ **Keyword Extraction Verification:**
- [ ] Have I extracted ALL hard skills from job description?
- [ ] Have I identified ALL soft skill exact phrases?
- [ ] Have I categorized each as Must-have vs Nice-to-have?
✅ **Experience Matching Validation:**
- [ ] Can I point to specific experience for each claimed skill?
- [ ] Am I using EXACT keywords from job description?
- [ ] Are soft skills demonstrated through specific examples with exact phrases?
---
## Step 1: Systematic Job Description Analysis
### 1.1 Required Keyword Extraction Protocol
**🎯 Hard Skills Extraction (Mandatory Process):**
**STEP A: Copy ALL technical requirements exactly as written:**
- Programming Languages: [List exactly as in job]
- Frameworks: [List exactly as in job]
- Tools: [List exactly as in job]
- Databases: [List exactly as in job]
- Methodologies: [List exactly as in job]
**STEP B: Categorize by priority:**
- **REQUIRED:** Keywords in "must-have," "required," or "essential" sections
- **PREFERRED:** Keywords in "nice-to-have," "preferred," or "bonus" sections
- **IMPLICIT:** Technical requirements mentioned in job duties
**🤝 Soft Skills Extraction (Exact Phrase Protocol):**
**STEP A: Extract exact phrases (copy-paste from job description):**
- Communication requirements: [Exact phrases]
- Leadership requirements: [Exact phrases]
- Work style requirements: [Exact phrases]
- Collaboration requirements: [Exact phrases]
**STEP B: Create exact phrase integration list:**
| Exact Job Phrase | Must Include In Resume | Bullet Point Strategy |
|-----------------|----------------------|----------------------|
| "Cross-functional collaboration" | ✅ Exact phrase required | Lead bullet with exact phrase |
| "Analytical thinking" | ✅ Exact phrase required | Include in problem-solving bullet |
| "Ownership and accountability" | ✅ Both terms required | Combine in leadership bullet |
### 1.2 Experience Dataset Mapping (Mandatory Verification)
**STEP A: Create skills inventory from experience:**
```
MY ACTUAL EXPERIENCE INVENTORY:
Hard Skills - Direct: [Angular 2+, RxJS, TypeScript, etc.]
Hard Skills - Transferable: [Related technologies I've used]
Soft Skills - Demonstrated: [Leadership examples, collaboration examples]
Quantified Results: [Specific metrics I can verify]
```
**STEP B: Match against job requirements:**
| Job Requirement | My Experience Status | Exact Keywords to Use | Verification Source |
|----------------|---------------------|---------------------|-------------------|
| Angular 2+ | ✅ Direct (5 years) | "Angular 2+" | NEG Digital role |
| Cross-functional collaboration | ✅ Demonstrated | "cross-functional collaboration with design and product teams" | NEG Digital role |
| Performance optimization | ✅ Direct | "performance optimization techniques" | Multiple roles |
---
## Step 2: Job Title Optimization (Strict Protocol)
### 2.1 Title Matching Decision Tree
**DECISION FLOW (Follow exactly):**
1. **Is my current title identical to job title?**
- YES → Keep current title
- NO → Go to step 2
2. **Is job title in compatible group with my experience?**
- Compatible Groups:
- Full Stack Developer ↔ Full Stack Software Engineer ↔ Software Engineer ↔ Software Developer
- Frontend Developer ↔ Frontend Software Engineer ↔ Frontend Engineer
- Backend Developer ↔ Backend Engineer ↔ API Developer
- YES → Use job title exactly
- NO → Keep current title
3. **Does job title include "Senior" and I have 3+ years experience?**
- YES → Add "Senior" prefix
- NO → Use base title only
4. **Does job title include specific technology (React Developer, Angular Developer)?**
- AND do I have 2+ years with that technology?
- YES → Use technology-specific title
- NO → Use general title
### 2.2 Title Verification Protocol
**Before finalizing, verify:**
- [ ] Title exactly matches job posting (character-by-character)
- [ ] Seniority level matches my actual experience
- [ ] I can defend this title in an interview
- [ ] Title appears in my most recent role only
---
## Step 3: Exact Keyword Integration Formula
### 3.1 Bullet Point Construction Protocol
**MANDATORY TEMPLATE:**
```
[Action Verb] + [EXACT job keyword/phrase] + [specific deliverable] + using [EXACT tech from job] + which [quantified result]
```
**EXAMPLES:**
**For "Cross-functional collaboration" requirement:**
```
Led cross-functional collaboration with design and product teams to develop [specific feature] using Angular 2+ and RxJS, which improved user experience metrics by [X]% for [trading platform/business system]
```
**For "Performance optimization" requirement:**
```
Implemented performance optimization techniques including lazy loading and bundle optimization using Angular 2+, which reduced load times by [X]% and improved application startup performance for [specific platform type]
```
**For "Analytical thinking" requirement:**
```
Applied analytical thinking to optimize database architecture and frontend performance using [specific tech], which reduced data retrieval times by [X]% and enhanced [specific business outcome]
```
### 3.2 Soft Skills Integration Checklist
**For EACH required soft skill, ensure:**
- [ ] Exact phrase from job description included
- [ ] Demonstrated through specific technical example
- [ ] Quantified outcome when possible
---
## Step 4: Skills Section Standardization
### Skill Section Guidelines
- Keep technical skills concise - prioritize most relevant skills for specific role
- Maximum 4 elements per standard category (languages, frameworks, databases)
- Architecture & Development Practices: Maximum 3 elements (due to longer technical terms)
- Reorder sections to prioritize job requirements at the top
- Use multiple skill sections when needed for better organization
### Interests Category Strategy
Add "Interests" at end of skills section to address gaps:
- Include technologies from job posting not in direct experience
- Particularly useful for "preferred" or "nice-to-have" requirements
- Keep under 3 technologies to maintain credibility
---
## Step 5: Introduction Optimization Formula
### 5.1 Introduction Construction Protocol (Strict Adherence Required)
**MANDATORY COMPONENTS:**
1. **Job title from posting** (exact match)
2. **"almost 5 years of experience"** (required phrase)
3. **General technical area** (broad, credible scope)
4. **1-2 soft skills from job requirements** (exact phrases when possible)
5. **Personal capability focus** (avoid industry/platform references)
**FORBIDDEN ELEMENTS:**
- ❌ Platform-specific mentions not in knowledge base ("e-commerce," "financial systems")
- ❌ Company context not explicitly documented in experience
- ❌ More than 2 sentences
- ❌ More than 2 soft skills
**APPROVED TEMPLATE:**
```
[Job Title] with almost 5 years of experience in [general technical area]. Demonstrated [soft skill 1] and [soft skill 2] while delivering [broad technical capability].
```
**CORRECT EXAMPLES:**
**For Frontend Role:**
```
Frontend Software Engineer with almost 5 years of experience in web application development. Proven cross-functional collaboration and analytical thinking in delivering user-focused solutions.
```
**For Full Stack Role:**
```
Full Stack Developer with almost 5 years of experience in software development. Strong problem-solving abilities and end-to-end ownership in building scalable applications.
```
**For Senior Role:**
```
Senior Software Engineer with almost 5 years of experience in frontend development. Demonstrated leadership and mentoring capabilities while maintaining high code quality standards.
```
### 5.2 Soft Skills Integration Options
**Choose 1-2 from job requirements (exact phrases preferred):**
- Cross-functional collaboration
- Analytical thinking
- Problem-solving abilities
- End-to-end ownership
- Leadership and mentoring
- Adaptability to rapid changes
- Performance-focused mindset
- Team collaboration
- Technical ownership
- Quality-driven development
### 5.3 Technical Focus Options (Use Only From Experience Dataset)
**Based on actual experience:**
- "developing high-performance Angular applications"
- "building complex web applications using modern frameworks"
- "architecting and developing enterprise-level solutions"
- "creating scalable frontend architectures with reactive programming"
- "developing full-stack applications with performance optimization focus"
### 5.4 Verification Protocol
**Before finalizing introduction, confirm:**
- [ ] Contains exactly required phrase "almost 5 years of experience"
- [ ] Uses exact job title from posting
- [ ] Includes 1-2 soft skills from job requirements
- [ ] Technical focus matches actual experience dataset
- [ ] NO industry context
- [ ] Maximum 2 sentences
- [ ] Flows naturally and professionally
---
## Step 6: Quality Assurance Protocol (MANDATORY)
### 6.1 Pre-Submission Checklist
**TECHNICAL ACCURACY:**
- [ ] Every technical skill claimed has specific experience backing
- [ ] All metrics are verifiable from actual work experience
- [ ] Technologies mentioned are ones actually used (not learned/studied)
- [ ] Job title matches exactly with target posting
**KEYWORD OPTIMIZATION:**
- [ ] 80%+ of required hard skills addressed
- [ ] All required soft skills included as exact phrases
- [ ] ATS-friendly exact keyword matches confirmed
**CONTENT AUTHENTICITY:**
- [ ] All bullet points traceable to specific job experiences
- [ ] No fabricated projects, metrics, or responsibilities
- [ ] Seniority level matches actual experience
- [ ] Can defend every claim in an interview
### 6.2 Common Error Prevention
**RED FLAGS - Stop if any apply:**
- Using technologies never actually worked with
- Adding "Senior" when job doesn't mention it
- Claiming leadership roles not actually held
- Inventing metrics not from actual work
- Using soft skill phrases without demonstrating examples
- Exceeding maximum bullet points per role (4 for most recent, 3 for others)
---
## Step 7: Final Validation Protocol
### 7.1 Keyword Density Verification
**REQUIRED CHECKS:**
1. **Count job keywords in final resume**
2. **Verify 60-80% match for required hard skills**
3. **Confirm all required soft skills appear as exact phrases**
4. **Check natural integration (no keyword stuffing)**
### 7.2 Experience Hierarchy Verification
**BULLET POINT ORDER (Mandatory):**
- **First bullet:** Must address top job requirement with exact keywords
- **Second bullet:** Must address second most important requirement
- **Remaining bullets:** Ordered by relevance to job requirements
- **Maximum limits:** 4 bullets for most recent role, 3 for others
### 7.3 Professional Presentation Check
**FINAL REQUIREMENTS:**
- [ ] Each bullet point maximum 2 lines
- [ ] Action verbs match target seniority level
- [ ] Technical complexity appropriate for role level
- [ ] Business impact statements align with company context
- [ ] Education section remains last
- [ ] Contact information includes exact link format
---
## Step 8: Personal Projects Section Protocol
### 8.1 Project Selection and Presentation
**SELECTION CRITERIA:**
- Prioritize projects using technologies mentioned in job posting
- Select projects that demonstrate required skills or methodologies
**MANDATORY RULE:**
- ❌ **DO NOT invent, add, or modify any project information**
- ✅ **Use only information explicitly documented in knowledge base**
### 8.2 Project Structure Template
**FORMAT:**
```
[Project Name] - [Brief description using job keywords] | [Tech stack]
• [Key feature/implementation that shows relevant skill]
• [Technical challenge solved or outcome achieved]
```
**OPTIMIZATION APPROACH:**
- Emphasize technologies and skills mentioned in job requirements
- Use job posting keywords in descriptions where naturally applicable
- Highlight aspects most relevant to target role (frontend/backend/full-stack focus)
### 8.3 Section Guidelines
**PLACEMENT:** Always last section on resume (after Skills)
**FOCUS:** Support technical claims made elsewhere in resume
**VALIDATION:** Each project must be verifiable from knowledge base and defendable in interviews.
---
## CONSISTENCY ENFORCEMENT RULES
### Mandatory Process Order
1. **ALWAYS start with complete job description analysis**
2. **ALWAYS create skills inventory before writing**
3. **ALWAYS verify job title matching protocol**
4. **ALWAYS use exact keyword integration formulas**
5. **ALWAYS complete full quality assurance checklist**
### Error Prevention Protocol
- **Never skip the pre-generation checklist**
- **Never use technologies not in experience inventory**
- **Never use industry references not in experience inventory**
- **Never invent missing information**
- **Never add seniority levels not in job posting**
- **Never exceed maximum bullet point limits**
- **Never submit without keyword density verification**
