Where backend interviews here actually go
Almost none of the backend loops in this market are algorithm gauntlets. The companies hiring are small enough that the person interviewing you will also be reviewing your pull requests, so they interview for the thing they need on Monday: can you take a vague requirement, model it, expose it, and keep it fast when the data grows.
Expect three rounds. A conversation about your last system, a practical or take-home task, and a session with whoever owns the codebase. The middle round is where offers are won and lost.
API design and data modelling
You will be asked to design something small and concrete — an orders endpoint, a booking flow, a notification queue. The interviewer is not looking for the perfect schema. They are listening for whether you ask what the data is for before you draw it.
Design the API for a delivery service. What are your endpoints, and what does a failed delivery look like in your data model?
Say the trade-off out loud. If you denormalise, name what you are buying and what you are giving up. Silence here reads as not having considered it.
- Resource naming and what belongs in a path versus a query
- Idempotency — what happens when the client retries
- Pagination that survives inserts, not just OFFSET
- Where validation lives, and what the caller sees when it fails
The slow query question
This one comes up in almost every backend loop in the region, and it is the single best-rewarded thing to prepare. The question is rarely phrased as a puzzle — it is phrased as a story about a page that got slow.
A report page took 200ms last month and takes 9 seconds now. Nothing in the code changed. Walk me through what you do.
A strong answer starts by measuring, not guessing. Say you would look at the query plan first. Then talk about what you expect to find: a missing index, a join that fans out, a N+1 that only shows up once the table is big enough.
Candidates who jump straight to "add an index" lose ground. Candidates who say "first I would find out which query" gain it.
Language depth: Python, Go, Node and PHP
All four are live in this market. Go and Python dominate new services; PHP is everywhere in existing systems and is not going anywhere. Whichever you claim, expect one round of genuine depth in it.
What gets asked per language
- Python — the GIL and what it does not stop, generators, where async actually helps and where it does not
- Go — goroutines and leaks, channels versus mutexes, why the error return is a design choice and not an inconvenience
- Node — the event loop, what blocks it, and how you would find out that something is
- PHP — request lifecycle, opcache, and how the framework you name actually boots
What interviewers here are really assessing
Teams in Central Asia are small. A backend hire is often the second or third engineer on a service, which means the interview is quietly checking whether you can be left alone with a problem.
- Do you ask about the requirement before you code against it
- Can you explain a decision to someone who is not an engineer
- What do you do when you do not know — guess, or say so and reason
- Have you ever operated what you built, or only shipped it
The last one carries real weight. An incident you handled badly and learned from interviews better than a system you built and never watched run.
What to focus on at your level
Junior · 0–2 years
One language properly, SQL you can write without a reference, and a project you can explain end to end. Nobody expects architecture.
Mid · 2–5 years
The slow-query answer, API design under discussion, and one production incident you can narrate honestly.
Senior · 5+ years
Trade-offs by default, a position on where complexity should live, and evidence you have made a call that turned out wrong and been fine about it.
Open Backend 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
Do I need to grind algorithm puzzles for these roles?
For most companies here, no. Practical rounds and system conversations decide the outcome far more often. A handful of larger employers and outsourcing firms do use algorithm screens, so ask the recruiter what the format is — that question is welcomed, not penalised.
How much does the framework I know matter?
Less than the reason you chose it. Being fluent in one framework and able to say what it does for you beats naming four.
Отвечать по-русски или по-английски?
Answer in whichever you think faster in, and say so at the start. Most technical interviews in the region run in Russian; the written task is often in English.