Skip to content
~/sph.sh

Salary, Impact, or Satisfaction? The Vocation Question Every Engineer Faces

Why the salary-vs-impact-vs-satisfaction debate is a false trichotomy, and what your answer reveals about your vocational development stage.

Abstract

Engineers wrestle with a recurring question: should I optimize for salary, impact, or satisfaction? After watching this dilemma play out across teams and organizations, I've come to believe the question itself is misleading. These three dimensions aren't competing choices; they're interconnected signals of where you are in your vocational development. Your answer reveals your current stage more than your actual needs.

The False Trichotomy

Open any tech forum and you'll find the debate raging. One camp says chase total compensation: everything else follows when you have financial security. Another argues for impact: build something that matters and the money will come. A third advocates for satisfaction: life's too short to be miserable at work, find what makes you happy.

Each camp has compelling arguments. And each is partly right. The problem is framing these as competing priorities when they actually represent different dimensions of the same vocational journey.

Think of it this way: asking "should I care about salary or impact?" is like asking "should I care about nutrition or exercise?" Both matter. The relevant question is which one needs attention right now, given where you are.

Three Stages of Vocational Development

Research in organizational psychology offers a useful lens here. Amy Wrzesniewski and colleagues identified three distinct work orientations in their foundational 1997 study: people view their work as a Job, a Career, or a Calling.

The fascinating finding: these orientations had nothing to do with the actual occupation. Among a group of administrative assistants doing identical work, roughly equal numbers fell into each category. The orientation lives in the person, not the position.

Dan Koe's HUMAN 3.0 framework maps a similar progression in the Vocation quadrant, moving from Conformist (following prescribed paths) through Individualist (pursuing personal ambition) to Synthesist (integrating multiple perspectives to create aligned value).

Self-Determination Theory adds another layer: our core psychological needs are autonomy, competence, and relatedness. A 2025 study found that when developer roles align with personality through these dimensions, motivation increases by an average of 23%.

Combining these frameworks, a practical three-stage model emerges:

Stage 1: Survival (Job Orientation)

At this stage, salary dominates. And that's completely rational. When basic financial needs aren't met, optimizing for "meaning" is a luxury you can't afford. Student loans, cost of living, supporting family members: these are real constraints.

Engineers at Stage 1 should not feel guilty about prioritizing compensation. Get your financial foundation right. Learn to negotiate. Understand your market value. These aren't shallow pursuits; they're prerequisites.

The signal that you're ready to move on: financial stress no longer drives your decisions, but you catch yourself thinking "is this all there is?"

Stage 2: Achievement (Career Orientation)

Most of the tech industry is optimized for Stage 2. Promotion cycles, leveling systems, scope expansion, TC benchmarking: these are all achievement-stage constructs. And they work well for engineers in this phase.

At Stage 2, impact becomes the primary metric. You want your work to matter. You want scope. You want to see your name on architectures that scale. The drive shifts from "pay me enough" to "let me do something significant."

This stage has genuine value. It builds competence, confidence, and professional identity. The problem isn't Stage 2 itself; it's getting stuck there.

The signals of Stage 2 stagnation:

  • You've achieved the title/TC you wanted, but the satisfaction was temporary
  • You optimize for scope in promotion documents rather than actual interest
  • You compare yourself to peers on metrics you don't actually care about
  • You're performing excellence rather than experiencing it

Stage 3: Integration (Calling Orientation)

Stage 3 isn't about abandoning salary or impact. It's about integrating them with a deeper sense of purpose. Engineers at this stage have typically secured their financial foundation (Stage 1) and proven their competence (Stage 2). Now they're asking a different question: "How does my work fit into the life I want to live?"

This often involves creating something (open source projects, teaching, writing, consulting, founding a company) rather than purely consuming roles designed by others. The Ikigai framework captures this well: the intersection of what you love, what you're good at, what the world needs, and what you can be paid for.

Importantly, Stage 3 can't be forced or skipped to. Engineers who try to jump directly to "calling" without the foundation of Stages 1 and 2 often burn out spectacularly. The mission-driven startup that pays below market and demands 60-hour weeks, mistaking sacrifice for purpose.

Why Most Engineers Get Stuck at Stage 2

The tech industry's incentive structures are built for Stage 2. Here's what reinforces the pattern:

Compensation culture: Tools like levels.fyi and communities like Blind create a monoculture around TC as the primary career metric. When everyone around you is optimizing for compensation, it feels irrational not to.

Leveling systems: Promotion criteria at most companies reward scope expansion and measurable impact: Stage 2 behaviors. There's no promotion rubric for "found deeper meaning in their work."

