Engineering and IT · Job description template

Backend Developer job description template

Every screen in your product depends on the APIs and data behind it. The backend developer designs and maintains those APIs, the database and the background jobs. They are accountable for data being correct, safe and quick to reach.

First-year outcomes

What should be visibly different a year from now. Results, not tasks.

  • The ten most used API endpoints respond in under 300 milliseconds for 95 percent of requests, shown on a monitoring dashboard.
  • Every database schema change goes through a versioned migration that has been run on staging first, with no manual production edits.
  • Every public endpoint is documented in an OpenAPI file that the frontend and mobile developers use without asking questions.
  • No customer data incidents caused by missing access checks, confirmed by a review of every endpoint against the permission rules.

The work

Recurring work

  • Build and change API endpoints for new product features.
  • Write and review database migrations and query changes.
  • Look into slow requests and errors flagged by monitoring or logs.
  • Maintain background jobs such as emails, imports and scheduled reports.

Projects

  • Add indexes and rewrite the slowest queries found in the database logs.
  • Move manual data fixes into repeatable, tested scripts.
  • Write the OpenAPI documentation for existing endpoints.

Decisions they own

  • How to model new data in the database.
  • The shape of request and response payloads for new endpoints.
  • When a task should run in a background job instead of during a request.

People they work with

  • Frontend and mobile developers, to agree API contracts before building.
  • The DevOps engineer or whoever runs infrastructure, about database load and deployments.
  • The product owner, to understand what data the business needs to keep and report on.

Requirements

Essential on day one

  • Building production APIs in at least one server language such as Python, Node.js, Java, Go or C#.
  • Writing SQL confidently, including joins, indexes and reading a query plan.
  • Understanding of authentication and authorisation for APIs.
  • Comfort with Git, code review and automated tests.

Helpful, but can be learned

  • Your specific framework, if they know a similar one.
  • Message queues and caching tools such as Redis.
  • Your cloud provider and monitoring tools.

How to assess it

One piece of evidence for each first-year outcome.

OutcomeEvidence to look for
Fast top API endpointsShow a slow query and its execution plan. A good candidate spots the missing index or the repeated query in a loop and explains how to confirm the fix.
Safe, versioned schema changesAsk how they would rename a column on a large live table. Good answers use a multi-step migration so old and new code both work during the deploy.
Documented endpoints others can use aloneAsk for an example of API documentation they wrote, or have them document one small endpoint. Good work shows required fields, error responses and an example.
No data incidents from missing access checksGive them an endpoint that returns an order by ID with no ownership check. Strong candidates spot it quickly and describe a consistent way to enforce permissions.

Opening for the job ad

You will own the APIs and data that every part of our product relies on. In your first year, our busiest endpoints should be quick, every schema change should be safe and repeatable, and our other developers should be able to use the API from the documentation alone.

Turning this into an ad? See how to write a job ad that gets applicants.

Next: interview for these outcomes

Eight structured questions for this role, each tied to an outcome above.

Backend Developer interview questions

Similar roles

Your next hire, start to finish, in one place.

Free workspace. No card. Full scoring free for 7 days.