The pandemic forced a massive experiment on the world, and now some of the largest technology companies are admitting the results: remote work isn’t a temporary accommodation. It’s the future. The question for IT professionals is how to position yourself in this seismic shift.

In May 2020, Twitter CEO Jack Dorsey announced that employees could work from home “forever” if they chose to. A week later, Mark Zuckerberg declared that Facebook expects 50% of its roughly 45,000-person workforce to be remote within five to ten years. Around the same time, Shopify’s Tobi Lutke announced the company would be “digital by default” because “office centricity is over.” Coinbase went remote-first. Square announced permanent remote options. These aren’t isolated personnel decisions. They’re structural commitments from companies with the market power to reshape entire industries.

What happens next? Every mid-size tech firm, every consulting company, every Fortune 500 with an IT department watches what Twitter and Facebook do and follows. The permission structure has changed. By June 2020, Gartner reported that 74% of CFOs intended to shift employees to permanent remote arrangements. A FlexJobs survey found 65% of workers wanted to stay fully remote after the pandemic, and 76% wanted at least some flexibility. The dominoes are already falling. And for IT professionals, this transition represents a genuine inflection point in how the industry works.

The Salary Question That Everyone’s Arguing About

Facebook’s announcement included a detail that sparked immediate backlash: the company would adjust compensation based on where employees actually lived. Move from San Francisco to Austin? Your salary adjusts downward to reflect Austin’s cost of living. This triggered a fierce debate that’s still unresolved.

The economic logic is straightforward from a management perspective. If you’re paying San Francisco salaries, you’re assuming San Francisco cost of living. A developer in Austin has lower expenses, so why pay the same? From that view, it’s rational.

But rational isn’t the same as right, and the worker perspective is equally logical: the value your work produces doesn’t change based on your zip code. If you’re writing the same code, shipping the same features, participating in the same meetings, why should your compensation drop because you chose to live somewhere cheaper? You’re not asking for a raise; you’re asking to keep what you earned.

This matters enormously for IT careers. Some companies, notably Zillow and later Reddit, chose not to adjust salaries geographically. They decided that if they’re genuinely “remote-first,” they’ll pay competitive rates regardless of location. Other companies will go Facebook’s route. Understanding which companies fall into which camp is now part of your career research.

For IT workers specifically, this creates a new form of arbitrage. A security architect earning San Francisco salaries while living in Kansas has just increased her purchasing power without changing jobs. But this only works if you work for a company that respects remote work enough to not penalize it. This is worth negotiating explicitly with any company that offers you a role. Ask the question directly: “If I move to a different state, will my compensation adjust?” Get the answer in writing.

Why This Matters for Infrastructure and Security

The permanent shift to remote work forces IT departments to solve problems they’d been deferring. The temporary VPN setup, the rushed Slack deployment, the “we’ll figure out security after the crisis” approach? These become permanent infrastructure. That changes everything about what IT teams need to build.

The old security model assumed a perimeter. Your office network was secure because you controlled it. Employees worked behind firewalls, connected to on-premises servers, trusted because they were physically in your building. The pandemic shattered that model. Employees are now everywhere. They’re on home networks you don’t control, on WiFi at coffee shops, on cellular connections from their car. You can’t trust location anymore.

This is where zero-trust security becomes non-negotiable. Instead of trusting based on network location, zero-trust assumes every request must be authenticated, every connection must be encrypted, every device must be verified. It’s more work. It’s more complex. And it’s exactly what organizations need when their workforce is genuinely distributed. Companies that committed to permanent remote work are committing, whether they realize it or not, to zero-trust architecture.

The infrastructure implications expand from there. Cloud-first architectures become cloud-only for many organizations. You can’t ask remote employees to VPN into your data center to access applications; you need those applications in the cloud where distributed teams can actually reach them efficiently. Identity management becomes critical. Endpoint security becomes premium. The “temporary” tools you deployed in March 2020 need to become permanent, hardened, scalable infrastructure.

This is simultaneously a massive amount of work and an enormous opportunity for IT professionals. Organizations need people who understand how to architect these systems. Someone has to design the zero-trust network for your company. Someone needs to manage identity across thousands of distributed users. Someone needs to keep the cloud infrastructure running and secure. Those someones are going to be in high demand, and they’re going to be well compensated.

