Since 2021 we have been assembling engineers for specific tasks, not for "vacancies in general". One month you reinforce a bank's team on the client side; the next project is full-cycle development of a platform for a telecom operator inside the SOWA team. Below: how the work is organised, which areas we recruit for regularly, and how hiring runs.
We don't promise a "friendly team" instead of a substantive answer about what you will actually do. Here is what you can verify in practice in your first month.
Banking, telecom, development — systems with real load, production incidents and security requirements, not test tasks for an internal portfolio. Across 30+ projects we have never sent an engineer to write CRUD "for practice".
Some roles mean embedding into the client's team under the outstaffing model: you work in their processes, stand-ups and Jira. Others are outsourcing projects where the team is entirely on SOWA's side and we own the result end to end.
ISO 27001 and NDA-first are not only for banking clients. For you it means a clear scope of responsibility, a well-run project onboarding, and no "figure it out yourself" situations when working with sensitive data.
98% of clients stay with us for repeat work, which means engineers move between domains instead of getting stuck on one stack. Six months on a banking backend with high fault-tolerance requirements broadens expertise faster than a year on a single internal product.
This is not a list of open positions with a fixed number of seats today — these are the areas where SOWA consistently looks for engineers for current and new projects. If your stack and level match, apply: we'll discuss the specific project at the interview.
Projects at the level of banking core backends and payment services — high load, strict SLAs, working in the client's team or as part of a dedicated SOWA team.
Backend and integration services for telecom platforms — queues, billing APIs, integration with external operator systems.
Internal platforms for development companies: property records, sales CRM, integration with accounting and BI systems.
Customer interfaces and self-service portals for projects across industries — from banking mobile web to operator dashboards.
Manual and automated testing for systems with high fault-tolerance requirements — regression, load testing, release test plans.
CI/CD, infrastructure and monitoring for projects with security and availability requirements — from banking environments to telecom billing.
Four steps without extra loops — from application to project start usually takes one to two weeks.
You send your CV and the stack you have worked with. We reply within 1–2 business days, even if there is no matching project right now.
A conversation with a SOWA engineer about your experience, real tasks and architectural decisions — no abstract guessing games.
Depending on the role and project — a compact test assignment in your stack or a live-coding session close to real work tasks.
We discuss the working format, the project and terms, sign the NDA and contract, and set the start and onboarding date.
It depends on the role and project: some positions (embedded banking teams, for example) require presence in the Tashkent office or a hybrid schedule due to the client's security requirements; others are fully remote. We clarify the format at the interview stage for each specific role.
The project is matched to your stack, level and experience at the technical interview stage — it may be embedding into a client's team (outstaffing) or working in a full SOWA project team (outsourcing). We are open about this before the offer, not after.
From application to offer usually takes one to two weeks — it depends on the current load in that area and your availability for the interview and test assignment.
Our hiring focus shifts with our projects. Send your CV to info@sowa.uz or through the contacts page — if your stack and level fit, we will get in touch even if there is no open position for your profile right now.
Send your CV