write-a-technical-resume

# write-a-technical-resume Demonstrate technical judgment through evidence, not a catalog of tools. ## When to use - Use for specialist technical roles where implementation and operating context matter. - Do not expose credentials, vulnerabilities, customer data, proprietary architecture, or inflated scale. ## Procedure 1. Decompose the target role into systems, problem types, seniority signals, collaboration, and operational responsibilities. 2. Build an evidence inventory of projects, architecture decisions, incidents, migrations, reviews, and measurable results. 3. Select experience that proves relevant depth, breadth, ownership, and learning. 4. Write bullets that identify the system, constraint, candidate decision, implementation, and verified outcome. 5. Define scale with correct units and period; distinguish team, service, and individual scope. 6. Group technical skills by demonstrated capability and remove unsupported keyword copying. 7. Explain reliability, security, testing, cost, accessibility, or maintainability tradeoffs where relevant. 8. Link only to safe public work and describe confidential systems at the permitted abstraction level. 9. Test every claim against source evidence and every section against the job criteria. ## Done - A technical resume maps role criteria to evidence-backed systems, decisions, scope, tradeoffs, and outcomes - Metrics, technologies, ownership, confidentiality, links, and seniority signals are verified against source records