I Turned Down a 30% Raise to Stay at a Remote Company — Here's What Retention Actually Looks Like From an IC's Desk

General
1

Six months ago, I got an offer from a well-known public company. The role was interesting — senior full-stack engineer on a greenfield project, modern stack, smart team. The total compensation was roughly 30% higher than what I’m making now.

I turned it down in 24 hours. Here’s why, and what I think it says about engineering retention in 2026.

The Deal-Breaker Wasn’t the Tech

The company required 4 days on-site in San Francisco. When I asked the hiring manager about flexibility, I got the corporate line: “We believe in the magic of in-person collaboration.” I asked for data supporting that belief. Silence.

Here’s my situation: I live in Portland. I have a home office I’ve spent 3 years optimizing. I contribute to open-source projects on Friday afternoons. I do my best deep work between 6-8 AM before Slack lights up. I’ve architected systems that handle millions of requests per day from this desk.

You’re telling me I need to move to a city with 2x cost of living, spend 90 minutes daily in a car, and sit in an open-plan office with noise-canceling headphones on… to do the same work I’m already doing? That’s not a perk. That’s a tax.

What Actually Keeps Me Where I Am

Let me be specific about what my current company gets right, because vague “culture” talk doesn’t help anyone:

1. Trust Is the Foundation, Not a Buzzword

My manager doesn’t track my hours. She tracks my output. When I said “I need Thursday afternoons for a personal commitment,” the response was “cool, just make sure your team knows your availability.” No questions. No suspicion. No passive-aggressive Slack status monitoring.

This sounds small, but it’s everything. Trust in leadership — knowing that the people making decisions about my career respect me as an adult — is the single biggest reason I stay. According to SignalFire’s research, I’m not alone. Trust, culture, and challenge consistently beat compensation in what retains senior engineers.

2. The Problems Are Genuinely Hard

I’m working on distributed systems challenges that make me think. Not “move this button 2 pixels left” work — actual architectural problems where the solution isn’t obvious and my experience matters. Technical challenge and depth keep engineers engaged, and that’s exactly what I experience daily.

When companies try to retain people with counter-offers, they’re missing the point. If the work is boring at $180K, it’s still boring at $230K. You just feel more expensive while being bored.

3. Open-Source Is Valued, Not Tolerated

I maintain a couple of open-source libraries that are used by thousands of developers. At my previous company, this was treated as a hobby that shouldn’t interfere with “real work.” At my current company, it’s in my performance review as a positive contribution. My open-source work is seen as building the company’s engineering brand and keeping me technically sharp.

SignalFire specifically calls out open-source credibility as a retention factor for senior engineers, and they’re right. Letting engineers build public reputation is a retention strategy that costs you nothing and returns compound value.

4. Internal Mobility Without Politics

When I got curious about our ML pipeline last year, I spent a quarter doing a rotation with the data team. No bureaucratic transfer process, no manager veto, no implication that I was “disloyal” to my team. Just a conversation, a plan, and a new set of problems to learn from.

I came back to my team with ML knowledge that directly improved our feature development. The company got a more versatile engineer. I got renewed energy. Everyone won.

What the 30% Raise Actually Represented

That 30% raise wasn’t about money. It was about a company trying to use compensation to overcome a structural disadvantage. They couldn’t offer remote work, they couldn’t offer the trust my current company gives me, and they couldn’t offer the kind of open-source-friendly culture I value.

So they offered money. And for a lot of engineers, that works — temporarily. The median tenure at companies that retain primarily through compensation is about 18 months, according to multiple studies. Then you’re right back to recruiting, onboarding, and ramping someone new.

A Message to Engineering Leaders

If you’re reading this as a manager, director, or VP: your retention problem isn’t a compensation problem. It’s a trust problem, a challenge problem, and a flexibility problem. The engineers you most want to keep — the senior ICs who ship reliable systems, mentor others, and improve your architecture — are the ones with the most options. And we’re choosing companies that treat us like adults over companies that offer bigger checks with more strings attached.

Anyone else turned down a raise to stay somewhere better? What was your deciding factor?

2

Alex, this hits home hard. I did basically the same thing last year and I want to share my version because I think the pattern matters.

My Version of Your Story

I got recruited by a unicorn in NYC. Design systems lead role, incredible product, team full of people I admired. The comp was about 25% above what I make. They wanted me in the office 3 days a week.

I live in Austin. I built my life here — my community, my studio space where I do side projects, my partner’s career. Moving wasn’t an option, and flying to NYC every week isn’t a life, it’s a commute with altitude.

When I told the recruiter that remote was non-negotiable, they came back with “we could do 2 days a week.” I asked: “Can you explain what I would do on those 2 in-office days that I can’t do over Figma and Zoom?” They couldn’t answer. Because the honest answer is “the CEO wants butts in seats” and everyone knows it.

The Design Perspective on Remote Work

