Remote developer jobs by stack

Remote developer jobs exist in every major stack, but each one hires differently: Python and TypeScript roles are spread across many kinds of companies, Go and Rust cluster in infrastructure and tooling, Ruby and PHP live in established products, and cloud or DevOps roles reward certifications and on-call experience. Search by stack first, then by region and timezone.

This guide walks through the main stacks one by one, describes the kinds of companies that tend to hire remotely in each, and shows how to search for them. It avoids made-up counts. For live numbers, the stack pages on RemoteBoard show the open roles today, computed from real listings.

Why searching by stack works

Job titles in software are inconsistent. "Software engineer", "backend developer", "platform engineer" and "product engineer" can describe the same work, or very different work. The stack is often the more reliable signal. A role that lists Go, Kubernetes and PostgreSQL tells you more than its title does.

RemoteBoard reads each job's title and description for technology names and tags it with the stack and skills it mentions. On the remote job search you can filter by several stack tags at once, and choose whether a job must match any of them or all of them.

Python

Python is used for backend web services, data engineering, machine learning, scientific computing, automation and scripting. That breadth means remote Python roles appear in many settings: SaaS companies, data platforms, fintech, research groups and infrastructure teams.

What to expect:

• Backend roles often pair Python with Django or FastAPI, PostgreSQL and a message queue.
• Data roles pair it with SQL, orchestration tools, warehouses and dataframe libraries.
• Machine learning roles pair it with deep learning frameworks and model serving tools.
• Platform and tooling roles use Python for automation alongside Go or shell.

Tips for applicants:

• Be specific about which kind of Python work you do. "Python developer" alone is broad.
• Show evidence of production work: tests, typing, packaging, deployment.
• For data and machine learning roles, show how your work reached users or decisions.

Browse current openings on the remote Python jobs page, which lists only roles that mention Python.

JavaScript and TypeScript

JavaScript runs in every browser, and TypeScript has become the default for many teams building larger front ends and Node.js services. Remote roles in this stack are widespread, from early-stage startups to large product companies.

What to expect:

• Frontend roles center on React, Vue, Svelte or Angular, with TypeScript, testing and accessibility.
• Full stack roles combine a front end framework with Node.js, a database and an API layer.
• Backend Node.js roles focus on APIs, event-driven services and serverless functions.

Tips for applicants:

• TypeScript experience is often expected even when the title says JavaScript.
• Accessibility, performance and testing skills stand out in frontend interviews.
• A small, well built public project can say more than a long list of frameworks.

Go

Go is popular for cloud infrastructure, networking, developer tools, distributed systems and high-throughput backend services. Remote Go roles tend to be at infrastructure companies, developer tooling vendors, fintech and larger SaaS platforms with heavy backend load.

What to expect:

• Work on APIs, microservices, command-line tools, Kubernetes operators or data pipelines.
• Strong emphasis on concurrency, observability and reliability.
• Frequent pairing with Kubernetes, gRPC, PostgreSQL and cloud platforms.

Tips for applicants:

• Show you understand concurrency patterns, profiling and error handling in Go.
• Open source contributions to Go infrastructure projects are well recognized.
• Many Go roles include on-call duties, so ask about the rotation.

Rust

Rust is chosen where performance and memory safety matter together: systems programming, databases, networking, blockchain infrastructure, embedded work, WebAssembly and performance-critical services. The remote Rust market is smaller than for the most common languages, but many Rust teams are distributed by design.

What to expect:

• Roles at infrastructure, database, security and developer tooling companies.
• Deep technical interviews on ownership, lifetimes, async and performance.
• Some roles ask for Rust plus another language, often Go, C++ or Python.

Tips for applicants:

• Real Rust code in a public repository is especially valuable, because the language is harder to learn on the job.
• Explain trade-offs you made, such as when you used unsafe code and why.

Ruby

Ruby, mostly through Ruby on Rails, powers a large number of established SaaS products and marketplaces. Many of these companies have worked remotely for years, and Rails teams are often comfortable with async work.

What to expect:

• Full stack product work on a mature codebase.
• Emphasis on testing, maintainability and shipping features end to end.
• Frontend work with Hotwire, React or a mix.

Tips for applicants:

• Experience upgrading large Rails applications is valued.
• Show product sense: how a feature you built changed something for users.

PHP

PHP remains one of the most widely deployed web languages. Modern PHP, often with Laravel or Symfony, runs SaaS products, ecommerce platforms, publishing systems and agency projects. Remote PHP roles appear at product companies, ecommerce businesses and agencies serving international clients.

What to expect:

• Laravel or Symfony applications with MySQL or PostgreSQL, queues and caching.
• Ecommerce roles around popular open source and hosted platforms.
• Agency roles with several client projects at once.

Tips for applicants:

• Show modern practice: typed code, tests, static analysis, automated deployment.
• For agency roles, show you can communicate directly with clients across time zones.

Java and the JVM

Java, Kotlin and Scala run large enterprise systems, banking and payments, high-scale backends and Android apps. Remote Java roles exist, but large enterprises sometimes limit them to specific countries for employment reasons.

What to expect:

• Spring Boot services, event streaming, relational databases and cloud deployment.
• Strong interest in system design and performance at scale.
• Kotlin roles for both backend and Android work.

Tips for applicants:

• Check the eligible regions carefully, because enterprise employers often hire only where they have entities.
• System design experience is a common interview focus.

Cloud and DevOps

Cloud, DevOps, site reliability and platform engineering roles focus on infrastructure, automation, reliability and developer experience. These roles are often remote friendly, because the work is already done on remote systems.

What to expect:

• Infrastructure as code, container orchestration, CI and CD pipelines, monitoring and incident response.
• Work across one or more major cloud providers.
• On-call rotations, which affect time zone requirements.

Tips for applicants:

• Certifications from cloud providers can help, especially early in a career, but real incident and migration stories matter more.
• Ask how on-call is organized across time zones, and how it is compensated.

Stack overview

Searching effectively on RemoteBoard

A few combinations work well.

• Stack plus region. Combine a stack filter with Worldwide, Europe or another region. Remote jobs worldwide is a good starting point when you need maximum eligibility.
• Stack plus timezone. Use the overlap slider so you see only roles whose hours you can cover.
• Stack plus salary. Set a salary floor in USD per year and tick "salary shown only" to see roles that publish a range.
• Any versus all. Choose "all" when you need a specific combination, such as Go and Kubernetes. Choose "any" when you are flexible, such as Python or Go.

The broader remote developer jobs page shows all software engineering roles across stacks, which helps when you are open to switching languages.

Moving between stacks

Many developers move between stacks during a career. Remote employers are often open to it if you show strong fundamentals and some real work in the new language.

Practical steps:

• Build one meaningful project in the target stack rather than several small tutorials.
• Contribute a fix to an open source project that uses it.
• Apply to roles that list your current stack as a plus, so the move is gradual.

Checklist for a stack-focused search

• [ ] I picked my primary stack and one or two secondary ones.
• [ ] I set stack filters with the right any or all choice.
• [ ] I added region and timezone filters that match my situation.
• [ ] I set a salary floor or ticked salary shown only.
• [ ] My portfolio shows production-quality work in the stack I am targeting.
• [ ] I saved the search as an alert.

The short version

The stack you work in shapes the kind of remote companies you will meet, the interviews you will face and the time zone expectations that come with the job. Search by stack first, then narrow by region, timezone and salary.

Start with remote developer jobs or the remote Python jobs page, and turn your search into a free job alert so new roles in your stack come to you.