Prova

Interview questions

Backend developer interview questions

Backend interviews check whether you can write correct code and whether you understand what happens to it in production: under load, with a slow database and at 3 a.m. when something breaks.

Rehearse this interview by voice2 minutes without an account, 3 more after sign-up. No card.

Questions by stage and what a strong answer includes

  1. 01

    What languages and frameworks do you work in?

    Strong answer: Primary language and framework (Go, Java with Spring, Python with Django or FastAPI, Node), database, message queue, cloud provider. Say what you have shipped in each, not only used.

  2. 02

    What kind of systems have you worked on?

    Strong answer: Type (payments, internal tools, APIs for mobile), scale in requests per second or data size, and your role in the team.

  1. 03

    Tell me about a production incident you handled.

    Strong answer: Detection, mitigation, root cause and what changed afterwards. A blameless postmortem mindset and a concrete prevention step.

  2. 04

    Describe a technical decision you made that you would now make differently.

    Strong answer: The context and constraints at the time, what you learned and how it changed your approach. Shows judgment, not perfection.

  1. 05

    How would you design a REST API for orders? What about versioning and idempotency?

    Strong answer: Resource naming, status codes, pagination, validation, idempotency keys for creation and payments, and a versioning strategy that does not break clients.

  2. 06

    A query that used to take 50 ms now takes 4 seconds. What do you check?

    Strong answer: Query plan, missing or unused indexes, table growth, locks, N+1 queries from the ORM, connection pool saturation. Measure before changing anything.

  3. 07

    When would you use a message queue instead of a direct call?

    Strong answer: Decoupling, spikes in load, retries and slow downstream work. Mention delivery guarantees, idempotent consumers and dead letter queues.

  4. 08

    Coding: implement a rate limiter for an API.

    Strong answer: Pick an algorithm (token bucket or sliding window), explain the trade-offs, handle concurrency and discuss how it would work across several instances with Redis.

  1. 09

    System design: design a URL shortener or a notification service.

    Strong answer: Requirements and scale first, then API, data model, storage choice, caching, failure modes and how you would monitor it. Make trade-offs explicit.

  2. 10

    How do you make sure your code is safe to deploy?

    Strong answer: Tests at the right levels, code review, feature flags, gradual rollout, metrics and alerts you check after the deploy, and a rollback plan.

  1. 11

    What matters to you in your next team?

    Strong answer: Concrete things: on-call expectations, code review culture, ownership of services, level and compensation range. Asking about on-call is normal and expected.

One answer, before and after

Tell me about a production incident you handled.

Weak answer

We had an outage once and I helped fix it. It was a database problem. We restarted things and it worked again, then we wrote a postmortem.

Strong answer in STAR

Situation
On a Friday evening our checkout API for a food delivery app started returning timeouts. Error rate went from under 0.1% to 18% within ten minutes.
Task
I was on call. I needed to restore checkout first and then find out why it happened.
Action
Dashboards showed the Postgres connection pool exhausted. A deploy two hours earlier had added a call to a loyalty service inside a database transaction, so connections were held while waiting on a slow external API. I rolled back the deploy, which brought errors down in four minutes, then moved the loyalty call outside the transaction with a timeout and a fallback.
Result
Checkout was fully back 14 minutes after the alert. In the postmortem we added a lint rule against network calls inside transactions and an alert on pool usage above 80%. The pattern did not recur.

Why it works

The weak answer is vague about cause and role. The strong one shows calm triage, rollback before debugging, a precise root cause and prevention. All numbers are illustrative: use your own.

How a practice session works

  1. 01

    Pick a stage, paste the job posting

    Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.

  2. 02

    Talk it through by voice

    The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.

  3. 03

    Get the review and drills

    A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.

Rehearse this interview by voice

Related roles