Full stack interview questions that test end-to-end product ownership

Example output

Illustrative examples only — not real candidate achievements or testimonials.

• Frame — onboarding design: I would sketch the company-profile step in Next.js, the Node handler, and the Prisma fields in one pass, then measure step completion — not tickets on only one side.

  Next.js + Prisma · step completion target 52% → 78%

• Frame — stuck checkout: browser shows a 400; Node log shows a missing Postgres constraint. I ship the constraint and the React error map together on Vercel.

  Postgres + React · mutation errors −60% after paired fix

• Frame — search slow: waterfall of client fetches plus missing trigram index. Collapse into one TypeScript loader and add the index in the same change.

  TypeScript + Postgres · search wait 1.8s → 420ms

• Frame — GraphQL empty table: mutation and React error map rewritten together so operators see actionable copy instead of a blank grid.

  GraphQL + React · admin support tickets −44%

• Frame — design review: Vercel preview must run the same Prisma migrate so design reviews the shipped shape, not a mock that lies.

  Vercel + Prisma · zero preview-to-prod schema-drift incidents that quarter

• Frame — ownership conflict: if UI can ship without the schema, I say so and define the temporary empty state — I do not pretend the path is full stack when it is not.

  Node.js + React · activation +19% once both halves landed

Product-slice design across the glass

Expect a prompt like "design onboarding" or "fix checkout." Walk the click → handler → row → response → UI state loop. Name where shared TypeScript types live, how empty states match API errors, and which Prisma field actually gates progress.

Do not answer like a backend-only candidate who never mentions the screen. Do not answer like a frontend-only candidate who never mentions the schema.

Strong frames end with how you would measure the slice — activation or step completion — not cluster CPU.

Debugging a stuck user journey

They will ask about a production bug that spanned browser and server. Your frame should open the Next.js network panel and the Node log together, then show a paired fix: Vercel rollback or hotfix plus a Postgres constraint or Prisma migrate.

Avoid a Datadog-only service narrative with no UI. Avoid a CSS-only layout narrative with no API.

Practice saying what you checked first on each side and what you refused to guess.

Collaboration without throwing work over the wall

Full stack loops also probe how you work with design and product when the contract changes. Talk about preview environments on Vercel that show the same Prisma shape eng ships, and how you negotiate scope when UI and schema cannot land the same day.

These are not personality quizzes. They are ownership quizzes: who updates the type, who updates the copy, who owns the empty state.

Frequently asked questions