What we do
Tools
Industries
Department
How we workLet's talk →
Home/Backend Developer
Backend Development

Hiring a Backend Developer? Decide Where the Business Rules Live First

The screens are what people see. The backend is where your business actually happens: what an order costs, who can see which customer, when an invoice counts as paid. A good backend developer puts each rule in one place every screen has to go through, and that decision matters more than which language they write it in.

Why the rules have to live on the server

Anything that runs in a browser or on a phone can be read and changed by the person holding it. So a discount worked out in the website's code, or a check that hides another customer's records on the screen, protects nothing. The server has to work it out again, or work it out only once and hand back the answer.

That's most of what backend work is: an API that every screen and every connected system calls, a database designed so bad data can't get in, and jobs that run in the background and recover when something fails. The language, whether Node, Python, Java or Go, is a smaller choice than where those lines get drawn.

Which rule belongs where

A quick way to check a backend design, or a quote for one.

The rule Where it belongs What goes wrong otherwise
Prices, discounts, tax and order totals Worked out by the backend, one function every screen calls The website, the app and the invoice each calculate it slightly differently, and the customer finds out first.
Who can see or change a record Checked by the backend on every request, against the logged-in user Change a number in the address and you see someone else's order. Broken object-level authorization is first on OWASP's list of API security risks for exactly this reason.
Things that must never be duplicated or missing (invoice numbers, one account per email) A constraint in the database itself Two requests at the same moment both pass the check in code, and you get two invoices with the same number.
Events from other systems, such as a payment confirmed or a parcel delivered A webhook handler that verifies the sender and ignores repeats Providers like Stripe can send the same event more than once, so an order marked paid twice ships twice.
Slow or fragile work: emails, PDFs, syncs to your accounting or CRM A background job queue with retries The customer's checkout hangs while the server waits on a third party, or the sync fails once and is never tried again.

Ask to see these before you sign off a backend

You don't need to read code to ask. A backend developer who can't produce them hasn't finished the job.

  • A written description of the API

    Usually an OpenAPI file listing every endpoint, what it accepts and what it returns. It's what lets a second developer, a mobile app or a partner build against it without guessing.

  • A diagram of the database tables

    Even a rough one. If nobody can draw how customers, orders and invoices relate, the next feature will be built on a guess.

  • Migrations for every database change

    Scripts that change the schema step by step, kept with the code. Without them, the test and live databases drift apart and nobody can rebuild either.

  • The list of who can call what

    Which roles exist and what each may do, and a test that tries to read another account's data and fails.

  • What happens when a background job fails

    Where the failure is logged, how many times it retries, and who gets told when it gives up.

  • How to run it on a new machine

    Written steps, or one command, to start the backend locally with test data. It's the quickest test of whether anyone else can take it over.

Let's talk

One backend that every screen and system agrees with

n-frames designs and builds backends for businesses whose website, app and internal tools need the same rules, and whose data has to reach their CRM, accounting or inventory system. We map where each rule lives before writing the API, and hand over the six items above with the code.

Design my backend →

Questions people ask

Does the backend language matter more than who is building it?

Less than people expect. Most mainstream backend languages can run a business app well. Where the rules live, how the database is designed and how failures are handled decide whether it holds up. We usually match the language to what your team or your existing systems already use.

Can you take over an existing backend from a freelancer who's gone?

Yes. We start by running it locally, writing down the API it actually exposes and drawing the database, since those are often missing. Then we check permissions on every endpoint before adding anything new, because that's where inherited backends most often leak.

Is this different from hiring an API developer specifically?

An API developer is often hired for one interface: connecting two systems, or exposing your data to a partner. Backend work covers the whole server side, including the database, permissions and background jobs. If you mainly need two existing systems talking, the API job is smaller.

How does backend work relate to the frontend and the database?

The frontend shows the screens and calls the backend's API. The backend applies the rules and reads and writes the database. Some teams split those across people, others hire a full stack developer. Complex data models sometimes need a database developer, and hosting and releases a DevOps engineer.

Which backend skills do interviewers actually probe?

Database design and SQL, how authentication and permissions work, and how you'd describe an API for someone else to build against, all in one language and its main web framework. Having deployed something real helps. Being able to explain why a rule lives on the server rather than in the browser goes a long way in interviews.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.