Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear word for word on 2 other registered channels. They sit inside a group of 4 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 25 comparable posts for this entry, running 31 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 4, the earliest publisher we hold is @p_rabota. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
15 measurements spanning 16 days, net +130. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 22,471–22,640 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
21 Aug 2026, 19:04
22,620
+6
19 Aug 2026, 16:53
22,614
+11
18 Aug 2026, 19:47
22,603
+10
17 Aug 2026, 19:27
22,593
+13
16 Aug 2026, 15:09
22,580
+5
14 Aug 2026, 20:35
22,575
+11
13 Aug 2026, 11:17
22,564
+4
12 Aug 2026, 13:15
22,560
+8
11 Aug 2026, 15:03
22,552
+9
10 Aug 2026, 11:37
22,543
+4
9 Aug 2026, 09:51
22,539
+7
8 Aug 2026, 05:52
22,532
+21
7 Aug 2026, 05:26
22,511
+16
6 Aug 2026, 08:10
22,495
+5
6 Aug 2026, 03:51
22,490
first reading
Engagement
65 posts held, back to 31 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 41 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
8.75%
avg views ÷ 22,620 subscribers
Avg views / post
1,980
65 posts measured
Reaction rate
0.142%
reactions ÷ views · ER floor
Posts in window
65
of 65 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 56 of 65 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 22 August 2026
Posts held
65 (31 July 2026 – 22 August 2026)
Views total
128,703
Reactions total
160
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 20:40 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
≈237
Videos
≈20
Links
≈4,630
Lifetime counters from Telegram’s own channel header, read 22 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
152 reactions across 45 posts, in 4 distinct kinds. The most used accounts for 54.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤔
83
54.6%
❤
63
41.4%
👍
4
2.63%
🔥
2
1.32%
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 56 of the 65 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 160reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 65 most recent posts we hold, published 31 July 2026 to 22 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.
Telegram Stars
Stars received
2
across the posts below
Posts paid on
2
of 65 we hold a reading for · 3%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @job_python. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 65 most recent posts we hold for this entry, published 31 July 2026 to 22 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
1.54%
1 of 65 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
2,410
over 1 measured post
Median views · rest
1,990
over 64 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
CQH36pWzJqVHzWjqgX1Pf5K1kqC6xMXmfgBYmHHPJF8bL8
1
17 August 2026
17 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 65 most recent posts we hold, published 31 July 2026 to 22 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
#middle #офис #краснодар #ростов
АВТОФОРМУЛА
Python-разработчик
Опыт работы: Python от 4 лет в коммерческой разработке
Формат работы: Краснодар, Ростов-на-Дону
ГК «Автоформула» — крупный федеральный специализированный маркетплейс по торговле автомобильными товарами. Лидирующие позиции на рынке запасных частей для автомобилей в России более 20 лет.
☑️ Чем предстоит заниматься
-Разработка Python-сервисов для аналити…
#middle #гибрид #офис
Яндекс
Python-разработчик в Yandex DataLens
Опыт работы: от 3 лет
Формат работы: гибридный или офис (Санкт-Петербург, Москва)
DataLens — облачный сервис визуализации и анализа данных. Широко используется как внутри Яндекса, так и за его пределами: в составе платформы Yandex Cloud. Ядро сервиса разрабатывается в опенсорсе.
☑️ Чем предстоит заниматься
-Строить гибкий API для решения задач анали…
#senior #удаленка #москва
ИТ-компания «Лоция»
Python-разработчик
Опыт работы: коммерческая бэкенд-разработка от 4 лет
Формат работы: можно удалённо (Москва)
Проект: AI-платформа нового поколения. Миссия — спроектировать и внедрить экосистему для комплексного управления большими языковыми моделями (LLM).
☑️ Чем предстоит заниматься
-Самостоятельная разработка функционала платформы на Python
-Тестирование нового фун…
⭐️ Стажер Python Developer (FastAPI)
Описание:
MISE - динамично развивающаяся компания в сегменте HoReCa. Создаём современные цифровые решения для ресторанов и лаунджей. У нас ценят инициативу, поддерживают развитие и всегда открыты к новым талантам. Сейчас в поисках команды стажеров.
Вилка: 50000 - 60000р/мес
Локация/Гражданство: РФ
Опыт: Без опыта
✨ Обязанности
• Разрабатывать REST API и серверную логику на Fast…
#middle #удаленка
Далее
ML-инженер
Формат работы: можно удалённо
Далее — один из крупнейших независимых digital-продакшнов в России, работает с 2005 года, в штате более 550 человек. Ищет ML-инженера в команду, которая реализует AI-решения для проектов компании.
☑️ Чем предстоит заниматься
-Поддерживать текущие алгоритмические решения
-Проектировать и внедрять AI-агентов (LLM, GPT-like модели) в различные процессы
…
#senior #гибрид #удаленка
X5 Tech
Senior Python Developer
Опыт работы: от 5 лет
Формат работы: гибрид или удалённо по России
X5 Tech — ИТ-подразделение X5 Group, управляющей сетями «Пятёрочка», «Перекрёсток» и «Чижик».
☑️ Чем предстоит заниматься
-Проектирование и разработка мобильных и веб-приложений, сервисов с использованием современных фреймворков (Django, Flask, FastAPI)
-Работа с базами данных: создание, опт…
#intern #удаленка #офис
Авито
Стажировка для разработчиков (направление Backend, Python)
Стажировка 9 месяцев, старт октябрь 2026, от 25 часов в неделю
Формат работы: удалённо или очно (Москва, Санкт-Петербург, Казань, Самара, Нижний Новгород)
AvitoTech — оплачиваемая программа стажировок для студентов 2–4 курса бакалавриата. Большинство бэкенд-команд Авито работают на Go, но в некоторых основной язык — Python, и д…
#middle #удаленка #data
OZON
Data Engineer, Ozon fresh
Опыт работы: в роли Data engineer от 2 лет
Формат работы: удалённая работа
Ozon fresh — сервис быстрой доставки свежих продуктов питания, товаров повседневного спроса, бытовой техники, электроники. Ищем Data engineer в группу товародвижения в отдел Data Science.
☑️ Чем предстоит заниматься
-Писать алгоритмы обработки больших данных (несколько сотен миллионов с…
#senior #офис #москва
Bell Integrator
Python Developer (AI, ML, Москва)
Опыт работы: коммерческая разработка на Python от 3 лет
Формат работы: Москва
Bell Integrator — крупный системный интегратор страны, аккредитованная ИТ-компания. Команда внедряет AI-агентов для проактивной диагностики маркетинговых показателей, поиска неочевидных взаимосвязей и генерации рекомендаций.
☑️ Чем предстоит заниматься
-Проектировать…
#junior #офис
ПАО Сбербанк
Junior Python-разработчик (стажировка)
Можно без опыта
Формат работы: офис (Москва, м. Кутузовская)
Разработка и поддержка Python-скриптов и микросервисов для интеграции AI-инструментов в банковские процессы. Стажировка 3 месяца с возможностью продления или перехода в штат.
☑️ Чем предстоит заниматься
-Разработка и поддержка Python-скриптов и микросервисов для интеграции AI-инструментов …
#middle #200k #удаленка
ООО «М-ТЕХ»
Python / LLM Engineer: RAG и ИИ-агенты
до 200 000 ₽
Опыт работы: коммерческая разработка на Python от 2–3 лет
Неполный рабочий день
Формат работы: можно удалённо (Москва, Санкт-Петербург, Самара)
ООО «М-ТЕХ» — динамично развивающаяся ИТ-компания, развивающая направление ИИ-автоматизации: прикладные LLM/RAG-решения и ИИ-агенты для процессов малого и среднего бизнеса.
☑️ Чем предс…
#senior #удаленка
VK
Ведущий Python-разработчик в Единые облачные технологии
Формат работы: удалённо
Сервисы VK работают бесперебойно благодаря сетевой инфраструктуре. Команда пишет инструменты автоматизации для ввода оборудования в работу, конфигурирования множества устройств и выполнения типовых задач на оборудовании.
☑️ Чем предстоит заниматься
-Писать код, тесты, планировать и создавать архитектуру
-Выполнять …
❤1
Showing the 12 most recent of 65 posts we hold for @job_python. 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 — 53,248 of 1,584,142entries 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 13 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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Однажды в трендах @trendo · 68,975 Telegram ranks this channel #34 of 90 here — alongside 89 others — read 20 August 2026
[PYTHON:TODAY] @python2day · 63,879 Telegram ranks this channel #36 of 91 here — alongside 90 others — read 21 August 2026
Python/ django @pythonl · 58,935 Telegram ranks this channel #42 of 84 here — alongside 83 others — read 22 August 2026
Young & Junior - вакансии IT @young_june · 71,900 Telegram ranks this channel #43 of 99 here — alongside 98 others — read 20 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 August 2026 — this
entry's latest reading, not the date you are reading this.
“Python Job | Вакансии | Стажировки” (@job_python), 22,620 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/job_python.
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.