Python Backend: market
Data as of November 19, 2026: 3,371 open Python Backend jobs, 34% remote among jobs that state a work format; median advertised salary $6,775/mo (from 550 postings that state a salary). Source: Zorky, updated daily.
Python Backend — server-side development in Python: REST/GraphQL APIs, business logic, integrations, task queues, background jobs. Role family: Django Developer (full-stack-leaning, ORM-heavy, large product monoliths), FastAPI Developer (async-first, microservices, ML APIs), Flask Developer (lightweight services, prototyping), Python Backend Engineer (general — Django/FastAPI/plain stack), Async Python Developer (aiohttp/Sanic/Starlette for high-throughput). Stack: Python 3.11+ (must), Django/FastAPI/Flask (must — one of), SQLAlchemy/Django ORM, PostgreSQL/MySQL, Redis, Celery/Arq/RQ for queues, Kafka/RabbitMQ for messaging, Docker+Kubernetes, pytest+alembic+poetry, asyncio, observability via Prometheus/Grafana/OpenTelemetry. The most in-demand tech — python, fastapi, django, cloud, ci/cd. Among jobs with a stated work format, 34% are remote. This is the most senior-heavy segment of the backend market: the market rarely hires Python Junior, expecting Middle+ with practical experience.
Data as of:
Key numbers for the Python Backend market: open jobs, median salary, observed talent pool and remote share.
The Python Backend market currently has 3,371 open roles, 2,778 of them freshly observed. Median salary $6,775/mo.
Among jobs with a stated work format, 34% are remote. The stack adapts well to remote — no special equipment, everything in Docker/k8s/Git. Russian banks — more often office due to compliance.
⚠ salary known for 550 of 3371 jobs; remote share from 2852 with a stated format; 2778 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Python Backend 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 | 377 |
| 2026-06-08 | 348 |
| 2026-06-15 | 364 |
| 2026-06-22 | 716 |
| 2026-06-29 | 715 |
| 2026-07-06 | 550 |
| 2026-07-13 | 922 |
| 2026-07-20 | 834 |
| 2026-07-27 | 472 |
| 2026-08-03 | 507 |
| 2026-08-10 | 356 |
| 2026-08-17 | 360 |
| 2026-08-24 | 411 |
| 2026-08-31 | 444 |
| 2026-09-07 | 418 |
| 2026-09-14 | 443 |
| 2026-09-21 | 742 |
| 2026-09-28 | 1,005 |
| 2026-10-05 | 852 |
| 2026-10-12 | 1,462 |
| 2026-10-19 | 1,028 |
| 2026-10-26 | 1,005 |
| 2026-11-02 | 830 |
| 2026-11-09 | 882 |
Active sources per week
Sources over the period: 349. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 40 |
| 2026-06-08 | 32 |
| 2026-06-15 | 39 |
| 2026-06-22 | 57 |
| 2026-06-29 | 96 |
| 2026-07-06 | 89 |
| 2026-07-13 | 105 |
| 2026-07-20 | 113 |
| 2026-07-27 | 105 |
| 2026-08-03 | 108 |
| 2026-08-10 | 64 |
| 2026-08-17 | 79 |
| 2026-08-24 | 76 |
| 2026-08-31 | 73 |
| 2026-09-07 | 78 |
| 2026-09-14 | 73 |
| 2026-09-21 | 95 |
| 2026-09-28 | 94 |
| 2026-10-05 | 95 |
| 2026-10-12 | 90 |
| 2026-10-19 | 117 |
| 2026-10-26 | 100 |
| 2026-11-02 | 98 |
| 2026-11-09 | 105 |
New sources connected: Jun 22 +27 · Jun 29 +47 · Jul 6 +29 · Jul 13 +28 · Jul 20 +22 · Oct 19 +17 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +6 | 348 |
| Jun 15 | +8 | 364 |
| Jun 22 | +27 | 716 |
| Jun 29 | +47 | 715 |
| Jul 6 | +29 | 550 |
| Jul 13 | +28 | 922 |
| Jul 20 | +22 | 834 |
| Jul 27 | +14 | 472 |
| Aug 3 | +15 | 507 |
| Aug 10 | +3 | 356 |
| Aug 17 | +9 | 360 |
| Aug 24 | +8 | 411 |
| Aug 31 | +6 | 444 |
| Sep 7 | +6 | 418 |
| Sep 14 | +6 | 443 |
| Sep 21 | +12 | 742 |
| Sep 28 | +6 | 1,005 |
| Oct 5 | +8 | 852 |
| Oct 12 | +9 | 1,462 |
| Oct 19 | +17 | 1,028 |
| Oct 26 | +8 | 1,005 |
| Nov 2 | +7 | 830 |
| Nov 9 | +8 | 882 |
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 | 377 | 40 |
| 2026-06-08 | 348 | 32 |
| 2026-06-15 | 364 | 39 |
| 2026-06-22 | 716 | 57 |
| 2026-06-29 | 715 | 96 |
| 2026-07-06 | 550 | 89 |
| 2026-07-13 | 922 | 105 |
| 2026-07-20 | 834 | 113 |
| 2026-07-27 | 472 | 105 |
| 2026-08-03 | 507 | 108 |
| 2026-08-10 | 356 | 64 |
| 2026-08-17 | 360 | 79 |
| 2026-08-24 | 411 | 76 |
| 2026-08-31 | 444 | 73 |
| 2026-09-07 | 418 | 78 |
| 2026-09-14 | 443 | 73 |
| 2026-09-21 | 742 | 95 |
| 2026-09-28 | 1,005 | 94 |
| 2026-10-05 | 852 | 95 |
| 2026-10-12 | 1,462 | 90 |
| 2026-10-19 | 1,028 | 117 |
| 2026-10-26 | 1,005 | 100 |
| 2026-11-02 | 830 | 98 |
| 2026-11-09 | 882 | 105 |
Salaries over time
Median Python Backend salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-08-31 | 6,514 | 14 |
| 2026-09-07 | 8,511 | 15 |
| 2026-09-14 | — | 5 |
| 2026-09-21 | 5,039 | 18 |
| 2026-09-28 | 5,858 | 121 |
| 2026-10-05 | 4,266 | 130 |
| 2026-10-12 | 5,500 | 151 |
| 2026-10-19 | 6,275 | 220 |
| 2026-10-26 | 6,746 | 210 |
| 2026-11-02 | 7,020 | 169 |
| 2026-11-09 | 5,807 | 165 |
The series starts on Aug 31: 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 | 6,514 |
| 2026-09-07 | 8,511 |
| 2026-09-14 | — |
| 2026-09-21 | 5,039 |
| 2026-09-28 | 5,858 |
| 2026-10-05 | 4,266 |
| 2026-10-12 | 5,500 |
| 2026-10-19 | 6,275 |
| 2026-10-26 | 6,746 |
| 2026-11-02 | 7,020 |
| 2026-11-09 | 5,807 |
Remote work over time
Share of Python Backend postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 37.5 |
| 2026-06-08 | 38.4 |
| 2026-06-15 | 39.8 |
| 2026-06-22 | 35.5 |
| 2026-06-29 | 40 |
| 2026-07-06 | 40.9 |
| 2026-07-13 | 38.5 |
| 2026-07-20 | 42.1 |
| 2026-07-27 | 45.3 |
| 2026-08-03 | 33.1 |
| 2026-08-10 | 32.1 |
| 2026-08-17 | 28.9 |
| 2026-08-24 | 28.1 |
| 2026-08-31 | 25 |
| 2026-09-07 | 22.2 |
| 2026-09-14 | 27.7 |
| 2026-09-21 | 41.1 |
| 2026-09-28 | 42.2 |
| 2026-10-05 | 36 |
| 2026-10-12 | 39.8 |
| 2026-10-19 | 37.4 |
| 2026-10-26 | 36.5 |
| 2026-11-02 | 35.1 |
| 2026-11-09 | 31 |
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 | 37.5 |
| 2026-06-08 | 38.4 |
| 2026-06-15 | 39.8 |
| 2026-06-22 | 35.5 |
| 2026-06-29 | 40 |
| 2026-07-06 | 40.9 |
| 2026-07-13 | 38.5 |
| 2026-07-20 | 42.1 |
| 2026-07-27 | 45.3 |
| 2026-08-03 | 33.1 |
| 2026-08-10 | 32.1 |
| 2026-08-17 | 28.9 |
| 2026-08-24 | 28.1 |
| 2026-08-31 | 25 |
| 2026-09-07 | 22.2 |
| 2026-09-14 | 27.7 |
| 2026-09-21 | 41.1 |
| 2026-09-28 | 42.2 |
| 2026-10-05 | 36 |
| 2026-10-12 | 39.8 |
| 2026-10-19 | 37.4 |
| 2026-10-26 | 36.5 |
| 2026-11-02 | 35.1 |
| 2026-11-09 | 31 |
Technologies over time
How the share of Python Backend postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | Python | cloud | AWS |
|---|---|---|---|
| 2026-08-10 | 98.6 | 12.7 | 7.9 |
| 2026-08-17 | 99.2 | 12 | 12 |
| 2026-08-24 | 99.3 | 11.5 | 11 |
| 2026-08-31 | 99.5 | 12.9 | 12.4 |
| 2026-09-07 | 99.5 | 14.9 | 12 |
| 2026-09-14 | 98.9 | 10.2 | 12.2 |
| 2026-09-21 | 97.3 | 15.8 | 11.9 |
| 2026-09-28 | 98.4 | 22 | 18.5 |
| 2026-10-05 | 98.1 | 22.2 | 19.2 |
| 2026-10-12 | 98 | 26.4 | 15.8 |
| 2026-10-19 | 97.6 | 26.2 | 20.9 |
| 2026-10-26 | 98 | 24.5 | 19.8 |
| 2026-11-02 | 96.6 | 21.2 | 16.6 |
| 2026-11-09 | 98.6 | 20.8 | 16.7 |
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 | Python | cloud | AWS | FastAPI | Docker |
|---|---|---|---|---|---|
| 2026-08-10 | 98.6 | 12.7 | 7.9 | 9.3 | 5.6 |
| 2026-08-17 | 99.2 | 12 | 12 | 9.8 | 4.7 |
| 2026-08-24 | 99.3 | 11.5 | 11 | 13.2 | 8.3 |
| 2026-08-31 | 99.5 | 12.9 | 12.4 | 11.5 | 9 |
| 2026-09-07 | 99.5 | 14.9 | 12 | 10.8 | 8.6 |
| 2026-09-14 | 98.9 | 10.2 | 12.2 | 10.6 | 7 |
| 2026-09-21 | 97.3 | 15.8 | 11.9 | 12 | 10.4 |
| 2026-09-28 | 98.4 | 22 | 18.5 | 19.9 | 17.6 |
| 2026-10-05 | 98.1 | 22.2 | 19.2 | 17.9 | 18.9 |
| 2026-10-12 | 98 | 26.4 | 15.8 | 18.5 | 17.6 |
| 2026-10-19 | 97.6 | 26.2 | 20.9 | 15.3 | 16.4 |
| 2026-10-26 | 98 | 24.5 | 19.8 | 16.7 | 16.4 |
| 2026-11-02 | 96.6 | 21.2 | 16.6 | 19.1 | 19.1 |
| 2026-11-09 | 98.6 | 20.8 | 16.7 | 18.8 | 15.9 |
Countries over time
How the share of Python Backend postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | Poland | USA | Russia |
|---|---|---|---|
| 2026-06-01 | 34.4 | 12.2 | 4.2 |
| 2026-06-08 | 36.7 | 21 | 1.8 |
| 2026-06-15 | 34.8 | 20.8 | 2.8 |
| 2026-06-22 | 42.4 | 17.1 | 1.9 |
| 2026-06-29 | 27.5 | 12.7 | 19.1 |
| 2026-07-06 | 24.9 | 14.7 | 14.9 |
| 2026-07-13 | 23.7 | 20.2 | 14.5 |
| 2026-07-20 | 26.3 | 13.1 | 16.2 |
| 2026-07-27 | 35.3 | 6.3 | 22.9 |
| 2026-08-03 | 18.2 | 10.1 | 20.2 |
| 2026-08-10 | 14 | 6.7 | 20 |
| 2026-08-17 | 15.9 | 7.9 | 17.8 |
| 2026-08-24 | 13 | 9.3 | 22.3 |
| 2026-08-31 | 9.3 | 11.6 | 14.3 |
| 2026-09-07 | 12.7 | 8.8 | 11.4 |
| 2026-09-14 | 8.3 | 13.6 | 12.6 |
| 2026-09-21 | 15 | 12.8 | 9.4 |
| 2026-09-28 | 25.9 | 9.9 | 11.5 |
| 2026-10-05 | 29.4 | 9.4 | 10.5 |
| 2026-10-12 | 21.9 | 13.6 | 6.1 |
| 2026-10-19 | 22.2 | 13.6 | 14.9 |
| 2026-10-26 | 15.6 | 10 | 7.3 |
| 2026-11-02 | 19.4 | 13.5 | 10.3 |
| 2026-11-09 | 20.9 | 10.2 | 10.9 |
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 | Poland | USA | Russia | UK | India |
|---|---|---|---|---|---|
| 2026-06-01 | 34.4 | 12.2 | 4.2 | 14.7 | 7.5 |
| 2026-06-08 | 36.7 | 21 | 1.8 | 10.7 | 7.7 |
| 2026-06-15 | 34.8 | 20.8 | 2.8 | 9.7 | 8.8 |
| 2026-06-22 | 42.4 | 17.1 | 1.9 | 3.8 | 7.1 |
| 2026-06-29 | 27.5 | 12.7 | 19.1 | 4.4 | 7.6 |
| 2026-07-06 | 24.9 | 14.7 | 14.9 | 4.5 | 7.3 |
| 2026-07-13 | 23.7 | 20.2 | 14.5 | 4.1 | 8.8 |
| 2026-07-20 | 26.3 | 13.1 | 16.2 | 11.5 | 9.5 |
| 2026-07-27 | 35.3 | 6.3 | 22.9 | 5.5 | 3 |
| 2026-08-03 | 18.2 | 10.1 | 20.2 | 14.8 | 10.3 |
| 2026-08-10 | 14 | 6.7 | 20 | 17.5 | 11.4 |
| 2026-08-17 | 15.9 | 7.9 | 17.8 | 20.6 | 11.1 |
| 2026-08-24 | 13 | 9.3 | 22.3 | 20.9 | 7.9 |
| 2026-08-31 | 9.3 | 11.6 | 14.3 | 19.7 | 9.7 |
| 2026-09-07 | 12.7 | 8.8 | 11.4 | 16.8 | 14 |
| 2026-09-14 | 8.3 | 13.6 | 12.6 | 17.8 | 11.8 |
| 2026-09-21 | 15 | 12.8 | 9.4 | 12 | 8.3 |
| 2026-09-28 | 25.9 | 9.9 | 11.5 | 9.3 | 7.6 |
| 2026-10-05 | 29.4 | 9.4 | 10.5 | 7.9 | 8.9 |
| 2026-10-12 | 21.9 | 13.6 | 6.1 | 5.9 | 10.8 |
| 2026-10-19 | 22.2 | 13.6 | 14.9 | 7.2 | 6.3 |
| 2026-10-26 | 15.6 | 10 | 7.3 | 7.4 | 11.1 |
| 2026-11-02 | 19.4 | 13.5 | 10.3 | 10 | 9.2 |
| 2026-11-09 | 20.9 | 10.2 | 10.9 | 11.6 | 8 |
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 Python Backend.
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 Python Backend jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 3,371 |
| Open demand | 3,371 |
| Observed supply | — not published |
Python Backend produces a steady flow of new openings thanks to the ML/AI wave and a mature product stack. Demand is growing especially in the FastAPI segment (new services) and among ML companies looking for backend for inference APIs.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Python Backend jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 14 |
| $1–2k | 31 |
| $2–3k | 33 |
| $3–4k | 38 |
| $4–5k | 58 |
| $5–6k | 65 |
| $6–7k | 58 |
| $7–8k | 49 |
| $8–9k | 30 |
| $9–10k | 25 |
| $10–12k | 49 |
| $12–15k | 28 |
| $15–20k | 65 |
| $20k+ | 7 |
- usable for the calculation: 550 (16.3%)
- stated but not converted to USD/month: 473 (14%)
- not stated: 2,348 (69.7%)
One in ten postings offers under $2,092, one in ten over $16,666. Half of the postings offer between $4,528 and $10,210. Sample: 550.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 14 |
| $1–2k | 1,000 | 2,000 | 31 |
| $2–3k | 2,000 | 3,000 | 33 |
| $3–4k | 3,000 | 4,000 | 38 |
| $4–5k | 4,000 | 5,000 | 58 |
| $5–6k | 5,000 | 6,000 | 65 |
| $6–7k | 6,000 | 7,000 | 58 |
| $7–8k | 7,000 | 8,000 | 49 |
| $8–9k | 8,000 | 9,000 | 30 |
| $9–10k | 9,000 | 10,000 | 25 |
| $10–12k | 10,000 | 12,000 | 49 |
| $12–15k | 12,000 | 15,000 | 28 |
| $15–20k | 15,000 | 20,000 | 65 |
| $20k+ | 20,000 | — | 7 |
Which countries have the most open Python Backend jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| Poland | 667 | 22.4% |
| United States | 377 | 12.7% |
| India | 285 | 9.6% |
| United Kingdom | 249 | 8.4% |
| Russia | 227 | 7.6% |
| Spain | 123 | 4.1% |
| Canada | 112 | 3.8% |
| France | 109 | 3.7% |
| Singapore | 94 | 3.2% |
| South Africa | 87 | 2.9% |
| Other countries | 646 | 21.7% |
The leader by Python Backend job count is Poland (667 positions). Moscow dominates thanks to large product companies and banks. Dubai, Cyprus, Lisbon — the main relocant hubs for Russian-speaking Python developers.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| PL | 667 |
| US | 377 |
| IN | 285 |
| GB | 249 |
| RU | 227 |
| ES | 123 |
| CA | 112 |
| FR | 109 |
| SG | 94 |
| ZA | 87 |
Which technologies are most often required in the same job as Python Backend.
Used together with
Share — how many of the 3,371 jobs in the Python Backend 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 Python Backend stack 2026: Python 3.11+ (must), Django/FastAPI/Flask (must — one of), SQLAlchemy/Django ORM, PostgreSQL, Redis, Celery/Arq, Kafka/RabbitMQ, Docker+Kubernetes, pytest+mypy+poetry, asyncio for Senior. Knowing 2+ frameworks — a Senior plus.
The most common pairs in Python Backend jobs: Django + PostgreSQL, FastAPI + SQLAlchemy, Django + Celery + Redis, FastAPI + asyncio + Pydantic, Python + Docker + Kubernetes. Learning roadmap: Django+PostgreSQL → FastAPI+SQLAlchemy → Celery/Arq → Docker/k8s.
Chart data
| Name | Count |
|---|---|
| python | 3,238 |
| cloud | 838 |
| aws | 660 |
| fastapi | 609 |
| docker | 586 |
| django | 525 |
| sql | 458 |
| postgresql | 419 |
| react | 393 |
| azure | 376 |
| kubernetes | 328 |
| java | 327 |
How many Python Backend jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 1,244 |
| middle | 269 |
| lead | 157 |
| junior | 142 |
| principal | 63 |
The biggest jump is between Junior and Middle. This is a senior-heavy segment: 60-80% of open jobs are Senior+, Juniors are hired rarely.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 1,244 |
| middle | 269 |
| lead | 157 |
| junior | 142 |
| principal | 63 |
Who hires the most for Python Backend and how concentrated demand is among the largest companies.
Employers
Demand is spread across 1,775 employers. The largest accounts for 1.1%, the top ten for 7.2%; the remaining 92.8% is long tail.
| share | value |
|---|---|
| top-1 | 1.1% |
| top-3 | 2.9% |
| top-10 | 7.2% |
| long tail | 92.8% |
⚠ 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 Python Backend jobs from.
Where Zorky sees this market
Observed across 154 sources; the largest accounts for 8.9% — this market does not rest on a single channel.
Python Backend jobs distribute between classic job sites (hh.ru, Habr Career, Djinni, NoFluffJobs) and Telegram channels. Internal HRMS of large product companies — a big invisible source.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| board | джоб-борды и агрегаторы | job boards & aggregators | 2,019 | 0.5989 |
| ats | ATS и карьерные сайты | ATS & career sites | 1,090 | 0.3233 |
| telegram | Telegram | Telegram | 234 | 0.0694 |
| community | сообщества и публичные профили | community & public profiles | 28 | 0.0083 |
The newest Python Backend jobs from company career sites.
Recent openings
- Senior Fullstack Engineer (Python + TypeScript) · INT
- Some Python jobs I came across this week
- Frontend Developer (React / Django) · RU
- Founding Staff Software Engineer • Python/FastAPI · US
- AI-разработчик (Python) · KZ
- Full-stack Developer (TypeScript / Python) · NL
- Process Automation Developer Python/AWS (Hybrid) · ES · $4,982
- Backend Java/Python Developer · ES · $4,846
Latest open Python Backend jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Python Backend is one of the largest backend-market segments by job count. By median salary slightly below Java/Go due to larger developer supply. Comparison with other backend stacks — 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: Backend
Related specializations
Inside Python Backend the specialisations split by framework: Django Developer (full-stack-leaning, monoliths), FastAPI Developer (async-first, microservices), Flask Developer (lightweight, legacy), Python Backend Engineer (general). Comparison with other Backend stacks (Java, Go, .NET, Node.js) — in the bar below.
Frequently asked questions
The most common questions about the Python Backend market: pay by level and geography, differences between Django/FastAPI/Flask, Python vs Java vs Go, remote, how Python Backend differs from Data Engineer and ML Engineer, how to start, Senior skills. Answers recompute automatically from current data.
What does a Python Backend Junior, Middle, Senior, or Lead earn?
Junior openings are scarce — the market expects 1-2 years of real experience or a strong pet project (a deployed Django/FastAPI app with PostgreSQL + Redis + Celery on GitHub). The biggest jump is between Junior and Middle (mastering SQLAlchemy/Django ORM, asynchrony, tests). Senior owns the service architecture + mentors Middle/Junior. Lead — owns several services + the hiring loop + cross-team architecture decisions. Career flow: Junior Python → Middle → Senior → either Tech Lead (management track) or Staff Engineer (technical track).
What stack does Python Backend most often need?
Top 5 technologies in Python Backend jobs: python, fastapi, django, cloud, ci/cd. Django dominates in legacy and large product monoliths (CMS, e-commerce, fintech). FastAPI — the pick for new services and ML APIs thanks to async + automatic OpenAPI generation. Flask still holds on in lightweight services and legacy. SQLAlchemy 2.0 (async-aware) is gaining ground in the FastAPI stack. PostgreSQL — primary DB, MySQL in legacy. Redis — cache + Celery broker. Celery + Arq for queues. Kafka/RabbitMQ for inter-service messaging. Docker + Kubernetes — standard. pytest — the test framework. poetry/pip-tools for deps management. asyncio + understanding the GIL — Senior must-have. Knowledge of type hints + mypy is mandatory in large teams.
Python vs Java vs Go — what to pick for Backend in 2026?
Python — the broadest entry-level market, the best ecosystem for ML/AI/data backend, fast prototyping. Salaries slightly below Java/Go on average due to a larger developer supply. Java — the foundation of enterprise/banks/telecom. Spring Boot — must. Long projects, stability. Go — a growing segment of high-load infra, DevOps-leaning services, k8s tooling. Career pick: Python — if you intersect with ML/data; Java — if enterprise/banks/maximum stability; Go — if infra/k8s/cloud-native. Many Seniors know 2 of the 3 for flexibility.
Django vs FastAPI vs Flask — what to learn in 2026?
Django — full-stack "batteries included": ORM, admin, auth, middlewares. Fits CMS / e-commerce / classic product monoliths. Sync-first (async exists in Django 5+ but isn't idiomatic). The largest job market for Junior/Middle. FastAPI — async-first, microservices-friendly, automatic OpenAPI/Swagger, native Pydantic validation. The pick for ML APIs, microservices, high-throughput services. Premium salaries for async mastery. Flask — minimalist, educational, great for lightweight services or legacy. Career strategy: Django first for a solid base (a year+), then FastAPI as the async extension. Flask — not required in 2026, but knowing the concept is useful. Junior: Django. Middle+: add FastAPI. Senior owns both and picks by task.
What share of jobs are remote?
Among jobs with a stated work format, 34% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Python Backend different from Data Engineer / ML Engineer?
Python Backend — REST/GraphQL APIs, business logic, state, integrations, queues. Focus: serve product requests and store state. Data Engineer — ETL/ELT pipelines, DWH modelling (dbt, Snowflake, ClickHouse, BigQuery), orchestration (Airflow, Dagster). Focus: move and transform large volumes of data. Technically partially overlaps (Python + SQL + Kafka), but DE is much closer to Spark/pyspark/dbt than to Django/FastAPI. ML Engineer — model deployment (FastAPI + ONNX/TorchServe), feature store, MLOps. Focus: production-ready inference. Career switch Python Backend → DE possible in 3-6 months (master Airflow + dbt + DWH); → ML Engineer in 6-12 months (master PyTorch/sklearn + MLOps stack).
Where to start to become a Python Backend developer in 2026?
Optimal roadmap: 1) Python core — Mark Lutz "Learning Python", LeetCode/Codewars for algorithms. 2) SQL to a confident level — PostgreSQL tutorial + window functions + indexes. 3) Django basics — Django tutorial + one real pet project (blog with auth + CRUD + REST API via DRF). 4) FastAPI — official tutorial + one async service (realtime websockets or ML-inference API). 5) Docker + basic Kubernetes. 6) pytest + mypy + poetry. 7) Redis + Celery/Arq for queues. 8) Pet project: end-to-end app (Django+DRF or FastAPI + PostgreSQL + Redis + Celery + Docker + pytest), deployed to VPS/Render/Railway, in a GitHub portfolio with a README. Courses: RealPython.com, FastAPI documentation, Karpov.Courses "Hard ML" (RU). Books: "Fluent Python" Luciano Ramalho, "Django for Professionals" William Vincent. Time to Junior role — 6-12 months of full-time study.
How many open jobs are in this sample?
The published sample contains 3371 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 Python Backend need?
A Senior Python Backend owns the full cycle: from requirements to production deployment. Python core: advanced idioms (descriptors, metaclasses, context managers, decorators), typing (mypy, pyright), asyncio at mastery level. Framework: Django ORM or SQLAlchemy 2.0 — query optimisation, N+1 detection, transactions, migrations (Alembic/Django migrations). Architecture: REST/GraphQL API design, event-driven (Kafka, RabbitMQ), idempotency, distributed locks, sagas. Testing: pytest fixtures + factories (factory_boy) + risk-based coverage. Test coverage targets depend on system risks and criticality; coverage alone does not guarantee quality. Google Testing. Performance: profiling (cProfile, py-spy), SQL optimisation, caching (Redis). DevOps: Docker + Kubernetes basics, observability (Prometheus + Grafana + OpenTelemetry), structured logging. Soft: code review, mentoring Middle/Junior, technical interviews, designing alongside PM/Product. English for Senior+ — must-have.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.