Tech Resume Optimizer
Tune a software-engineer, PM, or technical resume for ATS and recruiter scans before you apply or pitch clients.
Overview
Tech Resume Optimizer is an agent skill for the Validate phase that structures and sharpens technical resumes for ATS and engineering recruiters.
Install
npx skills add https://github.com/paramchoudhary/resumeskills --skill tech-resume-optimizerWhat is this skill?
- Structures resumes for SWE, PM, data, and DevOps with a 7-section recommended order
- Balances technical depth, scale metrics, and business impact for recruiters
- Optimizes technical skills blocks and project sections for ATS
- Contact block guidance for GitHub, portfolio, and technical links
- Philosophy section on what tech recruiters scan for first
- 7-section recommended resume order
- 6 criteria tech recruiters prioritize
Adoption & trust: 477 installs on skills.sh; 713 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have experience and projects but your resume reads generic, hides metrics, and fails ATS or technical recruiter scans.
Who is it for?
Builders updating a resume before an application sprint, contract pitch, or technical recruiter screen.
Skip if: Non-technical CVs, executive leadership bios with no hands-on stack, or roles where a portfolio alone replaces a resume without ATS requirements.
When should I use this skill?
User applies for software roles, wants a technical resume optimized, or mentions tech resume, developer resume, SWE resume, or PM resume.
What do I get? / Deliverables
You get a ordered, skills-forward resume draft with stronger technical achievements, links, and formatting aligned to SWE, PM, and related roles.
- Restructured resume sections with optimized skills and experience bullets
- Contact block including GitHub and portfolio placement
Recommended Skills
Journey fit
Resume work happens when you are proving hireability and scope—right after you know what role you want and before outbound applications. Landing-style artifacts sell you to humans and parsers; an optimized resume is your personal conversion page in job funnels.
How it compares
Use for guided resume structure and recruiter-oriented copy—not for LinkedIn post drafting or cover-letter-only rewrites.
Common Questions / FAQ
Who is tech-resume-optimizer for?
Solo builders and developers applying to software engineering, PM, data, DevOps, or other technical roles who want ATS-friendly structure and clearer impact bullets.
When should I use tech-resume-optimizer?
Use it during Validate when you are scoping outbound job or client applications, optimizing a developer or PM resume, or when you ask for help with SWE resumes, technical skills sections, or GitHub-linked contact blocks.
Is tech-resume-optimizer safe to install?
Review the Security Audits panel on this Prism page and treat resume content as sensitive personal data you paste into the agent session.
SKILL.md
READMESKILL.md - Tech Resume Optimizer
# Tech Resume Optimizer ## When to Use This Skill Use this skill when the user: - Is applying for software engineering roles - Wants to optimize a technical resume - Needs help with developer/PM/technical job applications - Mentions: "tech resume", "software engineer resume", "developer resume", "technical resume", "SWE resume", "PM resume" ## Core Capabilities - Optimize resumes for technical roles (SWE, PM, Data, DevOps) - Structure technical skills sections effectively - Highlight projects and technical achievements - Balance technical depth with business impact - Format for both ATS and technical recruiters - Include GitHub, portfolio, and technical links ## Tech Resume Philosophy **What Tech Recruiters Look For:** 1. Relevant technical skills (languages, frameworks, tools) 2. Scale and impact (users, transactions, data size) 3. Problem-solving abilities 4. System design understanding 5. Collaborative abilities 6. Growth trajectory ## Tech Resume Structure ### Recommended Order ``` 1. Contact Information (including GitHub, Portfolio) 2. Professional Summary (optional but helpful) 3. Technical Skills (critical for ATS) 4. Work Experience (with technical achievements) 5. Projects (especially for early career) 6. Education 7. Certifications (if relevant) ``` ### Contact Section for Tech ``` John Developer San Francisco, CA john@email.com | (555) 123-4567 LinkedIn: linkedin.com/in/johndev GitHub: github.com/johndev Portfolio: johndev.io ``` **Include:** - GitHub (required for SWE roles) - Portfolio/personal website - LinkedIn - Tech blog (if you have one) **Don't Include:** - Address (city/state is enough) - Photo - Social media (unless relevant) ## Technical Skills Section ### Organization Strategies **Option 1: By Category** ``` Languages: Python, JavaScript, TypeScript, Go, SQL Frameworks: React, Node.js, Django, FastAPI Databases: PostgreSQL, MongoDB, Redis, Elasticsearch Cloud/Infrastructure: AWS (EC2, S3, Lambda, RDS), Docker, Kubernetes, Terraform Tools: Git, JIRA, CI/CD, Datadog, Grafana ``` **Option 2: By Proficiency** (use carefully) ``` Expert: Python, React, PostgreSQL, AWS Proficient: Go, TypeScript, MongoDB, Docker Familiar: Rust, GraphQL, Kubernetes ``` **Option 3: Flat List** (ATS-friendly) ``` Skills: Python, JavaScript, TypeScript, React, Node.js, Django, PostgreSQL, MongoDB, AWS, Docker, Kubernetes, Git ``` ### What to Include **Languages:** - List languages you can code in confidently - Order by relevance to target role - Include query languages (SQL, GraphQL) **Frameworks/Libraries:** - Web: React, Vue, Angular, Django, Flask, Express - Data: Pandas, NumPy, TensorFlow, PyTorch - Testing: Jest, Pytest, Selenium **Databases:** - Relational: PostgreSQL, MySQL, SQL Server - NoSQL: MongoDB, DynamoDB, Cassandra - Caching: Redis, Memcached **Cloud/DevOps:** - Cloud: AWS, GCP, Azure (specific services) - Containers: Docker, Kubernetes - CI/CD: Jenkins, GitHub Actions, CircleCI - IaC: Terraform, CloudFormation ### What NOT to Include - ❌ Microsoft Office (assumed) - ❌ Operating systems (unless DevOps role) - ❌ Outdated tech (unless specifically required) - ❌ Skill bars or ratings (subjective and break ATS) - ❌ Every technology you've touched once ## Experience Section for Tech Roles ### The Technical Bullet Formula **[Action Verb] + [Technical What] + [Scale/Impact] + [Technology Used]** **Examples:** ❌ **Weak Technical Bullet:** ``` - Worked on backend services - Helped improve system performance - Built features for the product ``` ✅ **Strong Technical Bullet:** ``` - Architected microservices migration from monolith, reducing deployment time from 2 hours to 15 minutes and enabling independent team deployments - Optimized PostgreSQL queries and implemented Redis caching, reducing API latency by 60% (from 500ms to 200ms) for 100K daily active users - Built real-time not