Data science interviews probe three layers — statistics, machine learning, and product sense — and you have to be defensible on all three. Practice the questions Tashkent fintechs and remote EU employers actually ask, with real-time AI scoring on communication, technical depth, problem-solving, and cultural fit.
Data scientist roles in Tashkent are concentrated at fintechs (Click, Uzum, Payme), e-commerce (Uzum Market), and a small but growing set of EU remote employers hiring for experimentation platforms. The interview format is consistent: SQL screen, statistics and ML round, a product-sense case study (“our DAU dropped 12% — what do you do?”), and a behavioral round.
The questions below are pulled from real Tashkent interviews. Practice them out loud in the language your real interview will be in.
Approximate. Remote-first European roles typically pay 30–50% above local rates.
Junior
10–15M UZS / month
Mid-level
20–30M UZS / month
Senior
38M+ UZS / month (or EUR remote)
Pulled from real interviews recorded on NextSuhbat. Each item is a question you should expect, plus what the interviewer is really testing.
Recruiter screen
Why it is asked: Tests product impact. Lead with the decision that changed, not the model architecture.
Technical
Why it is asked: Communication test. If you say "probability the null hypothesis is true," you fail. Be precise.
Technical
Why it is asked: Tests whether you reach for power calculations and effect-size practical significance, not just the p-threshold.
Technical
Why it is asked: Bar for any ML role. The example matters more than the definition.
Technical
Why it is asked: Interpretability, sample size, regulatory constraints, deployment cost. Have a real opinion.
Coding
Why it is asked: EDA, leakage check, baseline, validation strategy, deployment, monitoring. The flow matters more than the syntax.
Coding
Why it is asked: Window functions, date math, anti-joins. Real product-analytics task.
System design
Why it is asked: Cover segmentation (geography, platform, cohort), instrumentation issues, external events, weekend effect, and when to escalate.
Behavioral
Why it is asked: Specific gap between offline and online metrics. What you noticed, how you debugged, what you changed.
Behavioral
Why it is asked: Tests judgment and communication. Pick a real example. Avoid sounding like you always cave or always fight.
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 interviewBuilt in Tashkent for Central Asia. All practice sessions support English, Russian, and Uzbek voice.
Why Mock Interviews Matter for Uzbekistan's Tech Job Seekers in 2026
Tashkent's IT job market is shifting fast — outsourcing studios, IT Park residents, and remote-first foreign companies all interview differently. Here's why structured interview practice is now the single biggest lever for landing a junior or mid-level offer in Uzbekistan, and how to do it without burning out your network.
How to Answer Salary Expectations Questions in Uzbekistan and Central Asia
The salary question is the one candidates in Tashkent, Almaty, and across Central Asia lose the most money on — not because they ask for too much, but because they answer it before doing the research. A practical guide to what to say, what to avoid, and how to anchor a number that reflects the real 2026 market.
How to Pass a Tech Interview in English When It's Not Your First Language — A Tashkent Developer's Playbook
Most engineers in Tashkent know the technical answer but freeze when the interview switches to English. This guide breaks down the four hidden traps, the 50-phrase vocabulary that covers 80% of behavioral and system design rounds, and a 30-day plan to interview in English with the calm of a native speaker — without pretending to be one.