Why this queue is worth knowing about
1C runs the finance and operations of an enormous share of businesses across Tajikistan, Uzbekistan and Kazakhstan. The work is unglamorous and extremely stable, and there are consistently fewer candidates per opening than for equivalent web development roles in the same cities.
It is also one of the few tracks here where deep local knowledge — tax rules, reporting formats, how a specific industry actually operates — is worth more than general programming ability.
Configuration versus code
The central judgement of the role, and the thing interviews probe hardest. Modifying a typical configuration makes updates painful forever; refusing to modify it makes the client's actual process impossible.
The client wants a field on a document that the standard configuration does not have. What do you do, and what do you tell them about updates?
The strong answer names the cost before the solution. Extensions where possible, modification where necessary, and an honest sentence about what the next update will require.
Exchange and integration
Almost every real deployment exchanges data with something — a bank, a warehouse system, a website, another 1C base. This is where most production problems live and therefore where interviews go.
- Exchange plans and how conflicts are resolved
- What happens when the other side is down mid-exchange
- Web services versus file exchange, and why you would choose the slower one
- Reconciliation — proving both sides agree afterwards
Reporting and the query language
Expect to be asked to build or fix a report. Query language fluency and the composition system are the practical core of the job.
- Query batches, temporary tables, and why the obvious join is slow
- Virtual tables for balances and turnover, and reading period boundaries right
- Report variants a user can change without calling you
- Rights and why a report must respect them
What interviewers here are really assessing
1C consultants sit between the accountant and the system, and the interview is as much about that position as about the platform.
- Can you talk to a chief accountant without either condescending or drowning
- Do you understand the business process, or only the document
- How do you handle a client who wants something that will break at year-end
- Can you leave the base maintainable by whoever comes after you
What to focus on at your level
Junior · 0–2 years
Typical configurations you can navigate, basic query language, and the ability to reproduce a user's problem accurately.
Mid · 2–5 years
Extensions and modifications with judgement, exchange you have debugged, and reports built from a vague request.
Senior · 5+ years
Architecture across several bases, migration and update strategy, and the standing to tell a client no.
Open 1C 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
Is 1C a career dead end?
The demand in this region has been steady for years and the candidate pool is thin. It is narrower than web development, and paid comparably or better at senior level for exactly that reason.
Do I need accounting knowledge?
Enough to follow the conversation. Consultants who genuinely understand accounting are rare and are paid accordingly — it is the highest-return thing to study alongside the platform.
Russian or English?
Russian, almost without exception. The platform, its documentation and the client conversation all run in it.