Ищем Senior BI-разработчика / аналитика – Apache Superset, HR Проектная работа: завершить три HR-дашборда птицефабрики и довести их до приёмки заказчиком: – Списочная численность – Движение и текучесть персонала – Переработки Что нужно сделать – Изучить материалы, уточнить требования и оценить объём работ – Согласовать HR-метрики и самостоятельно разработать SQL-витрины и бизнес-логику расчётов с учётом кадровой ис…

Channel
Data Science Jobs
@datascienceml_jobs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
21,625subscribers
+693 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001601022378 |
|---|---|
| Type | Channel |
| Username | @datascienceml_jobs |
| Description | админ - @workakkk @ai_machinelearning_big_data - Machine learning @itchannels_telegram - 🔥лучшие ит-каналы @pythonl - Python @pythonlbooks- python книги📚 @datascienceiot - ml книги📚 РЕЕСТР РКН: clck.ru/3Fmrbd |
| Created | Between 1 November 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 | 5 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/datascienceml_jobs |
Topic
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 20 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 18:17 | 21,625 | +14 |
| 4 Nov 2026, 21:14 | 21,611 | +7 |
| 3 Nov 2026, 22:10 | 21,604 | -1 |
| 2 Nov 2026, 20:20 | 21,605 | +6 |
| 1 Nov 2026, 17:45 | 21,599 | -13 |
| 31 Oct 2026, 20:28 | 21,612 | +11 |
| 30 Oct 2026, 20:38 | 21,601 | +1 |
| 29 Oct 2026, 19:10 | 21,600 | +9 |
| 28 Oct 2026, 19:41 | 21,591 | +2 |
| 27 Oct 2026, 16:46 | 21,589 | -2 |
| 26 Oct 2026, 18:17 | 21,591 | +1 |
| 25 Oct 2026, 15:29 | 21,590 | +2 |
| 24 Oct 2026, 14:56 | 21,588 | +3 |
| 23 Oct 2026, 17:15 | 21,585 | +12 |
| 22 Oct 2026, 14:49 | 21,573 | +110 |
| 21 Oct 2026, 10:50 | 21,463 | +21 |
| 20 Oct 2026, 05:38 | 21,442 | +8 |
| 19 Oct 2026, 04:06 | 21,434 | +29 |
| 18 Oct 2026, 05:56 | 21,405 | +32 |
| 17 Oct 2026, 04:06 | 21,373 | first reading |
Engagement
81 posts held, back to 23 June 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 74 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 12.4%
- avg views ÷ 21,625 subscribers
- Avg views / post
- 2,690
- 22 posts measured
- Reaction rate
- 0.337%
- reactions ÷ views · ER floor
- Posts in window
- 22
- of 81 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 18 of 22 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 81 (23 June 2026 – 6 November 2026) |
| Views total | 59,094 |
| Reactions total | 171 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 15:55 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
- 50
- Videos
- 3
- Links
- 528
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 53s
- Average length
- 27s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
683 reactions across 69 posts, in 27 distinct kinds. The most used accounts for 37.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🖕 | 253 | 37.0% | |
| 💊 | 104 | 15.2% | |
| 🤣 | 101 | 14.8% | |
| ❤ | 60 | 8.78% | |
| 😁 | 40 | 5.86% | |
| 👍 | 36 | 5.27% | |
| 🔥 | 21 | 3.07% | |
| 🥴 | 21 | 3.07% | |
| 🤔 | 12 | 1.76% | |
| 🤨 | 6 | 0.878% | |
| 😡 | 5 | 0.732% | |
| ❤🔥 | 3 | 0.439% | |
| 🍌 | 3 | 0.439% | |
| 🐳 | 3 | 0.439% | |
| 😍 | 2 | 0.293% | |
| 🥰 | 2 | 0.293% | |
| ✍ | 1 | 0.146% | |
| 🌭 | 1 | 0.146% | |
| 👏 | 1 | 0.146% | |
| 💘 | 1 | 0.146% | |
| 7 further kinds | 7 | 1.02% |
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 73 of the 81 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 773 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 81 most recent posts we hold, published 23 June 2026 to 6 November 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.
Advertising
- Ad load
- 11.1%
- 9 of 81 posts carry an ad marker
- Regulatory tokens
- 9
- posts carrying an erid · 9 distinct tokens
- Median views · ads
- 2,670
- over 9 measured posts
- Median views · rest
- 3,030
- over 72 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VSb5yHYHXY | 1 | 17 September 2026 | 17 September 2026 |
| 2VtzqujpVeT | 1 | 31 August 2026 | 31 August 2026 |
| 2Vtzqv48qtp | 1 | 16 September 2026 | 16 September 2026 |
| 2VtzqvvSNRk | 1 | 5 November 2026 | 5 November 2026 |
| 2VtzqwmU2gs | 1 | 19 August 2026 | 19 August 2026 |
| 2VtzqwzhWdT | 1 | 14 October 2026 | 14 October 2026 |
| 2VtzqxEGaWg | 1 | 28 September 2026 | 28 September 2026 |
| 2W5zFHUC8ad | 1 | 14 August 2026 | 14 August 2026 |
| 2W5zFJSkT7P | 1 | 15 September 2026 | 15 September 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 81 most recent posts we hold, published 23 June 2026 to 6 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 22 posts held from the last 30 days (4.55%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Data Scientist Fast Track: с 9 по 15 ноября ⚡️ Пройдите все этапы отбора в Авито в ускоренном формате и получите оффер за неделю! Почему именно фаст-трек? 🔸совмещённые этапы 🔸все даты известны заранее 🔸классная возможность оценить свои скилы 🔸результаты закрепляются на год Кого мы ждём? — кандидатов с опытом работы от 3,5 лет в крупных российских и международных IT-, BigTech- и FinTech-компаниях — с опытом полного…
👍2🤣1
📄 Backend-разработчик (Middle / Middle+) Компания - AИ МОП 💰 удаленно · полная занятость 💎 AI МОП делает голосовых ИИ-агентов, которые сами разговаривают с клиентами и продают. Здесь backend работает с живыми звонками: ошибка в коде может оставить клиента без звука или запустить повторный звонок. 📌 Задачи: - развивать сервисы на Python и FastAPI в большом продукте с несколькими командами - поддерживать телефонию: …
Технократия Data Engineer 🌍 Казань (релокация) Мы создаём финтех-продукты для рынков, где формируется будущее финансовых технологий. Работаем на международных проектах, совмещая скорость стартапов с надёжностью enterprise-разработки. Чем предстоит заниматься? • Проектировать и поддерживать интеграцию источников данных (взаимодействие с процессинговыми системами и Автоматизированной Банковской Системой / АБС); • Орг…
💊3❤1
Разработать ML-решение, которое аффектит сразу на миллионы пользователей и на бизнес? Это в Ozon Tech. Ребята как раз запустили Fast Track для некоторых вакансий — все этапы собесов займут до 5 дней. Куда можно пройти побыстрее: – в команду ранжирования, совершенствовать поисковую выдачу – в команду рекомендаций, развивать логику и точность ранжирования – в команду нейросеток, улучшать и масштабировать модели – в ко…
🤔5❤1👍1
#вакансия #seniordataengineer #ETL #миграция #ApacheSpark #PySpark #Airflow #NiFi #Kafka #Hadoop #Hive #Greenplum #ClickHouse #Oracle #PostgreSQL #SQL #телеком #удаленка #data #инженерияданных #ETLмиграция #ИП #проектнаяработа #Grafana #Prometheus #S3 #биллинг #highload Позиция: Senior Data Engineer (ETL-миграция) ЗП: 250 000 - 270 000 на руки Занятость: Полная Формат работы: Удаленный Локация: РФ, часовой пояс МСК …
🤨6💊3👍1😡1😭1
#senior #300k #удаленка IT-Implant Data Scientist (Middle+/Senior) от 260 000 до 290 000 ₽ за месяц, на руки Опыт работы: 3–6 лет Полная занятость График: 5/2 Формат работы: удалённо ☑️ Чем предстоит заниматься -Формулировать и декомпозировать бизнес-задачи в ML/аналитические решения -Проводить исследовательский анализ данных, проверять гипотезы и выбирать подходящие методы -Разрабатывать и валидировать модели: кла…
💊19❤3👍1🔥1
🚀 ВАКАНСИЯ | COLLECTION ANALYST Abc Staff ищет сильного Analyst для международного fintech-проекта. 🌍 Рассматриваем кандидатов, находящихся только за пределами РФ и готовыми работать по времени Индии. География не ограничена — важна возможность работать в международном формате. Что важно: ▪️ уверенный SQL и самостоятельная работа с данными; ▪️ умение анализировать данные, делать выводы и находить точки для оптим…
❤2👍2💊2🔥1
Привет! Это команда Cloud․ru ❤️ Мы участвуем в рейтинге работодателей от hh.ru и будем очень рады твоей поддержке. Верим, что работа должна быть не только про задачи и результаты, но и про людей. Если тебе близок такой подход и хочется, чтобы человекоцентричных компаний становилось больше, будем благодарны за твой голос! Поддержать нас просто: 1. Нажми «Голосовать» на лендинге рейтинга. 2. Войди в аккаунт hh.ru. 3…
😡4😍2❤1❤🔥1👍1🤔1😁1
Вакансия DA/DE в Альфа-Инсайт. Вендорсакая ставка. Требования: • Опыт работы от 2-х лет на позициях DA/DE в области DWH/BI. ➡️Обязательные hard skills: - Практический опыт работы с Apache Spark — ключевое требование - Продвинутое знание SQL: сложные joins, оконные функции, CTE, агрегации, подзапросы и оптимизация запросов. - Опыт оптимизации Spark-задач и SQL-запросов на больших объемах данных. - Опыт работы с S3 -…
👍1🔥1
#вакансия #fulltime #удаленка #Senior Локация: РФ Формат: Удаленно Период: долгосрок Занятость: фуллтайм Оформление по договору с ИП Оплата: от 1200 рублей в час до 1500 рублей в час Applied Scientist / MLOps Engineer (Обезличивание данных / Privacy AI) Чем предстоит заниматься (Ключевые задачи): 1. Развитие классификатора данных для полей БД (Tabular ML) Развитие существующей ML-модели (RandomForest), которая выя…
🤣20💊5❤1👏1
🧩 Data Pipeline Engineer @ Higgsfield AI Higgsfield AI — самая быстрорастущая AI-компания в истории. За 18 месяцев с запуска наша команда достигла $1B ARR, а 133 сотрудника уже стали долларовыми миллионерами. Ты можешь стать следующим. Что предлагаем: ⚡️ Высоконагруженные распределённые системы и отказоустойчивые пайплайны сбора данных 🔬 Работа рядом с ML-командой над задачами для AI-продукта 🎯 Ответственность за р…
💊15😁4🥴1
Showing the 12 most recent of 81 posts we hold for @datascienceml_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.
Posts recorded as deleted after publishing
We recorded 4 posts on @datascienceml_jobs as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 16 August 2026
- Most recent seen missing
- 3 November 2026
- Median time before seen missing
- 9 days
- Seen missing in the last 30 days
- 2
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@ai_machinelearning_big_data · 276,2004 postsAndroid разработка
@android_its · 4,8664 postsBig Data AI
@bigdatai · 18,3514 postsC++ Academy
@cpluspluc · 15,4644 postsАнализ данных (Data analysis)
@data_analysis_ml · 51,9294 postsМатематика Дата саентиста
@data_math · 14,4174 postsDevOps
@DevOPSitsec · 23,8724 postsАнглийский для программистов
@english_forprogrammers · 8,2454 postsGameDev Pulse
@GameDEV · 4,3594 postsGolang
@Golang_google · 40,4794 postsHaskell
@haskell_tg · 5934 postsJavascript
@javascriptv · 16,6974 postsLinux Academy
@linuxacademiya · 28,6534 postsKali Linux
@linuxkalii · 55,8264 postsMachine learning Interview
@machinelearning_interview · 30,5814 postsIT мемы | Мемы программиста
@memes_prog · 6,2264 postsМобильная разработка
@mobdevelop · 3,8474 postsPHP Academy
@phpshka · 9,1574 postsPython вопросы с собеседований
@python_job_interview · 24,9284 postsPython/ django
@pythonl · 58,3734 postsReact JS
@react_tg · 16,0804 postsRust
@rust_code · 9,1434 postsData Science. SQL hub
@sqlhub · 36,0524 postsИскусственный интеллект. Высокие технологии
@vistehno · 70,2234 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
- 3
- 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
- 3
- vacant every time we have ever looked
@datascienceml_jobs named 3 handles 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 12 posts, 8 August 2026 – 5 November 2026
named in 12 posts, 8 August 2026 – 5 November 2026
named in 10 posts, 8 August 2026 – 29 September 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@odsjobs · 14,549#1
@datasciencejobs · 22,544#2
@machinelearning_interview · 30,581#3
@ai_machinelearning_big_data · 276,200#4
@datajob · 15,107#5
@data_secrets · 95,989#6
@dev_connectablejobs · 29,046#7
@data_analysis_ml · 51,929#8
@not_boring_ds_jobs · 9,407#9
@not_boring_ds · 12,077#10
@datajobschannel · 12,605#11
@foranalysts · 37,758#12
@opento_data · 7,753#13
@machinelearning_ru · 18,350#14
@python_djangojobs · 15,130#15
@data_secrets_career · 7,384#16
@bigdatai · 18,351#17
@datafeeling · 14,205#18
@dealerAI · 17,075#19
@airi_research_institute · 13,960#20
@python_job_interview · 24,928#21
@sqlhub · 36,052#22
@datascjobs · 5,740#23
@start_ds · 11,471#24
@datascienceiot · 42,540#25
@pythonl · 58,373#26
@dsproglib · 18,299#27
@dataanlitics · 6,385#28
@zarplatnik_analytics · 11,699#29
@phystechcareerchannel · 7,610#30
@machinelearning_books · 16,969#31
@ds_interview_lib · 4,462#32
@ml4value · 5,678#33
@devsp · 19,680#34
@data_science_winners · 3,365#35
@zarubezhom_jobs · 106,258#36
@dreamdatajob · 1,426#37
@complete_ai · 7,880#38
@mashkka_ds · 5,302#39
@ml_data_science_job · 2,330#40
@hr_itwork · 11,125#41
@tagir_analyzes · 11,660#42
@data_hr · 11,150#43
@datajob_io · 882#44
@pro_python_code · 12,322#45
@ArtificialIntelligencedl · 16,826#46
@aihubvk · 2,483#47
@sberlogabig · 8,018#48
@datastorieslanguages · 3,854#49
@ml_inside · 4,080#50
@de_rabota · 5,223#51
@renat_alimbekov · 6,290#52
@dzis_science · 2,193#53
@rockyourdata · 23,686#54
@chad_protocol · 12,277#55
@ds_problems_lib · 3,970#56
@KarpovCourses · 27,307#57
@cryptovalerii · 32,021#58
@data_math · 14,417#59
@ai_newz · 98,218#60
@deep_school · 10,724#61
@seeallochnaya · 81,039#62
@vacancy_cs · 18,389#63
@yandexforml · 19,130#64
@ebaresearch · 5,380#65
@tech_priestess · 15,111#66
@boris_again · 17,967#67
@senior_augur · 8,357#68
@hrlunapark · 20,975#69
@new_yorko_times · 10,702#70
@llm_under_hood · 30,121#71
@nadlskom · 5,149#72
@postypashki_old · 47,060#73
@zheltyi_ai · 9,371#74
@rybolos_channel · 19,138#75
@grokaem_seby · 2,756#76
@researchoshnaya · 2,463#77
@DevOPSitsec · 23,872#78
@kantor_ai · 12,215#79
@blog_toxa · 4,362#80
@datafest · 8,850#81
@gernar228 · 5,698#82
@reliable_ml · 6,610#83
@denissexy · 140,405#84
@nodatanogrowth · 12,777#85
@neural · 11,729#86
@python_testit · 6,875#87
@pseudolabeling · 4,493#88
@neural_prosecco · 8,418#89
@toBeAnMLspecialist · 10,870#90
@knowledge_accumulator · 5,686#91
@vistehno · 70,223#92
@ml_jobs_kz · 11,217#93
@DataKatser · 2,185#94
@CVML_team · 6,118#95
@dl_stories · 15,546#96
@stuffyNLP · 6,720#97
Read from Telegram’s recommendation API, most recently 24 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@datasciencejobs · 22,544
Telegram ranks this channel #6 of 93 here — alongside 92 others — read 21 September 2026
@foranalysts · 37,758
Telegram ranks this channel #7 of 96 here — alongside 95 others — read 1 September 2026
@machinelearning_interview · 30,581
Telegram ranks this channel #9 of 98 here — alongside 97 others — read 7 September 2026
@data_analysis_ml · 51,929
Telegram ranks this channel #11 of 93 here — alongside 92 others — read 25 August 2026
@sqlhub · 36,052
Telegram ranks this channel #13 of 87 here — alongside 86 others — read 2 September 2026
@python_job_interview · 24,928
Telegram ranks this channel #14 of 90 here — alongside 89 others — read 15 September 2026
@datascienceiot · 42,540
Telegram ranks this channel #15 of 76 here — alongside 75 others — read 29 August 2026
@devsp · 19,680
Telegram ranks this channel #16 of 91 here — alongside 90 others — read 30 September 2026
@pythonl · 58,373
Telegram ranks this channel #22 of 84 here — alongside 83 others — read 22 August 2026
@dev_connectablejobs · 29,046
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 10 September 2026
@ai_machinelearning_big_data · 276,200
Telegram ranks this channel #24 of 95 here — alongside 94 others — read 10 August 2026
@job_python · 23,412
Telegram ranks this channel #36 of 96 here — alongside 95 others — read 19 September 2026
@remotejun · 26,799
Telegram ranks this channel #44 of 98 here — alongside 97 others — read 12 September 2026
@young_june · 78,833
Telegram ranks this channel #49 of 99 here — alongside 98 others — read 20 August 2026
@data_secrets · 95,989
Telegram ranks this channel #56 of 98 here — alongside 97 others — read 17 August 2026
@KarpovCourses · 27,307
Telegram ranks this channel #63 of 96 here — alongside 95 others — read 10 September 2026
@DevOPSitsec · 23,872
Telegram ranks this channel #66 of 90 here — alongside 89 others — read 18 September 2026
@relocateme · 34,638
Telegram ranks this channel #68 of 89 here — alongside 88 others — read 3 September 2026
@vistehno · 70,223
Telegram ranks this channel #72 of 94 here — alongside 93 others — read 20 August 2026
@dataflair · 18,615
Telegram ranks this channel #81 of 83 here — alongside 82 others — read 4 October 2026
@hrlunapark · 20,975
Telegram ranks this channel #83 of 88 here — alongside 87 others — read 28 September 2026
@yandexforml · 19,130
Telegram ranks this channel #90 of 96 here — alongside 95 others — read 4 October 2026
@stepik_courses · 28,924
Telegram ranks this channel #92 of 93 here — alongside 92 others — read 16 September 2026
This channel appears in 23 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Data Science Jobs” (@datascienceml_jobs), 21,625 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/datascienceml_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.