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

Channel

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

@ya_jobs

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

32,803subscribers

+361 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
DescriptionАктуальные вакансии для разработчиков в Яндекс Папка с каналами Яндекса для разработчиков: https://t.me/addlist/Hrq31w2p1vUyOGZi Все вакансии для разработчиков: https://ya.cc/t/t9Tlu_e74DqkMQ Номер заявления в РКН: 4962644000
Created17 August 2020 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/ya_jobs

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 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.

Growth

32,44132,80332,6226 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 subscribers19 August 2026 — 32,527 subscribers20 August 2026 — 32,540 subscribers21 August 2026 — 32,548 subscribers22 August 2026 — 32,566 subscribers24 August 2026 — 32,570 subscribers25 August 2026 — 32,578 subscribers26 August 2026 — 32,584 subscribers27 August 2026 — 32,591 subscribers28 August 2026 — 32,603 subscribers28 August 2026 — 32,597 subscribers30 August 2026 — 32,604 subscribers31 August 2026 — 32,603 subscribers31 August 2026 — 32,602 subscribers2 September 2026 — 32,623 subscribers3 September 2026 — 32,637 subscribers5 September 2026 — 32,664 subscribers8 September 2026 — 32,693 subscribers11 September 2026 — 32,708 subscribers13 September 2026 — 32,718 subscribers16 September 2026 — 32,725 subscribers19 September 2026 — 32,756 subscribers25 September 2026 — 32,803 subscribers6 August 202625 September 2026
34 measurements spanning 50 days, net +361. 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,387–32,857 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
25 Sept 2026, 04:4132,803+47
19 Sept 2026, 00:1932,756+31
16 Sept 2026, 12:4032,725+7
13 Sept 2026, 04:4232,718+10
11 Sept 2026, 04:1632,708+15
8 Sept 2026, 07:5432,693+29
5 Sept 2026, 01:3832,664+27
3 Sept 2026, 09:3332,637+14
2 Sept 2026, 02:4532,623+21
31 Aug 2026, 23:2832,602-1
31 Aug 2026, 01:0732,603-1
30 Aug 2026, 02:1632,604+7
28 Aug 2026, 23:4732,597-6
28 Aug 2026, 01:0332,603+12
27 Aug 2026, 00:3532,591+7
26 Aug 2026, 03:0232,584+6
25 Aug 2026, 06:2732,578+8
24 Aug 2026, 05:5532,570+4
22 Aug 2026, 17:0832,566+18
21 Aug 2026, 07:1832,548first reading

Engagement

152 posts held, back to 29 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.70%
avg views ÷ 32,803 subscribers
Avg views / post
1,870
77 posts measured
Reaction rate
0.106%
reactions ÷ views · ER floor
Posts in window
77
of 152 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 50 of 77 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 25 September 2026
Posts held152 (29 July 2026 – 25 September 2026)
Views total143,903
Reactions total101
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 07:06 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
≈704
Videos
≈103
Links
≈5,620

Lifetime counters from Telegram’s own channel header, read 26 September 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

214 reactions across 76 posts, in 10 distinct kinds. The most used accounts for 47.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10247.7%
👍3817.8%
🔥3817.8%
😁146.54%
👎83.74%
🤩52.34%
🤔41.87%
🤬20.935%
🤯20.935%
😱10.467%

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

Measured over the 152 most recent posts we hold, published 29 July 2026 to 25 September 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
0.658%
1 of 152 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,790
over 1 measured post
Median views · rest
2,040
over 151 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
eridPostsFirst seenLast seen
CQH36pWzJqE1dR7FuZ8VXKQnZsv3AXmjHd4tnmJikBC6yK114 September 202614 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 152 most recent posts we hold, published 29 July 2026 to 25 September 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

25 Sept 2026, 15:03 UTC871 viewsread 26 September 2026

🙂 NLP-разработчик в команду качества претрейна Alice LLM Ищем ML-разработчика, который будет улучшать качество претрейна Alice AI LLM. Это направление, отвечающее за умность базовой модели и качество данных. Какие задачи вас ждут: • Эксперименты с претрейн-моделями Ставить и анализировать вычислительно тяжёлые эксперименты с претрейн-стадией. Проверять гипотезы об источниках прироста ризонинг-способностей внутри р…

