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

markdown
## [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

1. Who you are — current role + years of experience
2. What you do — specific skills and focus areas
3. What you've built — 1-2 concrete accomplishments
4. 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