Tools, Frameworks & Resources¶
Frameworks and tools to help you grow at each level.
Career Planning Frameworks¶
The 5-Year Plan (Update Yearly)¶
Year 1:
- Goal: (e.g., "Reach Senior Engineer level")
- Key milestones: Own feature, mentor someone, 360 review
- Learning: Specific book/skill
- Evaluation: How will we know you've succeeded?
Year 2:
- Building on Year 1...
Year 3–5:
- Bigger goals, longer timeframe
Template to use annually:
Current Level: ___
Target Level in 5 years: ___
Why: ___
Year 1 goal: ___
Milestones: ___
Books/skills: ___
Year 2 goal: ___
[etc.]
The 5x5x5 Framework¶
Evaluate yourself every 5 months on 5 dimensions, 5-point scale:
| Dimension | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| Technical skills | Struggling | Basic | Competent | Advanced | Expert |
| Communication | Unclear | Mostly clear | Clear | Influential | Thought leader |
| Mentoring | None | Occasional | Regular | Structured | Multiplier |
| Business acumen | Clueless | Aware | Aligned | Strategic | Visionary |
| Leadership | None | Emergent | Demonstrated | Consistent | Org-wide |
Track over time. Where are you growing? Where are you stuck?
Self-Assessment Tools¶
The T-Shaped Engineer¶
Your skills should look like a T:
Frontend · Backend · Databases · Cloud · Security · AI tools ← breadth (the top bar)
───────────────────────────┬─────────────────────────────────
│
│ Deep expertise in 1–2 domains ← depth (the stem)
│
▼
Good: Frontend, Backend, Databases, DevOps, etc. (breadth) + Deep in Databases (depth)
Bad: Expert in 10 languages but can't architect a system (all breadth)
Bad: Ultra-deep in one area but can't talk to other teams (all depth)
Action: Where are you weak? Breadth or depth?
The Self-Assessment Scorecard¶
Rate yourself 1–5 on your target role's requirements. Identify gaps.
For Senior Engineer:
| Skill | 1 | 2 | 3 | 4 | 5 | Gap |
|---|---|---|---|---|---|---|
| System design | ✓ | Need: deeper understanding of distributed systems | ||||
| Technical judgment | ✓ | Good | ||||
| Cross-team influence | ✓ | Need: more visibility, bigger projects | ||||
| Mentoring | ✓ | Need: more structured mentoring | ||||
| Business acumen | ✓ | Good |
Frameworks for Career Conversations¶
1:1 Meeting Template (Monthly with Manager)¶
1. How am I doing on my current goals?
- Am I on track for promotion?
2. What's one thing I'm doing well?
- What should I double down on?
3. What's one area to improve?
- How do I get better?
4. What's blocking me or exciting me?
- How can you help?
5. What do you need from me?
Annual Promotion Readiness Check¶
3 months before target promotion:
Level I'm targeting: ___
What I've demonstrated:
- ✓ Scope (show examples)
- ✓ Independence
- ✓ Influence
- ✓ Quality
- ✓ Business acumen
What I still need to show:
- Missing area 1: Plan to demonstrate
- Missing area 2: Plan to demonstrate
Timeline: When will I have proof?
Negotiation Frameworks¶
Salary Negotiation (Rule of Thumb)¶
Data gathering:
- Get market data: Levels.fyi, Glassdoor, Blind, and pay ranges in job posts (now legally required in several U.S. states)
- Know your worth: years, experience, company stage
- Consider: Cost of living, total comp (stock/bonus), equity vesting schedule and refreshers, growth
Negotiation:
- Get the offer in writing and clarify level, location, bonus, equity, vesting, and refreshers
- Ask for a reasonable review period; an immediate deadline deserves scrutiny
- If you want to negotiate:
- "I appreciate the offer. Based on market data and my experience, I was expecting $X."
- Be specific and evaluate the whole package, not just base salary
- Competing offers can help, but never invent one
- Some employers use fixed bands; a respectful "no" to negotiation is not automatically a red flag
- Decide in advance which trade-offs would make you accept or walk away
Red flags:
- ❌ They refuse to explain the level, pay band, or offer terms
- ❌ The offer is materially below credible market evidence without a convincing trade-off
- ❌ They pressure you to decide immediately or threaten to rescind solely because you asked a polite question
Leadership Frameworks¶
Radical Candor 2x2¶
From Kim Scott's "Radical Candor":
| Challenge Directly: LOW | Challenge Directly: HIGH | |
|---|---|---|
| Care Personally: HIGH | 😟 Ruinous Empathy — kind but unhelpful; problems go unaddressed | ✅ Radical Candor — honest feedback delivered with genuine care |
| Care Personally: LOW | 🚫 Manipulative Insincerity — neither honest nor caring | ⚠️ Obnoxious Aggression — honest but harsh |
Radical Candor = High on both axes
- Care personally (genuine interest)
- Challenge directly (honest feedback)
How to apply:
- Give feedback quickly
- Be specific with example
- Show you care about their growth
- Listen to their perspective
- Follow up
Code Review Frameworks¶
The Good Code Review¶
1. Run the code (does it work?)
2. Read the code (is it clear?)
3. Consider maintainability (will junior understand this in 6 months?)
4. Check tests (covered adequately?)
5. Look for bugs (security, performance, edge cases?)
6. For AI-assisted changes: does the author understand it? Any invented APIs,
unneeded dependencies, or copy-pasted patterns that don't fit the codebase?
Give feedback:
- ✓ Celebrate good code
- ? Ask questions ("Have you considered...?")
- ! Flag issues ("This could fail if...")
- Follow up ("Does this help?" "Any questions?")
OKR Framework (Goal Setting)¶
Objective: What do we want to achieve? (qualitative)
Example: "Build world-class observability"
Key Results: How will we know we succeeded? (quantitative, 3-5 per objective)
Example:
- Reduce MTTR (Mean Time to Restore) by 50%
- 95% of deployments have full tracing
- Observability onboarding time < 1 day
Quarterly cadence:
- Q1: Plan OKRs
- Monthly: Check-ins
- Q-end: Reflection & next quarter planning
Engineering Effectiveness Frameworks¶
Useful once you lead a team or org — and for knowing how you might be evaluated.
| Framework | What It Measures | Use It For |
|---|---|---|
| DORA metrics | Change lead time, deployment frequency, failed deployment recovery time, change fail rate, deployment rework rate | Delivery throughput and instability of a team/system |
| SPACE | Satisfaction and well-being, Performance, Activity, Communication and collaboration, Efficiency and flow | A balanced view of developer productivity (never just one dimension) |
| DevEx | Feedback loops, cognitive load, flow state | Finding friction that slows engineers down |
Rules of thumb:
- Measure teams and systems, not individuals
- Pair quantitative metrics with surveys and conversations
- Treat activity metrics (commits, PRs, lines of code, AI-suggestion acceptance rates) as signals, never targets — they are trivially gamed
- For AI initiatives, compare representative tasks and team-level outcomes before and during a measured pilot. Include review effort, quality, rework, delivery throughput/stability, and total cost; DORA's 2026 ROI guide provides a current framework
Tools & Resources¶
Career Tracking¶
- Brag document: A running list of your wins, impact, and feedback — invaluable at review and promotion time
- Notion: Create your own career tracker
- Levels.fyi: Compare comp and title progression
Learning Management¶
- Roam Research: Note-taking for connected knowledge
- Obsidian: Knowledge base
- Readwise: Save + revisit key highlights from books/articles
- Spaced repetition: Anki for learning facts
- AI assistants: Use them to quiz yourself on what you've read, or to critique a design doc draft — not to replace the reading
Networking¶
- X / Bluesky: Follow people in your field
- LinkedIn: Maintain professional network
- Blind: Anonymous discussions (tech industry)
- local meetups: In-person community
Evaluation & Feedback¶
- 360 Review template: Ask managers, peers, reports: "What am I good at? Where do I need to grow?"
- CultureAmp: Employee feedback platform
- Self-reflection: Journal monthly on growth
Books & Learning¶
- Goodreads: Track books, find recommendations
- O'Reilly Learning Platform: Subscription covering most tech books
- Evernote: Book notes capture
- Blinkist: 15-min summaries of books
Company-Specific Resources¶
Check These When Evaluating a Company¶
Career progression:
- Does the company have defined levels? (Ask to see leveling doc)
- How often do people get promoted?
- Are there staff engineer roles? (IC track signal)
Compensation:
- Levels.fyi data for your role/company
- Blind data (anonymous salary data)
- Ask current employees
Culture:
- Glassdoor / Blind reviews (take with grain of salt)
- "How is the relationship between engineering and product?"
- "What's one thing you'd change about the engineering culture?"
- "How much does management respect engineering?"
Learning & Growth:
- "Is there a learning budget?" (How much? How used?)
- "Do people go to conferences?"
- "Are there internal training/workshops?"
- "Is there a mentorship program?"
AI & Tooling:
- "Which AI tools are engineers allowed to use? Who pays for them?"
- "How has AI changed how you evaluate engineers?"
Templates to Steal¶
Career Planning Document¶
# My 5-Year Plan
## Current State
- Level: ___
- Company: ___
- Comp: ___
- Skills strengths: ___
- Skills gaps: ___
## Year 5 Goal
- Target level: ___
- Target company: ___
- Target comp: ___
- Why: ___
## Year 1 Plan
[fill in...]
## Success Metrics (How will I know I'm on track?)
[fill in...]
Mentor Conversation Guide¶
# Questions for My Mentor
1. What was your career path from [my level] to [target level]?
2. What did you struggle with at my level?
3. What surprised you about [target role]?
4. What should I learn/practice now?
5. What books shaped your thinking?
6. What's one piece of advice you'd give?
7. Who else should I talk to?
Should I use all these frameworks?
No. Pick 2–3 that resonate. Frameworks are tools, not rules.
Where can I find these templates?
Copy them straight from this page (code blocks have a copy button) into Notion, Google Docs, Obsidian, or a private Git repo.
How often should I revisit these?
Quarterly (every 3 months). Career progress isn't linear; adjust as you learn.
Tools are helpful, but they're no substitute for honest reflection and action.