Channel
@avral_job
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
53subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001307100954 |
|---|---|
| Type | Channel |
| Username | @avral_job |
| Description | АвралДжоб - поиск (срочно) мест работы и работников. Работа, вакансии, резюме - рынок труда. Кто ищет, тот всегда найдет! Чат: @avral_Jb По вопросам: @Creator_ilja |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/avral_job |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:46 | 53 | no change |
| 7 Aug 2026, 11:12 | 53 | first reading |
15 posts held, back to 4 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 15 posts for this entry, the most recent from 15 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 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.
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.
Должность: Senior Data Scientist Компания: *** Заработная плата: от *** Требования: - Опыт на аналогичной позиции от 3-х лет; - Уверенные знания статистических методов; - Опыт работы с предиктивными алгоритмами (например, XGBoost); - Опыт построения моделей с сотнями тысяч параметров. - Практический подход к решению задач; - Профильное высшее образование; - Желание развиваться как менеджер. Обязанности: - Определит…
👨💻 Data Engineer Гибрид (Москва, Санкт-Петербург) Требования: – Опыт разработки на Go от 4 лет: глубокое понимание языка и опыт написания эффективного кода с акцентом на обработку данных. – Опыт работы с ClickHouse, MySQL и MongoDB. – Понимание принципов работы с Kubernetes. – Опыт разработки HTTP/gRPC API. – Опыт работы с Kafka и Redis.
Наблюдаю тренд, который меня одновременно и печалит, и заставляет задуматься о том, как вообще устроен рынок труда в аналитике В общем, сейчас попасть в российский big-tech аналитиком без опыта — это практически невозможная история. И я понимаю, почему люди продолжают хотеть туда попасть, потому что для карьерного роста различные Яндексы, Авито и Т-Банки — это действительно хорошая школа, где можно научиться работат…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Data Engineer Требования: – Опыт работы инженером данных от 4-5 лет. – Уверенно владеете Python на уровне написания Airflow DAG’ов. – Уверенно владеете SQL на уровне оптимизации запросов. Умеете читать планы запросов и предлагать варианты по улучшению производительности запросов. – Имеете опыт работы с Apache Airflow, знаете принципы построения пайплайнов. – Имеете опыт работы с dbt. – Знаете, что такое MPP (Massi…
Data Analyst Анализ данных и выявление инсайтов из больших датасетов, создание робастных аналитических решений от пайплайнов до дашбордов, написание эффективных SQL-запросов и оптимизация рабочих процессов, визуализация данных в BI-инструментах, кросс-функциональное сотрудничество с UX и маркетинговыми командами. 💼 4+ года опыта Data Analyst/Data Engineer, сильные навыки SQL и Python, опыт с ETL/ELT пайплайнами, зн…
В разработке нельзя предугадать две вещи: сроки и сообразительность юзеров. Change my mind 👉 @seniorFront
Первый рабочий день после праздников
Lead Data Scientist Требования: – Опыт в разработке и внедрении рекомендательных систем и ML-моделей в продакшн от 3 лет. – Глубокое понимание метрик качества рекомендаций, проблем холодного старта, разнообразия и новизны. – Навыки проведения A/B-тестирования и интерпретации результатов. – Уверенное владение Scala/Java и Python. – Знание и понимание принципов работы Spark, Airflow, Hadoop, HDFS, Kafka, Zookeeper,…
Немного базы вам
Showing the 12 most recent of 15 posts we hold for @avral_job. 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 — 1,370,628 of 1,480,944entries 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.
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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“АвралJob” (@avral_job), 53 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/avral_job.
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.