Systems Analyst: market
Data as of November 19, 2026: 802 open Systems Analyst jobs, 29% remote among jobs that state a work format; median advertised salary $8,441/mo (from 156 postings that state a salary). Source: Zorky, updated daily.
Systems Analyst — specialist who translates business requirements into a technical solution: designs how exactly the system should work, describes APIs and integration contracts, data model, logic, and technical specifications by which developers write code. If a Business Analyst answers "what and why", the Systems Analyst answers "how to implement it technically" (see /research/analyst/business-analyst). Systems Analyst is one of the most in-demand analytical roles in CIS IT, especially in enterprise, banks, and large custom development: its specification becomes the assignment for the development team. Role family: Systems Analyst (general — specs, APIs, integrations, data model), Business-Systems Analyst (combines business and systems analysis — common format in small teams), Senior / Lead Systems Analyst (complex integration projects, architectural decisions, mentorship), adjacent career target — Solution / System Architect (see /research/architect). Area of responsibility: requirements analysis and their translation into technical ones; API design (REST, sometimes SOAP / gRPC) and system interaction contracts; description of integrations between services; data model design; logic and algorithm description; writing technical specifications; diagrams (UML — sequence, component; ER diagrams); support for development and testing. Stack / tools 2026: SQL (mandatory — work with data model, verification), REST API and HTTP understanding, OpenAPI / Swagger (API contract description), Postman (API verification), UML (sequence, component diagrams), BPMN, ER diagrams (data model), JSON / XML formats, message queues (Kafka, RabbitMQ — at understanding level), Confluence + Jira, diagram tools (draw.io, PlantUML, Visio), basic understanding of architecture (microservices, monolith, client-server). Top stack: sql, agile, cloud, системный аналитик, bpmn. Among jobs with a stated work format, 29% are remote. Systems Analyst — highly in-demand role with good pay and a clear growth path into architecture; the closer the analyst is to the technical side, the higher their market value.
Data as of:
Key numbers for the Systems Analyst market: open jobs, median salary, observed talent pool and remote share.
The Systems Analyst market currently has 802 open roles, 695 of them freshly observed. Median salary $8,441/mo.
Among jobs with a stated work format, 29% are remote. SA work (analysis, API and integration design, specifications, diagrams) is done well at a distance; in the financial and government sector for sensitive systems there's an office requirement. Role scarcity expands job geography.
⚠ salary known for 156 of 802 jobs; remote share from 644 with a stated format; 695 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Systems Analyst postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 6 |
| 2026-06-08 | 2 |
| 2026-06-15 | 7 |
| 2026-06-22 | 14 |
| 2026-06-29 | 113 |
| 2026-07-06 | 69 |
| 2026-07-13 | 112 |
| 2026-07-20 | 94 |
| 2026-07-27 | 58 |
| 2026-08-03 | 58 |
| 2026-08-10 | 45 |
| 2026-08-17 | 62 |
| 2026-08-24 | 57 |
| 2026-08-31 | 54 |
| 2026-09-07 | 70 |
| 2026-09-14 | 48 |
| 2026-09-21 | 127 |
| 2026-09-28 | 125 |
| 2026-10-05 | 125 |
| 2026-10-12 | 344 |
| 2026-10-19 | 200 |
| 2026-10-26 | 209 |
| 2026-11-02 | 200 |
| 2026-11-09 | 244 |
Active sources per week
Sources over the period: 151. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 5 |
| 2026-06-08 | 2 |
| 2026-06-15 | 5 |
| 2026-06-22 | 9 |
| 2026-06-29 | 38 |
| 2026-07-06 | 22 |
| 2026-07-13 | 32 |
| 2026-07-20 | 39 |
| 2026-07-27 | 24 |
| 2026-08-03 | 29 |
| 2026-08-10 | 21 |
| 2026-08-17 | 24 |
| 2026-08-24 | 23 |
| 2026-08-31 | 20 |
| 2026-09-07 | 27 |
| 2026-09-14 | 18 |
| 2026-09-21 | 34 |
| 2026-09-28 | 43 |
| 2026-10-05 | 33 |
| 2026-10-12 | 40 |
| 2026-10-19 | 50 |
| 2026-10-26 | 45 |
| 2026-11-02 | 49 |
| 2026-11-09 | 46 |
New sources connected: Jun 29 +30 · Jul 6 +10 · Jul 20 +13 · Sep 21 +11 · Oct 12 +10 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +2 | 2 |
| Jun 15 | +3 | 7 |
| Jun 22 | +5 | 14 |
| Jun 29 | +30 | 113 |
| Jul 6 | +10 | 69 |
| Jul 13 | +9 | 112 |
| Jul 20 | +13 | 94 |
| Jul 27 | +3 | 58 |
| Aug 3 | +5 | 58 |
| Aug 10 | +3 | 45 |
| Aug 17 | +2 | 62 |
| Aug 24 | +1 | 57 |
| Aug 31 | +1 | 54 |
| Sep 7 | +5 | 70 |
| Sep 14 | +1 | 48 |
| Sep 21 | +11 | 127 |
| Sep 28 | +5 | 125 |
| Oct 5 | +4 | 125 |
| Oct 12 | +10 | 344 |
| Oct 19 | +7 | 200 |
| Oct 26 | +5 | 209 |
| Nov 2 | +7 | 200 |
| Nov 9 | +4 | 244 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 6 | 5 |
| 2026-06-08 | 2 | 2 |
| 2026-06-15 | 7 | 5 |
| 2026-06-22 | 14 | 9 |
| 2026-06-29 | 113 | 38 |
| 2026-07-06 | 69 | 22 |
| 2026-07-13 | 112 | 32 |
| 2026-07-20 | 94 | 39 |
| 2026-07-27 | 58 | 24 |
| 2026-08-03 | 58 | 29 |
| 2026-08-10 | 45 | 21 |
| 2026-08-17 | 62 | 24 |
| 2026-08-24 | 57 | 23 |
| 2026-08-31 | 54 | 20 |
| 2026-09-07 | 70 | 27 |
| 2026-09-14 | 48 | 18 |
| 2026-09-21 | 127 | 34 |
| 2026-09-28 | 125 | 43 |
| 2026-10-05 | 125 | 33 |
| 2026-10-12 | 344 | 40 |
| 2026-10-19 | 200 | 50 |
| 2026-10-26 | 209 | 45 |
| 2026-11-02 | 200 | 49 |
| 2026-11-09 | 244 | 46 |
Salaries over time
Median Systems Analyst salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-10-19 | 7,196 | 32 |
| 2026-10-26 | 8,333 | 46 |
| 2026-11-02 | 8,507 | 34 |
| 2026-11-09 | 9,167 | 65 |
The series starts on Oct 19: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | — |
| 2026-10-05 | — |
| 2026-10-12 | — |
| 2026-10-19 | 7,196 |
| 2026-10-26 | 8,333 |
| 2026-11-02 | 8,507 |
| 2026-11-09 | 9,167 |
Remote work over time
Share of Systems Analyst postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-22 | 58.3 |
| 2026-06-29 | 52.2 |
| 2026-07-06 | 37.5 |
| 2026-07-13 | 35.3 |
| 2026-07-20 | 34.8 |
| 2026-07-27 | 60.7 |
| 2026-08-03 | 25 |
| 2026-08-10 | 43.3 |
| 2026-08-17 | 17.9 |
| 2026-08-24 | 37.8 |
| 2026-08-31 | 33.3 |
| 2026-09-07 | 26.5 |
| 2026-09-14 | 19.4 |
| 2026-09-21 | 24.4 |
| 2026-09-28 | 40.2 |
| 2026-10-05 | 43.9 |
| 2026-10-12 | 30.2 |
| 2026-10-19 | 32.2 |
| 2026-10-26 | 32 |
| 2026-11-02 | 32.7 |
| 2026-11-09 | 29.3 |
The series starts on Jun 22: there is no data before that.
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | 58.3 |
| 2026-06-29 | 52.2 |
| 2026-07-06 | 37.5 |
| 2026-07-13 | 35.3 |
| 2026-07-20 | 34.8 |
| 2026-07-27 | 60.7 |
| 2026-08-03 | 25 |
| 2026-08-10 | 43.3 |
| 2026-08-17 | 17.9 |
| 2026-08-24 | 37.8 |
| 2026-08-31 | 33.3 |
| 2026-09-07 | 26.5 |
| 2026-09-14 | 19.4 |
| 2026-09-21 | 24.4 |
| 2026-09-28 | 40.2 |
| 2026-10-05 | 43.9 |
| 2026-10-12 | 30.2 |
| 2026-10-19 | 32.2 |
| 2026-10-26 | 32 |
| 2026-11-02 | 32.7 |
| 2026-11-09 | 29.3 |
Technologies over time
How the share of Systems Analyst postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | SQL | cloud | Oracle |
|---|---|---|---|
| 2026-08-10 | 60.7 | 3.6 | 3.6 |
| 2026-08-17 | 25.8 | 16.1 | 9.7 |
| 2026-08-24 | 47.1 | 0 | 5.9 |
| 2026-08-31 | 41.9 | 0 | 6.5 |
| 2026-09-07 | 40.5 | 7.1 | 7.1 |
| 2026-09-14 | 25 | 12.5 | 8.3 |
| 2026-09-21 | 23.8 | 15.9 | 11.1 |
| 2026-09-28 | 42.2 | 7.2 | 4.8 |
| 2026-10-05 | 45.1 | 17.1 | 7.3 |
| 2026-10-12 | 38.2 | 12.9 | 9 |
| 2026-10-19 | 40 | 12 | 12 |
| 2026-10-26 | 40.7 | 29.3 | 16.7 |
| 2026-11-02 | 44.6 | 17.3 | 14.4 |
| 2026-11-09 | 50.6 | 21.3 | 11 |
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | SQL | cloud | Oracle | Salesforce | user stories |
|---|---|---|---|---|---|
| 2026-08-10 | 60.7 | 3.6 | 3.6 | 0 | 0 |
| 2026-08-17 | 25.8 | 16.1 | 9.7 | 9.7 | 3.2 |
| 2026-08-24 | 47.1 | 0 | 5.9 | 5.9 | 2.9 |
| 2026-08-31 | 41.9 | 0 | 6.5 | 0 | 3.2 |
| 2026-09-07 | 40.5 | 7.1 | 7.1 | 2.4 | 9.5 |
| 2026-09-14 | 25 | 12.5 | 8.3 | 0 | 4.2 |
| 2026-09-21 | 23.8 | 15.9 | 11.1 | 9.5 | 3.2 |
| 2026-09-28 | 42.2 | 7.2 | 4.8 | 4.8 | 9.6 |
| 2026-10-05 | 45.1 | 17.1 | 7.3 | 6.1 | 8.5 |
| 2026-10-12 | 38.2 | 12.9 | 9 | 6.7 | 12.4 |
| 2026-10-19 | 40 | 12 | 12 | 9.6 | 10.4 |
| 2026-10-26 | 40.7 | 29.3 | 16.7 | 10 | 12.7 |
| 2026-11-02 | 44.6 | 17.3 | 14.4 | 9.4 | 16.5 |
| 2026-11-09 | 50.6 | 21.3 | 11 | 11 | 12.2 |
Countries over time
How the share of Systems Analyst postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | Russia | Australia |
|---|---|---|---|
| 2026-06-29 | 17 | 49.1 | 0.9 |
| 2026-07-06 | 26.2 | 24.6 | 10.8 |
| 2026-07-13 | 24.4 | 24.4 | 8.1 |
| 2026-07-20 | 9.9 | 44.4 | 3.7 |
| 2026-07-27 | 9.8 | 35.3 | 13.7 |
| 2026-08-03 | 22.6 | 45.3 | 5.7 |
| 2026-08-10 | 7.5 | 60 | 7.5 |
| 2026-08-17 | 16.4 | 30.9 | 21.8 |
| 2026-08-24 | 18.9 | 45.3 | 11.3 |
| 2026-08-31 | 2 | 51 | 15.7 |
| 2026-09-07 | 13.8 | 38.5 | 7.7 |
| 2026-09-14 | 21.3 | 38.3 | 12.8 |
| 2026-09-21 | 39.3 | 26.5 | 12 |
| 2026-09-28 | 22.8 | 32.5 | 13.2 |
| 2026-10-05 | 23.7 | 20.2 | 13.2 |
| 2026-10-12 | 50 | 12.8 | 6.2 |
| 2026-10-19 | 36.9 | 20.7 | 8.9 |
| 2026-10-26 | 45.7 | 11.4 | 7.6 |
| 2026-11-02 | 32.9 | 14.7 | 4.7 |
| 2026-11-09 | 49.2 | 14.4 | 4.6 |
The series starts on Jun 29: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | Russia | Australia | UK | Hong Kong |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | — | — | — | — | — |
| 2026-06-29 | 17 | 49.1 | 0.9 | 0 | 4.5 |
| 2026-07-06 | 26.2 | 24.6 | 10.8 | 0 | 6.2 |
| 2026-07-13 | 24.4 | 24.4 | 8.1 | 3.5 | 4.7 |
| 2026-07-20 | 9.9 | 44.4 | 3.7 | 13.6 | 6.2 |
| 2026-07-27 | 9.8 | 35.3 | 13.7 | 5.9 | 5.9 |
| 2026-08-03 | 22.6 | 45.3 | 5.7 | 3.8 | 1.9 |
| 2026-08-10 | 7.5 | 60 | 7.5 | 10 | 0 |
| 2026-08-17 | 16.4 | 30.9 | 21.8 | 3.6 | 0 |
| 2026-08-24 | 18.9 | 45.3 | 11.3 | 7.5 | 0 |
| 2026-08-31 | 2 | 51 | 15.7 | 9.8 | 0 |
| 2026-09-07 | 13.8 | 38.5 | 7.7 | 20 | 0 |
| 2026-09-14 | 21.3 | 38.3 | 12.8 | 10.6 | 0 |
| 2026-09-21 | 39.3 | 26.5 | 12 | 1.7 | 0.9 |
| 2026-09-28 | 22.8 | 32.5 | 13.2 | 2.6 | 7.9 |
| 2026-10-05 | 23.7 | 20.2 | 13.2 | 4.4 | 14 |
| 2026-10-12 | 50 | 12.8 | 6.2 | 4.7 | 7.7 |
| 2026-10-19 | 36.9 | 20.7 | 8.9 | 3.9 | 5.6 |
| 2026-10-26 | 45.7 | 11.4 | 7.6 | 3.8 | 5.4 |
| 2026-11-02 | 32.9 | 14.7 | 4.7 | 8.2 | 5.3 |
| 2026-11-09 | 49.2 | 14.4 | 4.6 | 2.6 | 2.6 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Systems Analyst.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Systems Analyst jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 802 |
| Open demand | 802 |
| Observed supply | — not published |
Systems Analyst — one of the most in-demand and scarce roles in CIS IT. Drivers 2026: growing number of systems and integrations, digitalisation of banks and enterprise, large market of custom development, microservice architecture (more integrations — more work for SA). Demand consistently high, especially in fintech and integration.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Systems Analyst jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 1 |
| $2–3k | 1 |
| $3–4k | 3 |
| $4–5k | 9 |
| $5–6k | 15 |
| $6–7k | 21 |
| $7–8k | 17 |
| $8–9k | 26 |
| $9–10k | 17 |
| $10–12k | 29 |
| $12–15k | 14 |
| $15–20k | 3 |
| $20k+ | 0 |
- usable for the calculation: 156 (19.5%)
- stated but not converted to USD/month: 178 (22.2%)
- not stated: 468 (58.4%)
One in ten postings offers under $5,000, one in ten over $12,195. Half of the postings offer between $6,458 and $10,291. Sample: 156.
Pay is determined by technical depth.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 1 |
| $2–3k | 2,000 | 3,000 | 1 |
| $3–4k | 3,000 | 4,000 | 3 |
| $4–5k | 4,000 | 5,000 | 9 |
| $5–6k | 5,000 | 6,000 | 15 |
| $6–7k | 6,000 | 7,000 | 21 |
| $7–8k | 7,000 | 8,000 | 17 |
| $8–9k | 8,000 | 9,000 | 26 |
| $9–10k | 9,000 | 10,000 | 17 |
| $10–12k | 10,000 | 12,000 | 29 |
| $12–15k | 12,000 | 15,000 | 14 |
| $15–20k | 15,000 | 20,000 | 3 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open Systems Analyst jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 335 | 48.1% |
| Russia | 86 | 12.3% |
| India | 40 | 5.7% |
| Canada | 35 | 5% |
| United Kingdom | 33 | 4.7% |
| Poland | 31 | 4.4% |
| Belarus | 24 | 3.4% |
| Hong Kong | 22 | 3.2% |
| Australia | 10 | 1.4% |
| Kazakhstan | 9 | 1.3% |
| Other countries | 72 | 10.3% |
The leader by Systems Analyst job count is the US (335 positions). Demand is concentrated in banks and fintech (largest hirer), IT integrators and custom development, telecom, large product companies, government sector. International companies hire Russian-speaking Seniors on full-remote.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 335 |
| RU | 86 |
| IN | 40 |
| CA | 35 |
| GB | 33 |
| PL | 31 |
| BY | 24 |
| HK | 22 |
| AU | 10 |
| KZ | 9 |
Which technologies are most often required in the same job as Systems Analyst.
Used together with
Share — how many of the 802 jobs in the Systems Analyst market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Systems Analyst tools and skills 2026: SQL (mandatory — data model), REST API and HTTP, OpenAPI / Swagger (API contracts), Postman, JSON / XML formats, message queues (Kafka, RabbitMQ — at understanding level), UML (sequence, component), BPMN, ER diagrams, draw.io / PlantUML / Visio, Confluence + Jira, understanding of architecture (monolith, microservices, integration patterns).
Common pairs: SQL + data model, REST API + OpenAPI / Swagger, API + Postman, UML sequence + integrations, JSON + API contracts. Learning roadmap: SQL → REST and HTTP → OpenAPI / Swagger → formats and integrations (JSON / XML, queues) → diagrams (UML, ER) → data model → architecture (monolith / microservices) → writing specifications → tools (Confluence, Jira) → pet project → Junior / internship as Systems Analyst.
Chart data
| Name | Count |
|---|---|
| sql | 221 |
| cloud | 128 |
| oracle | 76 |
| salesforce | 73 |
| user stories | 71 |
| sap | 60 |
| python | 55 |
| java | 47 |
| backlog | 46 |
| azure | 39 |
| servicenow | 24 |
| aws | 24 |
How many Systems Analyst jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 239 |
| middle | 64 |
| lead | 36 |
| junior | 33 |
| principal | 25 |
A Systems Analyst on average earns more than a Business Analyst of the same grade (technical component). Career flow: Systems Analyst → Senior SA → Lead SA → Solution / System Architect (natural target — /research/architect), or Product Owner, or technical lead.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 239 |
| middle | 64 |
| lead | 36 |
| junior | 33 |
| principal | 25 |
Who hires the most for Systems Analyst and how concentrated demand is among the largest companies.
Employers
Demand is spread across 579 employers. The largest accounts for 0.9%, the top ten for 6.3%; the remaining 93.7% is long tail.
| share | value |
|---|---|
| top-1 | 0.9% |
| top-3 | 2.3% |
| top-10 | 6.3% |
| long tail | 93.7% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Systems Analyst jobs from.
Where Zorky sees this market
Observed across 77 sources; the largest accounts for 16.5% — this market does not rest on a single channel.
Systems Analyst jobs: hh.ru ("systems analyst" / "business-systems analyst"), Habr Career, getmatch, LinkedIn, Telegram (systems analyst communities — large active community in Russia — and job channels). The real market is wider than exact search; part of "business-systems analyst" is counted nearby in business-analyst. NB: the Analyst / BI direction had difficulties with auto-classification — the visible number may understate the market.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 488 | 0.6085 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 248 | 0.3092 |
| telegram | Telegram | Telegram | 65 | 0.081 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0012 |
The newest Systems Analyst jobs from company career sites.
Recent openings
- Системный аналитик (AI агент) · RU
- а это уже не архитектор. это уже системный аналитик · RU
- Системный аналитик · KZ
- Sr. Business Systems Analyst · US
- Системный аналитик (стажер) · BY
- Требуется «Ведущий системный аналитик (DWDM / телеком)» (Москва) · RU
- Системный аналитик (стажировка) / TG · RU
- Ведущий системный аналитик (AI / AI Agents) · RU
Latest open Systems Analyst jobs — the most recent 10 positions with adequate description quality. NB: the role is often named "business-systems analyst" — the full list is in our CRM or via the "see all" link below.
Adjacent markets
Systems Analyst — the technical side of analytics, bridge between business and development. Borders Business Analyst (business side of requirements — /research/analyst/business-analyst), backend development (/research/backend), and the main career target — Solution / System Architect (/research/architect). Analyst specialisation comparison — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Analyst / BI
Related specializations
Inside Systems Analyst: Systems Analyst (general — specs, APIs, integrations, data model), Business-Systems Analyst (combines business and systems analysis — common format in small teams), Senior / Lead Systems Analyst (complex integration projects, architectural decisions). Adjacent career target — Solution / System Architect. Comparison with other analyst specialisations — in the bar below.
Frequently asked questions
The most common questions about Systems Analyst: pay, grades, tools and skills, Systems Analyst vs Business Analyst, what SA does (API, integrations, specs, data model), whether to code, remote, companies, how to start, Senior skills. Answers recompute automatically.
What does a Systems Analyst Junior, Middle, Senior, or Lead earn?
Junior describes simple requirements and specifications under mentorship. Jump to Middle — independent API and integration design, confident work with data model and SQL, writing full technical specifications. Senior leads complex integration projects, makes design decisions, influences architecture. Career flow: Systems Analyst → Senior SA → Lead SA, further — Solution / System Architect (natural and common target — see /research/architect), or Product Owner, or technical lead.
What tools and skills are most often required of a Systems Analyst?
Top 5: sql, agile, cloud, системный аналитик, bpmn. Data: SQL — mandatory (work with data model, table design, verification), ER diagrams, understanding of relational DBs, sometimes NoSQL. APIs and integrations — core of the profession: REST API and HTTP understanding (methods, codes, headers), OpenAPI / Swagger (contract description), Postman (verification), JSON and XML formats, sometimes SOAP (legacy) and gRPC; message queues (Kafka, RabbitMQ — at principle understanding level). Diagrams and modelling: UML (especially sequence and component diagrams), BPMN, ER diagrams; tools — draw.io, PlantUML, Visio. Documentation: Confluence (specifications, specs), Jira. Architecture: understanding of client-server model, monolith and microservices, integration patterns — enough to design a solution and speak with development as an equal. Skills: systems and technical thinking, ability to decompose complex things, precision and unambiguity in specifications, communication (with business analysts, developers, testers, architects), attention to edge cases. Coding is not required, but the closer the analyst is to the technical side (reads code, understands technology more deeply), the more valuable.
Systems Analyst vs Business Analyst — what's the difference?
This is the main question about the profession, and in Russia the distinction is especially clear. Business Analyst answers "what and why": works from the business side — elicits the need, describes business processes, formalises what problem needs to be solved and what the result for the business should be. Systems Analyst answers "how, technically": takes requirements and designs the solution — describes APIs and integration contracts, data model, system logic, writes technical specifications by which the team writes code. Roughly: BA looks toward business, SA — toward development; BA hands off work output to the systems analyst, SA — to developers. In practice: in enterprise, banks and large custom development BA and SA are separate roles with separate people; in small teams and product startups one person often combines them — hence the common "business-systems analyst" job. By skills: SA requires more technical depth (SQL, API, integrations, data model, architecture), BA — more stakeholder and business process skills. By pay: a Systems Analyst on average earns more due to the technical component. Career flow: BA often moves into SA after gaining technical horizon; SA further grows into Solution / System Architect.
What exactly does a Systems Analyst do — API, integrations, specifications?
A Systems Analyst's work is to design how the system should work technically and describe it so the team implements unambiguously. 1) Requirements analysis — take business requirements (from BA or customer) and figure out what technically needs to be done, identify missing details and edge cases. 2) API design — describe programmatic interfaces: which methods, which requests and responses, data formats, error codes, authorisation; fix the contract (often in OpenAPI / Swagger). 3) Integration design — design how systems and services exchange data: synchronously via API or asynchronously via queues, what data, in what format, what happens on failure. 4) Data model — design data structures and tables (ER diagrams), describe entities and relations. 5) Logic and algorithms — describe business logic, states, scenarios, error handling. 6) Diagrams — sequence diagrams (how components interact over time), component diagrams, integration schemes. 7) Specifications and specs — gather everything into a technical document understandable to development and testing. 8) Support — answer team questions during development, clarify, participate in reviews and testing, manage changes. Key: a Systems Analyst is a person who designs and precisely describes a technical solution without writing the code itself.
Does a Systems Analyst need to code?
Writing production code is not mandatory for a Systems Analyst — this is not a developer role. But technical depth is the essence of the profession, and here the requirements are higher than for a Business Analyst: 1) SQL — mandatory, not at the "heard of it" level but confidently (queries, joins, understanding of data model). 2) API and protocols — need to understand well how HTTP works, REST, what an API contract is, JSON / XML formats; ability to design an API and verify it in Postman. 3) Integrations and architecture — understand synchronous and asynchronous interaction, message queues, microservices and monolith, typical patterns. 4) Reading code and logs — a major advantage: ability to read code, understand what's happening, parse a log — this strongly raises the analyst's value. 5) One language at basic level — not mandatory, but many systems analysts learn Python or read code in the project's language, and it helps. Bottom line: professional coding is not needed, but the "technical ceiling" of a Systems Analyst directly determines pay and growth — the deeper they understand technology, the closer to the architect role and the more they earn. This is an engineering-oriented analytical role.
What share of jobs are remote?
Among jobs with a stated work format, 29% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
Where to start a Systems Analyst career in 2026?
People come into systems analysis from business analysis, testing, support, development, as well as directly after specialised training. Roadmap: 1) SQL — master confidently: queries, joins, aggregations, understanding of data model; this is the foundation. 2) API and HTTP — figure out how REST works, HTTP methods and codes, what an API contract is; learn to read and verify APIs in Postman. 3) OpenAPI / Swagger — learn to describe API contracts. 4) Formats and integrations — JSON and XML, synchronous and asynchronous interaction, basics — message queues (Kafka, RabbitMQ). 5) Diagrams — UML (sequence, component), ER diagrams, BPMN; tools draw.io / PlantUML. 6) Data model — table design, entities and relations. 7) Architecture — understand client-server, monolith and microservices, typical integration patterns. 8) Specifications — learn to write clear, unambiguous technical assignments. 9) Tools — Confluence, Jira. 10) Pet project / portfolio — design an API and integration for a clear task, describe the specification. Resources: systems analysis courses (Otus, specialised analytics schools), REST / OpenAPI documentation, systems analyst communities (in Russia this is an active and large community). A good entry path is from testing or business analysis, building up technical depth; aim for Junior / internship as a Systems Analyst.
How many open jobs are in this sample?
The published sample contains 802 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Systems Analyst need?
A Senior Systems Analyst designs technical solutions for complex systems and integrations. SQL and data: expert level, data model design, understanding of query performance, integrity edge cases. API design: design of convenient, consistent, versionable APIs, well-thought-out contracts, error handling, authorisation; fluent OpenAPI / Swagger. Integrations: design interaction of multiple systems — synchronous and asynchronous, via queues; understanding of reliability, idempotency, failure behaviour, data consistency between systems. Architectural thinking: see the solution as a whole, understand monolith and microservices, integration patterns, consciously choose approach and trade-offs — this is what turns a Senior SA into an architect. Specifications: write clear, unambiguous, complete technical documents leaving no room for different interpretation; think through edge cases before development. Diagrams: confident UML (sequence, component), ER, integration schemes as a working design tool. Technical horizon: reading code and logs, understanding the project stack, infrastructure at the top level. Decomposition: break a large complex task into designable and implementable parts. Communication: work with business analysts, developers, testers, architects, customer; ability to defend and explain a design decision. Mentoring: development of Junior analysts, specification standards on the team. English — for the international market and documentation. The main value of a Senior — design a technically correct, implementable solution for a complex task and describe it so the team implements without guessing; this is a direct springboard to an architect role.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.