25 Sept 2026, 12:05 UTC≈1,130 viewsread 26 September 2026

🍔 Аналитик промоэффективности в Яндекс Еду Привет! Мы работаем над тем, чтобы пользователи Яндекс Еды были довольны и оставались с нами: используем промоакции и меняем продукт, чтобы развивать бизнес. Сейчас мы ищем аналитика промоэффективности. Эта роль подойдёт тому, кому интересно совершенствовать клиентские механики и ставить эксперименты. Антон Рябченко, руководитель службы аналитики роста Промо — один из ключ…

25 Sept 2026, 09:03 UTC≈1,280 views3 reactionsread 26 September 2026

❤️ SRE в Поиск Поиском Яндекса пользуются сотни миллионов пользователей, сотни тысяч ядер обрабатывают миллиарды запросов в сутки, а некоторые микросервисы держат десятки миллионов RPS, обрабатывая петабайты горячих данных. Такой масштаб и критичность накладывает серьёзные требования на надёжность. Наша команда работает над всей инфраструктурой основного веб-поиска и поиска по картинкам. Мы ищем SRE, способных внедр…

🔥3

24 Sept 2026, 15:02 UTC≈1,530 views2 reactionsread 26 September 2026
Photo

📕 Станьте экспертом на курсе Яндекс Практикума В Яндекс Практикуме мы обучаем цифровым профессиям в лучших традициях Яндекса: с технологиями и поддержкой экспертов. В обучении студентов сопровождают наставники. 📌 Что делает наставник? Помогает студентам на протяжении обучения: отвечает на вопросы, проводит воркшопы и Q&A-сессии, направляет и поддерживает. Сейчас ищем действующих разработчиков на роль наставника ср…

❤1👎1

24 Sept 2026, 12:04 UTC≈1,580 views1 reactionsread 26 September 2026

📦 Разработчик на Java в команду контентной платформы Маркета Привет! Мы развиваем сервисы, от которых зависит, как устроен каталог и как товары отображаются на витрине. В нашей зоне ответственности — десятки тысяч категорий и параметров, более 2 млрд карточек и около 2 тыс. изменений групп карточек каждую секунду. Алексей Тришин, руководитель службы разработки контентной платформы Сейчас мы строим микросервисную ар…

😁1

24 Sept 2026, 09:04 UTC≈1,630 viewsread 26 September 2026

❣️ ML-разработчик в Международный Поиск Если какая-то технология приносит деньги, то она быстро становится сложносочинённой. Реклама в Яндексе как раз такая — одна из самых технологически сложных систем. Мы работаем на международном рынке рекламы, у нас весь рекламный стек свой. В команде можно и нужно крутить все части современной рекламной системы: кандидатогенерацию, предсказатели, рекомендации. Мы хотим улучшит…

23 Sept 2026, 15:02 UTC≈1,690 views4 reactionsread 26 September 2026

🖤 Аналитик-разработчик в команду разметки и анализа данных Фантеха Привет! Меня зовут Лёша Царёв, и я руковожу командой разметки и анализа данных в Фантехе Яндекса. Наша команда занимается самыми разными задачами в области дата-майнинга для контентных сервисов, а именно Яндекс Музыки, Кинопоиска, Яндекс Книг и т. д. Я ищу аналитика-разработчика, который поможет нам сделать рекомендации и поиск в наших сервисах лучше…

👍4

23 Sept 2026, 12:01 UTC≈1,610 views2 reactionsread 26 September 2026

❤️ Аналитик (KPI-сессии) в команду аналитики поиска Наша команда отвечает за прогнозирование и анализ ключевых KPI поискового продукта. Ищем аналитика, которому интересно работать на стыке продукта, бизнеса и данных. Важно понимать, что стоит за изменениями метрик, задавать правильные вопросы и объяснять результаты понятным языком. Какие задачи вас ждут: • Анализировать отклонения от прогноза Вы будете декомпозиро…

