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

The salary-versus-impact-versus-satisfaction debate is a fixture of engineering career forums, and the framing is where the confusion starts. Salary, impact, and satisfaction describe the dominant need at three different stages of vocational development. Treating them as competing priorities turns a sequencing question into a loyalty test, and the decisions that follow tend to misfire.

Organizational psychology has already mapped those stages. Wrzesniewski’s work-orientation research, Self-Determination Theory, and Dan Koe’s Vocation quadrant converge on the same three-step progression. Knowing which step you occupy tells you which dimension deserves attention now, and which one can wait.

The Three Camps

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. They talk past each other because they are answering from different points in 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 is a property of the person, and the job title predicts almost nothing about it.

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 the financial foundation right: learn to negotiate, and find out what your skills sell for on the open market. That work is a prerequisite for everything the later stages ask of you.

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, and you want 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. Stage 2 does its job well; the damage comes from staying in it long after that job is done.

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
• Excellence has become something you present to reviewers

Stage 3: Integration (Calling Orientation)

Stage 3 integrates salary and impact with a deeper sense of purpose; both stay on the table. 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.

The Stage 2 Trap

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 write a large share of new code, 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 of a Stage Transition

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 excitement you never had to rehearse
• The work leaves you with more energy than it took

A Practical Roadmap

If You’re at Stage 1

• Prioritize compensation without guilt. Market rate, negotiation skills, understanding equity: these are the foundation every later choice rests on
• Build transferable skills that outlive any single employer
• Set a financial target that represents “enough”. Without a threshold, you’ll optimize for salary indefinitely
• Avoid premature “purpose” pressure. A calling can wait; a solid foundation cannot

If You’re at Stage 2

• Start small experiments outside your main role: write about what you learn, contribute to open source, or mentor someone. These are low-risk ways to discover what energizes you beyond achievement
• Track where your energy goes. Which parts of your work create energy, and which drain it? That 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 keeps salary and impact as necessary conditions for fulfillment, and accepts that neither is sufficient on its own

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, the one chasing impact, and the one seeking satisfaction are each answering correctly for where they stand.

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

The stage model holds while your constraints are stable enough to plan around. Override it when circumstances force the issue. A layoff, a health event, or a new dependent can drop a Stage 3 engineer back to Stage 1 priorities within a week, and in that situation reverting is the correct response. Run the diagnostic questions again once the constraint lifts.

References

• Wrzesniewski, McCauley, Rozin & Schwartz (1997) - Jobs, Careers, and Callings: People’s Relations to Their Work - Foundational research establishing the three work orientations framework
• Dan Koe - HUMAN 3.0: A Map To Reach The Top 1% - Comprehensive self-development model with Vocation quadrant progression
• Dan Koe - HUMAN 3.0 Self-Discovery & Metatype Prompt - AI-assisted assessment tool for developmental mapping
• Wong et al. (2025) - Autonomy, Competence, and Relatedness in Software Development - Self-Determination Theory applied to developer processes and tools
• Saarimaki et al. (2024) - The Well-Being of Software Engineers: A Systematic Literature Review - Comprehensive review of factors predicting developer wellbeing
• ROMA Framework (2025) - Human-AI Programming Role Optimization - Personality-driven role alignment through Self-Determination Theory
• Ikigai for Software Developers - Practical Ikigai application for developer career decisions
• Software Engineer Job Satisfaction Statistics - Career path satisfaction data among software engineers
• 2025 Stack Overflow Developer Survey - Comprehensive developer satisfaction and workplace data
• Developer Burnout: Signs, Prevention, and Recovery - Burnout risk factors and prevention strategies for developers
• Daniel Pink - Drive: Intrinsic and Extrinsic Motivation in Software Development - SDT-based motivation analysis for software engineering