Remote jobs by role
Remote hiring didn't disappear after the return-to-office wave, but it did concentrate. The roles that stayed remote are the ones where the work is already asynchronous and the output is legible without somebody watching it happen, which is why engineering, design, analytics and support still list remote openings in volume while other functions quietly stopped.
Applying to remote roles means competing against a much larger pool than a local posting, so a generic resume performs worse here than anywhere else. Score your fit against the specific description before you spend time on it, and lead with evidence of the habits distributed teams actually need: written communication, ownership without supervision, and overlap you can genuinely commit to.
Each page below pulls live openings for that role from public job feeds, filterable by source, type and date.
Browse by role
What changed about remote hiring
The number of fully remote postings fell from its peak, but the share of applications chasing each one rose, which is the part that affects you. A remote listing now routinely draws several times the applicants of an equivalent on-site role, so the same resume that would be competitive locally can disappear in a remote pool.
A second shift is quieter and matters more for planning: many roles advertised as remote are remote within a country or a set of time zones rather than genuinely location-independent, usually for tax and employment-law reasons. Check the fine print before investing time, because "remote" and "remote, anywhere" are very different offers.
What remote employers screen for
Written communication does most of the work. When a team is distributed, your writing is the main artefact colleagues encounter, so evidence that you can explain a decision clearly in text is worth more than it would be on-site. Documentation you wrote, proposals you drove, or async processes you set up are all strong signals.
The second thing is ownership without supervision. Say what you delivered when nobody was checking in, and how you handled being blocked. Being specific about overlap hours also helps: a concrete commitment reads as far more credible than "flexible", which employers have learned to discount.
Watch for scams in remote listings
Remote postings attract more fraudulent listings than on-site ones, because the format makes it normal never to meet anyone. The reliable warning signs are structural: any request for payment, a request for bank details or identity documents before a genuine offer, interviews conducted entirely over a messaging app, an offer with no real interview, or a cheque you're asked to deposit and forward. Run anything that feels off through the scam detector before replying.
Common questions
Are remote jobs still widely available in 2026?
Yes, though concentrated in functions where the work is already asynchronous and the output is legible without supervision, such as engineering, design, analytics and support. The count of postings fell from its peak while applicants per posting rose, so the market is competitive rather than absent.
Does "remote" always mean I can work from anywhere?
No, and this is the most common misunderstanding. Many roles advertised as remote are remote within one country or a set of time zones, usually because of tax and employment-law constraints. Check the posting's fine print before applying.
What do remote employers screen for that on-site ones don't?
Written communication above all, because in a distributed team your writing is the main artefact colleagues encounter. After that, evidence of ownership without supervision, and a concrete commitment to overlap hours rather than a vague claim of flexibility.
Why do remote listings attract more scams?
Because the format makes never meeting anyone seem normal. Treat any request for payment, bank or identity details before a genuine offer, an interview held entirely over a messaging app, or a cheque you are asked to deposit and forward as reasons to stop immediately.
Prep for these roles with job search tools, resume tools and interview prep.
The geography that lives inside the remote job market
The word "remote" obscures a fundamental split in hiring: roles that are remote anywhere and roles that are remote in a specific country or time zone. A job posting that says "remote" might mean remote within the United States, remote within Europe, or genuinely location-independent. The difference affects your competitiveness, your taxes, and whether you can even apply. A role that's remote in the US and you're in Canada or Europe might be either inaccessible (company doesn't hire outside US) or competitive (company has international hiring and the remote role attracts global applicants). Read the fine print before investing time. Most job boards and company career sites now clarify this—look for "remote within" or "remote, US-based" or "remote, global." If it says just "remote" with no qualifier, ask or check the company's hiring policy on the application page.
The reason for geographic restriction is usually tax and employment law, not logistics. A US company hiring an employee in the EU triggers EU employment law compliance, which is costly. A Canadian company hiring a US employee needs a USMCA employment agreement and possibly a US tax ID number. Most companies prefer to avoid this complexity, so they restrict hiring to citizens or legal workers of a specific country. This is not discriminatory by their standards; it's a business constraint. What this means for you: a remote role in the English-speaking market often has a geographic scope. If you're outside that scope, check explicitly before applying. Applying to roles you're ineligible for wastes your time and theirs. Some companies list eligibility on the posting ("US-based only"); many don't, and you have to email and ask. The fastest way to check is to start the application. Most application systems will tell you immediately if your location is ineligible.
A second geography quirk is time-zone overlap. A role labeled "remote" might require you to maintain specific hours or timezone overlap with the team. A role that says "remote, flexible schedule" means asynchronous work is standard and no overlap is required. A role that says "remote" with no schedule clarification often means overlap with business hours of the company's main office is expected—so if the company is in San Francisco and you're in Sydney, you're looking at very early mornings or very late nights. Ask about this before interviewing. A role might be geographically open but time-zone incompatible with your life, which makes it less valuable than it appears.
How distributed-team hiring screens differently
Remote roles attract more applicants than equivalent on-site roles because they tap a global pool instead of a local market. For the same engineering role, an on-site posting might get 50 applications; a remote posting might get 500. This changes the screening dynamic. Recruiters move faster through remote applicant piles because they have volume. This means your resume has less time to make an impression. On-site, a recruiter might spend 45 seconds on each resume and flag twenty for phone screening. Remote, they might spend 15 seconds and flag ten. Consequently, your resume needs to be scannable and lead with relevance immediately. The first line of your professional summary and the first two bullets under your most recent role will carry most of the weight. If those don't immediately signal that you're qualified, your application won't make it past the initial screen, regardless of your background.
A second screening difference: distributed teams screen for collaboration patterns and communication skills more heavily than on-site teams. When everyone is in the same office, miscommunication is caught quickly in hallway conversations. When everyone is distributed, miscommunication can persist for days and damage projects. Hiring managers ask different questions for remote roles. They want to see evidence that you've written coherently (good communication in your resume, cover letter, application), managed projects across teams without constant meetings, and taken initiative without close supervision. Your resume should reflect this. A bullet like "Led a cross-team initiative to implement a new data pipeline despite conflicting priorities and asynchronous decision-making" tells a remote hiring manager that you can navigate complexity without being in the same room. A bullet like "Worked with the engineering team to deploy a new feature" doesn't.
Third, remote teams screen harder on timezone and availability because the math matters. If you're in a different timezone and unavailable for meetings during business hours, it creates friction. Most companies will still hire you—remote talent is often worth the coordination cost—but they screen for it explicitly. In interviews, expect direct questions about your timezone, your availability, and whether you've worked across timezones before. This is not discrimination; it's risk assessment. If you're in a timezone that works only during your very early mornings or very late evenings, some companies will pass. Others will love you because you provide coverage. The key is knowing which companies care about timezone alignment and which don't, so you can target your applications accordingly.
Resume tailoring for remote roles requires evidence of different skills
A resume that's competitive for an on-site role is often not competitive for the remote equivalent because the skills being evaluated are different. On-site roles evaluate how you perform under supervision, how you collaborate in person, and how fast you ramp. Remote roles evaluate how you self-manage, how clearly you communicate in writing, and how you ask for help when you're stuck. Your resume should reflect that. A bullet for an on-site role might be: "Collaborated with product to define requirements and shipped three new features." A bullet for a remote role should be: "Owned requirements gathering with product via Slack and email; shipped three new features with full documentation and peer-code-review before merge." The second version signals that you managed the coordination yourself without real-time collaboration, and you documented your work so others could understand it.
The evidence of independence matters more for remote. A bullet like "Led a project" is vague in any context, but in a remote context it's particularly weak. Specify: "Led end-to-end project to migrate our analytics stack; wrote a technical RFC, solicited feedback from four teams over email, incorporated feedback, and oversaw a three-week migration with daily async standups." This tells a remote hiring manager that you know how to propose changes, get buy-in without meetings, and track progress without real-time oversight. If you've worked on a distributed team before, say so. "Coordinated across a five-person team spanning three continents, managing a 48-hour cutoff window for a critical database migration" tells the interviewer that you have distributed-team experience and can manage complexity across time zones.
The tone of your resume for a remote role should emphasize ownership and communication. Remote jobs screen for people who don't need to be managed closely. Your cover letter (if you write one for remote roles) should address timezone explicitly if it's a mismatch. Something like "I'm based in [timezone] and available for core business hours [times]; my past roles have involved similar timezone spreads and I'm comfortable with the coordination overhead" signals that you've thought about it and are not asking the company to accommodate you. This is particularly important if you're in a significantly different timezone from the company.
Frequently asked questions
Do remote companies usually care about where I physically live?
Only for tax and legal reasons. A US company hiring a US employee remotely doesn't care if you're in Maine or California. They care if you're in Canada or Germany because that involves different employment law. Check the job posting or ask during application. Most posts clarify: "remote, US-based" or "remote, global."
If a role says remote but the interview is synchronous, what does that tell me?
It tells you the company values some real-time overlap but doesn't require it full-time. One or two synchronous meetings per week are normal in remote companies. If interviews are scheduled at a timezone that's unreasonable for you, flag it—ask if there's flexibility or if you need to pass.
Are remote roles actually less expensive than on-site roles?
Salary depends on role and company, not location. A remote engineering role at a top-tier company pays market rate; a remote role at a cost-conscious startup pays less. The overhead of remote hiring doesn't usually transfer to lower pay, unless the company explicitly hires in lower-cost-of-living regions.
How do I know if a remote role is actually async-friendly?
Ask during the interview: "What's the expected overlap between my timezone and the core team's?" and "How much of the work happens asynchronously versus in meetings?" Listen for answers about Slack, documentation, and async decision-making. If the answer is "most things are in meetings," it's not truly remote-friendly.
Should I mention in my resume that I've never worked remote before?
No. You don't need to. If you have experience in distributed teams (different offices, different departments), mention that instead. If you don't, just don't mention it. Let the interview address how you'll adapt.