❤1👍1

23 Sept 2026, 09:02 UTC≈1,680 views2 reactionsread 26 September 2026

🤍 Руководитель группы разработки Arcanum в DevTools Привет, я Тимур, руководитель службы инструментов репозитория. Мы создаём инструменты, которыми инженеры Яндекса пользуются для разработки. Вы поможете нам вывести надёжность и удобство нашей платформы на новый уровень. Если вам близка миссия улучшать жизнь разработчиков — вам точно к нам. Тимур Торубаров, руководитель службы инструментов репозитория Наша команда …

❤1👎1

22 Sept 2026, 15:00 UTC≈1,890 views0 reactionsread 26 September 2026

🙂Инженер данных в отдел аналитики Alice AI Наша команда разрабатывает базовую технологию, которая лежит в основе Алисы, Нейропоиска, Нейробраузера и многих других продуктов — большую языковую модель Alice AI. Мы также учим модель работать с агентами. Ещё мы создаём инфраструктуру бенчмарков, чтобы измерять, насколько новая версия модели лучше предыдущих версий и продуктов конкурентов. Какие задачи вас ждут • Разви…

22 Sept 2026, 12:01 UTC≈1,830 viewsread 26 September 2026

🚕 Руководитель группы моделирования симуляционной сцены в Автономный транспорт Чтобы эффективно оценивать качество релизов ПО беспилотного автомобиля, в Яндексе разработали систему симуляции. Она позволяет проанализировать поведение авто в виртуальном окружении, оценить влияние внешних и внутренних факторов на поведение автономного транспорта и предсказать последствия выбранного поведения. Какие задачи вас ждут • …

22 Sept 2026, 09:00 UTC≈1,850 viewsread 26 September 2026

🖤 ML-разработчик в Рекламу Мы умеем на лету генерировать персонализированные тексты рекламных объявлений, адаптируя предложение рекламодателя для пользователей. Внедряем генеративные, дискриминативные и ранжирующие модели в одну из крупнейших рекомендательных платформ. Вы станете работать в команде с сильными исследователями и инженерами, перенимать их опыт и влиять на то, как будет выглядеть реклама в интернете зав…

Showing the 12 most recent of 152 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.

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.

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.

