Guide

Most engineers optimize the next ticket and hope a career emerges. Career strategy is the opposite: periodically choosing environments that compound skills, optionality and compensation — then executing hard inside them. You will still be wrong sometimes; the point is to be wrong for reasons you chose, not by default.

Once a year, write a one-page plan: primary optimization (learning / comp / mission / lifestyle), target company stage, desired stem of the T, hard constraints, and a stay-or-go trigger. Revisit after any major offer or promo.

Early career (roughly first 5–8 years) usually leans learning and scope, because skills and reputation compound. Later you may deliberately optimize cash, lifestyle or mission. Doing all three at once is rare. Transferable craft — writing, production ownership, finishing — outlasts whichever framework is loud this year. When offers are close on paper, choose the team.

Concepts in this section

Read them in order.

StepConceptWhat it answers
1Company stageWhat are you trading: learning, scope, pay, risk?
2Choosing teamsWhy do manager, importance and growth beat the logo?
3T-shaped skillsWhat stem and crossbar should you build?
4Evaluating startup offersHow do you unbundle cash, equity, runway and scope?
5When to switchStay for a scope jump, or leave a structural block?
6Light public profileWhat discoverability is worth doing without a brand business?

Constraints that dominate

Visa, location, dependents, personal runway and health are not footnotes. Write them first. Within those constraints, optimize. A "dream" seed role that breaks your visa or sleep is mispriced risk.

Patrick McKenzie: describe business outcomes you create — revenue protected, cost removed, risk reduced — not "programmer" as an identity.

Example

Offer A: $180k cash + liquid RSUs, strong manager, moderate scope. Offer B: $140k + 0.15% at seed, claimed 18-month runway, you own the backend. Savings and appetite for scope can make B rational. Debt, dependents or visa can make A dominate. Constraints first; then the equity story.

Common mistakes

  • Logo over team. Manager and path usually eat strategy.
  • Romanticizing % without strike, preferences, dilution or runway.
  • Switching because a week was hard while a scope jump is coming — or staying in a structurally blocked promo.
  • Betting identity on one framework. Outcomes travel; fashions do not.

Key takeaways

  • Stage trades learning, scope, pay and risk; pick for this season.
  • Team (manager, importance, technical depth) usually beats logo.
  • Aim for T-shaped skills: a scarce stem plus a useful crossbar.
  • Startup equity is a distribution; learn the instruments.
  • Switch when growth is structurally blocked; leave with reputation intact.

Further learning

Charity Majors' Engineer/Manager Pendulum talk:

The Engineer/Manager PendulumInfoQ
The Pragmatic Engineer (Gergely Orosz)Observations across the software engineering industry.The Pragmatic Engineer Don't Call Yourself A Programmer (Patrick McKenzie)Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com