Telegram RegisterThe public register of Telegram
Telegram profile photo for Яндекс нанимает | Вакансии для разработчиков

Channel

Яндекс нанимает | Вакансии для разработчиков

@ya_jobs

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

32,521subscribers

+79 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001165814759
TypeChannel
Username@ya_jobs
Created17 August 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live18 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/ya_jobs

Growth

32,44132,52132,4816 August 2026 — 32,442 subscribers6 August 2026 — 32,441 subscribers7 August 2026 — 32,447 subscribers8 August 2026 — 32,451 subscribers9 August 2026 — 32,453 subscribers10 August 2026 — 32,461 subscribers11 August 2026 — 32,475 subscribers12 August 2026 — 32,485 subscribers14 August 2026 — 32,489 subscribers15 August 2026 — 32,500 subscribers17 August 2026 — 32,510 subscribers18 August 2026 — 32,521 subscribers6 August 202618 August 2026
12 measurements spanning 12 days, net +79. 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 32,429–32,533 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 10:3332,521+11
17 Aug 2026, 09:2432,510+10
15 Aug 2026, 18:2532,500+11
14 Aug 2026, 09:1832,489+4
12 Aug 2026, 22:1332,485+10
11 Aug 2026, 23:2232,475+14
10 Aug 2026, 21:3432,461+8
9 Aug 2026, 18:4332,453+2
8 Aug 2026, 18:1632,451+4
7 Aug 2026, 18:5732,447+6
6 Aug 2026, 17:5132,441-1
6 Aug 2026, 03:3532,442first reading

Engagement

50 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.08%
avg views ÷ 32,521 subscribers
Avg views / post
1,980
50 posts measured
Reaction rate
0.1%
reactions ÷ views · ER floor
Posts in window
50
of 50 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 33 of 50 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held50 (29 July 202617 August 2026)
Views total98,862
Reactions total65
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 00:58 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

63 reactions across 22 posts, in 7 distinct kinds. The most used accounts for 63.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4063.5%
👍914.3%
🔥711.1%
👎23.17%
😁23.17%
🤯23.17%
🤬11.59%

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 33 of the 50 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 65reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 50 most recent posts we hold, published 29 July 2026 to 17 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

17 Aug 2026, 15:02 UTC922 views0 reactionsread 18 August 2026

▶️ Ведущий разработчик / техлид в видеоплатформу Наша команда разрабатывает видеоплатформу, которая помогает множеству команд и продуктов в Яндексе (Кинопоиск, Музыка и др.) решать задачи, связанные с видео. Какие задачи вас ждут: • Проектирование распределённых систем Это роль для человека, который умеет развивать большие распределённые системы, работающие под высокой нагрузкой. Вам предстоит выбирать технологиче

17 Aug 2026, 09:01 UTC≈1,050 views0 reactionsread 18 August 2026
Forwarded from @Yandex4Developers

📕 Обсудили безопасность LLM, конфликты в переговорах и границы вайбкодинга — всё это в новом дайджесте Yandex for Developers 🚙 Куда сходить 🔴 5 сентября — deep tech night. Обсудим переход к генеративным моделям в RecSys, Physical AI, инфраструктуру RL-обучения, облако в эпоху AI, современную архитектуру NPU и другие темы 🔴 9 сентября — Data Dojo. Приглашаем тех, кто уже владеет основами ML и хочет двигаться дальше

16 Aug 2026, 15:02 UTC≈1,490 views1 reactionsread 18 August 2026

✨ Разработчик в команду тасклетов Yandex Infrastructure Тасклеты предоставляют интерфейс на различных языках программирования для запуска приложений в облачных окружениях. Сервис позволяет написать приложение на Python, Go, Java, NodeJS и запускать его в своих процессах автоматизации. Наша команда делает запуск таких приложений надёжнее и эффективнее, а анализ результатов — удобнее и быстрее. Какие задачи вас ждут:

🔥1

16 Aug 2026, 09:00 UTC≈1,430 views2 reactionsread 18 August 2026

🌐 Техлид ML-инфраструктуры в Рекламные технологии Привет! Меня зовут Макс, я руковожу командой ML в продукте OneRec в Директе. Мы создаём систему замера эффекта — инфраструктуру, которая разбивает общий прирост от всех рекомендаций на вклад отдельных изменений в продукт. В основе системы — граф метрик. Он связывает локальные воздействия с юнит-экономикой через причинно-следственные связи. Ещё у нас есть масштабная п

😁2

15 Aug 2026, 15:00 UTC≈1,550 viewsread 18 August 2026

🚕 Старший Android-разработчик в команду Geo Geo — геоплатформа, на которой работает Яндекс Go. Мы отвечаем за всё, что связано с картой и определением местоположения. Именно наш код позволяет водителю найти вас за минуту. Наша команда небольшая. Мы предоставляем столько самостоятельности и ответственности, сколько вы готовы взять на себя. Какие задачи вас ждут: • Разработка фич Вам предстоит вместе с продактом и д