AI anxiety: The AI wave is creating a new form of Stage 1 anxiety even among senior engineers. When AI tools generate close to half of new code for active users, questions about job security resurface. This can disguise itself as Stage 2 dissatisfaction ("I need more impact") when it's actually Stage 1 fear ("Am I still valuable?").

Cross-domain neglect: Dan Koe's framework makes an interesting observation: vocational problems often have solutions outside of work. An engineer stuck at Stage 2 might not need a better job. They might need to address neglected areas of health, relationships, or personal growth. Optimizing Vocation while ignoring Mind, Body, and Spirit creates a developmental imbalance that no career move can fix.

Signals You're Ready for the Next Stage

Rather than prescribing when to transition, here are diagnostic questions for each shift:

Stage 1 → Stage 2 Readiness

  • Do you have 6+ months of expenses saved?
  • Can you turn down a job offer without financial panic?
  • Do you find yourself wanting more than just a paycheck from your work?

Stage 2 → Stage 3 Readiness

  • Have you achieved a meaningful professional milestone, and found the satisfaction surprisingly short-lived?
  • Do you spend more energy on positioning your work than doing the work?
  • Are you drawn to activities (teaching, writing, mentoring) that don't fit neatly into your performance review?
  • Can you articulate what you'd work on if money weren't a factor, and is it different from your current work?

Channel Indicators

In Dan Koe's framework, "Channels" are moments of deep engagement that accelerate development. You know you've found a Channel when:

  • Time disappears while you're working on something
  • You research a topic voluntarily, outside of work hours, because you can't stop
  • You talk about a project with genuine excitement, not rehearsed enthusiasm
  • The work creates energy rather than draining it

What Actually Works

If You're at Stage 1

  • Prioritize compensation without guilt. Market rate, negotiation skills, understanding equity: these aren't shallow, they're foundational
  • Build transferable skills, not just company-specific knowledge
  • Set a financial target that represents "enough". Without a threshold,, you'll optimize for salary indefinitely
  • Avoid premature "purpose" pressure. You don't need a calling right now. You need a solid foundation

If You're at Stage 2

  • Start small experiments outside your main role. Write about what you learn. Contribute to open source. Mentor someone. These are low-risk ways to discover what energizes you beyond achievement
  • Pay attention to energy, not just outcomes. Which parts of your work create energy vs drain it? The pattern reveals more about your calling than any career framework
  • Invest in non-work domains. Physical health, relationships, creative hobbies: these often unlock vocational clarity more effectively than career tactics
  • Question your metrics. Are you optimizing for what you actually want, or for what the industry tells you to want?

If You're at Stage 3

  • Design your work to align all three dimensions. This might mean negotiating a different role, going independent, building a portfolio career, or creating something new
  • Accept that this stage looks different for everyone. There's no template for a Calling. The engineer who finds it in open source infrastructure is just as valid as the one who finds it in teaching
  • Stay grounded in the earlier stages. Integration doesn't mean ignoring salary or impact; it means they're necessary but not sufficient conditions for fulfillment

The AI Dimension

AI is scrambling these stages in interesting ways. When AI can generate code, documentation, and even architecture proposals, the "competence" dimension of Stage 2 gets destabilized. What does "impact" mean when your AI pair programmer does the implementation?

This is creating a paradox: AI tools increase productivity (Stage 2 metric) while potentially decreasing the felt sense of competence (a core Stage 2 need). Engineers who tie their identity entirely to coding ability face an identity disruption that looks like a Stage 2 problem but is actually a Stage 3 opportunity.

The engineers navigating this best are the ones who've already begun separating their identity from their output. They see AI as a tool that amplifies their judgment, taste, and architectural thinking. The very qualities that Calling-oriented work tends to develop.

Conclusion

The salary-impact-satisfaction question isn't a choice to make; it's a developmental stage to recognize. Each stage has legitimate needs and valid priorities. The engineer optimizing for TC isn't shallow. The one chasing impact isn't naive. The one seeking satisfaction isn't lazy.

What matters is honest self-assessment: which stage am I actually in? What does the next one require? And am I ready for the transition, or am I performing it?

The most fulfilling engineering careers don't choose between salary, impact, and satisfaction. They build each dimension in sequence, arriving at a place where the question itself dissolves. Because the work is well-compensated, meaningful, and energizing all at once. Not because you got lucky, but because you did the developmental work at each stage.

References

career-growth
job-satisfaction
burnout
developer-experience
ikigai
self-determination-theory
career-planning

Related Posts