Coaching vs Software Engineering: 6 Months of Career Coaching Insights for Developers

6 months ago I started my coaching program for tech workers in Europe.

Since then, I've worked with Software Engineers, Data Scientists, Data Engineers, Machine Learning Engineers, and more—helping them level up their tech careers.

I've learned a few things along the way.

Today I'm sharing insights that are valuable whether you're:

Looking for a coach to improve your career (what to look for)

Considering becoming a coach yourself (are you a good fit? Is it worth it?)

Explore strategic career opportunities →

The Fundamental Difference

Let's start from the basics:

Software engineering is about solving problems through collaborative software development.

Coaching is fundamentally different. It's built on three pillars:

1. Empathy and Emotional Intelligence ❤️

In the end, it all starts from the person you're coaching.

If you're not aware of them—how they're feeling, what they desire, what challenges them—you can't work effectively.

You coach humans, not robots.

This is the heart of coaching.

Software Engineering	Career Coaching
Solve technical problems	Understand human problems
Debug code & systems	Debug careers & mindsets
Work with deterministic logic	Work with emotions & uncertainty
Collaborate with other engineers	Build deep 1:1 relationships
Ship features	Transform lives

2. Intuition 🧠

There's an infinite amount of career choices one can make in the short and long term.

An infinite amount of variables at play.

You can't always logically and deterministically solve things.

It's important to have great intuition and be able to draw lines amid the chaos and, ultimately, just give good recommendations.

This is the brain of coaching.

Example: Client wants €150k remote role but has 2 years experience. Logic says "not realistic." Intuition says "check their background—previous consulting experience? Leadership? Domain expertise? Maybe they CAN make this jump with right positioning."

3. Systems and Tools 💪

Having flexible yet reliable systems that enable people with different backgrounds to improve their careers.

Practices, tools, mantras, algorithms, guidelines. Things like:

• The Skills Pattern Analysis Framework
• The Intentionality Framework
• CV optimization templates
• Interview preparation systems
• Salary negotiation frameworks

These will be the muscles of coaching.

For strategic career planning tools, check our comprehensive guides.

Don't Just Look for Accomplished Engineers

This is crucial: When looking for a tech career coach, don't just look for accomplished engineers.

Many accomplished engineers reached their position by leveraging their specific resources that may not apply to you:

Why Accomplished Engineers ≠ Good Coaches	Example
Lucky timing	Joined startup that went IPO (not repeatable)
Privileged background	Family connections landed first role (not universal)
Narrow path	Only worked at FAANG, can't advise on remote/LCLT
Over-optimization	Sacrificed everything for career (not sustainable)
Survivorship bias	"Just grind LeetCode" ignores those who tried and failed

What worked for them might not work for you.

People deny this, but a lot of accomplished engineers just got lucky and ended up in great jobs.

Others put huge amounts of effort into becoming top-tier engineers and could have gotten where they are with half the work if they'd been more strategic.

Calculate your optimal career path →

What to Look for in a Tech Career Coach

When evaluating potential coaches, look for someone who:

✓ Can and Wants to Understand You

Red flags:

• One-size-fits-all advice
• Doesn't ask about your background/goals
• Pushes their path as THE path
• Immediately sells their program

Green flags:

• Asks detailed questions about your situation
• Acknowledges your constraints (family, location, finances)
• Tailors advice to YOUR goals, not theirs
• Gives you honest assessment (including "you're on right track")

✓ Understands the Market and the Game

What this means:

• Knows salary ranges across different locations and companies
• Understands visa processes, remote work trends, tax optimization
• Has network across different company types (not just FAANG)
• Stays current with market shifts (AI boom, remote work, European opportunities)

Test question: "What's realistic TC for senior backend engineer in Poland vs Zurich vs remote US company?"

Good answer: Specific numbers with context and trade-offs

Bad answer: Vague or outdated information

✓ Is Gifted at This and Has Good Intuition

Coaching is partly art, not just science.

Signs of good intuition:

• Quickly identifies your actual bottleneck (not surface problem)
• Gives advice that "clicks" and feels right
• Can adapt strategy when something isn't working
• Balances competing priorities (money vs learning vs WLB)

