Job Description Proficiency in backend web development in Typescript/Javascript (NodeJS). Proficiency in widely-used DBMS technologies... ...the backend software Write clean code and tests to develop a functional and rel…
Engineering & IT · Remote
Remote Backend Developer jobs
Backend developers build the server-side logic, APIs, and data layers that applications run on. The job is designing services that stay correct, fast, and secure as usage grows.
5,362
Open roles today
$35–$91/hr
Typical pay range
$122k
Median, full-time
2
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open backend developer roles
4 shown of 5,362 · sorted by freshness
$40 - $42 per hour
Backend Engineer (JSON Schema Developer) is a remote evaluation track for reviewing backend engineer evaluation prompts and responses against AuraOne's quality rubric. Reviewers compare paired outputs, label edge cases,…
Seeking an experienced Backend Engineer focusing on building high-performance API based backend platform and highly reliable foundational... ...as Code using cloud-native tools and services Develop monitoring frameworks…
RESPONSIBILITIES Design, develop, and maintain scalable backend services for key components of the Xsolla platform . Architect and evolve microservices-based systems to support large-scale, high-performance operations. I…
02
What backend developers earn remotely
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$48 | $72k–$100k |
| Mid level | $48–$70 | $100k–$145k |
| Senior | $67–$91 | $140k–$190k |
National ranges — remote pay usually tracks the employer's base market.
03
What employers ask for
The skills these listings keep naming
A server language (Java, Go, Python, C#)API design (REST, gRPC)SQL and schema designCaching and queuesAuthentication and securityDistributed systems basicsDocker and CI/CDObservability and logging
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Design an API for a feature like comments or notifications.
Clarify requirements, then cover endpoints, data model, pagination, and error handling. Mentioning versioning and rate limits shows production experience.
How would you find and fix a slow database query?
Walk through reading the query plan, checking indexes, and considering caching or denormalization. Ground it in a query you actually fixed.
How do you keep two services consistent when both need to update data?
Discuss transactions, idempotency, and eventual consistency with outbox or saga patterns. Acknowledge tradeoffs rather than promising perfect consistency.
What do you monitor on a service you own?
Name the basics — latency, error rate, saturation — plus business-level signals. Bonus points for talking about alerts you tuned to reduce noise.
Tell me about a production incident you handled.
Structure it: detection, mitigation, root cause, prevention. Emphasize what changed afterward, not just the firefight.
How do you approach securing an API?
Cover authentication, authorization, input validation, and secrets handling. Naming OWASP-style risks concretely is enough; you are not expected to be a security engineer.
When would you choose a message queue over a direct call?
Talk about decoupling, retries, and absorbing spikes, and be honest about the added complexity of async debugging.
05
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
01
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
02
Name the databases and infrastructure you ran in production, not just languages.
03
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
04
If you designed an API others consume, say so and note how many teams or clients depend on it.
05
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
06
Where this role goes
Typical progression
01
Junior Backend Developer
02
Backend Developer
03
Senior Backend Developer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
Applying for backend developer jobs remotely?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.