Business Analyst in IT — CIS and Europe market

The median Business Analyst salary is $1956/mo per Zorky CRM data (108 active jobs). Junior —, Middle $1630/mo, Senior $2146/mo, Lead $1956/mo. Real 2026 bands: Junior BA at Russian companies — $800-1,400/mo, Middle — $1,600-3,000, Senior — $3,200-5,000, Lead BA — $4,500-7,000. At IT companies, fintech and enterprise the bands are higher than at non-IT. At international companies on full-remote a Senior BA — $4,000-7,500+. Salary is influenced by domain expertise (fintech, e-commerce, logistics), proximity to the technical side (a BA who understands API and architecture is valued higher), and the skill of working on complex multi-stakeholder projects.

Business Analyst salary ladder (median USD/mo): Junior —, Middle $1630/mo, Senior $2146/mo, Lead $1956/mo. Junior BA gathers requirements and maintains documentation under mentorship. Jump to Middle — independent work with stakeholders, confident process modelling (BPMN), requirements management on a project. Senior leads complex multi-stakeholder projects, builds methodology, mentors. Career flow: Business Analyst → Senior BA → Lead BA, or transition to Systems Analyst (if drawn to the technical side), to Product Owner / Product Manager (if drawn to product), to Project Manager.

Moscow: Junior BA — $800-1,400/mo, Middle — $1,600-3,000, Senior — $3,200-5,000 (at IT companies and fintech higher). St Petersburg — similar bands. Minsk / Kyiv — 10-25% below Moscow. Poland — €2,500-5,000 gross. 25.6% remote: BA work (interviews, modelling, documentation, calls) is done well at a distance. International companies hire Russian-speaking Senior BAs on full-remote — $4,000-7,500/mo (English required for the international market — BA is a communication role). Russian regions — base lower, but the role is often remote, which opens access to capital and international bands.

Top 5: go, 1с, bpmn, sql, confluence. Process modelling: BPMN — the key notation for describing business processes, UML — diagrams (use case, activity); tools — Camunda Modeler, Bizagi, draw.io, Visio. Documentation and tasks: Confluence (knowledge base, requirements), Jira (tasks, backlog). Collaboration: Miro (workshops, diagrams), Figma (review of mockups and prototypes). Data: basic SQL — a growing requirement (to verify data, understand table structure). Methodology: BABOK (Business Analysis Body of Knowledge from IIBA), requirement elicitation techniques (interviews, workshops, observation), user stories and use cases, gap analysis, prioritisation (MoSCoW etc.), Agile / Scrum and waterfall model. Understanding of technology: at a basic level — what is an API, integrations, architecture (the better the BA understands the technical side, the more valuable). Skills: communication and facilitation (the main thing — elicit and align requirements among different stakeholders), systems thinking, analytical mindset, clear writing, conflict-of-interest management, attention to detail. English — for international projects.

Three roles are often confused, especially in Russia. Business Analyst answers the question "what and why": works from the business side — elicits the need, describes business processes and requirements, formalises what needs to be done and what problem it solves. Systems Analyst answers "how, technically": takes requirements and designs the technical solution — specifications, API contracts, integrations, data model; closer to development (see /research/analyst/systems-analyst). In Russia this distinction is especially noticeable: in enterprise and banks BA and SA are different roles; in small teams one person often combines them ("business-systems analyst"). Product Manager is responsible for the product and its overall success: strategy, what to build and why from the market and user perspective, priorities, product metrics, accountability for outcome; BA — about requirements within a given direction, PM — about which direction to choose at all (see /research/pm). Nearby — Product Owner (a Scrum role — manages the backlog, closer to BA with a product lean) and Project Manager (responsible for timelines, resources, project risks, not the content of requirements). Career flow: BA → Systems Analyst, or BA → Product Owner → Product Manager — both forks are common.

A Business Analyst's work is the requirements lifecycle. 1) Elicitation — gather needs: stakeholder interviews, workshops, study of current processes and documents, observation of user work. 2) Analysis — figure out which real problem needs to be solved (not just write down "wishlist items"), identify contradictions between stakeholders, assess feasibility, find gaps (gap analysis between "as is" and "to be"). 3) Modelling — describe business processes (BPMN), draw interaction diagrams, visualise "as is" and "to be". 4) Documentation — formalise requirements so the team understands unambiguously: user stories with acceptance criteria, use cases, business requirements, with waterfall — specs. 5) Prioritisation and alignment — set priorities (MoSCoW etc.), align requirements with all sides, achieve shared understanding. 6) Development support — answer team questions during implementation, clarify details, manage requirement changes. 7) Acceptance — check that what's built matches the requirements. Key: BA is not a "secretary writing down wishlist items", but an analyst who digs to the real problem and translates it into a language understandable both to business and to the team. Methodological support — BABOK.

Yes, 25.6% of Business Analyst jobs are remote or hybrid. The main BA work — interviews and workshops with stakeholders, modelling, documentation, calls — is done well at a distance (Miro, video calls, Confluence). Nuance: for projects with many stakeholders and complex facilitation some companies prefer hybrid — some workshops are more effective in person; in the financial and government sectors there can be an office requirement. Russian IT companies, fintech and enterprise offer different formats. International companies hire Russian-speaking Senior BAs on full-remote. English for the international market is mandatory — business analysis is a 100% communication role, both interviews and requirements alignment happen in the project's language.

