Remote Work Pays $19K More on Average—But Only If You're in AI, Cybersecurity, or Data. Is Remote Work Becoming a Class Privilege?

General
1

We just wrapped Q1 hiring at our EdTech startup, and I need to talk about something uncomfortable that’s been bothering me for months.

Our latest opening for a Senior AI/ML Engineer attracted 847 applications. The salary range? $145K–$175K. Remote-first position. We made an offer to an exceptional candidate who’s currently a Principal Engineer at a FAANG company making $280K total comp. She accepted our offer at $165K base because it meant she could work from anywhere and have flexibility around her kids’ schedules.

Meanwhile, I’m watching my sister—an elementary school teacher in Atlanta making $52K—commute 45 minutes each way because her school district doesn’t offer remote options. She asked me last week if there are “work from home jobs” she could transition into. I looked into it. The entry point for truly remote work that pays a livable wage? You basically need to be a software engineer, product manager, data analyst, or work in cybersecurity. Average starting salaries: $110K–$130K.

Here’s the data that’s keeping me up at night:

According to recent research, remote workers in the U.S. earn an average of $19,000 more per year than their non-remote counterparts in equivalent roles. But that’s not the whole story. The real inequality is in access to remote work itself.

High-paying remote jobs in 2026 are overwhelmingly concentrated in:

  • AI and Machine Learning: Prompt engineers at companies like Anthropic earn up to $335,000. The field has seen a 135.8% surge in demand this year alone.
  • Cybersecurity: With cybercrime increasing, remote cybersecurity consultants command $110K–$130K+
  • Data Analytics: Senior remote data analysts earn $115K–$150K
  • Software Engineering: Median remote software engineer salary is $148,000

Meanwhile, if you’re in healthcare, education, administrative work, or service industries? Remote options are scarce to nonexistent, even when the work could theoretically be done remotely.

The geographic pay adjustment trap:

Here’s where it gets even more complicated. 44% of large companies (1,000+ employees) now have location-based pay policies for remote workers. Companies are reducing salaries by 10–25% when employees relocate to lower cost-of-living areas while staying remote.

So you finally get access to a remote role, move to a more affordable city to save money… and your employer cuts your pay because you’re no longer in an expensive metro. The flexibility dividend evaporates.

The willingness-to-sacrifice data is revealing:

Research shows that 40% of U.S. workers would accept 95% or less of their current salary for remote work options. But here’s the gendered dimension: women are more likely than men to accept significant pay cuts for flexibility. Women with children have the highest desire for remote work arrangements.

Tech workers would sacrifice up to 25% of total compensation to avoid commuting five days a week. At an average tech salary of $239,000, that’s nearly $60,000 they’re willing to give up. But can a teacher making $52K afford to sacrifice 25%? Absolutely not.

The senior vs. junior divide:

The data also reveals that senior employees have far more leverage to negotiate flexibility, while entry-level workers have less. This creates a dynamic where the people who might benefit most from in-office mentorship (entry-level workers) have less access to remote options, while experienced professionals who need less hand-holding get more flexibility.

My questions for this community:

  1. Is remote work becoming a class privilege? The data suggests yes, but I want to hear your experiences.

  2. What’s the solution here? Do we push for more remote-capable roles across all salary bands? Do we advocate for better remote infrastructure in education, healthcare, and public service?

  3. How do we address the equity gap? Marginalized communities face additional barriers—Black households have 20% more people and Latinx households have 80% more people living under one roof compared to White households, making “quiet space for Zoom calls” a privilege in itself.

  4. Should companies be required to justify geographic pay adjustments? If the work is the same, why should location matter?

I’ve built my career on the belief that technology can democratize opportunity. But right now, it feels like we’re creating a two-tier system: high-skill, high-pay, high-flexibility workers on one side, and everyone else on the other.

What are you seeing in your organizations? How are you thinking about this?

2

This hits hard, Keisha. I’ve been wrestling with this at the board level for the past year.

The uncomfortable truth from the C-suite perspective:

When we went remote-first in 2022, I genuinely believed we were democratizing access to opportunity. We could hire talent anywhere, right? Wrong. We created a different kind of gatekeeping.

Our last engineering hiring round: 1,247 applications for 5 senior roles paying $150K–$180K. Our customer success team hiring round the same quarter: 83 applications for 8 roles paying $55K–$70K, all required to be in-office in Seattle because “customer-facing roles need collaboration.”