Here’s something that doesn’t get discussed enough: design work is actually better remote. My best design work happens in focused blocks of 3-4 hours. Open offices are the worst possible environment for this. Every time someone taps your shoulder to “quickly look at something,” that’s 20 minutes of lost context.

My current setup: dedicated monitor for design work, second monitor for reference/documentation, standing desk I configured exactly how I like it, natural light from a window I chose, silence when I need it, music when I want it. No office in the world replicates this, because it’s mine.

What Keeps Me Here (Beyond Remote)

Similar to your list, Alex, but from the design side:

  • Autonomy over the design system — I make architectural decisions about our component library without going through 4 layers of approval
  • Engineers who respect design — this sounds basic but it’s shockingly rare. My engineering partners treat design specs as real requirements, not suggestions
  • Conference budget that’s actually usable — I speak at 2-3 conferences a year. My company covers it and celebrates it. At my last company, I had to fight for every conference as if I was asking for a vacation

The 30% raise would have evaporated when you factor in NYC cost of living, commute stress, and the loss of autonomy. It wasn’t even a real raise — it was a relocation penalty disguised as generosity.

Glad you made the same call I did. The companies that get this right are going to have unfair advantages in talent for the next decade.

3

Alex, I want to tell you something that might sound strange coming from a Director of Engineering: this post should be required reading for every engineering leader.

What Managers Learn From Posts Like This

When I read your breakdown, here’s what I take away as someone who manages 40+ engineers:

1. We’re competing against a feeling, not a number.

The “30% raise wasn’t about money” insight is critical. When my engineers get poached, the instinct is to match the offer. But you’re telling me — and the data confirms — that the decision framework isn’t financial. It’s experiential. You’re asking: “Will I be trusted? Will I be challenged? Will I be free?”

I can’t counter-offer my way to trust. I have to build it every single day through consistent actions.

2. The open-source point is a blind spot for most companies.

I’ll admit — I hadn’t connected open-source contributions to retention until I read the SignalFire data and your personal experience together. We’ve been treating OSS as “something engineers do on their own time.” But you’re telling me it’s a core part of what makes your job satisfying.

Starting next quarter, I’m adding open-source contributions as a recognized activity in our engineering ladder. Not required, but explicitly valued and discussed in performance reviews. Thank you for making me see this.

3. Internal mobility is a retention superpower.

Your ML rotation story is exactly the kind of thing that keeps senior ICs from getting restless. We have a similar program, but I’m realizing we don’t advertise it enough. Engineers don’t know it’s available unless their manager tells them, and not all managers are proactive about it.

The Uncomfortable Question for Leaders

Alex, your post forces managers like me to ask: “Would my best engineers turn down a 30% raise to stay?” If the honest answer is no, that’s not a compensation problem. That’s a leadership problem.

I’m going to use this post (with your permission) in our next engineering leadership offsite. The IC perspective is the one most often missing from retention strategy discussions.

4

Alex, I want to add the product perspective here because your story has direct implications for how we build product teams and think about velocity.

The Product Velocity Angle

When a senior IC like you turns down a 30% raise, my first thought as a VP Product isn’t about retention philosophy — it’s about what would have happened to our roadmap if you’d left.

Let me be blunt about the math:

  • You leave → 3-6 month backfill timeline (optimistic, given the market)
  • New hire arrives → 3-6 months to full productivity (understanding our systems, codebase, domain)
  • Total impact: 6-12 months of reduced velocity on every initiative you touch

For a senior full-stack engineer working on critical systems, that’s not just an engineering problem. That’s 2-3 quarters of product roadmap at risk. Features slip, competitive positioning weakens, customer promises get broken.

Team Composition and Stability

Here’s what product leaders rarely discuss publicly: the best product teams aren’t the ones with the best individual talent. They’re the ones with the most stable, trust-rich relationships.

When you’ve worked with the same engineers for 2+ years, the communication overhead drops to near zero. You can have a 5-minute conversation that replaces a 2-page spec because you share context. You can ship faster because trust has been built through cycles of delivery.

Every time we lose a senior IC and bring in a replacement — even a brilliant one — we reset the clock on that team trust and shared context. It takes 6-12 months to rebuild what the departing engineer took with them. No amount of documentation fully captures the institutional knowledge in a senior engineer’s head.

The Remote Work Enablement for Product Teams

Your point about doing deep work between 6-8 AM resonates with how I think about product development cycles. The best product work doesn’t happen in sync. It happens when:

  • Engineers have uninterrupted time to think about architecture
  • Designers have space to explore options without real-time feedback pressure
  • Product managers have time to synthesize customer feedback without meeting overload

Remote work enables all three. When companies mandate RTO, they’re not just losing talent — they’re degrading the conditions for high-quality product work.

The 30% raise you turned down was actually a bad deal for the offering company too, even if you’d accepted. They’d get you physically, but they’d lose the conditions under which you do your best work. That’s a terrible trade.