Remote Software Engineer Jobs

Remote SWE jobs still exist. You just have to know where — and how to stand out for them.

The mass RTO push from big tech made headlines, but it didn't kill remote engineering. Hundreds of remote-first companies are still actively hiring — and they receive fewer, more qualified applications than mega-corps. This guide tells you exactly where they are, what they pay, and what your resume needs to say.

Tailor My Resume for Remote Jobs →
The 2025 landscape

What happened to remote software engineering

In 2020–2022, virtually every tech company went remote. In 2023–2024, Amazon, Google, Meta, and others began mandating return-to-office. This created a sharp split: legacy tech companies are largely hybrid or in-person; remote-first companies (which were always fully distributed) have maintained their culture and kept hiring remotely.

For engineers who want remote, the strategy is now about targeting the right companies rather than filtering by job listing. A "remote" badge on LinkedIn from Amazon or Apple often means "remote for now" — not the same as GitLab's all-remote philosophy.

~15%
of software engineering roles are now fully remote (down from 60% peak)
3–5×
more applications per remote role vs equivalent in-office roles
92%
of remote-first companies report no plans to go back to offices
Where to look

Remote-first engineering companies worth targeting

These companies are remote by design — not by exception. Distributed culture is baked into how they operate, communicate, and build.

GitLab
Fully remote since founding. 2,000+ employees across 65+ countries.
All levels
Automattic
WordPress.com creator. Fully distributed, async-first culture.
All levels
Zapier
No-code automation leader. 100% remote, strong eng culture.
Mid–Senior
Hashicorp
Infrastructure software. Remote-friendly, acquired by IBM 2024.
Mid–Staff
Grafana Labs
Observability platform. Majority remote across US and Europe.
Mid–Senior
Fly.io
Developer-focused cloud infra. Small, remote, technical team.
Senior+
Netlify
JAMstack and edge deployment. Distributed team globally.
Mid–Senior
Elastic
Search and observability. Remote-friendly across many geographies.
All levels
Compensation

Remote software engineer salary ranges (US market, 2025)

Junior (0–2 yrs)
$90K–$140K
Remote-only companies often pay market rate regardless of location
Mid-level (3–5 yrs)
$140K–$200K
FAANG remote bands lean higher; startups vary by funding stage
Senior (6–10 yrs)
$180K–$270K
Some remote-first companies add location adjustments for international
Staff / Principal
$240K–$380K+
Equity compensation often larger than base at this level

Ranges are approximate and vary by company, tech stack, and geography. Equity not included.

Resume strategy

What your resume must signal for remote roles

Distributed team experience
Explicitly mention if you've worked with teams across time zones. 'Collaborated with distributed team across US, EU, and APAC' is a genuine signal — not filler.
Async communication tools
Mention Notion, Linear, Confluence, Loom, or Slack-async if you've used them as primary collaboration tools. Remote-first companies want engineers who document decisions, not just join calls.
Self-directed impact
Remote roles require initiative. Show projects you drove with minimal oversight — especially ones that went from idea to shipped without heavy management.
Written communication
PRD contributions, RFC authoring, detailed Jira tickets, Confluence documentation — any signal that you communicate clearly in writing strengthens a remote application.

Tailor your resume for the remote role you actually want.

ezapply reads the job description and rewrites your resume to match — highlighting your async work experience, distributed team background, and technical impact.

Tailor My Resume Free →
3 free resumes/month ATS score included No credit card
Common questions

Remote SWE job questions answered

Is the remote software engineering market getting better or worse?

It depends on the tier. Post-2023 RTO mandates hit big tech (Amazon, Google, Meta now require in-office days). But remote-first companies — those built remote — have stayed fully distributed. The market is more selective now: genuinely remote roles are fewer but the companies offering them are often stronger cultural fits for remote workers.

Do I need a different resume for remote roles vs in-office roles?

Yes. Remote roles screen for self-direction, async communication skills, and documentation habits. Add relevant experience: distributed team work, async tool proficiency (Notion, Linear, Loom, Confluence), and any metrics that show you drove impact independently. ezapply can tailor your resume to highlight exactly these signals.

Will remote companies adjust my salary based on where I live?

It varies significantly. Companies like GitLab and Automattic pay based on local market rates (lower in lower-cost cities). Others like Zapier pay a flat US rate regardless of location. Always ask in the recruiter call — it's a standard question and expected.

What time zone requirements do remote SWE jobs typically have?

Most US-based remote roles require US time zone overlap (typically ET or PT, or anywhere in the US). Global remote companies (GitLab, Automattic) have fewer restrictions but often expect 4 hours of overlap with your team. Some roles are fully async with no required overlap.

How do I find remote SWE jobs that aren't on LinkedIn?

Try: We Work Remotely (weworkremotely.com), Remote OK (remoteok.com), Himalayas (himalayas.app), and company career pages directly. Also search LinkedIn with 'remote' filter but check company-by-company — many 'remote' listings are actually hybrid or require proximity.

Related resources

The right remote job is out there. Make sure your resume is ready for it.

Paste your resume and a job description. Get back a tailored version that beats ATS filters and lands interviews.

Optimize My Resume Free →
3 free resumes/month ATS score included No credit card