Interview Questions for a Full Stack Developer
To interview a full stack developer, test both client and server competence plus the seam between them: API design, state management, authentication flow, and database modeling. This set probes how a candidate moves a feature end to end, where they place logic, and how they reason about contracts between frontend and backend.
Last updated
Structure a full stack interview around a single feature traced from UI to database, so you can see how the candidate connects layers rather than treating frontend and backend in isolation. Score breadth plus enough depth in at least one layer.
Technical & Role-Specific
What to look for: Coherent flow across request, validation, persistence, and response; clear ownership of error handling and loading states at each layer.
What to look for: Agreeing on a schema or OpenAPI spec first, mocking endpoints, versioning, and treating the contract as the source of truth.
What to look for: Knows client validation is UX only and the server is the trust boundary, never relying on the client for security.
What to look for: Understands tokens vs cookies, httpOnly and SameSite, refresh flows, CSRF, and where secrets live.
What to look for: Inspects query logs or an ORM profiler, uses eager loading or a join or batching, and verifies the count dropped.
What to look for: Shared types, codegen from the schema, or end-to-end typing; awareness that JSON over the wire is untyped.
What to look for: Updates local state immediately, reconciles with the server response, and handles the error path cleanly without leaving stale UI.
What to look for: Separates concerns into a service or domain layer, keeps controllers and components thin, and makes logic testable independent of the framework.
Behavioral
What to look for: Honest self-assessment, deliberate skill-building, and knowing when to pull in a specialist.
What to look for: Recognizes the contract gap, improves the handoff, and adds a test or schema check to prevent recurrence.
What to look for: Ownership end to end, realistic account of the integration pain, and pragmatic scoping.
What to look for: Reasons about trust, performance, data sensitivity, and duplication, placing security-critical logic server-side by default.
Situational / Problem-Solving
What to look for: Measures each layer with browser devtools, server timing, and DB logs before guessing, then fixes the proven bottleneck.
What to look for: Migration, API change, type updates, UI, and tests sequenced sanely, with backward compatibility considered.
What to look for: Weighs polling, SSE, and WebSockets against complexity and scale, and picks the simplest sufficient option.
What to look for: Versions the endpoint or adds the field additively, supports both shapes during transition, and coordinates the client cutover.
Full Stack Developer interview scorecard
Score every candidate on the same criteria, immediately after the interview, using evidence you actually heard rather than an overall impression. Agree the criteria with the panel before the first interview — deciding what counts after you have met people is how the loudest interviewer wins the debrief.
| Criterion | Evidence to record | Score 1-5 |
|---|---|---|
| Technical & Role-Specific | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Behavioral | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Situational / Problem-Solving | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Overall recommendation | Strong no / no / mixed / yes / strong yes, with the single reason that decided it | - |
Want this as a reusable document? Use the interview scorecard template.
Questions to avoid asking a Full Stack Developer
Exactly which questions are unlawful depends on where you are hiring, and the rules change — so treat this as the list of topics to route through your own employment counsel, not as a legal standard. The practical test that holds everywhere: if the answer could not change how the person does this job, you have no reason to ask it.
Recruiting terms explained
Related roles to hire
Frequently asked questions
How many interview rounds for a Full Stack Developer?
Should a full stack developer be equally strong on both sides?
What separates a full stack developer from a frontend or backend specialist?
Do I need a live coding round for this role?
Run these interviews structured, and compare candidates fairly
Pitch N Hire is an applicant tracking system with built-in interview scorecards. Load these questions into a scorecard so every interviewer assesses the same criteria and you can compare candidates side by side.
Free for 1 user · No credit card · Talk to a real hiring expert
See how much faster your team could hire
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
