👀 Python Developer Офис (Москва) СБЕР — работа в составе круглосуточной дежурной смены самого крупного корпоративного SOC в Восточной Европе (3-я линия реагирования). Требования: — опыт промышленной разработки на Python от 3 лет — практический опыт разработки кода с ИИ-агентами: Codex, Gemini, Claude Code, Qwen Code или аналоги — сильные навыки system design: умение спроектировать сервис целиком, выбрать паттерны в…

Channel
Python jobs — вакансии по питону, Django, Flask
@pydevjob
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,549subscribers
+23 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001362026498 |
|---|---|
| Type | Channel |
| Username | @pydevjob |
| Description | Лучшие вакансии для питонистов. По рекламе: @proglib_adv Учиться у нас: https://proglib.io/w/908673cc Для обратной связи: @proglibrary_feeedback_bot Наши каналы: https://t.me/proglibrary/9197 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/pydevjob |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:35 | 9,549 | +16 |
| 9 Aug 2026, 17:03 | 9,533 | +6 |
| 6 Aug 2026, 19:22 | 9,527 | +1 |
| 6 Aug 2026, 13:30 | 9,526 | first reading |
Engagement
24 posts held, back to 21 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.4%
- avg views ÷ 9,549 subscribers
- Avg views / post
- 1,470
- 24 posts measured
- Reaction rate
- 0.131%
- reactions ÷ views · ER floor
- Posts in window
- 24
- of 24 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 10 of 24 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 24 (21 July 2026 – 11 August 2026) |
| Views total | 35,323 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 08:23 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈199
- Videos
- ≈13
- Links
- ≈2,190
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
21 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤔 | 14 | 66.7% | |
| ❤ | 6 | 28.6% | |
| 👍 | 1 | 4.76% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 24 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 21 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
🙂 Python-разработчик от 100 000 до 130 000 ₽ Офис (Екатеринбург) BRANDPOL — международная аккредитованная IT-компания с 20-летней экспертизой в сфере цифровой защиты бизнеса. Требования: — Уверенное знание Python и опыт коммерческой разработки от 2-3 лет. — Опыт работы с backend-фреймворками: FastAPI, Django, Flask или аналогами. — Понимание принципов ООП, SOLID, REST API, асинхронного программирования. — Опыт рабо…
🤔7
😧 Python-разработчик от 100 000 до 130 000 ₽ Удаленно (Смоленск) Производственная компания «Технолайн» — российский производитель качественной бытовой техники. Требования: - Отличное знание Python; - Хорошая алгоритмическая база; - Знание ООП; - Умение работать в команде. ➡️ Подробнее о вакансии на hh.ru 📍 Навигация: База знаний • Задачи • Собеседования
🤔5❤1
🤗 AI Python Engineer Удаленно (Санкт-Петербург) CRT — IT-компания с 20-летним опытом разработки, понятными процессами и профессиональным менеджментом. Мы работаем с разными IT-проектами и базируемся в Тюмени. Требования: — От 3 лет коммерческой разработки на Python и сильный backend-фундамент — Практический опыт с LLM, RAG или AI-агентами в реальных проектах — Знание async, типизации, тестирования и разработки REST…
❤1
⌨️ Middle Python от 455 962 ₽ Гибрид (Амстердам) YoungCapital NEXT — это нидерландская кадровая компания и агентство по подбору персонала (аутстаффингу и детахеру), специализирующееся на трудоустройстве и профессиональном развитии молодых специалистов в сфере IT, финансов и государственного сектора. Требования: — HBO or university-level thinking and working ability; — At least 3+ years of Python development experie…
❤1
🫣 Lead Python-разработчик Гибрид (Москва) Альфа-Банк — это крупнейший частный универсальный банк в России, основанный в 1990 году. Он входит в список системно значимых кредитных организаций страны и обслуживает десятки миллионов физических и юридических лиц. Требования: — От 5 лет опыта продуктовой разработки; — Глубоко знать Python, микросервисы, контейнеры, K8s, REST, реляционные БД, Git, автотесты и CI/CD; — Име…
❤1
👅 Самое сложное — выбрать не курс, а направление Сегодня хочется разобраться в AI-агентах. Через пару недель появляется задача, где нужны алгоритмы. Потом понимаешь, что неплохо бы освежить Python или математику для Data Science. 🔜 Именно поэтому подписка на обучение многим оказывается удобнее отдельных курсов. Можно спокойно переключаться между темами, когда меняются задачи, а не покупать новую программу каждый ра…
Покупать новый курс каждый раз, когда меняется рабочая задача, — довольно странная механика. Нашли альтернативу 👇
🤨 Python-разработчик Офис (Москва) Сбербанк — крупнейший банк в России, Центральной и Восточной Европе, один из ведущих международных финансовых институтов. Самый дорогой российский бренд и самый сильный банковский бренд в мире по версии Brand Finance. Требования: — опыт промышленной разработки на Python. — глубокое понимание алгоритмов и структур данных. — навыки построения распределённых систем. — знание Linux и …
⌨️ Junior backend-разработчик (Django) Офис (Москва) Х5 — ведущая розничная компания с внушительным портфелем сервисов. Требования: – Опыт коммерческой разработки от 1-го года или наличие интересных пет-проектов. – Понимание принципов работы реляционных баз данных (в нашем случае PostgreSQL) – Навыки работы с Linux – Навыки работы с Git – Понимание, как устроен веб: HTTP, REST, принципы взаимодействия клиента и сер…
❤1
One Day Offer: заходи в команду, которая двигает финансы на терабайтах данных! 🔥 На связи блок «Финансы» в Сбере! Мы строим системы, которые автоматизируют казначейство, риск‑менеджмент, отчётность — и добавляем AI для точных прогнозов. На One Day Offer мы хотим найти коллег сразу в 3 продуктовые команды. Базовый стек и уровень задач одинаковы — выбирай направление по душе: ✔️ BigData: Spark (batch+streaming), сло…
🎯 У разработчика, DevOps-инженера и техлида разные причины задуматься о системной работе с AI-агентами Но цель одна: перейти от случайных удачных запусков к управляемому процессу на реальном проекте — с понятными правилами, ревью, контролем расходов и безопасности ✔️ На курсе «ИИ для разработчиков» участники выстраивают такой процесс на практике: подключают инструменты, задают границы для агента и учатся понимать,…
Showing the 12 most recent of 24 posts we hold for @pydevjob. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 1,159,600 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Python jobs — вакансии по питону, Django, Flask” (@pydevjob), 9,549 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/pydevjob.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.