The Talent Market Just Rewrote Itself

Here’s the part that should get every IT professional’s attention: geographic barriers to employment have collapsed. You no longer need to live where the jobs are. You can work for a San Francisco company from anywhere. But so can everyone else.

This is genuinely good for you if you’re living in a lower-cost area. If you’re in rural Georgia or small-town Texas, you now have access to West Coast compensation and West Coast company names on your resume. That’s transformative. A decade ago, the path to a high-salary IT career basically required relocating to a major tech hub at some point. Now you don’t.

But this same shift means you’re now competing for jobs against someone in Bangalore or Buenos Aires. The talent pool for each position is now effectively global. Companies can hire the best person for a role regardless of where they live. That’s ruthlessly efficient and genuinely meritocratic, but it also means the bar goes up. You’re not competing against the best people in your town or your country. You’re competing against the best people everywhere.

This has real implications for skill development. General IT competency matters less. Deep expertise matters more. Companies need cloud architects, not generalists who know a bit about everything. They need security specialists, not people with broad IT experience. They need people who can work asynchronously and communicate in writing, not people who rely on being in the room for meetings.

The skills that are premium right now are the ones that remote-first companies desperately need. Cloud infrastructure. Zero-trust security architecture. Identity and access management. DevOps practices. The ability to write clear documentation and communicate asynchronously. If you can credibly demonstrate expertise in any of these areas, you have real bargaining power.

What You Should Do Right Now

This shift is already happening. You don’t get to wait another year to think about it.

First, assess your current job situation. If you’re happy and your company is embracing remote work seriously, you’re in a good position. If you’re stuck working in an office while competitors are going remote, that’s a problem worth solving. Your bargaining power just increased substantially. Companies that want to attract talent now need to offer remote work as an option, or they need to offer something else that’s compelling enough to make up for that lack of flexibility.

Second, invest in skills that matter for distributed, cloud-first infrastructure. If you haven’t spent serious time with cloud platforms, now is the moment. If you don’t understand zero-trust security, learn it. If you can’t write clear technical documentation, develop that skill. These are the skills that remote-first organizations will pay for.

Third, think about where you want to live and which salary regions you want to work in. If you’re going to take advantage of geographic arbitrage, choose a company that won’t penalize you for it. Ask directly about their compensation philosophy. And frankly, if you live in a high-cost area, this is also an opportunity. You can remain in San Francisco or New York and compete for global jobs, though you’ll be competing on skills rather than location preference.

Fourth, understand that as companies embrace permanent remote work, the competition increases. The person who was previously blocked from applying because they lived in the wrong city is now competing for your next job. That’s not a threat; it’s a fact. Your competitive advantage comes from deep expertise, not from proximity to the office.

The companies making these announcements, from Twitter to Facebook to Shopify, aren’t doing this primarily out of altruism. They’re doing it because they realized they can access better talent, reduce real estate costs, and increase employee satisfaction all at once. That realization is rippling through the industry. And for IT professionals, this moment represents a genuine shift in bargaining power. The skills you have, the work you do, and your ability to communicate clearly now matter more than your ability to commute to an office building.

When you’re thinking about your next move in IT, remember that companies like Twitter and Facebook have already placed their bets. Permanent remote work isn’t coming someday. It’s here. The question is whether you’ll be positioned to take advantage of it.

And that positioning includes the basics. Permanent remote work means your home network, your personal computing setup, and your home internet connection are genuinely part of your work infrastructure now, not temporarily, but for the foreseeable future. I wrote last month about home networks as corporate infrastructure and the security gaps that creates, and those gaps matter even more when the arrangement is permanent rather than a stopgap. Your employer’s zero-trust policies will help, but so will your own diligence about the environment you’re working from every day.

The fundamental IT skills shortage that I wrote about earlier this year hasn’t gone away. If anything, the shift to permanent remote work has made certain skills even more scarce, because every company that commits to distributed work also commits to the infrastructure, security, and tooling that distributed work demands. The companies making these announcements are the ones that will be investing heavily in IT talent for years to come.

This isn’t about waiting for the market to settle. The market has already moved. The question now is whether you’ll move with it.