I pushed back. Hard. I ran a 6-month experiment where half our customer success team went remote. The results?

  • Customer satisfaction scores: No statistical difference (92% vs 93%)
  • Response times: Actually improved 12% for the remote group
  • Employee retention: Remote CS reps had 34% higher retention

You know what happened? We still reverted to in-office for CS. The executive reasoning? “Junior employees need mentorship and culture immersion.”

The mentorship excuse is often a cover for something else.

Here’s what I’ve observed: When we say “junior employees need in-office mentorship,” what we often mean is “we don’t trust remote collaboration tools” or “we haven’t invested in remote onboarding infrastructure” or honestly, “we like being able to see people working.”

The data doesn’t support the mentorship argument. Our remote senior engineers mentor effectively over Slack, Zoom, and async code reviews. But we don’t extend that same trust to customer success, recruiting, operations, or finance roles.

Geographic pay adjustments are the new redlining.

You asked whether companies should justify these adjustments. I’ll go further: they’re discriminatory in practice, even if not in intent.

When we apply a 25% pay cut because an engineer moves from San Francisco to Atlanta, we’re saying “your work is worth less based on where you live.” But the value delivered to customers doesn’t change. The code still runs the same. The impact is identical.

The rationale is “local market rates,” but that’s circular logic. Market rates are low in certain geographies because companies pay less there, which suppresses wages, which justifies paying less. It’s self-reinforcing inequality.

Here’s what I’m doing (and where I’m hitting resistance):

  1. Eliminated geographic pay adjustments for all roles above $100K. If you’re delivering value, location doesn’t matter. This was a 9-month battle with our CFO. We compromised: senior roles (Director+) get location-agnostic pay. IC roles still have adjustments. I hate the compromise but it’s progress.

  2. Audited every role for remote capability. Turns out 68% of our “must be in office” roles could be done remotely with minor process changes. We’ve moved 40% of those remote so far.

  3. Created remote career tracks for lower-wage roles. We now have remote customer success, remote operations, and remote recruiting coordinators. Starting pay: $65K–$85K (up from $55K–$70K when in-office). It’s not $150K engineering pay, but it’s progress.

But here’s where I’m stuck:

I can’t unilaterally change the market. If we pay customer success $150K to match engineering, we’d be bankrupt. The skills gap is real—prompt engineering and ML require specialized education that CS doesn’t. But the inequality in access to remote work perpetuates a cycle where people in lower-wage roles can’t upskill because they’re stuck commuting 90 minutes a day.

The solution I’m proposing internally:

  • Remote-first by default, with in-office exceptions that must be justified quarterly. Make the burden of proof go the other way.
  • Skills-based hiring that emphasizes remote-learnable skills. Our CS team now prioritizes written communication, async collaboration, and self-direction over “culture fit” (which often means “works well in an office”).
  • Internal mobility programs that help CS → Data Analysis → Engineering career progression with paid training time.

Your sister could benefit from programs like this. We’ve had 3 customer success team members transition to data analyst roles in the past 18 months through our internal training program.

The class privilege question:

Yes. Unequivocally yes. Remote work has become a perk of the professional class, and it’s calcifying economic stratification.

But I’m optimistic that this is solvable if we’re willing to challenge our assumptions about what roles “require” office presence and what skills “require” six-figure compensation to perform remotely.

The first step is calling it out, which you just did. Thank you for that.

3

Keisha, this resonates deeply. I’m seeing this play out in my own family in ways that feel increasingly unjust.

The Latino experience with remote work inequality:

My cousin is a social worker in El Paso making $48K. She works with at-risk youth, does crisis intervention, handles mountains of documentation—all of which could be done remotely for intake, case management, and follow-up. But her agency requires in-office presence 5 days a week.

Meanwhile, I’m a Director of Engineering at a Fortune 500 company making $195K base, working from my home office in Austin 4 days a week (we have a 1-day office requirement that I’m fighting to eliminate).

The work she does is arguably more essential to society than the financial services infrastructure I build. But I have flexibility and she doesn’t. I have the income to afford home office equipment, high-speed internet, and a dedicated workspace. She’s sharing a 3-bedroom apartment with her sister’s family—6 people total.

The “quiet space” privilege is real.

You mentioned that Latinx households have 80% more people under one roof compared to White households. I’ve seen this firsthand across my extended family and in my work with SHPE (Society of Hispanic Professional Engineers).

When we went remote in March 2020, three engineers on my team struggled significantly—not because they lacked skills, but because they didn’t have private space for video calls. One was sharing a bedroom with two younger siblings while his parents worked service jobs. Another was taking calls from his car in the garage.

