Remote Backend Jobs
176 Remote Jobs available
API Engineer
Supabase3 months agoWorldwideMid levelCI/CDDockerExpressSenior Backend Engineer, IAM
Reddit3 months agoUnited StatesSeniorAWSCI/CDGoogle CloudSenior Backend Engineer - Product
Mercury3 months agoCA · USCAD 167K–197K / yearSeniorSQLSenior Backend Engineer
Instrumentl4 months agoCA · USSeniorExcelSenior Software Engineer (Backend) - AI/ML
ClickHouse4 months agoNetherlandsSeniorAWSAzureGoogle CloudSenior Software Engineer (Backend) - AI/ML
ClickHouse4 months agoGermanySeniorAWSAzureGoogle CloudSenior Software Engineer, Backend (Infrastructure)
Affirm6 months agoUnited StatesUSD 173K–233K / yearSeniorAWSKotlinKubernetesSenior Software Engineer, Backend (Infrastructure)
Affirm6 months agoCanadaSeniorAWSKotlinKubernetesSenior Software Engineer - Backend - AI Clips Team
Restream7 months agoEuropeSeniorAWSDockerJavaScriptSoftware Engineer, Backend (Product)
Hex8 months agoUnited StatesUSD 199K–295K / yearAWSCI/CDExpressStaff Backend Engineer, Hub (East Coast)
Docker10 months agoUnited StatesPrincipalAWSCI/CDDockerBackend Engineer, Developer & End-user Experience Platform
Stripe11 months agoCA · IN · USAccessibilityAWSDockerBackend Engineer III
Monzo20 months agoUnited KingdomGBP 85K–110K / yearSeniorAWSCassandraDockerSenior Backend Engineer
Monzo20 months agoUnited KingdomSeniorJavaScalaStaff Backend Engineer
Monzo20 months agoUnited KingdomStaffAWSCassandraDockerSoftware Engineer (Backend)
Metabase78 months agoUnited StatesJavaScriptTypeScript
Showing 161–176 of 176
Backend roles own the services behind the product: APIs, data models, queues, background jobs, and the latency and correctness guarantees everything else is built on.
Remote backend openings cluster around infrastructure and fintech companies, API-first products, and any team large enough to have split its platform from its interface. Go, Python, Node, Java and Rust dominate the listings.
Read for scale and on-call: a backend role at ten requests a second is a different job from one at ten thousand. Check whether the team owns its own deployments, and whether the on-call rotation is compatible with your timezone.