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 3 other registered channels. They sit inside a group of 5 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 13 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 24 comparable posts for this entry, running 30 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 5, the earliest publisher we hold is @young_june. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, 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 4 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.
35 measurements spanning 44 days, net +2,352. 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 59,079–62,137 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
18 Sept 2026, 12:17
61,784
+90
16 Sept 2026, 06:57
61,694
+123
14 Sept 2026, 13:17
61,571
+88
13 Sept 2026, 02:41
61,483
+37
11 Sept 2026, 06:56
61,446
+260
8 Sept 2026, 11:41
61,186
+195
5 Sept 2026, 07:15
60,991
+135
3 Sept 2026, 10:06
60,856
+121
2 Sept 2026, 01:44
60,735
+43
1 Sept 2026, 03:05
60,692
+58
31 Aug 2026, 04:36
60,634
+39
30 Aug 2026, 07:25
60,595
+31
29 Aug 2026, 03:54
60,564
+102
28 Aug 2026, 01:16
60,462
+128
27 Aug 2026, 00:43
60,334
+15
26 Aug 2026, 04:04
60,319
+63
25 Aug 2026, 05:13
60,256
+24
24 Aug 2026, 00:56
60,232
+59
22 Aug 2026, 10:57
60,173
+35
21 Aug 2026, 03:07
60,138
first reading
Engagement
140 posts held, back to 30 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 103 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
4.03%
avg views ÷ 61,784 subscribers
Avg views / post
2,490
87 posts measured
Reaction rate
0.098%
reactions ÷ views · ER floor
Posts in window
87
of 140 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 49 of 87 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 21 September 2026
Posts held
140 (30 July 2026 – 21 September 2026)
Views total
216,680
Reactions total
122
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Sept 2026, 03:45 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
≈1,280
Videos
≈33
Links
≈4,120
Lifetime counters from Telegram’s own channel header, read 22 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.
Video runtime
8s
Average length
4s
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
177 reactions across 62 posts, in 6 distinct kinds. The most used accounts for 63.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
112
63.3%
🔥
36
20.3%
🆒
18
10.2%
👍
4
2.26%
👏
4
2.26%
🤝
3
1.69%
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 90 of the 140 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 183 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 140 most recent posts we hold, published 30 July 2026 to 21 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
1.43%
2 of 140 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
2,730
over 2 measured posts
Median views · rest
2,600
over 138 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
2SDnjcd9GCK
1
9 August 2026
9 August 2026
2VtzquYYjSC
1
7 September 2026
7 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 140 most recent posts we hold, published 30 July 2026 to 21 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.
Подборка для джунов
Стажёр:
- Разработчик .NET (Стажер) в Лоция
Junior:
- Junior Manual QA в DevCasi
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Совет на ближайшие годы — идите в Data Science и ML
Пока ИИ забирает работу у одних специалистов, другие строят на нём карьеру и зарабатывают всё больше. И вопрос уже не в том, изменит ли ИИ рынок, а в том, по какую сторону этих изменений окажетесь вы. DS/ML – один из самых прямых способов оказаться среди тех, кто на этом выигрывает
А чтобы не тратить годы на хаотичное обучение – держите в подписках Data Portal. Та…
Стажёр инженер по тестированию / Ozon Tech
🗺 Москва.
Обязанности:
- Проводить ручное тестирование
Требования:
- Обучение на технической специальности бакалавриата или магистратуры на данный момент
➡ Откликнуться
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Подборка для джунов
Стажёр:
- Intern Business Analyst в ПСБ
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Подборка для джунов
Стажёр:
- Business Analyst Intern в МТС
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Junior Frontend Developer / Рукомах
100k - 120k RUB в месяц
Обязанности:
- Разработка и поддержка пользовательских интерфейсов на React и Next.js
- Интеграция фронтенда с REST API и GraphQL
- Работа с дизайн-макетами в Figma
- Ведение кода в Git
Требования:
- Опыт работы с React и Next.js
- Знание TypeScript
- Понимание REST API и GraphQL
- Владение Git
➡ Откликнуться
Вакансии │ Стажировки │ За рубежом │ Удалёнка…
Подборка для джунов
Стажёр:
- Intern Product Manager в Яндекс
- Стажёр DevOps в Сбер
- Intern SQL Analyst в ПСБ
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Подборка для джунов
Стажёр:
- Стажер Swift/Kotlin разработчик в МТС
- Системный аналитик (стажёр) SDK в ПАО Сбербанк
- Стажёр DevOps инженер по автоматизации в ПАО Сбербанк
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Junior QA (manual) / TG @GameDev_and_Tech_vacancy
Обязанности:
- Следить за качеством игрового проекта на всех этапах
- Создавать и поддерживать тестовую документацию (чек-листы, тест-кейсы)
Требования:
- Оконченные курсы по тестированию ПО
- Интерес к AI и желание развиваться в этой области
➡ Откликнуться
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи …
Подборка для джунов
Стажёр:
- Стажер направления антифрод и информационная безопасность в X5
- Стажер бизнес-аналитик в МТС
- Стажёр Golang-разработчик в BelesAI
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИГТЕХ │ Мероприятия │ По всему миру │ IT и DIGITAL
🐣 Софи - первый ai ассистент для автооткликов и поиска работы.
Стажёр менеджер проектов / Альфа-Банк
🗺 Москва.
Обязанности:
- Помогать команде вести проекты и инициативы по развитию зарплатных проектов для клиентов малого и микробизнеса
- Работать с показателями продаж, собирать и структурировать информацию по проектам
Требования:
- Студент 3–4 курса, выпускник или магистрант
- Готов работать 40 часов в неделю
➡ Откликнуться
Вакансии │ Стажировки │ За рубежом │ Удалёнка │ БИ…
Как сопроводительное письмо влияет на приглашение на интервью?
На основе 1162 пользователей и 179771 отклика.
Сейчас будет интересно...
1. Персонализированный сопровод под вакансию приводит на 28% процентов больше реакцию / действий в следующий этап.
2. Самое интересно - Персонализированный сопровод увеличивает вероятность приглашение на интервью на 53%.
Это данные по 40.000 откликов.
Но самое главное мы пока н…
Showing the 12 most recent of 140 posts we hold for @yuniorapp. 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.
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.
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.
Handles this channel named that no longer answer
Dead references
2
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
2
vacant every time we have ever looked
@yuniorapp named 2 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.
@schools_hack_arc named in 3 posts, 9 September 2026 – 11 September 2026
@formfactor named in 2 posts, 30 August 2026 – 31 August 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.
Remocate: релокация, удалёнка, работа и вакансии @evacuatejobs · 135,729#1
Read from Telegram’s recommendation API, most recently 22 August 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.
New directions: вакансии и стажировки @newdirections · 46,900 Telegram ranks this channel #2 of 95 here — alongside 94 others — read 27 August 2026
Remocate: релокация, удалёнка, работа и вакансии @evacuatejobs · 135,729 Telegram ranks this channel #2 of 93 here — alongside 92 others — read 13 August 2026
Job for Junior @jobforjunior · 85,036 Telegram ranks this channel #4 of 99 here — alongside 98 others — read 18 August 2026
IT - стажировки и обучение @it_interns · 31,464 Telegram ranks this channel #5 of 97 here — alongside 96 others — read 6 September 2026
Changellenge >>: стажировки и вакансии @offervacancy · 38,199 Telegram ranks this channel #5 of 97 here — alongside 96 others — read 1 September 2026
Young & Junior - вакансии IT @young_june · 73,984 Telegram ranks this channel #5 of 99 here — alongside 98 others — read 20 August 2026
Remote Junior (INFLOW) @remotejun · 26,495 Telegram ranks this channel #6 of 98 here — alongside 97 others — read 12 September 2026
junojobs → стажировки в IT @juno_jobs · 31,343 Telegram ranks this channel #6 of 96 here — alongside 95 others — read 6 September 2026
Эйч Вакансии @hcareers_jobs · 40,472 Telegram ranks this channel #6 of 98 here — alongside 97 others — read 30 August 2026
Авоська — junior IT вакансии/cтажировки @jobs_juniors_remote · 29,353 Telegram ranks this channel #7 of 95 here — alongside 94 others — read 9 September 2026
A-Teams | Карьера @huggabletalents · 129,409 Telegram ranks this channel #7 of 96 here — alongside 95 others — read 13 August 2026
Норм работа @normrabota · 135,835 Telegram ranks this channel #7 of 99 here — alongside 98 others — read 13 August 2026
Вакансии с зп выше 50 тысяч @Well_paid_Job · 44,867 Telegram ranks this channel #8 of 87 here — alongside 86 others — read 28 August 2026
МИР КРЕАТОРОВ | Вакансии @mirkreatorovjob · 70,233 Telegram ranks this channel #8 of 96 here — alongside 95 others — read 20 August 2026
Вакансии в образовании @edujobs · 65,852 Telegram ranks this channel #9 of 99 here — alongside 98 others — read 21 August 2026
Джуниор Вакансии Стажировки IT @juniors_rabota_jobs · 67,854 Telegram ranks this channel #9 of 96 here — alongside 95 others — read 21 August 2026
СЕТИ — IT & Digital вакансии @it_vakansii_jobs · 95,470 Telegram ranks this channel #9 of 95 here — alongside 94 others — read 16 August 2026
Russian Speaking Jobs @rusukrjobs · 25,577 Telegram ranks this channel #10 of 95 here — alongside 94 others — read 14 September 2026
Аптуми (up to me) @uptume · 27,437 Telegram ranks this channel #10 of 92 here — alongside 91 others — read 10 September 2026
FutureToday @futru · 35,942 Telegram ranks this channel #10 of 99 here — alongside 98 others — read 2 September 2026
Young Стажёр - стажировки ИТ @young_intern · 44,235 Telegram ranks this channel #11 of 94 here — alongside 93 others — read 29 August 2026
Работа в медиа @dddwork · 106,205 Telegram ranks this channel #12 of 97 here — alongside 96 others — read 15 August 2026
Вакансии за рубежом @remote_jobs_relocate · 32,844 Telegram ranks this channel #13 of 95 here — alongside 94 others — read 5 September 2026
Рабочий Парк: вакансии, стажировки, волонтёрские программы @south_work · 131,865 Telegram ranks this channel #13 of 94 here — alongside 93 others — read 13 August 2026
This channel appears in 84 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.
Domains linked from posts
5 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“Юниор: стажировки и вакансии для молодых специалистов” (@yuniorapp), 61,784 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yuniorapp.
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.