Role
Backend engineer
Backend listings are written as a stack and read as a set of problems. The language is negotiable far more often than the listing admits; what is not negotiable is evidence that you have kept something running that other people depended on.
A backend engineer owns the part of a system users never see and always feel: data that must stay correct, requests that must be answered under load, and the failures that happen at three in the morning. The title covers a wide range — a four-person team’s backend engineer writes infrastructure, a bank’s does not — so what a listing is really asking is which half of that range you have lived in.
What most listings require
A server-side language
What it screens for: Not the language itself — whether you have maintained something written in it for long enough to have regretted a decision.
A sentence that proves it"I have owned our payments service in Python since 2021, including the rewrite of the retry logic after the duplicate-charge incident."
A relational database
What it screens for: Whether you understand that the database is the hard part. Schema design, indexes, and what a migration does under load.
A sentence that proves it"I moved our billing tables to Postgres in 2023 and wrote the migrations; the largest table had 40 million rows and we did it without downtime."
HTTP APIs
What it screens for: Whether you have designed an interface other teams had to live with, not just implemented one somebody specified.
A sentence that proves it"I designed the public API our two mobile clients use, including the versioning scheme when we had to change the order model in 2024."
Testing
What it screens for: Whether anyone can change your code safely after you leave.
A sentence that proves it"I brought our suite from 40 to 300 tests over a year, including the integration tests that run against a real database rather than a mock."
Production responsibility
What it screens for: The real screen. Have you been the person who gets paged?
A sentence that proves it"I was on the on-call rota for three years and wrote the runbook we still use for database failover."
What counts as a bonus
Containers and deployment
What it screens for: Whether you can get your own work in front of users without waiting for somebody else.
A sentence that proves it"I containerized our services in 2022 and set up the deploy pipeline we have used since."
Message queues or event streams
What it screens for: Whether you have worked on something that could not be done in a single request.
A sentence that proves it"I moved our report generation onto a queue so the request stopped timing out at 30 seconds."
Observability
What it screens for: Whether you find problems before a customer reports them.
A sentence that proves it"I added structured logging with a request id across our services, which is how we traced the slow checkout to a missing index."
The requirement nobody writes down
Whether you have maintained something for more than a year. A listing says "3+ years experience" because it cannot say "I want somebody who has lived with their own decisions long enough to have learned from them" — but that is the screen.
Where candidates come up short
- Production responsibility — people who have had it rarely think to say so, because to them it is just Tuesday.
- Database work, described as a technology rather than as a decision. "Postgres" proves little; "I chose the index that took the query from 4s to 40ms" proves a lot.
- Design of an interface somebody else consumed.
Related roles
Backend engineer: questions
- What is the one thing backend engineer listings screen for without writing it down?
- Whether you have maintained something for more than a year. A listing says "3+ years experience" because it cannot say "I want somebody who has lived with their own decisions long enough to have learned from them" — but that is the screen.
- What do candidates for backend engineer roles most often fail to evidence?
- Production responsibility — people who have had it rarely think to say so, because to them it is just Tuesday. Database work, described as a technology rather than as a decision. "Postgres" proves little; "I chose the index that took the query from 4s to 40ms" proves a lot. Design of an interface somebody else consumed.
- How do I turn this into something a company can check?
- Tell the agent what you actually did, in sentences like the examples on this page. Each becomes a claim carrying that sentence and the date it holds for, and a company matching you against a listing sees the requirement, the claim, and your own words behind it.
Prove it, requirement by requirement.
Write sentences like the ones on this page and each becomes a claim with a date. Then match yourself against a real backend engineer listing and read what is still unmet — that list is the plan.