jamestorrevillas Career Growth
The Developer Growth Model
Technical skills alone don't drive career growth. The formula:
Impact = Technical Skill × Communication × Ownership × Visibility
All four multiply — zero in any impact perception.
Levels of Developer Maturity
| Level | Focus | What Distinguishes You |
|---|---|---|
| Junior | Task execution | Completes assigned work |
| Mid | Feature ownership | Owns a feature end-to-end, asks fewer questions |
| Senior | System thinking | Thinks about trade-offs, teaches others, improves the team |
| Staff+ | Org impact | Shapes direction, multiplies other engineers |
To level up: Consistently operate at the level above your current one.
90-Day Growth Plan Template
GOAL: [specific capability or outcome in 90 days]
Month 1 — Foundation
- Learn: [specific skill/concept]
- Build: [small project or contribution]
- Measure: [how you'll know you've made progress]
Month 2 — Application
- Apply: [use the skill in real work]
- Teach: [explain it to someone else]
- Stretch: [attempt something harder]
Month 3 — Mastery
- Lead: [own something using this skill]
- Document: [write about what you learned]
- Review: [evaluate against original goal]
Skill Gap Analysis
Ask AI:
I'm a [current level] developer working with [stack].
I want to become a [target level/role].
What skill gaps do I likely have?
Prioritize by: (1) impact on current work, (2) career value.
Visibility Without Bragging
Growth requires visibility. Do this without self-promotion:
- Write internal documentation others will use
- Present your work in demos or team meetings
- Write commit messages and PR descriptions that tell a story
- Share what you learned from a bug in a team channel
- Review others' code thoughtfully — your name appears in their PRs
The Mentoring Multiplier
Teaching accelerates your own learning by 2x:
- Document your processes, not just your code
- Offer to explain concepts to teammates
- Write "what I learned" notes after completing complex tasks
- Pair program intentionally
Long-Term Signals of Senior+ Performance
- You reduce ambiguity for your team, not add to it
- You make the people around you more effective
- You anticipate problems before they happen
- You make technical arguments with trade-offs, not just opinions
- You deliver without being followed up on