Career Strategy: Run Yourself Like a One-Person Company
Topic: Career Strategy·4 Principles
"Management is not a promotion, management is a change of profession." — Charity Majors
This week's premise: A career is not an escalator that carries you up if you just log enough years. It is a company you own for life and run as CEO. It has positioning (which market to bet on), product iteration (a promotion is a lagging revenue number), strategic pivots (manager or IC, and when to switch), and exit timing (when to cut losses and leave). Most engineers only "perform well" passively — handing the power over their positioning, their promotion pace, and their stay-or-go decision to someone else's calendar. This week, take it back. This isn't about scheming; it's about running your own ten years like a business, and owning the outcome.
PRINCIPLE 01
Positioning: Bet Where Scarce Meets Strong — Don't Grind in a Crowded Lane
Positioning — Bet Where Scarce Meets Strong
PositioningDifferentiationLeverage
The Principle in One Line
Positioning isn't "what I feel like doing." It's the intersection of three circles: what the org is scarce in ∩ what I can be top-10% at ∩ what I'll invest in long-term. Work inside the intersection is leverage; effort outside it is just grinding.
In Their Words
"You need to think of yourself as an entrepreneur at the helm of at least one living, growing start-up venture: your career."— Reid Hoffman, The Start-up of You, Ch.1
The Positioning Grid: Which Quadrant to Bet On
Scene: BigCat's Positioning Conversation
Setup: You're a TLM with an AI/distributed-systems background. A skip-level asks, "In two years, what do you want to be known for here?"
✗ Common answer (no positioning)
"Something with large language models — that's what's hot. My tech is solid, I can run a team, I'll take on whatever's needed." — Chasing the hype plus "I can do anything" equals scarce in nothing. Everyone is crowding the LLM lane; with no differentiation, you can only compete on hours.
✓ Better answer (the three-circle intersection)
"What the org is most short on is people who can take AI training/inference to real production scale and lead a team to ship it — not demos, but the cost, stability, and scheduling problems under distribution. That sits right on my distributed-systems base. I want to be known as the person who keeps AI systems from collapsing at scale, and I'll pick projects and build a team around that."
Positioning Self-Check
Can I state "I want to be known for X" in one sentence? Is X narrow and specific enough?
Is X genuinely scarce in the org, or just my perception? (Verify demand with 2 skip-levels.)
Can I get into the org's top 10% on X? If not, treat it as a "learning zone" investment, don't force it.
In three years will X be scarcer or commoditized? (e.g. hand-written CRUD is already flattened by AI.)
Of my last 3 projects, how many actually built toward X vs. were just firefighting inertia?
Common Mistakes
Chasing hottest, not scarcest. The hottest lane is usually the most crowded, so scarcity is lowest. Sun Tzu: "avoid the strong, strike the weak" — attack the org's gaps, don't pile into the crowd.
Positioning too broad. "Full-stack + can manage + gets the business" equals no positioning. Broad = replaceable.
Mistaking title for positioning. "I'm a TLM" is a level, not a position. Positioning is "which class of problems I solve that others can't."
Female Leader's Note
Women face a double bind in self-positioning: declaring "I'm great at X" risks the "aggressive / show-off" label, while vague modesty forfeits the positioning payoff. The counter: frame with facts and needs, not adjectives. Don't say "I'm strong, I should own AI infra"; say "Over the last 3 quarters I handled X stability incidents in AI infra — I'd like to formally own it." Let the data say "I'm good" for you.
PRINCIPLE 02
The Promotion Curve: The Title Is a Lagging Indicator
Promotion Is a Lagging Indicator
PromotionVisibilitySponsor
The Principle in One Line
Promotion isn't "you get the title, then start doing the next level's work." It's "you've steadily done next-level work for two quarters, and the title merely ratifies it." Those who wait for permission wait forever.
In Their Words
"No one cares about your career as much as you do. It is up to you to keep yourself happy and challenged in your job."— Camille Fournier, The Manager's Path, Ch.2
Scene: A Promotion Is Evidence, Not a Request
Setup: You think you're ready for Staff / Senior Manager and want to raise it with your boss.
✗ Common approach (asking for it)
"I've been here three years, worked really hard, and I run a team now — can we consider bumping me up a level?" — Using tenure and effort as the argument. Your manager can't defend "hard work" for you in a calibration meeting.
✓ Better approach (evidence + recruiting a sponsor)
"I want to align on promotion. I put together a doc: the next-level responsibilities I've already been doing over the last three quarters — drove architecture decision X across three teams, grew two seniors who now run things independently. I want to confirm: what evidence is still missing? And in calibration, who can vouch for this impact?"
(The last line is the point: you're not asking for "approval," you're turning your manager into your sponsor — the one who speaks for you in the room you're not in.)
Promotion-Evidence Checklist
Do I keep a running "impact log" (brag doc) with quarterly results and quantified impact?
Is my evidence next-level scope, or just doing my current level diligently?
Do I know the explicit rubric from this level to the next? Which criteria are met, which are missing?
Do I have a sponsor? (Not a mentor — someone with decision power willing to vouch in calibration.)
Is my impact seen by the right people, or does only my direct manager know?
Common Mistakes
Confusing effort with impact. Overtime, tenure, "I tried hard" aren't promotion currency; attributable impact is.
A mentor but no sponsor. Mentors give advice; sponsors give opportunities. Promotion runs on the latter.
Working quietly, waiting to be discovered. Impact no one can attribute to you might as well not have happened.
Treating promotion as the finish line. Getting bumped up is a ticket to the next level, not a trophy.
Female Leader's Note
Research consistently shows men are often promoted on potential while women are held to proven results — at the same level, women run an extra "prove it again" lap. Two counters: first, translate potential into accomplished fact (fill the brag doc with impact that already happened, leaving no room for "she's not ready"); second, actively ask for a sponsor rather than wait to be noticed — studies find women get more mentors (advice) but fewer sponsors (opportunities), so patch that link deliberately.
PRINCIPLE 03
Dual Tracks: Manager and IC Are Two Professions, Not High and Low — a Pendulum
The Engineer / Manager Pendulum
Dual trackStaff+Pendulum
The Principle in One Line
Management isn't the "upgraded" version of being an IC — it's a different profession: different skills, different days, different source of fulfillment. The IC high track (Staff/Principal) is peer to management; swinging back and forth between the two isn't failure, it compounds your advantage.
In Their Words
"Management is not a promotion, management is a change of profession. The best line managers I've ever worked for are the ones who don't want your job."— Charity Majors, "The Engineer/Manager Pendulum" (2017)
The Dual-Track Ladder and the Pendulum
Scene: The TLM's Fork-in-the-Road Questions
Setup: You've been a TLM for two years, torn between climbing the manager track or swinging back to Staff IC.
✗ Wrong frame (treating it as a demotion)
"Going back to IC means admitting I failed at management, doesn't it? Once you've moved up, you don't go back." — Treating dual tracks as a one-way elevator, so "face" chains you to a path that doesn't fit you.
✓ Right frame (ask about energy, not face)
Ask yourself three questions: (1) Does my fulfillment come from "I cracked a hard problem myself" or "the team is stronger because of me"? (2) Which moments last week charged me, which drained me? (3) In five years do I want to be known as an architecture decision-maker or an org builder?
See Will Larson's Staff Engineer IC-track archetypes — Tech Lead / Architect / Solver / Right Hand: Staff+ isn't "coding at a higher level," it's an influence profession in its own right. Swinging back is changing your moveset, not a demotion.
Manager vs. IC Decision Checklist
Do my "charging" moments come more from deep technical problem-solving, or from growing people / building systems / cross-team work?
Can I accept that the manager track's fulfillment is indirect and lagging (team output shows up months later)?
If I pick the IC high track, do I understand Staff+ runs on "technical influence and judgment," not lines of code?
Is my company's IC ceiling truly peer to the manager track? (In some places, Staff+ exists in name only — that's a signal about the environment.)
Am I chained by "going back looks bad," rather than choosing by energy and long-term positioning?
Common Mistakes
Going into management to escape code. Management isn't "the reward of not coding," it's a harder, different skill set.
Staying on the manager track for face. Forcing an ill-fitting role because of "fear of looking like a step back" — you do both jobs badly.
Thinking Staff+ is just senior coding. The currency of Staff+ is technical judgment, cross-team influence, and "making complex problems clear," not output volume.
Grinding the IC track at a company with a low IC ceiling. Whether the track exists is an environment problem; don't fight structure with personal effort.
PRINCIPLE 04
When to Pivot: On-Time Always Feels Too Early
When to Pivot — On-Time Quitting Feels Early
PivotCut lossesExit
The Principle in One Line
When the signals to leave appear, "just wait a bit longer" always has reasons (sunk cost, unvested equity, face). But leaving at the right time almost always feels too early; by the time you're "sure you should go," you're usually a year late.
In Their Words
"Quitting on time will usually feel like quitting too early."— Annie Duke, Quit (2022)
Scene: Telling a "Trough" From a "Peak"
Setup: You're a bit bored in your current role, unsure if it's a temporary trough or a real time to pivot.
✗ The sunk-cost trap
"I've put four years in here, equity vests in one more — leaving now would be such a waste. Let me tough it out, maybe it'll get better." — Deciding stay-or-go on what's already been paid, which you can't recover whether you stay or leave.
✓ Opportunity-cost + inflection view
Switch the question: "If I were joining this company and this role fresh today, would I still choose it?" If no, then stay-or-go should be computed on the next year's growth and opportunity, not the last four years' ledger.
Layer on Andy Grove's "strategic inflection point": snow always melts first at the edges — the earliest signs of an org's decline, or your own stalled growth, show up at the periphery (good people start leaving; you haven't learned anything new in a year). Watch the edges; don't wait for the center to collapse.
Can I write down a stop-loss line in advance? ("If X doesn't improve for two straight quarters, I start looking" — set it when calm, not on impulse in a trough.)
Are my reasons to "wait" pointing at future opportunity, or just guarding past sunk cost?
Is what I've learned in the last 12 months enough to underwrite the positioning for my next jump?
Edge signals: are good colleagues leaving? Is my manager still fighting for resources for me?
Am I "running from" (push) or "running toward" (pull)? Both can justify leaving, but be clear which it is.
Common Mistakes · Owning the Gray
Deciding on sunk cost. Equity, tenure, "I've made it this far" — these are the past, not entries in the future's ledger.
Rage-quitting or leaving on a trough impulse. Set the stop-loss line when calm, not on your worst day.
Only "running from," never "running toward." A pivot without clear positioning (Card 1) just repeats the same rut somewhere else.
Toughing it out as "loyalty." Honestly: staying often has real upsides (relationships, equity, stability); leaving has real costs. There's no clean optimum here — only which cost you're willing to pay. Sun Tzu: "if outmatched, be able to avoid the enemy" — a graceful retreat from an unwinnable fight is also strategy.
Go Deeper
Doesn't "run yourself like a company" slide into refined selfishness, treating colleagues as resources?
It does, if all that's left is calculation. The difference: good career strategy aligns your growth with the org's output — the positioning you bet on is exactly what the org is scarce in, and your promotion rests on attributable, real impact. It requires you to deliver value and earn a sponsor's genuine backing, both built on trust, not scheming. The warning signs of the selfish slide: you start grabbing credit, hoarding information, doing only what helps your promotion. Strategy means owning your ten years, not turning every interaction into a transaction.
Positioning should be "narrow and deep," but tech moves fast — won't betting narrow get you obsoleted?
What's narrow is the problem domain, not the tech stack. "Keeping AI systems from collapsing at scale" is a problem domain; the underlying framework will change, but "judgment about stability at scale" is transferable and grows more valuable with age. Betting on a specific tool (a framework, a platform) is indeed risky; betting on a class of hard, durable problems is relatively cycle-resistant. Positioning plus staying in the "learning zone" to keep refreshing tools are not in conflict.
The pendulum sounds nice, but many companies have no truly peer IC high track. Then what?
This is exactly what "whether the track exists is an environment problem" means in the Card 3 checklist. If a company's Staff+ exists in name only and all power sits on the manager track, then "choosing the IC track" is empty talk there — and that itself is important information about the company, to feed into your Card 4 pivot call. Sometimes the right move isn't picking a track at your current company, but moving to one with genuinely equal dual tracks to swing your pendulum. Personal choice must respect structural reality.
"On-time always feels too early" — so how do I avoid becoming a job-hopper who never accumulates anything?
Annie Duke's line targets "should go but staying out of sunk cost," not "jump at the first discomfort." The dividing line is Card 4's pre-set stop-loss: writing down "what conditions make me leave" while calm both stops you from dragging on out of face and from jumping on a mood. Chronic job-hopping is usually the symptom of "only running from, never toward" (no positioning) — fix positioning first, then pivots accumulate. Depth takes time, but the wrong depth just wastes time; the key is telling which one you're in.
Promotion runs on sponsors, but if my org is politicized and sponsors are all faction games?
First separate sponsor from faction: a sponsor vouches for you based on your real impact; a faction is a self-interest bond based on picking a side. The healthy move is to let several people with decision power genuinely see your contribution, rather than betting your fate on a single patron — a single patron is both a faction risk and a fragility (they leave, you collapse). If promotion in your org is fully divorced from contribution and all that's left is side-picking, that's a strong pivot signal (back to Card 4). Politics can't be fully avoided, but you can choose to accumulate backing through contribution rather than dependence.
This Week's Practice · Your Day 43 Action
Do two concrete things this week — not reflection, not reading:
Step 1 (write your positioning sentence + verify): Complete this in one line: "In the next two years I want to be known as 'the person who's great at ___.'" It must be narrow and specific enough to pass Card 1's three-circle intersection. Then find 1 skip-level or senior peer and ask: "Will this capability really be scarce in the org over the next two years?" Use their answer to calibrate your positioning.
Step 2 (start a brag doc): Open a new doc, work backward through the last two quarters, and list — item by item — the next-level impact you're already delivering (quantified where possible). When done, stare at it and ask one reflection question: "Of this evidence, how many items are truly next-level work, and how many are just my current level done diligently?" The gap is what you build toward next quarter.