Remote Software Engineer Jobs

There is a real difference between a company that permits remote engineering and one built for it. Remote-first teams like Moonrig (developer infrastructure) and Cindergrid (incident response) run on written artifacts: design docs and RFCs instead of whiteboard huddles, recorded demos instead of status meetings, and pull request descriptions that stand alone. Driftline builds async video tooling and eats its own cooking, most decisions there live in threads you can read weeks later.

For you as a candidate, that means writing is a first-class engineering skill. Expect interviews to probe how you document decisions, how you disagree in writing, and how you unblock yourself when the person with the answer is asleep. Timezone overlap requirements are usually modest (two to four shared hours), but they are stated per listing, so check before applying. On-call expectations, where they exist, are also disclosed up front; that is part of what our vetting of remote first companies checks for.

Interview loops at the companies on this board lean practical: a scoped take-home or a pairing session on realistic code, then a systems conversation, then team fit. Pure algorithm gauntlets are increasingly rare in remote-first hiring because they predict little about async work. Prepare a repository you are proud of and be ready to walk through the tradeoffs out loud.

The scale of the occupation is easy to underrate. BLS counted 1,905,400 software developer, quality assurance analyst and tester jobs in 2025 and projects 185,400 more by 2035, a 10 percent rise, with a May 2025 median wage of $134,040. It is also the deepest entry pool in the field by a wide margin: about 106,100 openings a year, which is 43 percent of the roughly 245,700 openings across the eight computer and IT occupations BLS publishes separately, and more than twice the next largest, computer support specialists at 48,700. If you are choosing a lane rather than a job, that ratio is the single most useful number available, and remote IT jobs sets out how the rest of the field compares on pay, openings and how remote each part of it really is.

Compensation is the strongest argument for boards with mandatory salary bands: engineering pay varies widely, and the band tells you instantly whether a conversation is worth having. If you have been scrolling developer listings where pay is optional and half the roles are reposts, our RemoteOK alternative comparison sets out what changes when the band is mandatory. Mid-level remote engineers on this board typically see $115k to $170k, seniors $160k and up, with equity described in the listing where offered. Data-adjacent engineering is growing fastest; if you sit near that line, compare against remote data analyst jobs too. Details of how listings are vetted and refreshed are on the remote job board page.

One underrated feature of the job, if you are weighing engineering against other remote functions: it is the quietest professional work in the federal data. O*NET asks workers how often their job involves telephone conversations and scales the answer from 0 to 100. Software developers score 61 and computer programmers 60, against 80 for data entry keyers, 95 for bookkeeping clerks and 100 for customer service representatives. The mechanism is straightforward. Engineering output is an artifact that can be reviewed asynchronously in a pull request, so the code review thread replaces the call. If that matters to you, remote jobs with no phone calls lists the low-telephone slice of the board with the full occupational table.