The shape of a frontend loop here
React dominates new work in this market, with Vue holding a strong second place in Uzbekistan and Kazakhstan in particular. Expect a component task, a conversation about state, and — increasingly — a question about accessibility that would not have been asked two years ago.
The practical round is usually take-home or pair-built rather than whiteboard. Whatever you build, the follow-up is the real interview: why this structure, what would you change under pressure.
State, and where you put it
The most common failure is not knowing a state library. It is not being able to say why state should live in one place rather than another.
You have a form spread across three components and a value two of them need. Where does it live, and why not somewhere else?
- Local state, lifted state, context, and when context becomes a re-render problem rather than a solution
- Server state versus client state — what a query cache actually solves
- Derived state and why storing it is usually a bug waiting to happen
Rendering and why the page feels slow
«Тормозит» — так вопрос обычно и звучит, и это не то же самое, что «медленно». Интервьюеры ждут, что вы разделите время загрузки и стоимость взаимодействия.
A list of 500 rows is janky when you type in the filter box. What is happening and what do you do about it?
Name the measurement before the fix. Say you would profile, look at what re-renders, and only then reach for memoisation or virtualisation. Reaching for the fix first is the answer juniors give.
Accessibility, now asked in earnest
This changed recently in the region, largely because companies started selling to European clients who ask for it in procurement. You no longer need to be an expert, but you do need to not be surprised by the question.
- Semantic elements before ARIA — a button that is a div is the classic finding
- Keyboard order, focus rings, and why removing the outline is a bug
- Labels that are attached to their inputs, not merely near them
- Colour contrast as a design constraint you can name
What interviewers here are really assessing
Frontend hires in small teams end up owning the browser end of everything — including the bits nobody wrote down.
- Can you turn a design into a structure without being handed a spec
- Do you know what your framework is doing, or only how to use it
- How do you behave when the API you were promised does not exist yet
- Can you say no to a design that will not work on a phone
What to focus on at your level
Junior · 0–2 years
One framework properly, semantic HTML, and a project you built that runs. Explaining your own code clearly counts for more than its size.
Mid · 2–5 years
State decisions you can justify, a performance problem you actually diagnosed, and comfort with the accessibility basics.
Senior · 5+ years
Component API design, a view on where the boundary with backend sits, and the ability to argue for less JavaScript when that is the right answer.
Open Frontend roles right now
Read from the live roles on Nebryx when this page loaded — not a list written into the page. If it is empty, nothing matching is open today.
Frequently asked questions
React or Vue — which should I learn for this market?
React opens more doors overall. Vue is genuinely strong in Tashkent and Almaty, and being the person who knows it well is a real advantage in a smaller pool.
Do I need TypeScript?
Increasingly yes for new roles, and it is the single fastest thing on this list to become credible in. You do not need advanced types; you need to stop reaching for any.
Is a portfolio site expected?
A working project with a README beats a portfolio site. Interviewers here open the repository, not the landing page.