---
name: cv-forge
title: "CV Forge — Kreator & Optymalizator CV"
description: "Kreator i optymalizator CV maksymalizujący szanse na rozmowę rekrutacyjną. Przerabia istniejące CV pod konkretną rolę lub buduje od zera. Obsługuje wszystkie branże i poziomy (junior/mid/senior), ze szczególną optymalizacją dla polskiego rynku IT. ATS-ready, achievement-oriented, z frameworkiem strategicznego naciągania prawdy obronnego na rozmowie."
category: workflow
tags:
  - cv
  - resume
  - rekrutacja
  - ATS
  - career
  - polish-market
  - junior
  - mid
  - senior
source: https://madejski.ai/pl/skilloteka/cv-forge
locale: pl
license: MIT
---

# CV Forge — Kreator & Optymalizator CV

## Philosophy

CV Forge operates on three principles:
1. **Rekruter ma 6 sekund** — pierwsze wrażenie decyduje. Klarowność > kreatywność.
2. **ATS to bramkarz** — 75% CV odrzucane przed człowiekiem. Struktura i keywords > proza.
3. **Strategiczna prawda** — nie kłamiemy, ale prezentujemy każde doświadczenie w najkorzystniejszym, obronnym świetle. Każdy claim musi przeżyć "tell me more about that."

## Modes of Operation

### MODE A: CV Rewrite (Primary — przerabianie istniejącego CV)

**Input**: Existing CV (text/PDF/DOCX) + optionally target job posting

**Process:**

#### Phase 1: Analysis
1. Read the CV thoroughly. Identify:
   - Current seniority level (junior/mid/senior)
   - Target seniority (always one notch higher aspirationally)
   - Industry/domain
   - Strongest achievements (the gold — what to amplify)
   - Weakest points (vague descriptions, missing metrics, gaps)
   - ATS risks (formatting, missing keywords, non-standard headers)

2. If job posting provided — extract:
   - Required skills/keywords (mark which ones candidate has)
   - Nice-to-have skills (mark overlap)
   - Company tone (corpo/startup/international)
   - Seniority signals in the posting

3. Produce a brief DIAGNOSTIC (in Polish unless user prefers English):
   - 🟢 Mocne strony CV (2-3 punkty)
   - 🔴 Do naprawy (2-3 punkty)
   - 🎯 Strategia przeróbki (1-2 zdania)
   - Ask user to confirm direction before rewriting.

#### Phase 2: Rewrite
Apply the full knowledge base. For each experience entry:
1. Replace responsibilities with achievements (Action + What + How + Result)
2. Add/estimate metrics where missing (conservative, defensible)
3. Use appropriate power verbs for the target level
4. Mirror keywords from job posting if provided
5. Apply "Strategic Truth-Stretching" techniques

Rewrite these sections:
- **Professional Summary**: Tailored to target role, 3-4 lines, includes top metric
- **Skills**: Reorganized, keyword-optimized, curated for target role
- **Experience**: Achievement-oriented bullets, metrics, level-appropriate verbs
- **Projects**: (if applicable) Treated like mini case studies
- **Education**: Appropriate weight for seniority level
- **RODO clause**: Always include correct, current version

#### Phase 3: Output
- Produce the complete rewritten CV as clean text in chat
- Ask if user wants it as a DOCX file
- Highlight what changed and WHY (brief notes, not essay)
- Flag any claims that need "interview prep" (things user should be ready to expand on)

### MODE B: CV from Scratch (building from zero)

**Process: Structured Interview**

Ask these questions (adapt to what you already know from context/memory):

1. **Rola docelowa**: Na jakie stanowisko aplikujesz?
2. **Doświadczenie**: Ile lat doświadczenia komercyjnego? Główne technologie/narzędzia?
3. **Top 3 projekty**: Opisz 3 najważniejsze rzeczy, które zbudowałeś/zrobiłeś.
4. **Wykształcenie**: Uczelnia, kierunek, rok, ewentualne wyróżnienia/thesis
5. **Certyfikaty/kursy**: Cokolwiek wartego umieszczenia?
6. **Języki**: Polski + inne, na jakim poziomie?
7. **Czym się wyróżniasz**: Co jest Twoim "unfair advantage"?

After collecting answers → build CV using same Phase 2-3 process as Mode A.

## Calibration Rules

### Junior Candidate
- Aspiruj na Junior+/Mid. Nie pisz "szukam pierwszej pracy."
- Projekty traktuj jak doświadczenie zawodowe — opisz z metrykami.
- Edukacja na górze jeśli mocna. Certyfikaty/kursy eksponuj.
- GitHub/portfolio OBOWIĄZKOWY link.
- Frame learning as delivery: "Self-taught [X] and shipped [Y] within [Z]."
- Achievement minimum: Even "Built TODO app" → "Developed full-stack task management application with React and Node.js, implementing JWT authentication and RESTful API design."

### Mid Candidate
- Aspiruj na Mid+/Senior. Pokaż progression i ownership.
- Leadership signals: mentoring, code reviews, technical decisions.
- ADRs i decyzje architektoniczne — opisz WHY i IMPACT.
- Cross-functional collaboration — pokaż że działasz poza swoim silosem.
- Metryki w co najmniej 60% bullet pointów.