Example of good intuition:

Client says "I want big tech role" but intuition reveals they actually want financial security and interesting work—remote LCLT role might be better fit than big tech grind.

✓ Has Systems and Tools to Get Results

Not just vibes and motivation—concrete frameworks and tools:

What to Look For	Why It Matters
Structured process	Clear phases: assessment → strategy → execution
Proven frameworks	Repeatable systems that work for multiple people
Concrete deliverables	Optimized CV, LinkedIn, job search strategy, etc.
Accountability systems	Regular check-ins, progress tracking
Success metrics	How do they measure if coaching is working?

For structured career planning approaches, see our comprehensive framework.

Real Coaching Outcomes

Here's what good coaching should achieve for you:

1. Clarity in Career Vision

Before coaching:

• "I want to make more money I guess?"
• "Should I learn React or Vue?"
• "Maybe apply to some jobs?"

After coaching:

• "€120k remote role from Poland saving €70k/year toward €350k FIRE number"
• "Focus on Python + AWS + K8s based on SPA analysis of target roles"
• "Apply to 50 remote-first US companies over next 8 weeks"

2. High-Quality Strategies with Implementation Steps

Before coaching:

• Vague goals without execution plan
• Paralyzed by too many options
• Don't know where to start

After coaching:

Phase	Timeline	Actions	Success Metrics
Preparation	Weeks 1-4	Update CV, optimize LinkedIn, build portfolio	CV gets 15%+ response rate
Application	Weeks 5-12	Apply to 50 companies, 10/week	5-8 interviews secured
Interview	Weeks 8-16	Practice technical, negotiate offers	2-3 offers received
Transition	Weeks 16-20	Accept offer, relocate/setup remote	Started new role

3. Additional Value-Adds

Beyond strategy and execution:

Networking:

• Teaching you how to network effectively
• Giving you access to coach's network
• Introductions to people at target companies

Materials optimization:

• CV review and complete rewrite
• LinkedIn profile optimization
• Portfolio project guidance

Unique insights:

• Inside information on companies/markets
• Salary negotiation tactics that work
• Interview insights from specific companies

Acceleration:

• Fast-track your progress (what would take 3 years solo → 1 year with coaching)
• Avoid common mistakes
• Get personalized advice for your specific situation

4. Better Job Outcomes

Ultimately, the coaching should help you get better opportunities:

Real message from my coaching program (translated from Italian):

"You're doing great. For me, quite simply, you've changed my life just by helping me reorganize my thoughts in priority order and setting long-term goals, not to mention the execution part."

Concrete outcome examples:

• €65k local role → €120k remote role (18 months)
• Junior in Spain → Mid-level in Switzerland (12 months)
• No offers in 6 months → 3 offers in 8 weeks

For more transformation stories, see our career success examples.

Should YOU Become a Coach?

Now let's address whether you should transition from software engineering to coaching.

Short answer: For most developers, probably not worth it financially.

Longer answer: It depends on several factors.

The Money Question

Reality check: In most cases, it's not financially optimal.

Income Source	Typical Range (Europe)	Effort Required	Scalability
Senior SWE employee	€80k-€200k/year	40-50h/week	Limited (time-for-money)
Freelance developer	€100k-€250k/year	35-45h/week	Medium (higher rate)
SaaS founder	€0-€500k+/year	50-70h/week	High (productized)
Career coaching	€20k-€80k/year	30-50h/week	Low (time-for-money)

If you're a good developer, you'll probably make more money in less time:

• As an employee (less stress)
• As a freelancer (higher rates)
• Building SaaS products (leveraging dev skills)

Engineering Manager perspective:

The job is somewhat similar to coaching (working with people, career development), but still quite different. As a coach, you need to know much more about:

• Different markets and opportunities
• Various companies and their cultures
• Current hiring trends across Europe
• Specific salary negotiations tactics
• etc.

When Coaching Might Make Sense

Scenario 1: You Genuinely Enjoy It

Test before committing:

Try coaching for free first:

• Help colleagues within your company
• Mentor junior developers
• Offer free 1:1 sessions to friends
• Volunteer on mentorship platforms

