Skip to main content
βš›οΈ

Frontend Developer Interview Prep β€” for engineers in Tashkent and Central Asia

Practice the exact questions Tashkent's IT Park residents, EPAM Tashkent, Yandex.Uzbekistan, and remote-first European companies actually ask frontend candidates. Run a 20-minute AI mock interview in English, Russian, or Uzbek with real-time scoring on communication, technical depth, problem-solving, and cultural fit.

A frontend role in Tashkent in 2026 means one of three things: building product UI for a local company, joining an outsourcing studio that ships to US clients, or interviewing remote with a European startup. Each track filters for different signals, but the question bank converges on a small, predictable set. The candidates who get offers are not the ones who memorize answers β€” they are the ones who have rehearsed delivering them out loud, in the language the interview will be conducted in, until the words come without effort.

This page is a focused prep guide for that role: the questions that come up most, what each one is really testing, and a free way to practice them under real interview conditions.

Core skills tested

  • JavaScript fundamentals (closures, hoisting, event loop)
  • React or Vue + modern hooks / composition API
  • TypeScript at a daily-use level
  • CSS layout (flex, grid) + responsive design
  • Browser networking (fetch, CORS, caching)
  • Performance: Core Web Vitals, lazy-loading, code-splitting
  • Accessibility basics (semantic HTML, ARIA, keyboard nav)
  • Git workflow + reading other people's pull requests

Salary ranges in Tashkent (2026)

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

Junior

8–12M UZS / month

Mid-level

15–25M UZS / month

Senior

30M+ UZS / month (or EUR remote roles)

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 your most recent project.

    Why it is asked: Communication test. Two minutes max β€” user problem, your role, the choice you are most proud of, the metric that improved.

  2. 2

    Technical

    Explain the difference between let, const, and var.

    Why it is asked: Tests whether you can talk through hoisting and the temporal dead zone in your second language without losing your train of thought.

  3. 3

    Technical

    What is the event loop, and why does Promise.resolve().then(...) fire before setTimeout(0)?

    Why it is asked: Almost guaranteed in senior interviews. Strong answers cover call stack, macrotask queue, microtask queue.

  4. 4

    Technical

    What does useEffect with an empty dependency array do, and when would you use it?

    Why it is asked: Unavoidable on any React stack. Bonus points for cleanup function, StrictMode double-execution, and why fetching in useEffect is increasingly being replaced.

  5. 5

    Technical

    Walk me through what happens when a user types a URL into the browser.

    Why it is asked: The classic. Cover DNS, TCP, TLS, HTTP, parsing, CSSOM, render tree, layout, paint, composite. Do not skip TLS.

  6. 6

    Coding

    Build a typeahead search component with debounced input.

    Why it is asked: Tests debounce, controlled inputs, handling stale responses (the seventh keystroke comes back before the eighth β€” most miss this), accessibility.

  7. 7

    Coding

    Implement a function that flattens an arbitrarily nested array.

    Why it is asked: Tests recursion vs iteration, edge-case handling for non-array values.

  8. 8

    System design

    Design the frontend architecture for a Telegram-style messenger.

    Why it is asked: Real-time updates (WebSocket vs SSE), offline state, message ordering, what to render on the server vs client.

  9. 9

    Behavioral

    Tell me about a time you disagreed with a teammate about a technical decision.

    Why it is asked: Use situation-task-action-result. Pick a story where you were right but not righteous, or where you were wrong and learned something specific.

  10. 10

    Behavioral

    Tell me about a time something you shipped broke in production.

    Why it is asked: Wrong answer: "nothing I shipped has ever broken." Right answer: 90-second story with specific numbers and a concrete change you made afterwards.

Practice these questions out loud β€” for free

Reading is not practice. Run a 20-minute AI mock interview in English, Russian, or Uzbek and get a scorecard against communication, technical depth, problem-solving, and cultural fit.

Start free mock interview

Built in Tashkent for Central Asia. All practice sessions support English, Russian, and Uzbek voice.