Skip to main content
🤖

ML Engineer Interview Prep — modeling + production systems — for engineers in Tashkent and Central Asia

ML engineering interviews probe both modeling depth and production rigor — you have to convince the interviewer you can build a model AND deploy it. Practice the questions Tashkent fintechs and EU remote employers ask, with real-time AI scoring on communication, technical depth, problem-solving, and cultural fit.

ML engineering is the rarest of the roles on this site in Tashkent — and the best-compensated for that reason. Local fintechs are starting to hire (fraud, scoring, personalization), and EU remote employers pay 2x what they pay a local data scientist. The interview format reflects that: deep modeling questions, deep systems questions, and almost no patience for fluff.

The questions below are pulled from real interviews. Practice them out loud — most ML candidates lose offers because they cannot articulate why their model failed in the exact terms the interviewer wants.

Core skills tested

  • Classical ML: regression, gradient boosting, calibration
  • Deep learning fundamentals: backprop, optimizers, regularization
  • PyTorch (or TensorFlow) at production level
  • Feature engineering and feature stores
  • Model serving: batch vs real-time, latency budgets
  • Experimentation: offline metrics vs online metrics, A/B tests
  • Monitoring: data drift, model drift, prediction logging
  • Solid Python + SQL fundamentals

Salary ranges in Tashkent (2026)

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

Junior

12–18M UZS / month

Mid-level

25–38M UZS / month

Senior

45M+ UZS / month (or EUR remote, often double local rate)

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 the most complex model you have shipped to production.

    Why it is asked: Two minutes. The user-facing decision, the modeling choice, the deployment shape, the metric that moved.

  2. 2

    Technical

    Walk me through gradient descent and explain why we use mini-batches in practice.

    Why it is asked: Bar for any DL role. Cover memory, noise as regularization, and parallelism on GPUs.

  3. 3

    Technical

    Explain the difference between L1 and L2 regularization with one concrete example.

    Why it is asked: Sparsity vs smoothness. Tie L1 to feature selection and L2 to coefficient stability.

  4. 4

    Technical

    How do you detect data drift in production?

    Why it is asked: Tests practical MLOps. Cover PSI, KS test, prediction-distribution monitoring, and the action threshold.

  5. 5

    Technical

    You ship a fraud model. The recall on the new fraud pattern is 12%. What do you do?

    Why it is asked: Practical question. Cover error analysis, label quality, feature gaps, retraining cadence, and a non-ML hotfix in parallel.

  6. 6

    Coding

    Implement softmax in PyTorch by hand.

    Why it is asked: Tests numerical-stability awareness. Subtract the max before exp, or you fail with overflow.

  7. 7

    Coding

    Write a function that computes per-class precision and recall from y_true and y_pred without using sklearn.

    Why it is asked: Bar for any ML role. The math should be muscle memory.

  8. 8

    System design

    Design a recommendation system for a marketplace with 5M items and 50ms p99 serving budget.

    Why it is asked: Cover candidate generation, ranking, embedding store, cold start, and the offline-online evaluation pipeline.

  9. 9

    Behavioral

    Tell me about a model that performed great offline and badly in production.

    Why it is asked: Specific story. Distribution shift, feedback loops, label leakage are all valid root causes.

  10. 10

    Behavioral

    How do you decide whether a problem needs ML at all?

    Why it is asked: Tests judgment. Strong answers cite when a heuristic, a SQL rule, or a config switch is enough.

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.