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.

Talking Past Each Other#

Open any tech forum and you’ll find the debate raging. One camp says chase total compensation, because everything else follows once you have financial security. Another argues that if you build something that matters, the money will come. A third says life is too short to be miserable at work.

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.

The Stage Model#

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.

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.

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 names three core psychological needs: 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:

Survival#

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, and supporting family members are real constraints.

Engineers at Stage 1 should not feel guilty about prioritizing compensation. Learning to negotiate and finding out what your skills sell for on the open market is the prerequisite for everything the later stages ask of you. You are ready to move on when financial stress no longer drives your decisions and you still catch yourself thinking “is this all there is?”

Achievement#

Most of the tech industry is optimized for Stage 2. Promotion cycles, leveling systems, scope expansion, and TC benchmarking are 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.”

The stage builds competence, confidence, and professional identity. Problems start when engineers stay in it long after those are secure.

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

Integration#

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, commonly at a mission-driven startup that pays below market and demands 60-hour weeks.

The Stage 2 Trap#

The tech industry’s incentive structures are built for Stage 2, and they reinforce the pattern from several directions at once.

Tools like levels.fyi and communities like Blind create a monoculture around total compensation as the primary career metric. When everyone around you is optimizing for compensation, it feels irrational not to. Promotion criteria at most companies compound this by rewarding scope expansion and measurable impact, both Stage 2 behaviors.

The AI wave adds a newer layer. When AI tools write a large share of new code, questions about job security resurface even among senior engineers, and this Stage 1 anxiety can disguise itself as Stage 2 dissatisfaction (“I need more impact”) when it’s actually Stage 1 fear (“Am I still valuable?”).

Dan Koe’s framework points somewhere else for the rest. Vocational problems often have solutions outside of work, and an engineer stuck at Stage 2 might not need a better job at all. The neglected area could be health, relationships, or personal growth.

Testing Your Own Stage#

The move out of Stage 1 is the easier one to check. Do you have 6+ months of expenses saved? Can you turn down a job offer without financial panic? Until those answers are yes, prioritizing compensation is the right call, and the work behind it is plain enough. Know your market rate, learn to negotiate, understand how equity works, and build transferable skills that outlive any single employer. Set a number that represents “enough”, because without a threshold you will optimize for salary indefinitely.

Stage 2 is harder to read from the inside. Have you achieved a meaningful professional milestone, only to find the satisfaction surprisingly short-lived? Do you spend more energy positioning your work than doing it? Can you name what you’d work on if money weren’t a factor, and is it different from what you do now? If those questions land, the next step is a small one. Writing about what you learn, contributing to open source, or mentoring someone are low-risk ways to find out what energizes you beyond achievement. Non-work domains count too, since physical health, relationships, and creative hobbies often unlock vocational clarity more effectively than career tactics.

Dan Koe’s framework calls the moments of deep engagement that accelerate development Channels. You know you’ve found one 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

Stage 3 has no template. Designing work that aligns all three dimensions might mean negotiating a different role, going independent, building a portfolio career, or creating something new. The engineer who finds a Calling in open source infrastructure is just as valid as the one who finds it in teaching.

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?

The paradox is that AI tools increase productivity (a 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 feel this disruption most acutely.

The ones navigating it best have already begun separating their identity from their output. They see AI as a tool that amplifies their judgment, taste, and architectural thinking.

When the Model Breaks Down#

The stage model holds while your constraints are stable enough to plan around. 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.

References#

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