Resume & Portfolio
Core Principle
Your resume is not a job description of what you did — it's a curated argument for why you're the right person for a specific role. Every line should earn its place.
Resume Writing Formula
For Each Role / Project
[Action verb] [what you built/did] [using/with what]
[that resulted in / achieving] [measurable outcome]
Examples:
WEAK: "Worked on BTT module development"
STRONG: "Built Query Clarity Assessment Agent achieving 95%+ test
coverage, unblocking production deployment for the team"
WEAK: "Helped with frontend development"
STRONG: "Implemented LaunchDarkly feature flagging for BTT UI,
enabling safe gradual rollout to production users"
Strong Action Verbs by Category
- Built/Created: Developed, Engineered, Architected, Implemented
- Improved: Optimized, Reduced, Accelerated, Automated
- Led: Spearheaded, Owned, Drove, Championed
- Collaborated: Partnered, Coordinated, Mentored, Facilitated
What to Quantify
If you can answer any of these, include the number:
- How many users/requests does this serve?
- What % did you improve (performance, coverage, speed)?
- How many team members did this affect?
- How much time did it save?
- What was the scale? (lines of code, services, endpoints)
If you can't quantify, describe impact on the team or project instead.
Portfolio Project Writeup Template
## [Project Name]
**Problem:** [What problem does this solve? Why does it matter?]
**My Role:** [What specifically did YOU build or own?]
**Technical Approach:** [Key decisions and why you made them]
**Result:** [What was the outcome? What would you do differently?]
**Stack:** [Technologies used]
LinkedIn / Professional Bio
Structure
- Who you are — current role + years of experience
- What you do — specific skills and focus areas
- What you've built — 1-2 concrete accomplishments
- What you're interested in — where you want to grow
What NOT to Include
- "Passionate about technology" (everyone says this)
- Long lists of tools without context
- Vague phrases like "strong work ethic" or "team player"
- Job descriptions instead of accomplishments
Honesty Rules
- Never claim sole ownership of team work — say "contributed to" or "part of the team that"
- Don't inflate titles or scope
- If you used AI to build something, it's still valid — just know it deeply enough to discuss it
- Gaps in employment are fine — be prepared to explain, not hide them
1---2name: resume-portfolio3description: Resume & Portfolio4---56# Resume & Portfolio78## Core Principle9Your resume is not a job description of what you did — it's a curated argument for why you're the right person for a specific role. Every line should earn its place.1011---1213## Resume Writing Formula1415### For Each Role / Project16```17[Action verb] [what you built/did] [using/with what]18[that resulted in / achieving] [measurable outcome]19```2021Examples:22```23WEAK: "Worked on BTT module development"24STRONG: "Built Query Clarity Assessment Agent achieving 95%+ test 25 coverage, unblocking production deployment for the team"2627WEAK: "Helped with frontend development"28STRONG: "Implemented LaunchDarkly feature flagging for BTT UI, 29 enabling safe gradual rollout to production users"30```3132### Strong Action Verbs by Category33- **Built/Created:** Developed, Engineered, Architected, Implemented34- **Improved:** Optimized, Reduced, Accelerated, Automated35- **Led:** Spearheaded, Owned, Drove, Championed36- **Collaborated:** Partnered, Coordinated, Mentored, Facilitated3738---3940## What to Quantify4142If you can answer any of these, include the number:43- How many users/requests does this serve?44- What % did you improve (performance, coverage, speed)?45- How many team members did this affect?46- How much time did it save?47- What was the scale? (lines of code, services, endpoints)4849If you can't quantify, describe impact on the team or project instead.5051---5253## Portfolio Project Writeup Template5455```markdown56## [Project Name]5758**Problem:** [What problem does this solve? Why does it matter?]5960**My Role:** [What specifically did YOU build or own?]6162**Technical Approach:** [Key decisions and why you made them]6364**Result:** [What was the outcome? What would you do differently?]6566**Stack:** [Technologies used]67```6869---7071## LinkedIn / Professional Bio7273### Structure741. **Who you are** — current role + years of experience752. **What you do** — specific skills and focus areas763. **What you've built** — 1-2 concrete accomplishments774. **What you're interested in** — where you want to grow7879### What NOT to Include80- "Passionate about technology" (everyone says this)81- Long lists of tools without context82- Vague phrases like "strong work ethic" or "team player"83- Job descriptions instead of accomplishments8485---8687## Honesty Rules88- Never claim sole ownership of team work — say "contributed to" or "part of the team that"89- Don't inflate titles or scope90- If you used AI to build something, it's still valid — just know it deeply enough to discuss it91- Gaps in employment are fine — be prepared to explain, not hide them
jamestorrevillas