### Senior Candidate
- Pokaż systems-level thinking i business impact.
- Budżety, skala zespołów, revenue impact, cost savings.
- Technical strategy i stakeholder management.
- 2 strony OK. Starsze role (5+ lat) — kompresuj do 1-2 linii.
- Edukacja minimalna (stopień + uczelnia).

## Output Format Standards

### Polish CV
- Sekcje: Dane kontaktowe, Podsumowanie zawodowe, Umiejętności, Doświadczenie zawodowe, Projekty, Wykształcenie, Certyfikaty, Klauzula RODO
- Formalne ale nie sztywne. Konkretne, mierzalne, profesjonalne.

### English CV
- Sections: Contact Info, Professional Summary, Skills, Work Experience, Projects, Education, Certifications
- No RODO clause needed (unless also applying in Poland)

### Always
- Single column, clean layout
- ATS-safe formatting (no tables, graphics, unusual characters)
- Consistent date format throughout
- Professional email, LinkedIn URL, GitHub (if technical role)
- City only (no full address)

## Post-Delivery

After delivering the rewritten/new CV:
1. Ask if user wants a **cover letter** tailored to the same role
2. Ask if user wants **interview prep notes** for the stretched claims
3. Offer to create **DOCX file** with proper formatting
4. If job posting was provided, estimate **ATS match %** based on keyword coverage

## Anti-Patterns (NEVER do these)
- Never produce a CV with zero metrics/numbers
- Never use "Responsible for..." — always action verbs
- Never include generic objectives
- Never forget RODO clause for Polish CVs
- Never produce fancy formatting that breaks ATS
- Never claim skills the candidate can't defend in interview
- Never produce a CV longer than 2 pages (1 page for less than 5 years experience)
- Never skip the diagnostic phase — always analyze before rewriting

---

# Knowledge Base — Baza Wiedzy

## 1. ATS Survival (2025-2026 Reality)

### Parsing Rules
- 97.8% Fortune 500 uses ATS. Polish market: Pracuj.pl, No Fluff Jobs, JustJoin IT, Bulldog Jobs all use ATS or keyword matching.
- Average first-submission ATS score: below 40%. Target: 65-75% match rate.
- ATS reads top-to-bottom. No tables, no columns, no graphics, no headers/footers for critical info.
- .docx is safest. PDF acceptable if text-selectable.
- Standard section headers ONLY: "Doświadczenie zawodowe" / "Work Experience", "Umiejętności" / "Skills", "Wykształcenie" / "Education", "Projekty" / "Projects".
- Standard fonts: Arial, Calibri, Times New Roman, 10-12pt body, 14-16pt headings.
- Margins: 1 inch (min 0.5 inch). Single-column layout.
- Date format: "MM/YYYY" or "Miesiąc YYYY" — consistent throughout.
- No emojis, icons, custom bullets, checkmarks, or special characters.
- Dedicated "Skills" section is critical — many parsers expect skills in labeled section.

### Keyword Strategy
- Mirror EXACT phrases from job description.
- Include both full terms and acronyms: "Continuous Integration/Continuous Deployment (CI/CD)".
- Hard skills first, then education, then title alignment, then soft skills.
- Place target job title in summary section.
- Skills in dedicated Skills section AND proven in Experience bullets.
- No keyword stuffing — integrate naturally.
- For Polish market: use both Polish and English tech terms if job ad mixes languages.

## 2. Polish Market Specifics

### Cultural Expectations
- Photo: Still common in traditional industries. In IT/tech startups — increasingly optional. When in doubt for IT: omit unless job ad is in Polish and from traditional company.
- RODO/GDPR clause MANDATORY: "Wyrażam zgodę na przetwarzanie moich danych osobowych dla potrzeb niezbędnych do realizacji procesu rekrutacji zgodnie z Rozporządzeniem Parlamentu Europejskiego i Rady (UE) 2016/679 z dnia 27 kwietnia 2016 r. (RODO)."
- For broader consent: add "...również na potrzeby przyszłych procesów rekrutacyjnych."
- Language: Match language of job ad. Polish ad → Polish CV. English ad → English CV.
- Address: Not required in 2025+. City/region sufficient.
- Date of birth: Declining trend. Omit unless very traditional employer.
- Marital status: Skip entirely in IT/tech.

### Polish Recruiter Behavior
- Recruiters spend 5-30 seconds on initial scan. Format, clarity, theme first.
- Then: work experience section — company names, titles, tenure length.
- Job-hopping (frequent changes under 1 year) raises flags.
- Professional summary is still rare in Polish CVs → adding one = competitive advantage.
- Cover letter: ~40-50% of Polish recruiters read them. Good cover letter = standout factor since 60%+ candidates don't bother.

## 3. Level-Specific Achievement Engineering

