Fullstack Developer Interview Prep — for engineers in Tashkent and Central Asia

Core skills tested

• JavaScript / TypeScript across both client and server
• A real backend framework (Next.js API routes, NestJS, Express, FastAPI, etc.)
• SQL fluency + at least one ORM (Prisma, TypeORM, SQLAlchemy)
• REST and basic GraphQL — when to use which
• Auth flows: cookie sessions, JWT, OAuth handoffs
• Deployment: at least one PaaS (Vercel, Railway, Render) end-to-end
• Reading and reviewing code outside your comfort zone
• Comfort drawing system diagrams during interviews

Salary ranges in Tashkent (2026)

Approximate. Remote-first European roles typically pay 30–50% above local rates.

What you will actually be asked

Pulled from real interviews recorded on NextSuhbat. Each item is a question you should expect, plus what the interviewer is really testing.

1. 1

   Recruiter screen

   Walk me through a feature you owned end-to-end — UI, API, and database.

   Why it is asked: Tests scope and communication. Two minutes — what the user did, the schema, the endpoint, the UI. Be specific.

2. 2

   Technical

   Where would you run authentication logic — client, edge, or server — and why?

   Why it is asked: Tests fullstack thinking. Strong answers cover token storage, refresh flow, and what each layer can and cannot trust.

3. 3

   Technical

   Explain server components vs client components in modern React frameworks.

   Why it is asked: Increasingly common at companies on Next.js. Bonus for the hydration mental model and when to use which.

4. 4

   Technical

   A user reports the app is slow. Walk me through how you would investigate.

   Why it is asked: Tests breadth. Cover network panel, server-side timing, DB query plan, frontend render, caching layer.

5. 5

   Technical

   How would you design optimistic UI for a comment-posting flow?

   Why it is asked: Tests how you reason about consistency between client and server when the network is unreliable.

6. 6

   Coding

   Build a /search endpoint and a UI typeahead that hits it, with debounce and cancel-on-stale.

   Why it is asked: Touches both layers. Tests debounce, AbortController, and a real backend handler with input validation.

7. 7

   Coding

   Implement a function that paginates a list of items by cursor, not offset.

   Why it is asked: Tests if you understand why offset pagination breaks at scale and how cursor-based works.

8. 8

   System design

   Design a notification system that delivers in-app, email, and push, with user-level preferences.

   Why it is asked: Touches DB schema, queues, fan-out, and per-channel rate limits. Cover preferences as a first-class concept.

9. 9

   Behavioral

   Tell me about a time you made the wrong technical call and had to undo it.

   Why it is asked: Pick a specific moment, not a vague theme. Mention the cost, what you noticed, and how you reversed it.

10. 10

    Behavioral

    Why fullstack and not specialize?

    Why it is asked: A real reason ("I want to ship features end-to-end") beats a defensive one. Avoid sounding like a backup plan.