12 May 2026, 07:12 UTCviews —
Python_Jobs pinned Deleted message
Channel
Python_Jobs
@Pythonist_Jobs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,317subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001730459309 |
|---|---|
| Type | Channel |
| Username | @Pythonist_Jobs |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/Pythonist_Jobs |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 17:24 | 1,317 | -2 |
| 24 Aug 2026, 17:16 | 1,319 | +1 |
| 21 Aug 2026, 03:08 | 1,318 | +2 |
| 18 Aug 2026, 08:42 | 1,316 | -1 |
| 15 Aug 2026, 18:57 | 1,317 | -2 |
| 12 Aug 2026, 11:44 | 1,319 | +2 |
| 9 Aug 2026, 17:21 | 1,317 | -2 |
| 7 Aug 2026, 03:53 | 1,319 | no change |
| 6 Aug 2026, 23:17 | 1,319 | first reading |
Engagement
20 posts held, back to 8 December 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 4 | 80.0% | |
| 👍 | 1 | 20.0% |
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 4 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 5reactions 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 8 December 2025 to 12 May 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
30 Mar 2026, 14:24 UTC≈1,030 views2 reactionsread 6 August 2026
Добрый день! Коротко о проекте: Мы разрабатываем приложение для удобного и, самое главное, легального вывода криптовалюты на банковские карты. Занятость: - Полная / Частичная, только удаленная работа. Мы ищем: - Node.js + TypeScript разработчика. - и / или - Python разработчика. Необходимые навыки: - Знание баз данных PostgreSQL - Опыт работы с API и интеграциями - Опыт работы с криптовалютами и б…
👍1👎1
7 Mar 2026, 15:22 UTC892 viewsread 6 August 2026
Ищу frontend/fullstack - разработчиков уровня middle в команду активно развивающихся проектов TrueSpace и SWOIS Нужны люди, которые хотят делать интересный и качественный продукт. Идейные люди! Frontend: - TypeScript, Next.js + React и/или Vue + Nuxt, Tailwind CSS, Zod Backend: - TypeScript, опыт с любым бэкенд-фреймворком на JS/TS (Express, Fastify, Hono, Nitro и т.д.) - SQL, PostgreSQL, умение работать с ORM/que…
14 Feb 2026, 12:00 UTC705 viewsread 6 August 2026
Python Developer Компания: РТК-ЦОД Зарплата: Не указана Тип занятости: Почему Python Developer никогда не теряет время? Потому что он всегда следит за своим кодом! Подробнее: https://telegra.ph/Python-Developer-02-14-4 #python
14 Feb 2026, 07:00 UTC563 viewsread 6 August 2026
Full Stack Developer (JavaScript / Node.js / Python) Компания: ООО TECHIFY Зарплата: Не указана Тип занятости: Ищем Full Stack Developer, чтобы вы могли стать волшебником! Кодите на JavaScript, Node.js и Python — превращайте баги в фичи и читайте мысли пользователей (особенно, когда они забыли пароли). Если вы умеете делать приложения такие же красивые, как утренний кофе, и надежные, как тетя Валя на семейных пр…
13 Feb 2026, 17:00 UTC440 viewsread 6 August 2026
Стажер-Тестировщик ПО (Автоматизатор) Компания: Itransition Зарплата: Не указана Тип занятости: Хотите проверить, как много ошибок можно найти в коде, не находя своих шнурков? Мы ищем стажера-тестировщика ПО! Ваши обязанности: искать баги так, как будто это сокровища, и автоматизировать тесты так, чтобы роботы завидовали вашим навыкам. Мы обеспечим вас всем необходимым: кофе, настольными играми и надеждой, что о…
13 Feb 2026, 12:00 UTC377 viewsread 6 August 2026
Аналитик клиентской эффективности Компания: ООО HeadHunter::Бизнес аналитики Зарплата: Не указана Тип занятости: Почему клиентская эффективность не ездит на такси? Потому что она всегда ищет оптимальный маршрут! Подробнее: https://telegra.ph/Analitik-klientskoj-ehffektivnosti-02-13 #python
13 Feb 2026, 07:00 UTC365 views1 reactionsread 6 August 2026
Senior Backend Python Engineer Компания: KARIMBERDIYEV ALIJON TOJIDDIN O‘G‘LI Зарплата: Не указана Тип занятости: Почему у Senior Backend Python Engineer такая высокая зарплата? Потому что они пишут код, а не истории! Подробнее: https://telegra.ph/Senior-Backend-Python-Engineer-02-13 #python
👎1
12 Feb 2026, 17:00 UTC312 viewsread 6 August 2026
Middle+ Backend-разработчик (Python/FastAPI) Компания: ООО Киго Зарплата: Не указана Тип занятости: Почему мы не берем Junior? Они не успевают за нашим FastAPI! Подробнее: https://telegra.ph/Middle-Backend-razrabotchik-PythonFastAPI-02-12 #python
17 Jan 2026, 07:00 UTC582 views1 reactionsread 6 August 2026
IT specialist Компания: ООО RECURO Зарплата: от 300 до 500 $ за месяц до вычета налогов Тип занятости: Почему IT specialist всегда носит с собой розетку? Чтобы не отключаться от работы! Подробнее: https://telegra.ph/IT-specialist-01-17-2 #python
👎1
20 Dec 2025, 12:00 UTC682 views1 reactionsread 6 August 2026
Data analyst / Аналитик данных (стажер) Компания: Aston Зарплата: от 90 000 до 100 000 ₽ за месяц до вычета налогов Тип занятости: Почему стажер-аналитик всегда с собой имеет лупу? Потому что данные нужно рассмотреть с максимальным вниманием! Подробнее: https://telegra.ph/Data-analyst--Analitik-dannyh-stazher-12-20 #python
👎1
16 Dec 2025, 07:00 UTC597 viewsread 6 August 2026
Python-разработчик Компания: Сбер для экспертов Зарплата: Не указана Тип занятости: Почему Python-разработчики всегда в хорошем настроении? Они знают, как обрабатывать исключения! Подробнее: https://telegra.ph/Python-razrabotchik-12-16-2 #python
Showing the 12 most recent of 20 posts we hold for @Pythonist_Jobs. 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,187,090 of 1,628,524entries 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.
Mentions
Named by 1 registered channel — 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Python_Jobs” (@Pythonist_Jobs), 1,317 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Pythonist_Jobs.
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.