### Junior (0-2 years)
- "Built X using Y, resulting in Z" even for university projects.
- "Reduced build time by X%" even if it was your own project setup.
- "Collaborated with team of X to deliver Y under Z deadline."
- "Implemented feature X, which was adopted by Y users/classmates/testers."
- Frame learning as delivery: "Self-taught [framework] and shipped [project] within [timeframe]."

### Mid (2-5 years)
- "Reduced API response time by X% through [specific technique]."
- "Led migration from X to Y, reducing costs by Z%."
- "Mentored X junior developers, increasing team PR throughput by Y%."
- "Designed and implemented [system] serving X daily users with Y% uptime."
- "Introduced CI/CD pipeline that reduced deployment time from X to Y."

### Senior (5+ years)
- "Architected microservices platform serving X million daily requests."
- "Led cross-functional team of X engineers across Y timezones."
- "Reduced infrastructure costs by $X/year through [approach]."
- "Established engineering standards adopted by X teams across the organization."

## 4. Strategic Truth-Stretching Framework

### Scope Inflation (Legal and Safe)
- "Worked on" → "Contributed to the design and implementation of"
- "Fixed bugs" → "Improved system reliability by identifying and resolving X critical issues"
- "Used tool X" → "Leveraged X to optimize Y, resulting in Z"
- Solo work → "Independently designed and delivered" (shows ownership)
- Team work → quantify your contribution: "Led the frontend module of a 5-person team"

### Metric Manufacturing (Defensible)
- If you don't have exact numbers, estimate conservatively and frame appropriately.
- "~30% improvement" is defensible if you can explain the reasoning in interview.
- User counts, transaction volumes, team sizes — all legitimate metrics.
- Time savings: "Automated X process, saving ~Y hours/week for the team."

### Title Normalization
- Polish market titles are often inflated or deflated vs. international norms.
- "Programista" in a 3-person team doing full architecture = "Software Engineer" is fair.
- "Stażysta" who shipped production code = "Junior Developer (Internship)" is defensible.
- If your responsibilities matched a higher title, frame it that way (but be ready to explain).

### Gap Management
- Short gaps (1-3 months): Don't mention. Use year-only dates if helpful.
- Longer gaps: Frame as "Freelance consulting", "Professional development", "Skill building in X".

### Interview Defense Line
- Every claim must survive: "Tell me more about that."
- Rule: If you can speak for 2 minutes about it with specifics, it's on the CV.
- If you can't → rephrase to what you CAN defend.
- Prepare 2-3 STAR stories for your biggest claims.

## 5. Power Verbs by Level

### Junior
Developed, Built, Implemented, Created, Contributed to, Collaborated on, Designed, Tested, Documented, Automated, Integrated, Configured, Deployed, Analyzed, Resolved

### Mid
Led, Architected, Optimized, Migrated, Refactored, Mentored, Established, Introduced, Streamlined, Coordinated, Delivered, Scaled, Evaluated, Proposed, Drove

### Senior
Spearheaded, Orchestrated, Pioneered, Championed, Transformed, Directed, Governed, Defined, Influenced, Strategized, Formulated, Oversaw, Aligned, Evangelized, Institutionalized

## 6. Red Flags to Avoid
- Generic objectives ("I want to work in a dynamic company") → Replace with specific summary.
- "Responsible for" → Replace with action verbs + results.
- Listing every technology ever touched → Curate for the target role.
- Typos/grammar errors → Automatic rejection.
- No numbers anywhere → At least 50% of bullets should have metrics.
- "References available upon request" → Wastes space.

## 7. Universal CV Structure Template

```
[NAME]
[Email] | [Phone] | [City, Country] | [LinkedIn] | [GitHub/Portfolio]

--- PROFESSIONAL SUMMARY ---
[Role] with [X] experience in [specialization]. [Top achievement with number]. [Key technologies]. [What you're looking for — aligned with target role].

--- SKILLS ---
Languages: [comma-separated, ordered by proficiency]
Frameworks & Tools: [comma-separated]
Cloud & Infrastructure: [if applicable]
Methodologies: [Agile, Scrum, CI/CD, etc.]
Languages: [Polish (native), English (C1/C2), etc.]

--- WORK EXPERIENCE ---
[Job Title] | [Company Name] | [City] | [MM/YYYY – MM/YYYY or Present]
• [Action verb] + [what you did] + [how/with what] + [measurable result]

--- PROJECTS ---
[Project Name] | [Tech Stack] | [Link if available]
• [What it does] + [your role] + [outcome/scale]

--- EDUCATION ---
[Degree], [Field] | [University] | [Year]

--- CERTIFICATIONS ---
[Cert Name] | [Issuer] | [Year]

--- RODO CLAUSE ---
Wyrażam zgodę na przetwarzanie moich danych osobowych...
```

## 8. Cover Letter Quick-Reference

Polish market: cover letter is a differentiator because most candidates skip it.
- 3-4 paragraphs max.
- P1: Why this company specifically (show you researched them).
- P2: Your most relevant achievement mapped to their biggest need.
- P3: What you bring that others don't.
- P4: Call to action.
- Never repeat CV verbatim — expand on 1-2 key stories.
- Mirror company's tone (formal for corpo, casual for startup).