Meanwhile, I had a home office. My white colleagues in suburban Seattle had home offices. The assumption that “everyone can just work from home” ignored massive disparities in home environments.

The skills barrier is both real and constructed.

Michelle’s point about the skills gap is important, but I want to add nuance: some of these “skill requirements” are gatekeeping disguised as merit.

Example from our recent hiring:

  • Data Analyst role (remote, $115K–$135K): Required 4-year degree in CS, statistics, or related field + 3 years experience
  • Operations Coordinator role (in-office, $58K–$68K): Required 2-year degree or equivalent experience

The Operations Coordinator role involves complex scheduling, data entry, vendor management, and reporting. With 3 months of SQL training and access to modern analytics tools, that person could do 70% of the Data Analyst work.

But we draw a hard line: degree required for the remote role, no degree flexibility. This systematically excludes first-generation college students, career switchers, and people from communities where 4-year degrees aren’t the default path.

What I’m trying internally (with mixed success):

  1. Created an apprenticeship program for first-gen college students and career switchers. We hire them as “Associate Data Analysts” at $75K remote, give them 6 months of training, then promote to full Data Analyst at $110K. We’ve brought 4 people through this program so far.

  2. Eliminated degree requirements for mid-level IC roles. If you can pass the technical assessment and have demonstrated experience, degree doesn’t matter. This took 18 months of internal advocacy and is still controversial with some hiring managers who view degrees as “quality signals.”

  3. Pushed for remote-first by default. Similar to Michelle’s approach, I’m requiring managers to justify why a role must be in-office rather than justifying why it can be remote. Success rate so far: moved 12 roles from in-office to remote, including 3 operations roles and 2 recruiting coordinator roles.

Where I’m hitting walls:

Our HR leadership insists on “competitive benchmarking” for comp, which means replicating market inequalities rather than fixing them. When I proposed paying Operations Coordinators $85K for remote work (to match cost of living + remove commute burden), I was told it would “compress” with other roles and “create internal equity issues.”

Translation: we can’t pay lower-wage roles too much because then people will question why higher-wage roles make so much more.

The generational and cultural disconnect:

I’m also seeing a generational divide in who believes remote work is effective. Executives in their 50s and 60s who built careers on face-time and “putting in the hours” at the office are far more skeptical of remote work than those of us who’ve experienced it.

This plays out racially and culturally too. Latino and Black professionals I mentor report more pressure to “prove” their productivity when remote, while white colleagues are given the benefit of the doubt. The surveillance mindset—“I need to see you working to believe you’re working”—hits marginalized communities harder.

What would actually help:

  1. Federal remote work equity standards. If a role can be performed remotely >50% of the time, companies should be required to offer remote options or justify exceptions annually.

  2. Subsidized home office infrastructure for lower-wage remote workers. Tax credits or direct subsidies for internet, equipment, and workspace setup for workers earning <$75K.

  3. Skills-based hiring becoming the norm, not the exception. Eliminate degree requirements for roles where skills can be demonstrated through assessments, portfolios, or project work.

  4. Transparency in geographic pay adjustments. If companies are going to adjust pay based on location, they should publish the methodology and allow employees to review and challenge it.

Keisha, your point about technology democratizing opportunity really stings. We had that moment in 2020-2021 when it seemed like remote work would level the playing field. Instead, it’s amplified existing inequalities.

I don’t have all the answers, but I’m committed to using my position to push for change internally. And to your sister—if she’s interested in transitioning to tech, I’m happy to connect her with resources and mentorship through SHPE. We have programs specifically for career switchers from education and public service.

4

This conversation is uncomfortable in the best way. Let me add the product and business perspective, because I think there’s a market failure happening here that we’re not talking about enough.

The talent market is segmenting in bizarre ways.

From a pure market dynamics perspective, remote work should be expanding access to opportunity, not concentrating it. Here’s what I mean:

Pre-pandemic, if you lived in rural Iowa, your job options were limited to what existed within commuting distance. Post-pandemic, theoretically you can access jobs from companies anywhere. That should be democratizing.

But instead, we’re seeing what economists call “superstar effects” and “winner-take-all markets.” The top 20% of knowledge workers can now work for the top 20% of companies from anywhere. Meanwhile, the bottom 80% are competing for increasingly commoditized roles with diminishing location-based moats.

Remote work eliminated geography as a competitive advantage for workers.

Think about it: if you’re a teacher in Atlanta, you used to compete with other teachers in Atlanta. Now? In theory you could compete for remote education coordinator roles nationally… except those roles don’t exist at scale.

