Backend Developer (Python / Scraping Product) в компанию CyberYozh Международная, быстрорастущая экосистема компаний в сфере кибербезопасности, образования и технологий. Основные проекты представлены на cyberyozh.com. 📝 Обязанности - Разработка, тестирование и интеграция API-функционала для продуктов экосистемы. - Работа с бэкенд-частью скрапинг-инфраструктуры: управление задачами парсинга, обработка и отдача собра…

Channel
Python Вакансии & Работа
@YotolabPython
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,452subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002616587099 |
|---|---|
| Type | Channel |
| Username | @YotolabPython |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/YotolabPython |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 01:58 | 1,452 | -2 |
| 18 Aug 2026, 23:53 | 1,454 | +7 |
| 15 Aug 2026, 15:45 | 1,447 | -4 |
| 11 Aug 2026, 18:02 | 1,451 | -1 |
| 7 Aug 2026, 22:01 | 1,452 | no change |
| 7 Aug 2026, 16:08 | 1,452 | first reading |
Engagement
20 posts held, back to 24 March 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.6%
- avg views ÷ 1,452 subscribers
- Avg views / post
- 227
- 2 posts measured
- Reaction rate
- 2.73%
- reactions ÷ views · ER floor
- Posts in window
- 2
- of 20 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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (24 March 2026 – 6 August 2026) |
| Views total | 454 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 22:01 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.
Reaction mix
78 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 25.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 20 | 25.6% | |
| 👎 | 16 | 20.5% | |
| 🤡 | 15 | 19.2% | |
| ❤ | 9 | 11.5% | |
| 💩 | 6 | 7.69% | |
| 😁 | 5 | 6.41% | |
| 🤔 | 2 | 2.56% | |
| 🤨 | 2 | 2.56% | |
| 👍 | 1 | 1.28% | |
| 🔥 | 1 | 1.28% | |
| 🤬 | 1 | 1.28% |
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 14 of the 20 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 78reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 March 2026 to 6 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
AI-разработчик (Python/Go) в AdTech-компанию под NDA Компания строит инструменты для digital-маркетинга и автоматизации в сфере арбитража трафика. Код пишется с помощью AI-агентов через интеграцию в рабочий процесс. 📝 Обязанности - Разработка backend-сервисов с использованием AI-агентов (Claude Code, Codex и др.) для ускорения работы - Проектирование и реализация интеграций с внешними API (рекламные сети, трекеры, …
🤡6❤1
🐍 Python-разработчики, нужен ваш технический взгляд! Мы только запустили Racing Rodeo — автомобильную карточную игру внутри Telegram Mini App. Сейчас хотим проверить игру на реальных пользователях, найти ошибки и получить честную обратную связь. Особенно интересно мнение Python-разработчиков: ⚙️ корректно ли работает игровая логика; 🌐 нет ли ошибок при загрузке и обмене данными; 🏁 стабильно ли проходят гонки и сох…
Python-разработчик Junior (интеграционные решения) в финтех компанию (NDA) 📝 Обязанности - Разработка интеграционных решений для платежных систем. - Работа с FastAPI (RESTful, аутентификация, обработка ошибок). - Работа с PostgreSQL/MySQL, NoSQL (MongoDB, Redis). - Документирование и code review. 🔍 Требования - Опыт интеграции сторонних сервисов в продукт будет большим плюсом, но не обязательно - Python 1+ год, HTT…
❤1
Tech Lead (Python + React / Vue / Next.js + AI) в компанию ApexPlay 📝 Обязанности - Разработка и архитектура (60% времени): — Писать код на Python (FastAPI / Django) для бэкенда. — Закрывать фронтенд-задачи на React / Vue / Next.js (админки, простые интерфейсы, интеграция с Telegram Mini Apps). — Проектировать архитектуру микросервисов под высокие нагрузки (десятки тысяч пользователей). — Работать с PostgreSQL, Redi…
Python Backend Developer — Senior / Tech Lead (CTO проекта) в технологический стартап Стартап на стадии MVP разрабатывает продукт с использованием современных Python-технологий. 📝 Обязанности - Проектирование и развитие архитектуры backend-сервисов; - Интеграция backend и frontend, проектирование REST API; - Техническое лидерство: code review, менторство, формирование стандартов разработки; - Принятие финальных тех…
😁2
Lead Backend Developer в компанию PaySol Основное направление деятельности — разработка и развитие собственной CRM системы. 📝 Обязанности - Проектирование и развитие архитектуры проектов, принятие ключевых технических решений. - Работа с командой: performance и код-ревью, декомпозиция задач. - Разработка микросервисов, передача кода разработчикам, код-ревью. - Участие в DevOps-процессах: CI/CD, контейнеризация, инф…
Senior Python/Django Developer в компанию CyberYozh CyberYozh — образовательные и инструментарные платформы в сфере кибербезопасности и анонимности онлайн. Международная компания с 11-летним опытом на рынке. 📝 Обязанности - Разработка, тестирование и интеграция функционала. - Участие в планировании задач и предложение улучшений. - Поддержка стабильности и сопровождение решений. - Взаимодействие с другими командами …
🤡3
Middle+/Senior Python Developer в компанию Омега Солюшнс Омега Солюшнс — международный проект, связанный с разработкой высоконагруженных систем и обработкой больших объемов данных для заказчика из США и ЕС. 📝 Обязанности - Разработка и поддержка backend-сервисов на Python - Работа с веб-приложениями на Django и FastAPI - Разработка решений для обработки больших объемов данных - Оптимизация производительности высоко…
🤣2🤨2🤬1
MlOps / Python Backend Engineer (ML) в компанию Selecty 📝 Обязанности - Продуктизация и внедрение ML-моделей в production; - Рефакторинг кода от DS-команд под production-стандарты; - Разработка backend-сервисов и REST API для ML-решений; - Интеграция сервисов через Kafka и микросервисную архитектуру; - Участие в построении и развитии ML-пайплайнов; - Взаимодействие с DS, MLOps и аналитиками; - Участие в архитектурны…
👍1
Middle Fullstack Developer (Python + React) в компанию ИП Мы развиваем ERA2.ai и аналогичные продукты — это агрегаторы нейросетей для русскоязычного рынка. 🔍 Требования Backend (опыт от 2 лет): - Python 3.8+, FastAPI, asyncio, SQLAlchemy, Alembic - PostgreSQL, Redis - Celery - Docker, Git, GitHub Actions, Nginx, CI/CD - Prometheus + Grafana - REST, WebSockets - pytest, Poetry, Linux - Опыт декомпозиции монолитов на…
🤡6😁3❤2
Python-разработчик в компанию Soft Media Group Soft Media Group — IT-компания с государственной аккредитацией. 📝 Обязанности - Разработка веб браузерной игры на Python FastAPI + ReactJS; - Оптимизация, поддержка новых или существующих проектов. 🔍 Требования - Опыт коммерческой разработки на FastAPI от 1 года; - Опыт работы с PostgreSQL или другой реляционной БД; - Понимание принципов ООП, Solid и паттернов проекти…
👎8
Showing the 12 most recent of 20 posts we hold for @YotolabPython. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@YotolabPython named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Python Вакансии & Работа” (@YotolabPython), 1,452 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/YotolabPython.
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.