Tech Resume Optimizer

---
name: tech-resume-optimizer
description: Optimize resumes for software engineering, PM, and technical roles
---

# 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, ordered by relevance to target role, including 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]**

❌ **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 notification system using WebSockets and AWS SNS, handling 1M+ messages daily with 99.9% delivery rate
```

See `references/bullet-examples.md` for more strong-bullet examples by role (Software Engineer, Data Engineer, DevOps/SRE, Technical PM).

### Technical Metrics to Include

- **Scale:** users ("serving 500K DAU"), requests ("handling 10K requests/second"), data ("processing 50TB daily"), uptime ("maintaining 99.99% availability")
- **Performance:** latency ("reduced from Xms to Yms"), speed ("improved by X%"), load time ("decreased by X seconds")
- **Efficiency:** cost ("reduced AWS costs by 40%"), time ("cut deployment time from X to Y"), resources ("reduced memory usage by X%")
- **Business:** revenue ("features drove $XM revenue"), conversion ("improved checkout by X%"), engagement ("increased DAU by X%")

## Projects Section

Critical for junior engineers, career changers, bootcamp graduates, and anyone with experience gaps. See `references/projects-section.md` for the recommended format, a worked example, and what makes a project worth including.

## Education Section for Tech

Format varies by background (traditional CS degree, bootcamp, self-taught). See `references/education-examples.md` for examples of each.

## Tech-Specific Tips

GitHub profile optimization, handling a tech-stack mismatch, and preparing your resume to survive the technical interview it leads to — see `references/tech-tips.md`.

## Output Format

When optimizing a tech resume:

```markdown
# TECH RESUME OPTIMIZATION

## Technical Skills Restructure
**Current:** [Their current skills section]
**Optimized:**
Languages: [Ordered list]
Frameworks: [Ordered list]
Databases: [Ordered list]
Cloud/Tools: [Ordered list]

## Experience Improvements

### [Company/Role]

**Current Bullet 1:**
"Worked on backend services"

**Improved:**
"Designed and deployed 5 Node.js microservices handling 50K requests/minute, reducing system coupling and enabling independent team deployments"

**Current Bullet 2:**
[Continue for each bullet]

## Projects to Highlight
[Suggestions based on their background]

## GitHub Recommendations
- [ ] Add READMEs to pinned repos
- [ ] Pin X project (most relevant)
- [ ] Add profile README

## Technical Gaps to Address
- [Missing skill] → [How to address in resume/cover letter]
```

## ATS + Tech Recruiter Balance

Remember: Your resume must pass ATS AND impress technical recruiters.

**For ATS:** include exact skill keywords, use standard section headers, avoid tables and graphics.

**For Tech Recruiters:** show technical depth, include metrics and scale, demonstrate problem-solving, show you understand systems.

---

## Related Skills

| Skill | When to apply |
|-------|--------------|
| `resume-ats-optimizer` | Validate keyword placement and ATS compatibility |
| `resume-bullet-writer` | Strengthen technical achievement bullets with impact and scale |
| `resume-quantifier` | Add DAU, latency, uptime, and cost metrics to technical bullets |
| `resume-section-builder` | Structure technical skills section and project order correctly |
| `resume-tailor` | Adjust tech stack emphasis per specific role or company |
| `job-description-analyzer` | Extract exact tech keywords and stack requirements from JD |
| `interview-prep-generator` | Prepare to discuss every system and project on the resume |
| `linkedin-profile-optimizer` | Sync GitHub, portfolio, and tech skills to LinkedIn |
| `career-changer-translator` | Reframe non-tech experience for technical roles |