Full Stack Developer Interview Questions

Prepare for your full stack developer interview with 10 expert-curated questions and sample answers covering frontend, backend, databases, and delivery.

behavioral Questions

Tell me about a feature you owned from idea to production. What would you do differently?

behavioralintermediate

Sample Answer

I owned our self-serve onboarding flow: Next.js wizard, Node APIs, Stripe integration, and the schema beneath it. It lifted activation 24%. What I'd change: I built all five steps before shipping any — releasing step one alone behind a flag would have surfaced two weeks earlier that users stalled on the data-import step, which became the real project. I now ship the smallest observable slice first.

Tip: The 'what would you change' half is the actual question — have genuine reflection ready.

What part of the stack are you strongest in, and how do you handle the parts you're weaker on?

behavioralbeginner

Sample Answer

I'm backend-leaning — schemas, APIs, and data flows are where I add the most. On deep frontend work like animation performance or intricate CSS, I know enough to be productive and crucially when to pull in a specialist or invest learning time. I'd rather give you an honest map of my coverage than claim a uniform 50/50 that doesn't exist in anyone.

Tip: Honesty here builds trust — interviewers know 'equally expert at everything' is fiction.

technical Questions

Walk me through what happens when a user submits a form in your app, end to end.

technicalbeginner

Sample Answer

Client-side validation gives instant feedback, then the form submits — ideally with optimistic UI. The request hits the API where the real validation happens (never trust the client), the handler authorizes the user, writes within a transaction, and returns a typed response. The client updates its cache — with TanStack Query, invalidating the affected queries — and the UI reflects truth. Errors at each layer surface as field-level messages, not toasts saying 'something went wrong'.

Tip: This question tests whether you genuinely think across the stack — rehearse it as one fluid story.

How do you decide what logic lives on the client versus the server?

technicalintermediate

Sample Answer

Security and integrity logic always lives server-side: authorization, pricing, validation that matters. The client gets duplication of validation for UX speed, presentation logic, and interaction state. Anything involving secrets, money, or other users' data never trusts the browser. With server components and actions blurring the line, my rule stays the same — the server is the source of truth, the client is a fast view of it.

Tip: 'Client validation is UX, server validation is security' is the crisp line interviewers want.

Design the data model for a multi-tenant SaaS application.

technicaladvanced

Sample Answer

For most SaaS scale, a shared database with a tenant_id column on every table is right — simplest operations, easiest cross-tenant analytics. I'd enforce isolation in depth: tenant_id in every query via the ORM layer, row-level security in Postgres as a safety net, and composite indexes leading with tenant_id. Schema-per-tenant or database-per-tenant only becomes worth the operational cost for compliance-heavy or wildly unequal tenants.

Tip: Mention row-level security as defense-in-depth — the single-missing-WHERE-clause disaster is the known risk.

How do you keep TypeScript types in sync between your frontend and backend?

technicalintermediate

Sample Answer

Single source of truth, generated outward: either a shared package of Zod schemas that validate at runtime and infer static types, tRPC for end-to-end inference in monorepos, or OpenAPI-generated clients when the API serves external consumers too. Hand-maintained duplicate interfaces drift within weeks — the moment types are written twice, they're already wrong somewhere.

Tip: Naming Zod/tRPC/OpenAPI codegen shows you've solved this in practice, not just felt the pain.

How do you approach authentication and session management in a web app?

technicalintermediate

Sample Answer

I default to a proven library or service — NextAuth, Auth0 — over hand-rolling. Sessions live in httpOnly, secure, sameSite cookies rather than localStorage, which XSS can read. Short-lived access tokens with refresh rotation, CSRF protection on mutations, and rate limiting on auth endpoints. The principle: authentication is a solved problem where creativity is a liability.

Tip: 'httpOnly cookies, not localStorage' is the security litmus test embedded in this question.

How do you test a full stack feature?

technicalbeginner

Sample Answer

Unit tests for business logic on both sides, integration tests for API endpoints against a real test database, component tests for UI behavior with Testing Library, and a few end-to-end Playwright tests covering the critical journey. The distribution matters: heavy E2E suites get slow and flaky, so I push coverage down the pyramid and keep E2E for what genuinely needs a browser.

Tip: Show you test the API contract layer — full stack candidates often only describe UI tests.

situational Questions

Your page makes 14 API calls on load. How do you fix it?

situationalintermediate

Sample Answer

First measure which calls block rendering versus which can defer. Then consolidate: a backend-for-frontend endpoint or GraphQL layer that aggregates what the page needs in one round trip, parallelize what remains, cache stable data with proper headers, and lazy-load below-the-fold data. Often half the calls serve data the page doesn't even display — deleting is the best optimization.

Tip: The BFF/aggregation pattern is the expected centerpiece; 'delete unused calls' shows pragmatism.

A stakeholder wants a feature in two weeks that you estimate at six. What do you do?

situationalbeginner

Sample Answer

I find out what the two weeks is really about — usually a demo, a customer commitment, or a launch event. Then I scope to that need: which thinnest slice delivers the moment? Often a polished happy path with manual fallbacks behind the scenes serves the demo, while the full build continues honestly. What I won't do is silently compress quality — cut scope visibly, never corners invisibly.

Tip: 'Negotiate scope, not quality' with a concrete slicing example is the mature answer.

Preparation Tips

1

Prepare one end-to-end feature story you can narrate across UI, API, database, and deployment.

2

Practice both a frontend exercise (build a component) and a backend one (design an endpoint) — loops test both.

3

Be fluent in your data layer: schema design and a few non-trivial SQL queries from memory.

4

Review auth fundamentals — session vs. token, cookie security — it appears in most full stack loops.

5

Know your deployment story: how your code gets from laptop to production, including CI and rollback.

Practice Full Stack Developer Interview Questions

Get AI-powered feedback on your answers and ace your next interview.

Start Interview Prep

Related Interview Questions

Frontend Developer

Prepare for your frontend developer interview with 10 expert-curated questions and sample answers covering React, performance, CSS, and behavioral topics.

Backend Developer

Prepare for your backend developer interview with 10 expert-curated questions and sample answers covering APIs, databases, system design, and behavioral topics.

Software Engineer

Prepare for your software engineer interview with 10 expert-curated questions and sample answers covering coding, system design, and behavioral topics.