15 Aug 2026, 09:01 UTC≈1,530 views1 reactionsread 18 August 2026

👥 Дата-аналитик в Yandex Crowd Мы работаем с крупнейшими технологичными продуктами экосистемы Яндекса — Алисой AI, Яндекс Путешествиями, Бизнесом, Яндекс ID, Браузером и другими сервисами. Ими каждый день пользуются миллионы людей. Главное направление работы команды — аналитические инструменты, которые повысят эффективность бизнеса. Наша задача — создать лучшую службу поддержки. Она должна быстро помогать пользовате

1

14 Aug 2026, 15:04 UTC≈1,650 views0 reactionsread 18 August 2026

🔎 ML-разработчик в команду Alice AI VLM Reasoning Привет! Я Лёша, руководитель команды Alice AI VLM Reasoning. Мы учим мультимодальные модели рассуждать: понимать документы, графики, таблицы и интерфейсы, аккуратно распознавать текст, а также доводим поведение модели до продуктового качества через RLHF. Если вы хотите драйвить мультимодальный reasoning и RL-алайнмент, работать со сложнейшими задачами на стыке текста

14 Aug 2026, 12:03 UTC≈1,780 views0 reactionsread 18 August 2026

🙃 Middle+/Senior-разработчик на Golang в финтех-стартап внутри экосистемы Яндекс ID ОФП (Оператор финансовых платформ) — финтех-стартап внутри экосистемы Яндекс ID. Мы создаём витрину финансовых продуктов, которая делает доступ пользователя к банковским сервисам простым, безопасным и технологичным. Какие задачи вас ждут: • Построение инфраструктуры с нуля Наши сервисы будут развёрнуты в Yandex Cloud, и впереди у н

14 Aug 2026, 09:03 UTC≈1,740 viewsread 18 August 2026

☁️ Разработчик на Java в команду IAM (Security Yandex Cloud) Ни одна сложная система не может обойтись без модели разграничения доступа. Одна из основных задач команды IAM (Identity & Access Management) — предоставление инструментов для построения таких моделей. Кроме того, наша команда занимается задачами управления доступом, группировки ресурсов, логической изоляции между ними, координации сессий и групп пользоват

13 Aug 2026, 15:04 UTC≈1,850 viewsread 18 August 2026

❤️ Разработчик в команду оптимизации разметок Поиска с Алисой Наша команда развивает поисковую строку с Алисой. Основополагающая часть любого ML — датасеты, и мы отвечаем за ускорение и удешевление процесса их сбора. От этого зависит частота релизов, которые напрямую влияют на пользователей Поиска. Мы работаем с быстро развивающимися продуктами на стыке ML и краудсорсинга. Какие задачи вас ждут: • Встраивание ML-м

13 Aug 2026, 12:04 UTC≈1,800 viewsread 18 August 2026

🔍 Аналитик-разработчик в Автономный транспорт Мы превращаем сложную физическую реальность, в которой существуют автономные роботы, погода, городская логистика, в понятную цифровую экономику. Сейчас направление роботов переходит от R&D-стартапа к масштабному бизнесу. Ищем человека, который поможет нам не просто расти, а расти эффективно. Вам предстоит создавать метрики качества работы операторов удалённого управления

13 Aug 2026, 09:01 UTC≈1,790 viewsread 18 August 2026

❣️ Аналитик-разработчик в Яндекс Кит Привет, меня зовут Макс, я руковожу В2В-аналитикой в Transactional AI. Наши цели — развивать независимый еком и транзакции через Яндекс, быть надёжным партнёром для бизнеса, помогать пользователям быстро находить нужные товары. Год назад мы создали Яндекс Кит — продукт, который позволяет открыть интернет-магазин за неделю. Уже сейчас 2500 магазинов работают на Ките. Нам нужен сил

Showing the 12 most recent of 50 posts we hold for @ya_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 — 403,751 of 1,549,376entries 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.

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 3 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.

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.

Young&&Yandex
@Young_and_Yandex · 110,454
Telegram ranks this channel #10 of 92 here — alongside 91 others — read 14 August 2026
Яндекс
@yandex · 554,668
Telegram ranks this channel #23 of 96 here — alongside 95 others — read 9 August 2026
ТЕХНО: Яндекс про технологии
@techno_yandex · 232,682
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 11 August 2026
Карьера в Сбере!
@careersber · 137,529
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 13 August 2026
Т-Образование
@tbank_education · 111,534
Telegram ranks this channel #59 of 91 here — alongside 90 others — read 14 August 2026

This channel appears in 5 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 18 August 2026 — this entry's latest reading, not the date you are reading this.

“Яндекс нанимает | Вакансии для разработчиков” (@ya_jobs), 32,521 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/ya_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.