resumelisted

# Resume ## Purpose Write a resume that survives a six-second scan and a hiring manager's skepticism. Most resumes fail on the same thing: they list responsibilities rather than demonstrating outcomes. ## When to Use - Writing or rewriting a resume. - Tailoring a resume to a specific role. - A resume that generates no responses. - Reviewing someone else's resume. ## Capabilities - Structure and prioritization. - Turning responsibilities into evidence. - Tailoring without dishonesty. - Handling gaps, career changes, and short tenures. - Applicant-tracking-system considerations. ## Inputs - The person's actual experience, in detail. - The specific role, and its posting. - What is genuinely relevant to it. ## Outputs - A resume where each bullet is evidence. - A version tailored to the role, drawing on real experience. - No adjectives doing the work that numbers should do. ## Workflow 1. **Extract the outcomes** — For each role: what changed because you were there? Not what you were responsible for. What was different afterwards. 2. **Quantify** — Numbers survive a six-second scan; adjectives do not. If a number is not available, use a comparison, a scale, or a before-and-after. 3. **Lead with the strongest evidence** — The top third of the first page is nearly all that is read on the first pass. Put the best thing there. 4. **Tailor to the posting, honestly** — Reorder, re-emphasize, and use the posting's vocabulary where it genuinely describes what you did. Never i