Auto-deploy: 2026-05-26 15:31:32
This commit is contained in:
@@ -77,7 +77,7 @@ CRITICAL RULES:
|
||||
- NO brackets or placeholders — use ACTUAL names and data
|
||||
- Every sentence specific to THIS job at ${co}
|
||||
- Under 300 words total
|
||||
- Tone MUST be highly professional, McKinsey-style, and executive. Focus on enterprise-scale impact and technical architecture. DO NOT mention military history or "Lieutenant Colonel".`;
|
||||
- Tone MUST be highly professional, McKinsey-style, and executive. Focus on enterprise-scale impact and technical architecture. DO NOT mention military history. DO NOT use buzzwords like "sanctioned markets", "serving millions", "disruptive".`;
|
||||
|
||||
P.cvtips = `You are a LinkedIn optimization expert and ATS specialist.
|
||||
IMPORTANT: Respond ENTIRELY in English regardless of the job posting language.
|
||||
@@ -90,10 +90,10 @@ ${ctx}
|
||||
Respond EXACTLY:
|
||||
|
||||
## LINKEDIN HEADLINE
|
||||
[One headline, EXACTLY under 80 characters, ATS-optimized, high-impact and professional]
|
||||
[One headline, EXACTLY under 80 characters, ATS-optimized. Format like: Senior Backend Engineer & Systems Architect | PHP, NestJS, GIS | CTO at Intaleq]
|
||||
|
||||
## PROFESSIONAL SUMMARY
|
||||
[3-4 sentences tailored summary ready to paste — in English. CRITICAL: Use a McKinsey-style, executive, and highly professional tone. Focus purely on technical architecture, enterprise-scale impact, and business value. DO NOT mention military history or "former Lieutenant Colonel".]
|
||||
[3-4 sentences tailored summary ready to paste — in English. CRITICAL: Use a McKinsey-style, executive, and highly professional tone. Focus purely on technical architecture, enterprise-scale impact, and business value. DO NOT mention military history. DO NOT use buzzwords like "sanctioned markets", "serving millions", "solo-adapted", "disruptive", "cutting-edge".]
|
||||
|
||||
## ATS KEYWORDS TO ADD
|
||||
- [10-15 specific keywords from this job that MUST appear in CV]
|
||||
|
||||
Reference in New Issue
Block a user