If after 10+ sessions you still enjoy it, then maybe pursue it.

Signs you enjoy coaching:

• Energized after sessions (not drained)
• Think about client's problems between sessions
• Excited to prepare for meetings
• Feel rewarded by their progress

Scenario 2: You're Really Good at It

If you're really good at coaching, it becomes more fun AND more financially viable:

Good coaching → Client results → Satisfaction + Higher prices + More clients

Coaching Quality	Typical Outcomes	Pricing Potential	Client Volume
Average	Some clients get results, many don't	€50-€150/session	Low (no referrals)
Good	Most clients see improvement	€150-€300/session	Medium (some referrals)
Excellent	Clients consistently get €30k-€80k+ raises	€300-€500+/session	High (strong referrals)

If you're excellent, you can command premium prices and get clients through referrals (not cold outreach).

This makes it more financially interesting and more enjoyable.

Scenario 3: Side Hustle, Not Main Income

Best of both worlds:

• Keep your €100k-€150k dev job (financial security)
• Coach 3-5 clients on the side (€15k-€30k extra/year)
• Do it because you enjoy it, not because you need the money

This removes financial pressure and lets you be selective about clients.

Rules of Thumb: Will You Like Coaching?

Ask yourself these questions:

Question	Why It Matters	If Yes →	If No →
Do you like working 1:1 with people?	Coaching is fundamentally relational	Could be good fit	Probably not for you
Do you enjoy socializing and deep conversations?	Each session is 60+ min of talking	Essential skill	Will drain you
Do you like the "strategic" aspect of careers?	Planning moves, exploring options, preparing for interviews	Core of the work	You'll be bored
Do you like sales and marketing?	Need to get clients somehow	Can build coaching business	Struggle to find clients
Are you willing to invest in audience building?	Social media, content creation for client acquisition	Can grow sustainably	Dead on arrival

Honest assessment: If you answered "No" to 3+ questions, don't do coaching.

You'll either fail or be miserable (or both).

Explore alternative career paths →

What I Like About Coaching

Having done both software engineering (8+ years) and coaching (6 months), here's what I prefer about coaching:

1. More "Human" and Less Alienating

Software engineering:

• Working with nodes, clusters, scripts, monitoring systems
• Debugging abstract technical problems
• Limited human interaction (Slack, standups, PRs)

Coaching:

• Working with people's life goals, passions, personalities, limits
• Solving human problems with real impact
• Deep 1:1 relationships

Personal take: After years at Oracle dealing with distributed systems, coaching feels like I'm doing something more "human."

2. Less Fake and Corporate

Big tech environment:

• Office politics matter a lot
• "Managing optics" is critical
• Need to hide aspects of personality
• Promotion requires playing the game

Coaching:

• Much less politics involved
• If people work with me, they usually like what I do and who I am
• Most of the time I also like them (nice personal match)
• More authentic interactions

Caveat: This might be biased. You could find:

• Tech job in chill company with little politics
• OR run coaching program in "mainstream"/salesy way with lots of politics

But coaching offers more chances to be authentic and less political.

3. Leverages My Full Skill Set

My "success" as a dev came from:

• 50%: Being good at coding, math, collaborative engineering
• 50%: Being good at navigating European market and getting good offers

Coaching leverages BOTH sides, not just technical.

Plus:

• I did competitive sailing for 10+ years (worked with coaches, understand coaching dynamics)
• I taught math/physics as part-time job during studies (experience working 1:1, enjoy teaching)

Result: Coaching feels like using more of my abilities, not just technical skills.

4. Direct and Warm Impact

Software engineering impact:

• Improve performance metric by 15%
• Increase system reliability
• Ship feature → see usage numbers

Cold and indirect.

Coaching impact:

• Build personal relationship with someone
• See aspects of their life changing in real time
• Direct gratitude and transformation

Warm and direct.

This can be very rewarding.

For more on finding rewarding career paths, see our career strategy articles.

What I Don't Like About Coaching

It's not all sunshine and rainbows.

1. Not All Clients Are a Match

Sometimes the match just isn't there.

Mismatch examples:

