Engineering
Backend engineer job description
Backend engineer job description. This page describes the role for a small team.
What a backend engineer owns on a small team, what to write in the post, and a salary band you replace with the one you will actually pay.
Published November 21, 2026 · 5 min read
A backend engineer on a small team ships the product. They take a problem that already has a user, turn it into a change in the codebase, and stay with it until it is in production and the edge cases are written down. They are not a department. On a team of ten to forty people they are often one of three people who can deploy.
The post has one job: tell a capable person what they will do in the next year, who they will work with, and what the seat pays. A list of twenty tools does not do that. Neither does a paragraph about passion.
What the work actually is
In the first year the engineer will spend most days inside one product. A typical week is a feature that a customer asked for, a bug that support can reproduce, and a review of someone else's change. They will also be the person who gets the alert when a job fails at night, at least until the team is large enough to share that.
Write the post around that week. Name the product surface. If the engineer will own billing, say billing. If they will not touch the mobile app, say that too. Candidates sort themselves out when the boundary is visible.
The failure mode on a small team is a post written for a company of two hundred. It asks for distributed systems, a public speaking record, and five years of a framework the product does not use. The people who can do the real job assume they are underqualified. The people who match the list on paper want a scope you do not have.
What to put in the post
State the reporting line in one sentence. "You will work with the founder and one other engineer" is more useful than a culture paragraph. State the stack in the words the codebase uses. If the API is TypeScript and the data lives in Postgres, write that. Add the thing that is painful today, such as a test suite that is thin around payments, so the candidate knows what they are walking into.
Put the salary band in the post. Use the band for the country of employment, not a converted figure from another market. The band on this page, €48,000 to €78,000 with a midpoint around €62,000, is an example for a mid-level engineer employed in France, outside Paris, in 2026. Replace it. A Paris seat, a senior seat, or a German contract is a different number. If you already know the number you will offer, publish that number.
Say how the work is tracked. Applications, interviews, and the offer should live on one record, not in three inboxes. Teams that hire engineers this way usually keep the role itself in an applicant tracking system, with the same stage names they use for every other seat.
Leave out the tools you do not use, the benefits you are still deciding, and any line that could describe a different job. "Fast-paced" and "rockstar" tell a careful candidate that the post was not written by the person who will manage them.
Example: a third engineer at a 30-person company
A B2B logistics company in Lyon had two engineers and a product manager. The post they published asked for Kubernetes, a computer science degree, and "ownership mindset." They got applicants who wanted a platform team. The person they needed was someone who had shipped a web API and was willing to sit with a warehouse supervisor to see why a status was wrong.
They rewrote the post around three tasks: fix the status bug, add the export the supervisor had asked for, and leave the setup notes better than they found them. They published €52,000 to €68,000 because that was the band the board had already approved. The shortlist got shorter and more relevant. The hire was not faster because of a clever keyword. It was faster because the wrong people stopped applying.
The same post is the document the product manager uses when they write the first tickets. If the post and the tickets describe different jobs, the engineer will notice in the first month.
How the description is used after you publish it
The post is also the spec you score applicants against. When two people read the same CV, they should be checking it against the same three tasks, not against a private idea of the role. Keep the published text, the internal scorecard, and the interview questions pointed at those tasks. When the work changes, change the post. A description that still lists a migration you finished last year will keep attracting the wrong applications.
Frequently asked questions
Should a small team hire a generalist or a specialist?
Hire the person who can ship in the codebase you have. A specialist is the right hire when one skill is the bottleneck, such as a data pipeline nobody else can change. A generalist is the right hire when the next six months are a mix of product work, bugs, and the occasional deploy.
What salary should the post show?
Show the band you will pay for this seat, in the country where the person will be employed. The figures on this page are an example for a mid-level engineer in France, outside Paris. They are not a national survey. A post with no numbers wastes the first week on people who will decline the real number.
How is this different from a senior engineer post?
A senior engineer is hired to change how the team works: design reviews, incident ownership, and the shape of the system. A software engineer post that copies a senior list will attract people who expect that scope and reject people who would do the job well.
Qonir is ATS software for small teams. The job, the candidate, and the stage stay on one record.
Tags
- engineering
- job description
- small teams
