Greetings, Master adventurer. You have gathered power across every realm, but a hero without a chosen path wanders in circles. Two great roads now diverge before you: the road of the individual contributor, who grows ever deeper in craft, and the road of the manager, who grows ever wider in people. This quest, Career Advancement, hands you the map for both - and the negotiation skills to claim the rewards you have earned.

Whether you are eyeing your first staff-engineer promotion, weighing a management offer, or simply tired of leaving money and growth on the table, this adventure forges the strategist’s eye for your own career.

📖 The Legend Behind This Quest

The old legends are full of heroes who reached the final hall only to freeze, unsure which crown to claim. Some seized a crown that did not fit and spent their reign miserable; others refused all crowns and faded into obscurity. The wise ones studied the two thrones first, tried each briefly, and chose with clear eyes - knowing the choice could be remade if it proved wrong.

Your career is that final hall. The IC-vs-management fork, the leveling ladders, the brand you build, and the offers you negotiate are not luck - they are skills. This quest teaches you to navigate them on purpose.

🎯 Quest Objectives

By the time you complete this epic journey, you will have mastered:

Primary Objectives (Required for Quest Completion)

• The IC vs Management Fork - Understand both tracks and choose with clear eyes
• Leveling and Promotion - Read a rubric and build an evidence-based promotion case
• Building a Technical Brand - Become known for something, inside and outside your company
• Negotiation - Negotiate offers and raises without anchoring against yourself

Secondary Objectives (Bonus Achievements)

• The Brag Document - Track your impact so review season never surprises you
• Staff+ Archetypes - Recognize the tech-lead, architect, solver, and right-hand patterns
• Reading Total Compensation - Understand base, bonus, equity, and vesting

Mastery Indicators

You’ll know you’ve truly mastered this quest when you can:

• Explain the IC vs management fork and why it is reversible
• Map your recent work to a real leveling rubric
• State the one thing you want to be known for
• Hold a number in a negotiation without immediately discounting it

🗺️ Quest Prerequisites

📋 Knowledge Requirements

• Several years of engineering experience
• An honest sense of what energizes vs drains you
• Completion of Technical Leadership (recommended)

🛠️ System Requirements

• A document tool for a brag doc and a promotion case
• Your company’s leveling rubric, if one exists (or a public one)
• Optional: a peer to role-play a negotiation with

🧠 Skill Level Indicators

This 🔴 Hard quest expects:

• You are ready to steer your career instead of drifting through it
• You can advocate for yourself, even when it feels uncomfortable
• Ready for 3-4 hours of focused, reflective work

🌍 Choose Your Adventure Platform

Your career artifacts (brag doc, promotion case) need a private, durable home. Choose yours.

🍎 macOS Kingdom Path

🪟 Windows Empire Path

🐧 Linux Territory Path

☁️ Cloud Realms Path

🧙‍♂️ Chapter 1: The Two Roads - IC vs Management

At a certain level, the ladder forks. The individual-contributor (IC) road leads to staff, principal, and distinguished engineer. The management road leads to manager, director, and VP. Neither is “up” from the other - they are parallel ladders of equal seniority.

⚔️ Skills You’ll Forge in This Chapter

• The real differences between the two tracks
• Reading the signals about which fits you
• Knowing the fork is reversible

🏗️ The Fork, Compared

The honest self-test (answer for real, not aspirationally):
  - When you ship something great, did the joy come from BUILDING it
    or from the TEAM pulling it off together?
  - Last month, were your best moments in code/design, or in 1:1s?
  - Would you rather be the best engineer in the room or the reason
    the room works?
There is no wrong answer — only an honest one.

The most important truth: the fork is reversible. Many people manage for a few years, then return to IC (“the pendulum”). Trying management is not a one-way door. Choose based on what energizes you now, knowing you can re-choose later.

🔍 Knowledge Check: The Two Roads

• What does a manager give up that a staff IC keeps?
• What energizes you more - building, or enabling others to build?
• Why is the IC/management fork reversible?

⚡ Quick Wins and Checkpoints

• Took the self-test: You answered the energizer questions honestly
• Named a leaning: You stated which road pulls you right now and why

🧙‍♂️ Chapter 2: Leveling and the Promotion Case - Making Impact Legible

Promotions are not granted for working hard; they are granted for operating at the next level *already, visibly, with evidence. A leveling rubric is the rule book; your job is to map your work onto it and make the case undeniable.*

⚔️ Skills You’ll Forge in This Chapter

• Reading a leveling rubric
• Keeping a brag doc
• Building a promotion case from evidence

🏗️ The Brag Doc and Promotion Case

The single highest-ROI career habit is a brag document: a running, private log of what you shipped, fixed, and enabled - updated the day it happens, not at review time.

# Brag Doc — <year>

## <Project / contribution>
- What: <what you did, one line>
- Impact: <the OUTCOME — numbers if possible: "cut p95 latency 40%",
           "unblocked 3 teams", "saved $X/mo">
- Scope signal: <self / team / org / company — maps to leveling rubric>
- Evidence: <link to PR, doc, dashboard, kind words from others>

Then map it to the leveling rubric. Levels usually scale on three axes:

Scope of impact:   self  ->  team  ->  multiple teams  ->  org  ->  company
Ambiguity handled: well-defined tasks -> open problems -> vague mandates
Autonomy:          needs direction -> self-directed -> sets direction for others

A promotion case is an argument: “Here is the rubric for the next level. Here are 4-6 concrete examples, with evidence, where I already operated at that level.” Promotions reward demonstrated next-level work, so the case is strongest when you have already been doing the job. Find your manager an advocate-ready packet; do not make them assemble your evidence for you.

🔍 Knowledge Check: Leveling

