Career Growth Plan Template

# Career Growth Plan: [Name]

**Created:** [YYYY-MM-DD]
**Last Updated:** [YYYY-MM-DD]
**Manager:** [Manager Name]
**Review Frequency:** [Monthly/Quarterly]

---

## Current State

### Role & Level

**Current Title:** [Title]
**Level:** [Level]
**Team:** [Team]
**Tenure in Role:** [Time]

### Strengths

*What are you great at? What do others rely on you for?*

1. [Strength 1]
2. [Strength 2]
3. [Strength 3]

### Areas for Development

*What skills or behaviors need improvement?*

1. [Development area 1]
2. [Development area 2]
3. [Development area 3]

### Recent Accomplishments

*Key achievements in the past 6-12 months*

- [Accomplishment 1]
- [Accomplishment 2]
- [Accomplishment 3]

---

## Career Vision

### Long-Term Goal (3-5 years)

*Where do you want to be in your career?*

[Description of long-term aspirations]

### Medium-Term Goal (1-2 years)

*What's the next milestone?*

[Specific role, level, or achievement you're working toward]

### Why This Path?

*What motivates this direction?*

[Explanation of why this path is meaningful to you]

---

## Gap Analysis

### Skills Gap

| Required Skill | Current Level | Target Level | Gap |
|----------------|---------------|--------------|-----|
| [Skill 1] | [1-5] | [1-5] | [Description] |
| [Skill 2] | [1-5] | [1-5] | [Description] |
| [Skill 3] | [1-5] | [1-5] | [Description] |

### Experience Gap

| Required Experience | Current State | What's Needed |
|---------------------|---------------|---------------|
| [Experience 1] | [Current] | [Gap] |
| [Experience 2] | [Current] | [Gap] |
| [Experience 3] | [Current] | [Gap] |

### Behavior/Competency Gap

| Competency | Current | Target | Development Need |
|------------|---------|--------|------------------|
| [Competency 1] | [Description] | [Target] | [Need] |
| [Competency 2] | [Description] | [Target] | [Need] |

---

## Development Goals

### Goal 1: [Title]

**Description:** [What you want to achieve]

**Why it matters:** [How this connects to your career vision]

**Success criteria:** [How you'll know you've achieved it]

**Timeline:** [Target date]

**Actions:**
- [ ] [Action 1] - [Due date]
- [ ] [Action 2] - [Due date]
- [ ] [Action 3] - [Due date]

**Resources needed:**
- [Resource 1]
- [Resource 2]

**Support from manager:**
- [Support needed]

### Goal 2: [Title]

[Same structure as above]

### Goal 3: [Title]

[Same structure as above]

---

## Learning Plan

### Formal Learning

| Learning Activity | Type | Timeline | Status |
|-------------------|------|----------|--------|
| [Course/Book] | [Course/Reading] | [Dates] | [Status] |
| [Certification] | [Certification] | [Dates] | [Status] |
| [Training] | [Workshop] | [Dates] | [Status] |

### On-the-Job Learning

| Project/Activity | Skills Developed | Timeline |
|------------------|------------------|----------|
| [Project 1] | [Skills] | [Dates] |
| [Project 2] | [Skills] | [Dates] |

### Social Learning

| Activity | Purpose | Frequency |
|----------|---------|-----------|
| [Mentor meetings] | [Purpose] | [Frequency] |
| [Peer learning] | [Purpose] | [Frequency] |
| [Community participation] | [Purpose] | [Frequency] |

---

## Support Network

### Mentors

| Name | Area of Expertise | Frequency |
|------|-------------------|-----------|
| [Name] | [Area] | [Frequency] |

### Sponsors

| Name | How They Support |
|------|------------------|
| [Name] | [Support type] |

### Peers/Learning Partners

| Name | Shared Goals |
|------|--------------|
| [Name] | [Goals] |

---

## Progress Tracking

### Quarterly Check-Ins

**Q[X] [Year] Review:**

*Progress on goals:*
- Goal 1: [Status and notes]
- Goal 2: [Status and notes]
- Goal 3: [Status and notes]

*Wins:*
- [Win 1]
- [Win 2]

*Challenges:*
- [Challenge 1]
- [Challenge 2]

*Adjustments needed:*
- [Adjustment 1]

---

## Next Steps

### Immediate (Next 30 days)

1. [Action 1]
2. [Action 2]
3. [Action 3]

### This Quarter

1. [Focus area 1]
2. [Focus area 2]

### Discussion Topics for Next 1:1

- [Topic 1]
- [Topic 2]

---

## Signatures

**Employee:** _______________ **Date:** _______________

**Manager:** _______________ **Date:** _______________

# Career Growth Plan: Alex Rivera

**Created:** 2025-10-01
**Last Updated:** 2025-10-15
**Manager:** Sarah Chen
**Review Frequency:** Monthly in 1:1s, Formal quarterly

---

## Current State

### Role & Level

**Current Title:** Senior Software Engineer
**Level:** L5 (Senior)
**Team:** Platform Team
**Tenure in Role:** 18 months

### Strengths

1. **Technical depth** - Deep expertise in distributed systems and database performance. Go-to person for complex debugging.

2. **Reliability** - Consistently delivers on commitments. Projects are well-tested and documented.

3. **Mentoring (informal)** - Junior engineers seek me out for help. Patient teacher who explains concepts clearly.

4. **System design** - Can design end-to-end systems considering scalability, reliability, and maintainability.

### Areas for Development

1. **Cross-team influence** - Tend to focus on my team's work. Need to build relationships and drive initiatives across teams.

2. **Difficult conversations** - Avoid giving hard feedback to peers. Need to address issues more directly.

3. **Strategic thinking** - Good at solving problems given to me. Need to better identify which problems to solve.

4. **Written communication** - Design docs are thorough but sometimes too long. Need to communicate more concisely for leadership audiences.

### Recent Accomplishments

- Led migration of payment service to new infrastructure (reduced costs 40%)
- Designed and implemented caching layer (improved latency by 60%)
- Mentored 2 engineers through their first production deployments
- Wrote ADR for database selection that became team standard
- On-call reliability: zero escalations in last 6 months

---

## Career Vision

### Long-Term Goal (3-5 years)

I want to be a **Staff Engineer** with significant technical influence across the engineering organization. I see myself as someone who tackles the hardest cross-cutting problems, mentors senior engineers, and shapes technical direction.

I'm NOT interested in management long-term (I tried a 3-month stint and realized I prefer technical depth), but I want the influence and organizational impact of a senior technical leader.

### Medium-Term Goal (1-2 years)

**Promotion to Staff Engineer (L6)** within 18 months.

This means demonstrating:
- Technical leadership beyond my team
- Organizational impact (not just project impact)
- Ability to influence without authority
- Strategic technical judgment

### Why This Path?

I love solving complex technical problems and helping others grow. The Staff track lets me do both while increasing my leverage. I've seen Staff engineers have tremendous impact by tackling problems that span teams and by elevating the technical bar across the organization.

I also want to continue coding. Staff at our company still writes code (30-50%), which is important to me.

---

## Gap Analysis

### Skills Gap

| Required Skill | Current Level | Target Level | Gap |
|----------------|---------------|--------------|-----|
| System Design | 4 | 5 | Can design complex systems, need more practice with org-wide architecture |
| Technical Writing | 3 | 4 | Docs are thorough but need to be more concise and strategic |
| Cross-team Communication | 2 | 4 | Limited experience driving cross-team initiatives |
| Technical Strategy | 2 | 4 | Good at tactical, need strategic perspective |
| Stakeholder Management | 3 | 4 | Comfortable with engineering leadership, less so with product/exec |

### Experience Gap

| Required Experience | Current State | What's Needed |
|---------------------|---------------|---------------|
| Led cross-team technical initiative | Zero | Lead at least one cross-team project |
| Architecture review participation | Attended some | Regular participant, then leader |
| Technical roadmap ownership | Contributed to team roadmap | Own or significantly influence org roadmap |
| Executive presentation | Zero | Present to eng leadership at least once |
| Tech blog/conference talk | Zero | Publish or present externally |

### Behavior/Competency Gap

| Competency | Current | Target | Development Need |
|------------|---------|--------|------------------|
| Influence without authority | Limited to team | Cross-org | Build relationships, practice persuasion |
| Giving difficult feedback | Avoids | Direct but kind | Practice in low-stakes situations |
| Strategic thinking | Reactive | Proactive | Read more strategy content, practice identifying opportunities |
| Executive communication | N/A | Competent | Learn to communicate to non-technical audiences |

---

## Development Goals

### Goal 1: Lead Cross-Team Technical Initiative

**Description:** Identify and lead a technical initiative that spans at least 2 teams and delivers measurable organizational value.

**Why it matters:** Demonstrates ability to influence beyond my team, build consensus, and deliver results across organizational boundaries. Core Staff competency.

**Success criteria:**
- Initiative identified and scoped by end of Q4
- Execution plan with buy-in from affected teams
- Measurable improvement (performance, reliability, developer experience)
- Positive feedback from other team leads

**Timeline:** Q4 2025 - Q2 2026

**Actions:**
- [ ] Identify 2-3 potential initiatives (Oct 15)
- [ ] Discuss with Sarah to align on scope (Oct 22)
- [ ] Socialize with other team leads (Nov 1-15)
- [ ] Write proposal/RFC (Nov 30)
- [ ] Get approval and begin execution (Dec 15)
- [ ] Complete initiative and measure impact (Q2 2026)

**Resources needed:**
- Time allocation (Sarah to help negotiate 20% for this)
- Access to other teams' metrics and roadmaps
- Architecture review slot for proposal

**Support from manager:**
- Introduction to other team leads
- Sponsorship in leadership discussions
- Coaching on stakeholder management

### Goal 2: Improve Executive Communication Skills

**Description:** Develop ability to communicate technical concepts effectively to non-technical and leadership audiences.

**Why it matters:** Staff engineers regularly present to leadership, influence budget decisions, and represent engineering in cross-functional discussions. My current style is too detailed for these audiences.

**Success criteria:**
- Complete executive communication training
- Present to engineering leadership at least once
- Positive feedback on clarity and strategic framing
- Write one "executive summary" doc that gets leadership approval

**Timeline:** Q4 2025 - Q1 2026

**Actions:**
- [ ] Take "Communicating with Executives" course (Oct)
- [ ] Shadow Sarah in 2 leadership meetings (Oct-Nov)
- [ ] Practice presenting initiative proposal to Sarah first (Nov)
- [ ] Present to engineering leadership (Dec or Jan)
- [ ] Write exec summary for 2025 platform retrospective (Jan)
- [ ] Get feedback and iterate (ongoing)

**Resources needed:**
- Access to recommended training
- Sarah's time for coaching and shadowing
- Opportunity to present in leadership forum

**Support from manager:**
- Recommend resources and training
- Allow me to shadow leadership meetings
- Create opportunity for leadership presentation
- Provide direct feedback on my communication

### Goal 3: Build Regular Feedback Practice

**Description:** Develop habit of giving timely, specific feedback to peers, including difficult conversations when needed.

**Why it matters:** Staff engineers must elevate others' work, which requires giving feedback. Avoiding difficult conversations limits my ability to improve team output and mentor senior engineers.

**Success criteria:**
- Give feedback to at least 2 peers per week
- Have one "difficult" feedback conversation per month
- Track feedback given and outcomes
- Feedback becomes natural, not forced

**Timeline:** Ongoing, assess quarterly

**Actions:**
- [ ] Read "Radical Candor" (Oct)
- [ ] Set up weekly reminder to reflect on feedback opportunities (Oct)
- [ ] Practice SBI model in low-stakes situations (Oct-Nov)
- [ ] Have first difficult conversation with support from Sarah (Nov)
- [ ] Keep feedback log to track patterns (ongoing)
- [ ] Request feedback on my feedback from recipients (quarterly)

**Resources needed:**
- Book / training resources
- Safe space to practice and debrief

**Support from manager:**
- Coach me before difficult conversations
- Debrief after to improve
- Model good feedback in our 1:1s

---

## Learning Plan

### Formal Learning

| Learning Activity | Type | Timeline | Status |
|-------------------|------|----------|--------|
| Radical Candor (book) | Reading | Oct 2025 | In progress |
| Staff Engineer by Will Larson | Reading | Nov 2025 | Not started |
| Executive Communication Workshop | Course | Oct 2025 | Enrolled |
| System Design Interview Prep (for Staff calibration) | Self-study | Dec 2025 | Not started |

### On-the-Job Learning

| Project/Activity | Skills Developed | Timeline |
|------------------|------------------|----------|
| Lead cross-team initiative | Influence, stakeholder mgmt | Q4-Q2 |
| Architecture review participation | Strategic thinking, communication | Ongoing |
| Mentoring Jamie (formal) | Teaching, feedback | Q4 |
| On-call lead rotation | Operational leadership | Q1 2026 |

### Social Learning

| Activity | Purpose | Frequency |
|----------|---------|-----------|
| 1:1 with David (Staff Eng) | Learn from Staff experience | Monthly |
| Platform leads sync | Build cross-team relationships | Biweekly |
| Write for eng blog | Practice external communication | Quarterly |
| Local meetup talks | Build presentation skills | 2x/year |

---

## Support Network

### Mentors

| Name | Area of Expertise | Frequency |
|------|-------------------|-----------|
| David Kim | Staff Engineer experience, system design | Monthly |
| Lisa Wang | Cross-functional communication | As needed |

### Sponsors

| Name | How They Support |
|------|------------------|
| Sarah Chen (manager) | Visibility, opportunities, coaching |
| James Lee (VP Eng) | Sponsor for cross-team initiatives |

### Peers/Learning Partners

| Name | Shared Goals |
|------|--------------|
| Mike Johnson | Both targeting Staff, peer learning |
| Emma Davis | Feedback accountability partner |

---

## Progress Tracking

### Q4 2025 Review (October 15)

*Progress on goals:*

**Goal 1 (Cross-team initiative):** On track
- Identified API consistency as potential initiative
- Initial conversations with Auth team lead
- Next: scope proposal and socialize

**Goal 2 (Exec communication):** On track
- Enrolled in workshop (starts Oct 20)
- Shadowed one leadership meeting
- Noted how Sarah frames updates

**Goal 3 (Feedback):** Progressing
- Started Radical Candor book
- Gave feedback to 3 peers this week (positive)
- Haven't had difficult conversation yet (need to do this)

*Wins:*
- Caching project launched successfully, 60% latency improvement
- Got positive feedback from Jamie on mentoring
- Architecture review slot confirmed for November

*Challenges:*
- Difficult conversation avoidance—need to just do it
- Finding time for reading with project deadlines

*Adjustments needed:*
- Block 1 hour/week for reading (put on calendar)
- Identify specific difficult conversation to have in next 2 weeks

---

## Next Steps

### Immediate (Next 30 days)

1. Complete executive communication workshop
2. Write draft RFC for API consistency initiative
3. Have first difficult feedback conversation
4. Shadow 2nd leadership meeting

### This Quarter

1. Get API consistency initiative approved
2. Complete Radical Candor book
3. Present something to engineering leadership

### Discussion Topics for Next 1:1

- Review RFC draft together
- Discuss difficult conversation I need to have
- Get Sarah's feedback on my communication in recent meetings

---

## Signatures

**Employee:** Alex Rivera **Date:** October 15, 2025

**Manager:** Sarah Chen **Date:** October 15, 2025