A Business Analyst does not need to code — this is not a developer role. Technical education is desirable but not mandatory: people successfully come into business analysis from very different fields. What really matters: 1) Analytical and systems thinking — ability to decompose complex things into parts, see connections, dig to the essence. 2) Strong communication — half of BA work is communication, facilitation, alignment. 3) Domain expertise — deep understanding of the subject area (finance, logistics, e-commerce, insurance) is often more valuable than technical background; that's why BA successfully attracts people from business subject areas. 4) Basic understanding of technology — not coding, but understanding what API, integrations, databases, architecture are at a high level; and this understanding is worth growing — the better the BA understands the technical side, the more valuable, and the easier to grow into a Systems Analyst. 5) Basic SQL — a growing requirement, worth learning. Bottom line: BA is a role accessible without a technical degree and without code, but requiring analytical thinking, communication, and constant growth of technical horizon.

At the top: Sber, Yandex, T-Bank. Business analysts are needed by almost everyone who commissions or develops software. Banks and fintech: Sber, T-Bank, Alfa-Bank, VTB, Gazprombank — the largest hirer of BA (many complex products and processes). Large IT and product companies: Yandex, VK, Ozon, Wildberries, Avito. IT integrators and outsourcing / product studios: Krok, Lanit, IBS, EPAM, Naumen etc. — a large pool of BA jobs. Telecom: MTS, Beeline, MegaFon, Rostelecom. Government sector and government digitalisation — many projects with business analysis. Industry, insurance, retail, logistics, edtech — everywhere processes are automated. International companies — hire Russian-speaking Senior BAs on full-remote. Demand is wide and sustained; Business Analyst is one of the most common analytical roles in Russia.

Business Analyst — a role accessible for entry, including from non-IT. Roadmap: 1) Understand the essence of the profession — what requirements are, the requirements lifecycle, the BA's role on the team; read about BABOK (Business Analysis Body of Knowledge from IIBA) — this is the methodological base. 2) Process modelling — master BPMN (key skill), UML basics; practice drawing "as is" and "to be" processes. 3) Requirements techniques — interviews, workshops, writing user stories with acceptance criteria, use cases, gap analysis, prioritisation. 4) Tools — Confluence, Jira, Miro, draw.io / Visio. 5) Basic SQL — master queries and understanding of data structure. 6) Technical horizon — figure out at a high level what API, integrations, client-server, databases are. 7) Agile / Scrum — understand how team work is organised. 8) Use your background — domain experience (banks, logistics, insurance) is a strong advantage, not a hindrance; BA often attracts people from subject areas, from support, from testing, from project roles. 9) Portfolio / pet project — describe a process and requirements for a clear task to show the skill. Resources: business analysis courses (Otus, ScrumTrek-style programmes, analytics schools), IIBA / BABOK materials, business analyst communities. Aim for Junior BA and internships, when you have a domain — for a role with a lean into a familiar industry.

108 active open Business Analyst positions in the Zorky CRM sample. The real market is wider: the role is named differently — "business analyst", "business-systems analyst", "requirements analyst", "BA", sometimes mixed with "systems analyst" and "product analyst"; exact-term search doesn't catch everything. Geography: 🇷🇺 Russia, EN, 🇧🇾 Belarus. Sources: hh.ru, Habr Career, getmatch, LinkedIn, Telegram (business and systems analyst communities, job channels). Business Analyst is one of the most common analytical professions in Russia, demand is wide and sustained (banks, IT integrators, product companies, government sector). NB: the Analyst / BI direction historically had difficulties with automatic job classification — the visible number may understate the real market.

A Senior Business Analyst leads complex projects and is responsible for requirements quality overall. Requirements elicitation: mastery of interviews and workshop facilitation, ability to get stakeholders talking, identify the real problem behind "wishlist items", work with conflicting interests of different sides. Analysis: systems thinking, gap analysis, feasibility and impact assessment, ability to see what's missing from requirements and anticipate problems. Modelling: confident BPMN / UML, design of target processes, not just description of current ones. Documentation: clear, unambiguous, testable requirements (user stories with acceptance criteria, use cases, specifications) — so business and team understand the same way. Requirements management: traceability, change management, versioning, project-level prioritisation. Technical horizon: understanding of API, integrations, architecture, data model, basic SQL — enough to speak with development in the same language and assess technical feasibility. Domain expertise: deep knowledge of the project's industry. Methodology: BABOK, flexibility between Agile and waterfall, ability to set up the analysis process on a project. Stakeholder management: work with customers and management, expectation management, argumentation. Communication: oral and written — the BA's main tool. Mentoring: development of Junior analysts, review of their work, team standards. English — for international projects. The main value of a Senior — turning blurry, contradictory business needs into clear, agreed, implementable requirements.

Data is collected automatically from 1000+ sources — Telegram job channels and job boards across CIS and Eastern Europe (HH, Habr Career, Djinni, DOU, NoFluffJobs, JustJoin.it, Pracuj.pl and others). Parsing runs 24/7, duplicates are filtered by description and URL, salary outliers are stripped. Detailed methodology — on the "How it works" page.