resume-bullet-extraction
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseResume Bullet Extraction
简历项目符号条目提炼
"Your resume isn't a job description. It's a highlight reel of impact."
"你的简历不是职位描述,而是成果亮点集锦。"
Purpose
用途
Transform completed work into powerful resume bullet points that demonstrate value and technical competence.
将已完成的工作转化为能够体现价值与技术能力的有力简历项目符号条目。
The Bullet Formula
项目符号条目公式
[Strong Action Verb] + [What You Did] + [Technical Context] + [Impact/Result][有力动作动词] + [你完成的工作] + [技术背景] + [成果/影响]Components
组成部分
| Component | Purpose | Example |
|---|---|---|
| Action Verb | Shows initiative | Engineered, Architected, Optimized |
| What You Did | The accomplishment | JWT authentication system |
| Technical Context | Shows skill | using React, Node.js, Redis |
| Impact | Why it matters | reducing auth errors by 40% |
| 组成部分 | 作用 | 示例 |
|---|---|---|
| 动作动词 | 展现主动性 | Engineered, Architected, Optimized |
| 你完成的工作 | 具体成就 | JWT认证系统 |
| 技术背景 | 展示技能 | using React, Node.js, Redis |
| 成果 | 说明重要性 | 减少40%的认证错误 |
Strong Action Verbs
有力动作动词
Building/Creating
构建/创建类
- Engineered
- Architected
- Developed
- Implemented
- Built
- Designed
- Engineered
- Architected
- Developed
- Implemented
- Built
- Designed
Improving
优化改进类
- Optimized
- Enhanced
- Refactored
- Modernized
- Streamlined
- Accelerated
- Optimized
- Enhanced
- Refactored
- Modernized
- Streamlined
- Accelerated
Problem Solving
问题解决类
- Resolved
- Debugged
- Eliminated
- Reduced
- Prevented
- Mitigated
- Resolved
- Debugged
- Eliminated
- Reduced
- Prevented
- Mitigated
Leading/Collaborating
领导协作类
- Led
- Spearheaded
- Collaborated
- Mentored
- Coordinated
- Led
- Spearheaded
- Collaborated
- Mentored
- Coordinated
Impact Quantification
成果量化
Always try to quantify. If you can't measure directly, estimate reasonably.
始终尝试量化成果。如果无法直接衡量,可合理估算。
Performance
性能表现
- "reducing load time by 60%"
- "improving response time from 2s to 200ms"
- "handling 10,000+ concurrent users"
- "将加载时间缩短60%"
- "将响应时间从2秒提升至200毫秒"
- "支持10,000+并发用户"
Reliability
可靠性
- "achieving 99.9% uptime"
- "eliminating production errors"
- "reducing bug reports by 50%"
- "实现99.9%的正常运行时间"
- "消除生产环境错误"
- "将Bug报告减少50%"
Business
业务价值
- "increasing user retention by 25%"
- "supporting 50,000 monthly active users"
- "saving 10 hours/week of manual work"
- "将用户留存率提升25%"
- "支持50,000月度活跃用户"
- "每周节省10小时手动工作时间"
Scale
规模
- "processing 1M+ transactions daily"
- "managing 500GB of user data"
- "serving 100+ API endpoints"
- "每日处理100万+交易"
- "管理500GB用户数据"
- "提供100+ API端点"
Bullet Templates
项目符号条目模板
Feature Implementation
功能实现
[Verb] [feature] using [technologies] that [impact]
Examples:
- Engineered JWT authentication with refresh token rotation using Node.js and Redis, eliminating session hijacking vulnerabilities
- Built real-time notification system using WebSockets and React, improving user engagement by 35%[动词] [功能] using [技术栈] that [成果]
示例:
- Engineered 带刷新令牌轮转的JWT认证系统 using Node.js和Redis,消除会话劫持漏洞
- Built 实时通知系统 using WebSockets和React,将用户参与度提升35%Performance Optimization
性能优化
[Verb] [what] by [how], resulting in [metric]
Examples:
- Optimized database queries through index analysis and query restructuring, reducing API response time by 70%
- Accelerated page load performance by implementing code splitting and lazy loading, improving Core Web Vitals by 40%[动词] [优化对象] by [优化方式], resulting in [指标]
示例:
- Optimized 数据库查询 through 索引分析与查询重构,将API响应时间缩短70%
- Accelerated 页面加载性能 by 实现代码分割与懒加载,将Core Web Vitals提升40%Bug Fix / Problem Solving
Bug修复/问题解决
[Verb] [problem] by [solution], preventing [impact]
Examples:
- Resolved race condition in checkout flow by implementing optimistic locking, preventing duplicate charges
- Eliminated memory leak in React components through proper cleanup, reducing crash reports by 90%[动词] [问题] by [解决方案], preventing [影响]
示例:
- Resolved 结账流程中的竞态条件 by 实现乐观锁,防止重复扣费
- Eliminated React组件中的内存泄漏 through 正确的资源清理,将崩溃报告减少90%Architecture / Refactoring
架构/重构
[Verb] [system] from [old] to [new], enabling [benefit]
Examples:
- Migrated monolithic application to microservices architecture using Docker and Kubernetes, enabling independent team deployments
- Refactored authentication module from session-based to JWT, reducing server memory usage by 60%[动词] [系统] from [旧架构] to [新架构], enabling [收益]
示例:
- Migrated 单体应用 to 微服务架构 using Docker和Kubernetes,支持团队独立部署
- Refactored 认证模块 from 基于会话 to JWT,将服务器内存占用减少60%Quality Checklist
质量检查清单
- Starts with strong action verb (not "Responsible for")
- Includes specific technologies
- Has quantifiable impact OR clear business value
- Is one concise sentence
- Avoids jargon recruiters won't understand
- Demonstrates ownership ("I" is implied)
- Would make sense to a technical interviewer
- 以有力动作动词开头(而非“负责”)
- 包含具体技术栈
- 具备可量化成果或明确业务价值
- 为简洁的单句
- 避免招聘人员无法理解的行话
- 体现主动性(隐含“我”的主语)
- 能让技术面试官理解
Bad vs Good Examples
反面与正面示例
Bad
反面示例
❌ "Worked on the login system"
- No action verb, no specifics, no impact
❌ "Responsible for user authentication"
- Passive, no accomplishment shown
❌ "Helped with performance improvements"
- Vague, no ownership, no metrics❌ "参与登录系统开发"
- 无动作动词、无细节、无成果
❌ "负责用户认证"
- 被动表述,未展示成就
❌ "协助性能优化"
- 模糊不清,无主动性、无指标Good
正面示例
✅ "Engineered JWT authentication with refresh token rotation, reducing session vulnerability surface and supporting 50,000+ daily active users"
✅ "Optimized PostgreSQL queries through index analysis, reducing average API response time from 800ms to 120ms"
✅ "Built responsive dashboard using React and D3.js, enabling real-time visualization of 1M+ daily events"✅ "Engineered 带刷新令牌轮转的JWT认证系统,减少会话攻击面并支持50,000+日活跃用户"
✅ "Optimized PostgreSQL查询 through 索引分析,将平均API响应时间从800毫秒缩短至120毫秒"
✅ "Built 响应式仪表盘 using React和D3.js,支持100万+每日事件的实时可视化"Extraction Flow
提炼流程
Step 1: Identify the Highlight
步骤1:确定亮点
"What's the most impressive aspect of what you just built?"
Options:
- Technical complexity solved
- Business problem addressed
- Performance improved
- Scale achieved
- Security enhanced
"你刚完成的工作中,最令人印象深刻的部分是什么?"
可选方向:
- 解决的技术复杂度问题
- 解决的业务问题
- 提升的性能
- 实现的规模
- 增强的安全性
Step 2: Draft the Bullet
步骤2:草拟条目
Use the formula: Verb + What + Technical Context + Impact
使用公式:动词 + 工作内容 + 技术背景 + 成果
Step 3: Quantify
步骤3:量化成果
"Can we add numbers? How much faster? How many users? What percentage improvement?"
"我们能否添加数字?速度提升了多少?覆盖多少用户?提升了百分之多少?"
Step 4: Polish
步骤4:打磨优化
- Remove weak words ("helped", "assisted", "worked on")
- Add specific technologies
- Ensure it stands alone (no context needed)
- 删除弱化表述(如“协助”“参与”“从事”)
- 添加具体技术栈
- 确保条目独立可懂(无需额外背景)
Resume Section Placement
简历板块放置
| Bullet Type | Resume Section |
|---|---|
| Feature/System built | Projects or Experience |
| Performance optimization | Experience (shows impact) |
| Architecture decision | Experience or Technical Skills |
| Learning/Growth | Skills or Side Projects |
| 条目类型 | 简历板块 |
|---|---|
| 构建的功能/系统 | 项目经历或工作经验 |
| 性能优化 | 工作经验(体现成果) |
| 架构决策 | 工作经验或技术技能 |
| 学习/成长 | 技能或副业项目 |
Socratic Bullet Questions
苏格拉底式条目提问法
- Finding impact: "If this feature didn't exist, what would break?"
- Quantifying: "How many users does this affect? How much time does it save?"
- Technical depth: "What would you tell a technical interviewer about how this works?"
- Differentiation: "What makes your implementation better than a basic solution?"
- 挖掘成果: "如果这个功能不存在,会有什么问题?"
- 量化成果: "这影响了多少用户?节省了多少时间?"
- 技术深度: "你会向技术面试官如何解释它的工作原理?"
- 差异化: "你的实现比基础方案好在哪里?"
Save Location
保存位置
Bullets are compiled in STAR story files:
ownyourcode/career/stories/[date]-[feature-name].mdThe resume bullet appears at the end of each story for easy extraction.
条目会被整理到STAR故事文件中:
ownyourcode/career/stories/[date]-[feature-name].md简历项目符号条目会放在每个故事的末尾,方便提取。