Engineering and IT · Interview questions

Full Stack Developer interview questions

These questions check whether a candidate can own a whole feature, from data model to screen to launch. Use the same questions with every candidate and score 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. Pick one feature you built across the whole stack. Walk me through it from the first conversation to the week after release.

    What it tests
    Shipping whole features end to end.
    A strong answer
    They cover the data model, the API, the interface and the release, and explain trade-offs at each layer. They also say how they checked customers were using it.
    Watch for
    Only ever describing one layer, with someone else doing the rest.
  2. Here is a brief: let customers invite teammates to their account by email. Split it into the smallest set of releases you would ship, and tell me what is in the first one.

    What it tests
    Scope to production quickly, work sample.
    A strong answer
    The first release covers sending an invite and accepting it, with one role. Resending, expiry rules and role choices come later. They name the tables, endpoints and screens needed.
    Watch for
    A single big release that includes every possible option.
  3. Tell me about a time a feature took much longer than planned. What happened and what do you do differently now?

    What it tests
    Delivery pace.
    A strong answer
    They name the real cause, such as unclear scope or a hidden data problem, without blaming others. They describe a concrete change, like shipping a thinner first version or checking data earlier.
    Watch for
    No change in approach after the delay.
  4. You are adding a discount code field to checkout. Where should the validation logic live, and why?

    What it tests
    Judgement about where logic belongs.
    A strong answer
    The server must validate the code and calculate the price, because the browser can be changed by the user. The interface can do quick checks for a better experience but is never trusted.
    Watch for
    Calculating the final price only in the browser.
  5. Show me, or describe, a pull request description you are proud of. What did you put in it and why?

    What it tests
    Spec, tests and changelog outcome.
    A strong answer
    It explains what changed and why, how to test it, edge cases and screenshots of the interface. It links to tests that cover the main paths.
    Watch for
    Descriptions that only say fixed stuff or link to a ticket.
  6. A customer says invoices show the wrong total, but only sometimes. You own the feature. How do you track it down?

    What it tests
    Debugging across the stack.
    A strong answer
    They collect examples, compare stored data with what the screen shows, and check the server calculation and any rounding or timezone logic. They add a test that reproduces the case before fixing it.
    Watch for
    Patching the display without checking whether the stored data is wrong.
  7. What have you done to make it easier for a new developer to get a project running on their machine?

    What it tests
    Local setup outcome.
    A strong answer
    They give concrete steps, such as a single start script, a seed data command and a setup guide they asked a new person to follow. They fixed the gaps that person found.
    Watch for
    Saying setup is easy if you already know the stack.
  8. After you release a feature, how do you find out whether it was worth building?

    What it tests
    Features used by real customers.
    A strong answer
    They agree a simple signal before release, such as how many accounts use it in the first month, and check it. They share the result with the product owner, even when usage is low.
    Watch for
    Treating the release as the end of the job.

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.

Full Stack 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.