Backend Developer Interview Questions in Uzbekistan: What Tashkent Companies Actually Ask in 2026

We watch hundreds of backend mock interviews a month, and the pattern is stable: Tashkent candidates fail the same eight questions, and they are rarely the exotic ones. Local fintechs — the banks, the payment apps, the e-commerce platforms — care about databases under load. Remote-first foreign employers care about algorithms and communication in English. Below is what both actually ask, and what a strong answer contains.

Databases: where local interviews are won and lost

Payment companies live and die by their databases, and their interviews show it. Expect these — and expect follow-ups when your answer is textbook-shallow:

• “What actually happens when you add an index?” — they want write-cost trade-offs and when an index is not used, not the definition of a B-tree.
• “Two users pay from the same balance at the same moment. Walk me through it.” — isolation levels, row locking, idempotency keys. This is the signature Tashkent fintech question.
• “When would you deliberately denormalize?” — read-heavy reporting, caching layers, and knowing what consistency you gave up.

APIs and services: the middle of every loop

• “Design the API for a taxi order.” — resource modeling, status transitions, what returns 409 versus 422, versioning.
• “REST or gRPC here — and why?” — they are checking if you choose by context (public vs. internal, browser vs. service mesh) or by fashion.
• “The endpoint got slow. What do you do first?” — the interviewer wants a method: measure, profile, find the N+1, check the pool, only then touch the cache. Guessing at answers here is the most common failure we see.

Concurrency and infrastructure

Mid-level and up, every loop probes whether you have run something in production. The recurring questions: what a message queue buys you over an HTTP call (and what it costs), how you would make a payment webhook idempotent, what happens when Redis goes down and your cache empties into the database, and — increasingly, even locally — what is actually inside the Docker image you deploy. You do not need Kubernetes war stories for a mid role. You do need to never say “the queue just handles it.”

The two-worlds problem: stack and language

Local product companies and studios still lean Java, .NET, and PHP; remote-first employers interview almost exclusively in Go, Python, and Node.js. The questions above survive the stack divide — transactions are transactions — but the languagedivide is real. An export-oriented IT Park resident will run at least one round in English, and “I understand but cannot explain indexes in English” fails exactly like not knowing indexes. If English rounds scare you, rehearse the eight questions above in English specifically; the vocabulary is small and learnable in a week.

How to prepare in two weeks

Pick the five questions from this article that scare you most and answer them out loud, daily, until the answers bore you. Then pressure-test: a twenty-minute backend mock interview with follow-ups will show whether your indexing answer survives a second “why?” — which is precisely where real Tashkent interviews are decided. Do one mock in your interview language per day for a week and the real loop will feel like a repeat.