Yandex for Developers
@Yandex4Developers · 28,505
#1
Young&&Yandex
@Young_and_Yandex · 111,329
#2
Yandex for Backend
@yandexforbackend · 10,122
#3
Яндекс
@yandex · 582,624
#4
VK Team
@vkjobs · 25,707
#5
Яндекс Образование
@Education_Yandex · 37,959
#6
AvitoTech
@avitotech · 25,625
#7
Ozon Tech
@ozon_tech · 29,768
#8
ФКН: Вакансии
@vacancy_cs · 16,939
#9
Yandex for ML
@yandexforml · 18,854
#10
T-Crew
@t_crew · 43,385
#11
ТЕХНО: Яндекс про технологии
@techno_yandex · 226,241
#12
Время Валеры
@cryptovalerii · 30,829
#13
Поступашки - ШАД, Стажировки и Магистратура
@postypashki_old · 45,531
#14
Dev & ML Connectable Jobs
@dev_connectablejobs · 27,959
#15
Avito Career
@avito_career · 66,216
#16
Код Желтый
@kod_zheltyi · 33,061
#17
Rozetked
@rozetked · 656,361
#18
Код.ру
@d_code · 406,147
#19
Lamoda Tech
@latech · 10,983
#20
Хабр
@habr_com · 132,465
#21
Как мы делаем Яндекс
@yandexhabr · 3,375
#22
Институт AIRI
@airi_research_institute · 13,654
#23
Yandex for Frontend
@yandex4frontend · 10,858
#24
Алгоритмы - Собеседования, Олимпиады, ШАД
@algoses · 12,070
#25
ИТ-Пикник
@IT_picnic · 23,126
#26
Яндекс нанимает | Вакансии для PM
@ya_jobs_pm · 29,939
#27
Yandex Infrastructure
@yandex_infrastructure · 4,682
#28
ФКН НИУ ВШЭ
@fcs_hse · 14,370
#29
DeepSchool
@deep_school · 10,738
#30
Нескучный Data Science
@not_boring_ds · 12,052
#31
Ozon Tech | Вакансии
@ozon_tech_vacancies · 3,594
#32
Machinelearning
@ai_machinelearning_big_data · 279,417
#33
Data Secrets
@data_secrets · 94,138
#34
Минцифры России
@mintsifry · 234,926
#35
Карьера в Сбере!
@careersber · 136,237
#36
Яндекс Музей
@yandexmuseum · 9,080
#37
Data Science Jobs
@datasciencejobs · 22,137
#38
Yandex Cloud
@yandexcloudnews · 21,888
#39
Злой коллега
@zloy_kollega · 45,024
#40
getmatch: канал про карьеру в IT
@g_jobchannel · 18,874
#41
ML Underhood
@MLunderhood · 4,805
#42
Типичный программист
@tproger · 78,305
#43
vc.ru
@vcnews · 112,033
#44
Connectable Jobs
@zarubezhom_jobs · 103,632
#45
Start Career in DS
@start_ds · 11,495
#46
Техножрица 👩‍💻👩‍🏫👩‍🔧
@tech_priestess · 14,890
#47
МТС Банк | Карьера
@mtsbankcareer · 30,329
#48
Уставший техдир
@tired_glebmikheev · 17,248
#49
Хабр Карьера
@habr_career · 33,171
#50
ecom.tech
@ecomtech_channel · 7,580
#51
CodeCamp
@codecamp · 181,400
#52
Inside Yandex Cloud
@cloud_track · 8,057
#53
Библиотека Go-разработчика | Golang
@goproglib · 24,076
#54
Alfa Digital
@alfadigital_jobs · 54,435
#55
IT Юмор
@ithumor · 60,568
#56
Журнал «Код»
@thecodemedia · 49,237
#57
Chad Protocol - карьера, IT, успех
@chad_protocol · 11,571
#58
🏆 AIeron | Data Feeling
@datafeeling · 14,242
#59
Data jobs feed
@datajobschannel · 12,272
#60
Зарплатник Аналитика
@zarplatnik_analytics · 11,546
#61
Remocate: релокация, удалёнка, работа и вакансии
@evacuatejobs · 135,997
#62
Тагир Анализирует
@tagir_analyzes · 11,702
#63
8БИТ. Журнал Яндекс Образования
@journal_yandex_education · 13,420
#64
Яндекс Практикум. Программирование и анализ данных
@practicumtech · 11,237
#65
Т-Образование
@tbank_education · 113,416
#66
Раньше всех. Ну почти.
@bbbreaking · 1,974,402
#67
ODS #jobs
@odsjobs · 14,059
#68
Медуза — LIVE
@meduzalive · 1,122,482
#69
эйай ньюз
@ai_newz · 96,889
#70
Love. Death. Transformers.
@lovedeathtransformers · 25,677
#71
еба́ные идеи для резерча
@ebaresearch · 5,333
#72
Сиолошная
@seeallochnaya · 79,594
#73
addmeto
@addmeto · 71,835
#74
Эксплойт
@exploitex · 2,041,128
#75
Take Friends to Luna Park
@hrlunapark · 20,296
#76
Avito Team
@TeamAvito · 16,332
#77
Жёлтый AI
@zheltyi_ai · 9,387
#78
Т-Инвестиции
@tb_invest_official · 528,596
#79
Т-Банк
@tbank · 331,521
#80
Denis Sexy IT 🤖
@denissexy · 137,325
#81
Нескучный Data Science Jobs
@not_boring_ds_jobs · 9,120
#82
Phystech.Career
@phystechcareerchannel · 7,254
#83
Kantor.AI
@kantor_ai · 12,217
#84
Кинопоиск | Фильмы и сериалы
@kinopoisk · 806,604
#85
New Yorko Times
@new_yorko_times · 10,554
#86
Job for Analysts & Data Scientists
@foranalysts · 36,643
#87
Go jobs — вакансии по Go
@godevjob · 11,278
#88
Data jobs — вакансии по data science, анализу данных, аналитике, искусственному интеллекту
@datajob · 14,805
#89
Media Rare
@media_rare · 25,869
#90
Книжный куб
@book_cube · 15,749
#91
42 секунды
@ftsec · 19,382
#92
Kali Novskaya
@rybolos_channel · 19,011
#93
Golang
@Golang_google · 40,461
#94
Computer Science Abroad
@computerscienceabroad · 4,945
#95
Neural Shit
@NeuralShit · 53,680
#96

