How To Find a Remote Software Engineering Job

Software engineering is one of the most remote-friendly professions, but it is also one of the most competitive remote markets. Engineers from many countries apply to the same roles, and many employers can only hire in certain locations. Searching well means looking where engineering roles are actually posted and presenting your work the way remote teams evaluate it.

This guide builds on our general guide to finding a remote job with what is specific to engineers.

Define your search by stack, domain and level

Engineering titles are inconsistent: a "software engineer", "backend developer" and "platform engineer" can do very similar work. Search by what you actually do:

• Stack: languages and frameworks you can work in professionally, such as TypeScript and React, Python, Go, Java or Rust.
• Domain: payments, developer tools, data infrastructure, health, e-commerce or another area where your experience is deep.
• Level: junior, mid-level, senior, staff. Apply at the level your experience supports; a well-matched level gets more replies than an ambitious one.

JobsRemoteList has collections that follow this logic, such as remote React jobs, backend roles and full-stack roles, alongside the main remote software engineering category.

Where remote engineering roles are posted

Company ATS boards

Tech companies post almost all engineering roles on Greenhouse, Lever, Ashby or similar boards first. Searching these directly, or through a site that reads them, shows roles soon after they open. See how to search Greenhouse, Lever and Ashby boards.

Engineering communities

The monthly "Who is hiring?" thread on Hacker News, language and framework communities, and open-source project channels are places where engineering managers post directly. Many posts state clearly whether the role is remote and where.

Startup and investor boards

Early-stage companies often hire engineers remotely. See how to find remote startup jobs.

Companies behind tools you use

If you know a developer tool, database or framework well, the company behind it is a strong target: your experience is directly relevant and you can talk about the product credibly.

What remote engineering teams look for

Beyond technical skill, distributed teams evaluate how you work when nobody is in the same room:

• Written design: can you explain a technical decision in a document others can review asynchronously?
• Code review quality: clear pull request descriptions, small focused changes, constructive review comments.
• Ownership: taking a problem from vague to shipped, including testing, monitoring and follow-up.
• Communication across time zones: updates that let others continue without waiting for you.

Show these in your resume bullets and in interviews with specific examples: "wrote the design doc for…", "led the migration of…, coordinating with engineers in three time zones".

Signs in a listing that a team works well remotely

• The listing names the time zones or overlap hours the team works in.
• It mentions written practices such as design documents, RFCs or written updates.
• The interview process is described, including how long it takes.
• Salary information or the company’s pay model is stated.
• The team or engineering blog shows engineers in several countries.

Listings that describe only office perks, or that say "remote" in the title but ask for regular office days in the text, are worth a question before you apply.

Present your work so it can be checked

Remote reviewers cannot ask a colleague about you, so make your work easy to verify:

• link to public code, open-source contributions or technical writing where you have them;
• for private work, describe the system, your role, the scale and the result in concrete terms;
• keep your GitHub or portfolio focused: a few well-documented projects beat many abandoned ones;
• make sure your profiles match your resume on dates and titles.

The remote engineering interview process

Common stages are a recruiter call, a technical screen (live coding or a take-home task), a system design interview for mid-level and senior roles, and conversations about collaboration and past projects. Some remote companies also ask for a written exercise, such as reviewing a pull request or writing a short design proposal.

Practise coding while talking through your thinking on a video call, because that is how most remote technical interviews run. Prepare a reliable setup: a working microphone, a shared editor you know, and a backup connection if possible. Our guide to preparing for a technical interview and the list of software engineer interview questions go into detail.

Questions to ask remote engineering teams

• How are technical decisions made and recorded?
• What does on-call look like across time zones?
• How long does a typical pull request wait for review?
• How do new engineers get their first change into production?

The answers tell you more about day-to-day remote work than any careers page.

Searching as a junior engineer

Remote junior roles exist but are scarce, because teams find it harder to mentor new engineers remotely. Improve your odds by:

• targeting companies with structured graduate or apprenticeship programmes;
• contributing to open-source projects, where maintainers see your work and communication directly;
• considering hybrid or local roles for your first year, then moving to remote with experience;
• searching junior software engineer jobs and entry-level remote roles specifically.

Searching as a senior engineer

Senior engineers have more options, but competition for the best-paid remote roles is intense. Focus on fewer, better-matched applications; use referrals from your network; and be ready to show impact beyond your own code, such as mentoring, design leadership and decisions that improved reliability or cost.

Contracts, employer of record and location

If you live outside the countries where a company has an entity, you may be hired as a contractor or through an employer of record. Both are common in remote engineering. Understand what each means for your taxes, benefits and notice period before you accept, and confirm the pay model, since many companies adjust salaries by location. Our guide to how remote salaries work explains the options, and the software engineer salary guide gives a starting point for ranges.

A focused weekly plan for engineers

1. Check alerts and the boards of your shortlisted companies twice a week.
2. Send two or three tailored applications, each with one specific technical example in the cover note.
3. Spend one session on interview practice: a coding problem out loud or a system design sketch.
4. Spend one session on visible work: a pull request, a blog post or improving a project’s documentation.

Avoid offers that ask you to pay for "training" or to use your own accounts to move money; scammers target engineers too. See how to avoid remote job scams.