Skip to main content
PProfileMatch

21 open Backend Developer jobs

Real, currently-open Backend Developer roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Backend Developer guide.

Hiring snapshot for Backend Developer

The most common locations right now are Dublin (3), New York, NY (HQ) (3), Remote, United Kingdom (2). 5 of these 21 roles (24%) list a remote option. 13 were posted in the last two weeks. By team, the biggest groups are Engineering (21).

Computed from the 21 open listings shown below.

Guide: working as a Backend Developer

Backend developers build the server-side logic, APIs and data storage that applications depend on. Typical work includes designing endpoints, writing database queries and migrations, handling authentication, adding caching or queues for slow operations, and making sure services log useful information when something fails in production.

Core skills employers look for

  • REST API design and versioning
  • Relational schema design
  • Query tuning and indexing
  • Token or session authentication
  • Caching with Redis or similar
  • Message queues and async jobs
  • A server framework (Spring, Express)
  • Logging, metrics and error handling

How to stand out when you apply

  • Build an API with pagination, input validation, rate limiting and correct HTTP status codes, then document it with an OpenAPI spec so a reviewer can try it quickly.
  • Show you understand data: include a schema diagram, explain an index you added with the query plan before and after, or describe a migration run without downtime.
  • Mention how your service behaves under failure, such as retries with backoff, idempotency keys for payment-like requests, or timeouts on calls to other services.
  • Containerise the project with a Dockerfile and a compose file that also starts the database, so anyone can run it locally with a single command.

What the interviews usually cover

Rounds commonly include a coding problem, an API or schema design exercise, and deep questions on databases: transactions, isolation levels, indexes and N+1 queries. You may be asked how to handle concurrent updates to the same record, or how you would investigate a slow endpoint. Senior roles add service-level design covering caching, queues and consistency trade-offs.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company