Read from Telegram’s recommendation API, most recently 5 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.

Yandex for Developers
@Yandex4Developers · 28,505
Telegram ranks this channel #3 of 94 here — alongside 93 others — read 9 September 2026
VK Team
@vkjobs · 25,707
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 13 September 2026
Хабр Карьера
@habr_career · 33,171
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 4 September 2026
Young&&Yandex
@Young_and_Yandex · 111,329
Telegram ranks this channel #10 of 92 here — alongside 91 others — read 14 August 2026
Яндекс Образование
@Education_Yandex · 37,959
Telegram ranks this channel #12 of 96 here — alongside 95 others — read 31 August 2026
T-Crew
@t_crew · 43,385
Telegram ranks this channel #12 of 95 here — alongside 94 others — read 29 August 2026
Журнал «Код»
@thecodemedia · 49,237
Telegram ranks this channel #14 of 97 here — alongside 96 others — read 25 August 2026
Поступашки - ШАД, Стажировки и Магистратура
@postypashki_old · 45,531
Telegram ranks this channel #17 of 90 here — alongside 89 others — read 28 August 2026
Злой коллега
@zloy_kollega · 45,024
Telegram ranks this channel #18 of 98 here — alongside 97 others — read 28 August 2026
Яндекс нанимает | Вакансии для PM
@ya_jobs_pm · 29,939
Telegram ranks this channel #20 of 98 here — alongside 97 others — read 8 September 2026
AvitoTech
@avitotech · 25,625
Telegram ranks this channel #21 of 96 here — alongside 95 others — read 14 September 2026
Ozon Tech
@ozon_tech · 29,768
Telegram ranks this channel #22 of 98 here — alongside 97 others — read 8 September 2026
Avito Career
@avito_career · 66,216
Telegram ranks this channel #22 of 98 here — alongside 97 others — read 21 August 2026
Код Желтый
@kod_zheltyi · 33,061
Telegram ranks this channel #23 of 96 here — alongside 95 others — read 4 September 2026
Яндекс
@yandex · 582,624
Telegram ranks this channel #23 of 96 here — alongside 95 others — read 9 August 2026
ТЕХНО: Яндекс про технологии
@techno_yandex · 226,241
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 11 August 2026
Карьера в Сбере!
@careersber · 136,237
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 13 August 2026
Yandex Cloud
@yandexcloudnews · 21,888
Telegram ranks this channel #32 of 97 here — alongside 96 others — read 22 September 2026
Яндекс Практикум
@yndx_practicum · 34,046
Telegram ranks this channel #36 of 97 here — alongside 96 others — read 3 September 2026
Ozon Team
@ozonteam · 22,918
Telegram ranks this channel #42 of 89 here — alongside 88 others — read 19 September 2026
Data Science Jobs
@datasciencejobs · 22,137
Telegram ranks this channel #44 of 93 here — alongside 92 others — read 21 September 2026
МТС Банк | Карьера
@mtsbankcareer · 30,329
Telegram ranks this channel #56 of 99 here — alongside 98 others — read 7 September 2026
Игромир
@Igromir_cloud · 58,836
Telegram ranks this channel #58 of 89 here — alongside 88 others — read 22 August 2026
Т-Образование
@tbank_education · 113,416
Telegram ranks this channel #59 of 91 here — alongside 90 others — read 14 August 2026

This channel appears in 25 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Яндекс нанимает | Вакансии для разработчиков” (@ya_jobs), 32,803 subscribers as measured 25 September 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.