• Client wants something you can't deliver (magic fix, no effort required)
• Personality clash (communication styles don't align)
• Different values (they want prestige, you optimize for freedom)
• Unrealistic expectations (€200k salary with 1 year experience, no special skills)

Options:

• Try to make it work (communicate, adjust approach)
• Cut it short gracefully (refund, recommend someone else)

Not a big deal, but requires care and emotional energy.

2. Marketing and Sales Can Be Tiring

Most devs don't understand how hard sales/marketing is.

We rely on recruiters and marketing teams. We think it's "easy and simple."

Reality: It's not easy.

Challenge	Why It's Hard	Impact
Constant output required	Need to always be selling, regardless of mood	Exhausting
No one buys from grumpy you	Must maintain positive energy always	Draining
High-quality content needed	Just to get some customers, need lots of great content	Time-consuming
Consistency matters	Can't go silent for 2 months and expect clients	Pressure

In today's world, to get coaching clients, you need:

• Strong social media presence (LinkedIn, Twitter)
• Consistent content production (weekly at minimum)
• Trust-building over months/years
• Personal brand development

This takes time and energy that software engineers don't typically spend.

3. It's Not a Stable Career

At least, not in the same way as being a software engineer.

Software engineer:

• Thousands of job openings
• Apply to 50 companies → likely get 2-5 offers
• If one job ends, find another in 1-3 months
• Predictable income trajectory

Coach:

• Few "coaching jobs" to apply to
• Must build your own client base
• If clients dry up, back to square one
• Unpredictable income (feast or famine)

Software engineers have it on easy mode in terms of career stability.

If you rely on marketplaces (not your own brand), you won't build decent income or stability.

4. Emotional Labor

Software engineering:

• Problems have solutions
• Systems don't have emotions
• Turn off laptop → work is done

Coaching:

• Problems are complex (career + life + emotions)
• Clients have bad days, doubts, fears
• Hard to "turn off" (think about clients outside sessions)

Emotional labor is real—and not everyone is suited for it.

The Comparison Matrix

Aspect	Software Engineering	Career Coaching
Income potential	€80k-€200k+ (employee)<br>€100k-€250k+ (freelance)	€20k-€80k (most)<br>€80k-€150k+ (top 5%)
Stability	Very high (always jobs available)	Low (need to constantly get clients)
Skill leverage	Technical skills only	Technical + strategic + emotional intelligence
Human connection	Limited (team, meetings)	Deep (1:1 relationships)
Impact visibility	Indirect (metrics, features)	Direct (life transformations)
Stress type	Technical complexity, deadlines	Emotional labor, client acquisition
Career progression	Clear (junior → senior → staff → principal)	Unclear (depends on your brand building)
Work-life boundary	Easier to disconnect	Harder to disconnect
Scalability	Limited (freelancing) to High (SaaS products)	Very limited (1:1 time)

My Recommendation

For 95% of developers: Stick with software engineering or freelancing.

You'll make more money, have more stability, and leverage your existing skills better.

Consider coaching IF:

1. You've tested it (free sessions) and genuinely enjoy it
2. You're good at it (people get results working with you)
3. You're willing to build an audience (content creation, social media)
4. You treat it as side hustle, not main income (keep dev job)
5. You value the human connection more than maximum income

Don't do coaching IF:

• You're doing it primarily for money (you'll make less than dev work)
• You don't enjoy 1:1 deep conversations (you'll hate it)
• You're not willing to do sales/marketing (you'll have no clients)
• You want stable, predictable income (coaching isn't that)

Alternative: Content Creation

If you like the "teaching" aspect but want scalability:

Consider content creation instead of 1:1 coaching:

• YouTube channel (tech education)
• Blog + newsletter (career advice)
• Courses (productized knowledge)
• Books (leveraged time)

Advantages over coaching:

• Scalable (help 1000s vs 10s)
• More stable (audience compounds)
• Less emotional labor (one-to-many, not 1:1)
• Can combine with dev career

For examples of successful content, see our blog articles.

Final Thoughts

Coaching is very different from software engineering.

Don't romanticize it. Don't assume accomplished engineers make good coaches.

If you're looking for a coach: Find someone with empathy, market knowledge, intuition, and proven systems.

If you're considering becoming a coach: Test it first, be honest about fit, and probably keep it as a side hustle.

For most developers, focusing on your engineering career (optimizing location, remote work, freelancing) will yield better financial outcomes.

But if you're one of the few who genuinely enjoys coaching and is good at it, it can be deeply rewarding.

Explore your strategic career options →

---

Frequently Asked Questions

How do I know if I have the right personality for coaching vs continuing as a developer?

Take the "energized or drained" test over 5-10 mentoring sessions. Set up experiment: Offer free 1:1 career advice sessions to colleagues or online (r/cscareerquestionsEU, LinkedIn). Do 5-10 sessions of 60 minutes each. Track your energy. After each session, ask: (1) Do I feel energized or drained? (2) Am I thinking about their problems afterward (engaged) or trying to forget (overwhelmed)? (3) Am I excited for next session or dreading it? Developer personality (most people): Drained after 1:1s, prefer working with code/systems, uncomfortable with emotional conversations, need alone time to recharge. Coach personality (rare): Energized by helping others, enjoy deep conversations, comfortable with emotions/uncertainty, social interaction is recharging. Reality check: Most developers are introverts who chose coding precisely to avoid constant human interaction. Coaching requires CONSTANT human interaction. If you picked coding because you liked working alone with computers, coaching probably isn't for you. Mixed personality: Keep dev job (financial security + technical work) + coach 2-3 clients on side (human connection fix). Best of both worlds.

What's a realistic timeline to build a coaching business to €50k/year income?

2-3 years minimum if starting from scratch with no audience. 6-12 months if you have existing audience/network. Year 1 (Audience building): Build social media presence (LinkedIn, Twitter), post valuable content 3-5x/week, grow to 2000-5000 followers, offer free sessions to build testimonials. Income: €0-€10k (maybe a few clients from network). Year 2 (Client acquisition): Continue content, grow to 10,000+ followers, convert audience to clients, charge €150-€300/session or €1500-€3000/month for program. Income: €20k-€40k (5-10 active clients). Year 3 (Optimization): Increase prices, productize offering (group coaching, courses), referrals from satisfied clients. Income: €40k-€80k (10-15 clients or scalable products). Math: To make €50k/year from 1:1 coaching: At €200/session, need 250 sessions/year = ~5 sessions/week. Or at €2000/month program, need ~2 new clients/month (assuming 3-6 month engagements). Reality: Most people quit before Year 2 because Year 1 is mostly work without income. You need either (1) financial runway to survive low income period, or (2) keep dev job and build coaching as side hustle. Shortcut: If you already have audience (10,000+ followers, newsletter with 5000+ subscribers), you can reach €50k within 6-12 months. Without audience, no shortcut exists.

Should I get certified as a career coach or is hands-on experience more valuable?

Hands-on experience and results >>> certifications. Certifications are mostly irrelevant for tech career coaching. What matters to clients: (1) Can you help me get better job? (2) Do you understand tech market? (3) Do you have results from other clients? (4) Do you understand my situation? What doesn't matter: (1) ICF certification, (2) Life coaching degree, (3) General coaching certifications. Why: Tech career coaching is niche. Generic coaching certifications don't teach you: European tech market dynamics, salary negotiation for developers, how to optimize LinkedIn for SWE roles, which companies pay well remotely, etc. What's more valuable than certifications: (1) Your own career success (went from €50k to €150k? That's credibility), (2) Client testimonials (3 people you helped land €100k+ roles? That's proof), (3) Market knowledge (you know salary ranges, companies, trends), (4) Frameworks and systems (documented processes that work), (5) Content demonstrating expertise (blog posts, tweets, guides showing you know your stuff). When certification might help: If you're transitioning from non-tech background into tech career coaching (shows commitment), or if you want to work for established coaching platform (they sometimes require it). Bottom line: Don't spend €5k and 6 months on certification. Instead: help 10 people for free, document results, build content showing expertise. That's your "certification."

How do I price my coaching services and what's the typical pricing structure in Europe?

Pricing depends on: your experience, client results, and delivery format. Start low, raise prices as you prove value. Typical European tech career coaching prices: Beginner coach (0-10 clients): €50-€100/hour or €500-€1000/month. You're unproven, charge accordingly. Established coach (10-50 clients, some results): €150-€300/hour or €1500-€3000/month. You have testimonials and systems. Premium coach (50+ clients, consistent results): €300-€500+/hour or €3000-€6000/month. You reliably help clients get €30k-€80k+ raises. Pricing structures: (1) Hourly (€100-€300/hour): Simple but not scalable. Client pays per session. Good for starting. (2) Monthly retainer (€1000-€3000/month): 2-4 sessions/month + async support. More stable income. (3) Fixed program (€3000-€8000 for 3-6 months): Comprehensive coaching package. Highest value. (4) Results-based (€5000 + 5-10% of salary increase first year): Align incentives. Hard to enforce. My recommendation for starting: Month 1-3: Free (build testimonials). Month 4-6: €50-€75/hour (early adopter pricing). Month 7-12: €100-€150/hour (raise prices as you improve). Year 2+: €200-€300/hour or move to program model (€2000-€4000). Pricing psychology: Charge enough that clients take it seriously (too cheap = not valued), but not so much that you have impostor syndrome. Start where you're 70% confident in value, raise prices every 10 clients.

What are the legal and tax implications of running a coaching business in Europe?

Varies significantly by country—you'll likely need to register as self-employed/sole proprietor. Consult local accountant. General structure across EU: Registration: Register as self-employed (freelancer, sole proprietor, or equivalent in your country). Takes 1-4 weeks, usually €0-€500 in fees. Taxes: (1) Income tax (15-45% depending on country and income level), (2) Social contributions (10-30% for healthcare, pension), (3) VAT (register if over threshold, typically €20k-€40k revenue). Country examples: Poland: Register as sole proprietor (działalność gospodarcza). Income tax: 12-32% or flat 19%. Plus ZUS (social) ~€200-€400/month. IP Box might not apply to coaching. Germany: Freiberufler (freelancer) status. Income tax: 14-45% progressive. Plus health insurance ~€400-€800/month. Portugal: Self-employed (trabalhador independente). Income tax: 14.5-48%. Plus social security 21.4% of income. Spain: Autónomo status. Income tax: 19-47%. Plus social security ~€300/month minimum. Switzerland: Register as self-employed. Income tax varies by canton (10-25% effective). Plus AVS/AHV social insurance ~10%. Practical steps: (1) Month 1: Consult local accountant (€100-€300), understand requirements. (2) Month 2: Register business (bring expected revenue estimates). (3) Ongoing: Track income/expenses (simple spreadsheet), file quarterly/annual taxes. (4) Keep it simple: Don't incorporate until €50k+ revenue (sole proprietor is simpler). Tax optimization: Structure as freelancing from low-tax country if remote coaching (same optimization as remote dev work). See our tax optimization guide.

If coaching income is lower than engineering, why do you do it?

Because I optimize for enjoyment and lifestyle, not maximum income—I've already hit my financial independence number. Context: After 8 years in tech (Oracle, other roles), I reached my COAST-FIRE goals. At that point, optimizing for pure income has diminishing returns. My current optimization function: (1) Enjoyment (do I like the work?), (2) Freedom (location independence, schedule flexibility), (3) Impact (am I helping people directly?), (4) Sufficient income (€40k-€60k covers lifestyle + some growth). Why coaching makes sense FOR ME NOW: Coaching €40k-€60k/year + investment income = sufficient total. That's plenty for my lifestyle (LCLT location, low expenses). I enjoy it more than engineering work. More human connection, less corporate politics, direct impact. Location + schedule freedom (work from anywhere, set own hours). Why this might NOT make sense for you: If you're early in your career with limited savings → you need to build financial security first. Engineering (€80k-€150k) gets you there faster than coaching (€20k-€60k). Once you hit your FI targets, THEN you can optimize for enjoyment over maximum income. My path isn't THE path: For most people, staying in engineering/freelancing makes more sense (better income, less stress, leverage existing skills). I'm an edge case where I've already built financial buffer and now optimize differently. See our financial independence framework for stages of career optimization.