Generate Resume

---
description: Generate a tailored resume for a company and role. Usage: /generate-resume CompanyName RoleTitle, optional context about the role
---

# Resume Generation Command

You are generating a tailored resume for: **$ARGUMENTS**

## Step 1: Load Context (parallel)

Read ALL of these files simultaneously using parallel tool calls:
- `Job_Applications/Templates/master-template.tex` — the formatting template
- `docs/RESUME_GENERATOR_PROMPT.md` — all content generation rules
- `docs/RESUME_CONTEXT.md` — enhanced bullets for FSU, BookedFlow, Building Portal, SkillSync MCP

## Step 2: Find Reference Resumes

Search `Job_Applications/Companies/` for 2 existing `.tex` resumes most similar to this role type. Read them to understand proven bullet patterns.

## Step 3: Classify Role Type

Determine which category best fits:
- **ai-ml**: Multi-agent systems, RAG pipelines, model evaluation, inference optimization
- **fullstack**: Product impact, user-facing features, deployment velocity, end-to-end ownership
- **backend**: Distributed systems, throughput, reliability, API architecture
- **devops-infra**: Infrastructure reliability, deployment frequency, incident reduction, cost optimization
- **data-platform**: Data pipelines, ETL, analytics, data infrastructure

## Step 4: Parse the Role

Extract from the user's input:
- **Company name** (sanitize for folder name: spaces → underscores)
- **Role title** (sanitize for filename)
- **Key requirements** (if a JD was provided or can be inferred)
- **Context clues** (team, domain, tech stack from recruiter message)

## Step 5: Generate Resume .tex

Create the full LaTeX file following ALL these rules:

### Formatting Rules (from master-template.tex)
- Charter font, 10pt, letterpaper, 0.225in margins
- Blue section rules: `\color{metablue}\titlerule` (NOT darkgray)
- Blue bordered tcolorbox around Projects section
- Section headings: Blue (`metablue` RGB 24,119,242), ALL CAPS via `\scshape`
- Contact: Phone | blue location pin | email | GitHub | website

### Section Order (MANDATORY)
1. Header & Contact Info
2. Professional Summary (2 lines MAX rendered)
3. Work Experience (all roles, most recent first, 3-5 bullets each)
4. Projects (2-3 in tcolorbox, NO blank lines between \resumeItem entries)
5. Technical Skills (4-5 categories, job-relevant keywords)
6. Education (NO graduation dates — leave date field empty)
7. Publications & Awards (3 items: IJAST paper, Hackathon 2nd place, AWS cert)

### Content Rules
- Each bullet: 270-350 chars plain text
- Bold: Only 1-2 key terms per bullet; metrics in plain text NOT bold
- Achievement formula: [Action Verb] + [What] + [Tool/Method] + [Quantified Result] + [Business Impact]
- NEVER change: Job titles, company names, employment dates, degree info
- 80%+ keyword match with job description
- Interview defensible — choose explainable over impressive
- Exactly 2 pages (mandatory)

### Contact Details (ALWAYS use these)
- Name: {{USER_FULL_NAME}}
- Email: {{USER_EMAIL_WORK}}
- Phone: {{USER_PHONE}}
- GitHub: github.com/{{USER_GITHUB}}
- Website: {{USER_WEBSITE}}
- Location: {{USER_LOCATION}}

### User Constraints (CRITICAL)
- Java: NOT proficient. Include only as an ATS keyword in Skills. Never lead with Java.
- Go: Not used in production. Frame as transferable skill only.
- Spring Boot / Aspire Systems: Say "event-driven services" or "microservices" generically. Never "Java/Spring Boot microservices".
- Never use "Senior Software Engineer" -- that is not the actual title.
- Real strengths: Python, TypeScript, React/Next.js, multi-agent systems, MCP tooling, ML pipelines on GPU clusters.
- Every achievement must be interview-defensible -- choose explainable over impressive

## Step 6: Write the File

Save to: `Job_Applications/Companies/{Company}/{Company}_{Role}.tex`
- Company folder name: PascalCase with underscores (e.g., `ByteDance`, `Scale_AI`)
- Filename: `{Company}_{Role_With_Underscores}.tex`

Create the company directory if it doesn't exist, then write the .tex file.

The PostToolUse hook will automatically compile to PDF and report page count.

## Step 7: Handle Compile Result

- If hook reports **2 pages**: Done!
- If hook reports **>2 pages**: Reduce spacing — use `\vspace{-Xpt}` between sections, tighten bullet text, reduce to 2 projects
- If hook reports **<2 pages**: Add detail to bullets, add a 3rd project, expand skills
- If hook reports **compile error**: Fix the LaTeX error and re-save
- Iterate until exactly 2 pages

## Step 8: Report

Provide a brief summary:
- **File**: path to the .tex and .pdf
- **Role type**: classification used
- **Tailoring decisions**: What was emphasized/de-emphasized and why
- **Keyword coverage**: Key terms matched from JD
- **Experience gaps**: Anything the user should prepare for in interviews