Engineering and IT · Interview questions

Backend Developer interview questions

These questions check whether a candidate can build APIs that stay fast, correct and secure as data grows. Ask every candidate the same questions and score each answer against the notes.

The questions

Ask every candidate the same questions in the same order, and score each answer against the notes before you talk it over with the panel.

  1. Tell me about an API endpoint you made faster. How did you find the cause and how did you prove it was fixed?

    What it tests
    API response time outcome.
    A strong answer
    They started from monitoring or logs, found a specific cause such as an N+1 query or missing index, and fixed it. They show before and after timings under real load.
    Watch for
    Adding a cache to hide a slow query without understanding why it was slow.
  2. Here is an endpoint: GET /orders/{id} loads the order from the database and returns it. What is wrong with it from a security point of view, and how would you fix it across the codebase?

    What it tests
    Access control outcome, practical code review.
    A strong answer
    They see that any signed-in user can read any order by changing the ID. They suggest checking ownership in a shared layer, such as a policy or query scope, and adding tests for it.
    Watch for
    Suggesting random IDs as the only protection.
  3. You need to split a full_name column into first_name and last_name on a table with five million rows, with no downtime. Walk me through the steps.

    What it tests
    Safe schema changes outcome.
    A strong answer
    They add new columns, write to both, backfill in batches, switch reads, then drop the old column in a later release. They run each step on staging first and have a way back.
    Watch for
    A single migration that locks the table during business hours.
  4. Describe API documentation you wrote that other developers relied on. How did you keep it accurate?

    What it tests
    Documentation outcome.
    A strong answer
    They describe a format such as OpenAPI, generated or checked in the build so it cannot drift from the code. They mention examples and clear error responses.
    Watch for
    Documentation that lives in one person's head or an old wiki page.
  5. Tell me about a time a background job failed silently and nobody noticed for a while. What did you change afterwards?

    What it tests
    Reliability of background work.
    A strong answer
    They explain the root cause and then added alerts, retries with limits and a way to see failed jobs. They made the job safe to run twice.
    Watch for
    Fixing the one failure without adding any way to detect the next one.
  6. The mobile developer asks for an endpoint that returns a user with all their orders, payments and messages in one call. How do you respond?

    What it tests
    API design and working with client developers.
    A strong answer
    They ask what the screen actually needs and propose a response that fits it, with pagination for long lists. They weigh one large call against several small ones and agree the contract before coding.
    Watch for
    Building exactly what was asked even if it will return megabytes of data.
  7. Someone asks you to fix a wrong balance for one customer by running an UPDATE directly on the production database. What do you do?

    What it tests
    Data safety and discipline.
    A strong answer
    They find out why the balance is wrong first. They fix the cause and correct the data through a reviewed, repeatable script or migration with a record of what changed.
    Watch for
    Running the update by hand with no review and no record.
  8. How do you decide what to cover with automated tests in a backend service?

    What it tests
    Correctness and safe change.
    A strong answer
    They test business rules, permissions and data changes with integration tests against a real database. They keep unit tests for complex logic and avoid tests that only repeat the code.
    Watch for
    Relying only on mocks so the tests never touch real queries.

New to structured interviews? Read how to run structured interviews and how to build an interview scorecard.

Start from the job description

These questions follow the first-year outcomes in the matching template.

Backend Developer job description template

Similar roles

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

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