• What three axes typically scale across levels?
• Why log impact the day it happens instead of at review time?
• What makes a promotion case strong rather than wishful?

🧙‍♂️ Chapter 3: Brand and Negotiation - Claiming Your Worth

Two final skills turn your work into recognition and reward: a technical brand that makes you known for something, and the negotiation backbone to capture the value you create.

⚔️ Skills You’ll Forge in This Chapter

• Building a technical brand
• Understanding total compensation
• Negotiating without anchoring against yourself

🏗️ Brand and the Negotiation Playbook

A technical brand is simply: when people in your domain hear your name, what do they think of? Build it by being known for one thing first - depth beats a scattered presence:

• Pick a niche (“the X person”) and go deep before going wide
• Make work visible: talks, posts, OSS, internal docs others reuse
• Help publicly and consistently - reputation compounds like interest

For negotiation, first read total comp, not just base salary:

Total compensation =
  Base salary      (the safe, recurring number)
+ Bonus            (target % — confirm if it's reliable or aspirational)
+ Equity           (RSUs/options — ask: strike, vesting schedule, current value,
                    refresh policy; a 4-yr cliff vs monthly vesting matters a lot)
+ Sign-on          (one-time — often the most negotiable lever)
+ Benefits         (401k match, learning budget, remote stipend)

The negotiation rules that protect you:

• Never name a number first if you can avoid it. “I’d like to understand the band for this level first.”
• Anchor high but reasonable when you must — you can come down, you can’t go up.
• Negotiate the whole package — if base is capped, ask for sign-on, equity, or a faster review.
• Get competing offers if you can; leverage is the real currency.
• Stay warm, never threaten. “I’m excited to join — can we close the gap on X?” beats ultimatums.
• Silence is a tool. After you state a number, stop talking. Let them respond.

The biggest mistake is anchoring against yourself - discounting your number before they even push back. State it, then be quiet.

🔍 Knowledge Check: Brand and Negotiation

• What is the one thing you want to be known for?
• Name three levers beyond base salary in an offer
• Why should you avoid naming the first number?

🎮 Mastery Challenges

🟢 Novice Challenge: Start a Brag Doc

Objective: Create a brag doc and backfill the last six months.

Requirements:

• At least five entries with impact stated as outcomes
• A scope signal on each (self / team / org / company)
• Evidence linked where possible

Validation: You could hand it to your manager and they’d understand your value.

🟡 Intermediate Challenge: Build a Promotion Case

Objective: Map your work to a real leveling rubric and draft a promotion case.

Requirements:

• The next level’s rubric, with its expectations stated
• 4-6 concrete examples mapped to rubric criteria
• An honest gap analysis of where you’re not yet at-level

Validation: A peer reads it and agrees the case is evidence-based, not wishful.

🔴 Advanced Challenge: Run a Negotiation

Objective: Role-play (or run for real) an offer or raise negotiation.

Requirements:

• Research the band before the conversation
• State a number and then stay silent
• Negotiate at least one non-base lever (equity, sign-on, review timing)

Validation: You held your number without immediately discounting it.

🏆 Quest Rewards & Achievements

🎖️ Badges Earned:

• 🏆 Pathfinder - You chose your track with eyes open
• 🛡️ Master Negotiator - You argued your worth without flinching

🛠️ Skills Unlocked:

• Leveling and Promotion Strategy - Make your impact legible
• Offer Negotiation - Capture the value you create

🔓 Unlocked Quests:

• Architecture Reviews - Demonstrate the staff-level judgment promotions reward
• Mentorship Programs - Sponsor others as you climb

📊 Progression Points: +90 XP

🗺️ Next Steps in Your Journey

Continue the Main Story:

• 🎯 Architecture Reviews - Show the judgment that earns the next level

Explore Side Adventures:

• ⚔️ Mentorship Programs - Lift others as you rise
• ⚔️ Tech Speaking and Writing - Build the brand that opens doors

Character Class Recommendations

💻 Software Developer: Continue to Architecture Reviews
🏗️ System Engineer: Explore Mentorship Programs
🛡️ Security Specialist: Advance to Tech Speaking and Writing

📚 Resources

Official Documentation

• StaffEng - the staff engineer path - Definitive guide to IC leveling and promotion
• progression.fyi - public leveling rubrics - Real engineering ladders to study
• levels.fyi - compensation data - Total-comp benchmarks by level and company

Community Resources

• Julia Evans - Get your work recognized: write a brag document - The canonical brag-doc post
• Charity Majors - The engineer/manager pendulum - Why the fork is reversible
• Patrick McKenzie - Salary Negotiation - The classic, thorough negotiation guide

Learning Materials

• The Staff Engineer’s Path - Tanya Reilly - The IC senior track in depth
• Never Split the Difference - Chris Voss - Negotiation tactics from a hostage negotiator

🤝 Quest Completion Checklist

• ✅ Completed all primary objectives
• ✅ Took the IC vs management self-test honestly
• ✅ Started a brag doc and mapped a promotion case
• ✅ Practiced a negotiation, holding your number
• ✅ Explored the resource library
• ✅ Identified your next quest in the journey

🕸️ Knowledge Graph

Structured wiki-links connect this quest to the IT-Journey knowledge graph. Open the Obsidian Graph View to explore connections.

Level hub: [[Level 1111: Leadership & Innovation]] Overworld: [[🏰 Overworld - Master Quest Map]] Prerequisites: [[Innovation and R&D: Experimentation and Managing Technical Bets]] Unlocks: [[Architecture Reviews: Running Reviews, ADRs, and Trade-off Facilitation]] Obsidian docs: [[Obsidian Knowledge Graph and Wiki Links]]