Skip to main content
11 min read

Frontend Developer Interview Questions Asked by Uzbek Tech Companies in 2026

We watched 200+ frontend interviews recorded on NextSuhbat over the last six months and pulled the questions that came up at least twice. The pattern is clearer than you might expect: most Uzbek tech employers — IT Park residents, EPAM Tashkent, Yandex.Uzbekistan, and the new wave of remote-first European startups hiring through TaskUs and Andela — gravitate toward the same twelve to fifteen questions. If you can answer these well, you will pass eighty percent of the phone screens for a junior or mid-level frontend role in Tashkent.

What companies are actually screening for

Frontend interviews in 2026 are not about memorizing the spec. Recruiters are filtering for three things, in this order: can you communicate clearly under pressure; do you have a real mental model of how the browser executes your code; and have you shipped something — anything — that survived contact with real users. The questions below all map back to one of those three signals.

Round 1 — phone screen / recruiter call (15 to 30 minutes)

  • “Walk me through your most recent project.” Almost every Tashkent screen opens with this. The recruiter is testing communication, not architecture. Two minutes max. Lead with the user problem, then your role, then the technical choice you are most proud of, then the metric that improved. Do not narrate every commit.
  • “Why are you leaving your current role?”Never criticize a manager. Frame the move as a pull (“I want to work on consumer-scale React”) not a push (“my team is disorganized”). IT Park employers especially screen for stability — a candidate who changes companies every six months is harder to sponsor for permits and harder to plan projects around.
  • “What is your salary expectation?”Anchor at a specific number, not a range. For a junior role in Tashkent expect 8–12 million so'm monthly; mid-level 15–25 million; senior with English 30 million and up. If you are interviewing remote for a European employer, quote in EUR and remember the offer will land 30–50% below their local rates.

Round 2 — technical screen (45 to 60 minutes)

  • “Explain the difference between let, const, and var.” Cliché but still asked, and a surprising number of candidates fumble it. The interviewer is not testing whether you know var is function-scoped — they are testing whether you can explain hoisting and the temporal dead zone in your second language without getting lost mid-sentence.
  • “What is the event loop?” Almost guaranteed in a senior interview, common in mid-level. Strong answers cover the call stack, the macrotask queue, the microtask queue, and at least one practical consequence — for example, why Promise.resolve().then(...) fires before a setTimeout(0).
  • “What does useEffect with an empty dependency array do, and when would you use it?”React-specific but unavoidable in any company using Next.js or a React-based stack. Bonus points for mentioning the cleanup function, double-execution in StrictMode during development, and why “data fetching in useEffect” is increasingly being replaced by Server Components or library-level fetchers.
  • “How does this behave in arrow functions versus regular functions?”The question is really “do you understand lexical scope?” A clear answer with one concrete example beats three sentences of theory.
  • “Walk me through what happens when a user types a URL into the browser.” The classic. Cover DNS, TCP handshake, TLS, HTTP request, server response, HTML parsing, CSSOM, render tree, layout, paint, composite. Do not skip TLS — half of candidates do, and that is exactly the gap a senior frontend role expects you to close.

Round 3 — coding / pair-programming (60 to 90 minutes)

For frontend roles the coding round usually lands in one of two formats: a small DOM manipulation challenge (build a tabs component, debounce an input, infinite scroll) or an algorithmic problem at the easy-to-medium LeetCode level. Companies hiring for product roles tend to prefer the DOM challenge. Outsourcing studios serving US clients tend to prefer the algorithm.

  • Build a typeahead search component. Tests debounce, controlled inputs, handling stale responses (the seventh keystroke comes back before the eighth — most candidates miss this), and basic accessibility.
  • Implement a function that flattens a nested array. Asks if you can write a recursive solution and an iterative one, and whether you handle non-array values gracefully.
  • Build a star-rating component. Looks easy. Surfaces whether you understand event delegation, hover states, and how to keep the click handler decoupled from rendering.

Round 4 — system design (only for mid and senior)

  • “Design the front-end architecture for a Telegram-style messenger.” The interviewer wants to see how you think about real-time updates (WebSocket vs SSE), offline state, message ordering, and what to render server-side versus client-side.
  • “How would you build an infinite-scroll feed that performs on a low-end Android device?” Almost always asked at companies serving Central Asia or South Asia. Cover virtualization, image lazy-loading, request batching, and the difference between offset-based and cursor-based pagination.

Round 5 — behavioral / culture fit

  • “Tell me about a time you disagreed with a teammate about a technical decision.” Use the situation-task-action-result frame. Pick a story where you were right, but not righteous; or where you turned out to be wrong and learned something specific.
  • “Tell me about a time something you shipped broke in production.”The wrong answer is “nothing I shipped has ever broken.” The right answer is a 90-second story with specific numbers (what percent of users, how long, what the root cause was) and a concrete change you made afterwards.
  • “Why do you want to work here specifically?”One sentence about the company, one sentence about a specific product or technical detail you have noticed, one sentence about how you would contribute. Generic answers — “great culture,” “learning opportunity” — get filed under polite-rejection.

Common patterns that kill otherwise good candidates

We see four failure modes again and again in NextSuhbat scorecards, and all four are fixable:

  • Filler words in the second language.A candidate who says “uh” or “ya'ni” once a sentence in English signals nervousness even when their technical answer is strong. Recording yourself once is usually enough to fix it.
  • Premature optimization talk. Mentioning Big-O on a question that does not require it makes you sound junior, not senior. Solve the problem first, talk about complexity only if asked or if there is an obvious tradeoff.
  • Apologizing for not knowing.“Sorry, I don't know” ends the conversation. “I have not used X directly, but based on Y I would expect Z” keeps it alive and shows reasoning.
  • Not asking any questions at the end. Every Tashkent recruiter we have spoken to flagged this as the single most common reason a strong candidate gets passed over. Have three questions ready. They should be specific to that company, not generic.

How to practice the right way

Reading this list is not practice. The questions land differently when an interviewer is actually waiting for your answer and the silence is on you. Run at least five end-to-end mock interviews before your first real one — out loud, under time pressure, in the language you expect to interview in. NextSuhbat is built exactly for this; a free first session takes about twenty minutes and gives you a scorecard against communication, technical depth, problem-solving, and cultural fit. Use it, use a friend, use a senior engineer if you can find one. The mode does not matter. The reps do.

Final note for Tashkent candidates

English fluency is now the single biggest salary differentiator in Tashkent. A junior developer who can interview comfortably in English makes 40–60% more than the same engineer who only interviews in Russian, because they unlock the entire remote-first European market. If your technical answers are solid in Russian or Uzbek but freeze when you switch to English, that is the highest-leverage thing to fix. It is also the thing AI mock interviews do best — practicing the same answer ten times in a row in a second language without embarrassing yourself in front of a real person.