But if you’re a software engineer in Atlanta, you now compete with engineers in San Francisco, Austin, Seattle, New York, and Bangalore. That drives salaries up for high-skill roles because companies are competing globally for talent.

The asymmetry is brutal: high-skill workers get access to global opportunities with upward wage pressure. Lower-skill workers get… nothing, or worse, downward wage pressure as their local jobs get outsourced to lower-cost geographies.

The willingness-to-pay gap reveals the inequality.

Keisha mentioned that 40% of workers would accept 95% or less of current salary for remote work. That stat looks different when you break it down by income level:

  • Workers earning $150K+: Would sacrifice $15K–$60K for remote flexibility (10–25%)
  • Workers earning $50K: Can’t afford to sacrifice $5K–$12K (10–25%) because they’re already stretched thin

So the people who could most benefit from reducing commute costs (gas, car maintenance, time) are the least able to negotiate for remote options or accept pay cuts to get them.

This is a market failure. The people with the highest willingness to pay (in percentage terms) have the lowest ability to pay (in absolute terms).

Geographic pay adjustments are economically indefensible.

I’m going to disagree slightly with Michelle and Luis here. Geographic pay adjustments do make economic sense—but only if you apply them consistently.

If we’re going to say “an engineer in Atlanta should make 25% less than an engineer in San Francisco because cost of living is lower,” then we also need to say “our customers in Atlanta should pay 25% less for our software because their purchasing power is lower.”

We don’t do that. We charge the same SaaS subscription fee whether you’re in SF or rural Texas. Why? Because the value delivered is the same regardless of customer location.

The same logic applies to labor. If an engineer delivers the same value, location shouldn’t matter. The “market rate” argument is just arbitrage—companies want to pay SF rates for customers and Atlanta rates for employees.

But here’s the hard part: the skills gap is real and growing.

Luis is right that some skill requirements are gatekeeping. But I also want to acknowledge that the gap between what an AI/ML engineer does and what a customer success rep does is real, and it’s widening.

The median data scientist today needs to understand:

  • Python and SQL (programming fundamentals)
  • Statistical modeling and probability
  • Machine learning algorithms and frameworks
  • Cloud infrastructure (AWS, GCP, Azure)
  • Data visualization and communication
  • Business context and problem-solving

That’s 2-4 years of specialized education beyond a bachelor’s degree, or 5-10 years of hands-on experience.

A customer success rep needs strong communication, problem-solving, empathy, and product knowledge. These are incredibly valuable skills, but they’re also more teachable and require less specialized technical background.

So what’s the solution? I see three paths:

1. Massively expand skills-based hiring and training.

Instead of requiring a 4-year CS degree for data analyst roles, create 6-month intensive boot camps with guaranteed job placement. Fund these through a combination of:

  • Company-sponsored programs (like Luis’s apprenticeship)
  • Government workforce development programs
  • Income share agreements where students pay tuition as % of future income

This expands the pipeline of people who can access high-paying remote roles.

2. Create more mid-tier remote roles ($75K–$95K).

Right now we have a bimodal distribution: high-skill roles at $110K+ and low-skill roles at $50K–$70K. There’s not much in between that’s remote-accessible.

We need to create remote roles for:

  • Technical support specialists ($75K–$85K)
  • Data operations coordinators ($70K–$85K)
  • Customer success engineers ($80K–$95K)
  • Sales development reps with product depth ($75K–$90K)

These roles require some technical skills but not ML or advanced programming. They’re bridges into higher-paid technical work.

3. Advocate for policy changes around remote work equity.

I’m generally skeptical of regulation, but I think Luis’s proposal for transparency in geographic pay adjustments is smart. If companies are going to adjust pay by location, they should publish:

  • The adjustment formula
  • The data sources for cost of living
  • Appeals processes for employees who disagree

Additionally, tax incentives for companies that create remote roles in lower-cost geographies could help spread opportunity.

The bottom line from a product perspective:

We build products to solve customer problems. Right now, there’s a massive unmet customer need: people in mid-skill, mid-wage roles who want remote work flexibility but don’t have access to it.

The companies that figure out how to:

  1. Create genuinely valuable remote roles at $75K–$95K
  2. Build training pipelines to help people access those roles
  3. Design remote-friendly workflows that don’t assume everyone has a home office

…those companies will unlock a huge talent pool and build competitive advantage.

But it requires viewing this as a market opportunity, not just a social justice issue. Both can be true simultaneously.

Keisha, thank you for starting this conversation. It’s one we should have been having more explicitly for the past 3 years.