Telegram RegisterThe public register of Telegram
Telegram profile photo for Local Talent | Developers

Channel

Local Talent | Developers

@local_talent_developers

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,919subscribers

+65 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002169879733
TypeChannel
Username@local_talent_developers
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/local_talent_developers

Growth

7,8547,9217,887.57 August 2026 — 7,854 subscribers8 August 2026 — 7,883 subscribers11 August 2026 — 7,909 subscribers14 August 2026 — 7,902 subscribers17 August 2026 — 7,897 subscribers20 August 2026 — 7,895 subscribers24 August 2026 — 7,896 subscribers27 August 2026 — 7,903 subscribers31 August 2026 — 7,907 subscribers2 September 2026 — 7,921 subscribers7 September 2026 — 7,919 subscribers7,9197 August 20267 September 2026
11 measurements spanning 31 days, net +65. 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 7,844–7,931 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 11:187,919-2
2 Sept 2026, 15:377,921+14
31 Aug 2026, 01:267,907+4
27 Aug 2026, 17:287,903+7
24 Aug 2026, 10:387,896+1
20 Aug 2026, 12:537,895-2
17 Aug 2026, 14:567,897-5
14 Aug 2026, 06:357,902-7
11 Aug 2026, 06:567,909+26
8 Aug 2026, 08:167,883+29
7 Aug 2026, 12:477,854first reading

Engagement

22 posts held, back to 11 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
54.7%
avg views ÷ 7,919 subscribers
Avg views / post
4,330
5 posts measured
Reaction rate
1.04%
reactions ÷ views · ER floor
Posts in window
5
of 22 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 4 of 5 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 August 2026
Posts held22 (11 May 202625 August 2026)
Views total21,660
Reactions total172
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 20:00 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

Video runtime
1h 13m
Average length
1h 13m

Measured directly from 1 video 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

1,451 reactions across 21 posts, in 25 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢33923.4%
🤣23216.0%
😁17912.3%
🤯14810.2%
😭1298.89%
🔥1147.86%
644.41%
👍513.51%
👌362.48%
😐362.48%
👏211.45%
🤔201.38%
🥴201.38%
🗿151.03%
🤪140.965%
🤨80.551%
👀70.482%
😱60.414%
🦄30.207%
🐳20.138%
5 further kinds70.482%

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 21 of the 22 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 1,451 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 11 May 2026 to 25 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

25 Aug 2026, 12:48 UTC≈3,110 views63 reactionsread 28 August 2026
Photo

Зарплата 610 000 у Senior ML-разработчика в Сбере Какой у тебя технический стэк? python, pyspark, fastapi, airflow, dbt, kafka, hadoop Как выглядит твой стандартный рабочий день? С утра 2 дейлика по двум проектам, потом работа, иногда синки оперативные Как ты оцениваешь культуру компании или коллектив? С этим все максимально ок Что больше всего нравится в компании? много денег Что не устраивает в компании? проце

🔥40😁13👏53🙈2

19 Aug 2026, 10:25 UTC≈4,660 views46 reactionsread 28 August 2026

🎉🎉🎉 Оффер на архитектора на 150к$ в год с полной удаленкой на США Формат работы: “Карьерная группа” - наша авторская программа карьерного сопровождения для ИТ и digital специалистов - 94% ИТ и digital специалистов за 3 месяца получают ТОПовые офферы в ИТ в 7 направлениях (product / project management, аналитики, разработчики, 1С, С-level позиции: СРО, РМО, СТО, СОО, ССО) от таких компаний как AVITO, Яндекс, Т-банк,

😐22🤣116🔥4👍2💯1

19 Aug 2026, 10:24 UTC≈4,140 views26 reactionsread 28 August 2026
Photo

Photo, posted without a caption

🔥15🤔53😁2🤣1

17 Aug 2026, 10:34 UTC≈4,630 views37 reactionsread 28 August 2026
Photo

Зарплата 506 333 у Senior ML-разработчика в VK Какой у тебя технический стэк? Python, Java, SQL Как выглядит твой стандартный рабочий день? Работаю в среднем с 9-17/19 в зависимости от загруженности. В дни, когда дежурю могу подключаться уже в позднее время для решения вопросов. По задачам это: 1. Аналитика А/Б тестов, делаю какие-нибудь запросы в SQL 2. Пишу продуктовый код на Java 3. Ставлю новые А/Б 4. Хожу на в

🔥19👀75👏3🤔3

13 Aug 2026, 13:13 UTC≈5,120 viewsread 28 August 2026

Как сделать рынок прозрачнее? Заполните нашу анонимную анкету в Local Talent , расскажите про ЗП и то, как проходит ваш рабочий день. Поделитесь мнением о компании: что нравится, что хотелось бы изменить? Кстати, вопросов стало меньше)) Делитесь анкетой с коллегами и знакомыми, чтобы потом обсудить их анкеты здесь)) 🔗 Заполнить анкету можно по ссылке.

31 Jul 2026, 14:09 UTC≈6,780 views15 reactionsread 28 August 2026
Video

🟢Запись эфира "Технический скрининг или МОК-собес с ИТ рекрутером" В ходе собеседования разобрали: - Общие вопросы, которые с вероятностью 90% вам зададут на собесе • ТОП 3 причины, почему вы заваливаете самый первый - он же типа самый легкий этап - Ключевые вопросы по техничке, к которым надо быть готовым - Ну и конечно по базе пройдемся - что на рынке труда, какие ЗП, что с hh, как ИТ рекрутеры своих жертв находят

🔥6😁4👍32

29 Jul 2026, 13:20 UTC≈6,070 views12 reactionsread 28 August 2026
Photo

🔥 ЭФИР. Технический скрининг или МОК-собес с ИТ рекрутером. Будет супер полезно: разрабам, аналитикам,архитекторам, СТО и техническим менеджерами, в т.ч. delivery и engineering Уже в этот четверг. 19:00 по мск В ходе собеседования разберем: - Общие вопросы, которые с вероятностью 90% вам зададут на собесе • ТОП 3 причины, почему вы заваливаете самый первый - он же типа самый легкий этап - Ключевые вопросы по техни

🔥53👍2🥴1😱1

14 Jul 2026, 14:08 UTC≈8,100 views61 reactionsread 28 August 2026
Photo

Зарплата 375 000 у Senior Бэкенд-разработчика в Х5 Tech Бонусы и дополнительные плюшки в компании ДМС со стоматологией Сколько часов в день в среднем занимают встречи? до 1 часа Сколько часов в день в среднем работаешь над задачами? Не считая встреч 6-8 часов Какой у тебя технический стэк? python/fastapi Как выглядит твой стандартный рабочий день? утром закругляюсь по вчерашним таскам, дальше дейлик, после дейли

👌33👍15😢7🔥51

7 Jul 2026, 13:20 UTC≈7,840 views227 reactionsread 28 August 2026
Photo

Зарплата 80 000 у Middle Fullstack-разработчика Бонусы и дополнительные плюшки в компании Ничего нет Сколько часов в день в среднем занимают встречи? 1-2 часа Сколько часов в день в среднем работаешь над задачами? Не считая встреч 4-6 часов Какой у тебя технический стэк? TS, JS, Node.js, Vue, LLM, RAG, OCR Как выглядит твой стандартный рабочий день? Продолжаю задачи, над которыми работал накануне. В течение дня

🤯148🤣32😭30😐10😱3😁21💔1

26 Jun 2026, 11:14 UTC≈7,580 views76 reactionsread 28 August 2026
Photo

Зарплата 412 500 у Team Lead Бэкенд-разработчика в Cбере Бонусы и дополнительные плюшки в компании все перечисленное Сколько часов в день в среднем занимают встречи? 4-6 часов Сколько часов в день в среднем работаешь над задачами? Не считая встреч 4-6 часов Какой у тебя технический стэк? смешанный Как выглядит твой стандартный рабочий день? в 8 на месте, до девяти совместный кофе со смолтолками, в девять начинае

😢4016👏9😁6🤨3🔥1🦄1

24 Jun 2026, 11:50 UTC≈6,340 views29 reactionsread 28 August 2026

🎉🎉🎉 Оффер на функционального архитектора 1С на 460к + премии - кейс нашего подписчика Формат работы: “Карьерная группа” - наша авторская программа карьерного сопровождения для ИТ и digital специалистов - 94% ИТ и digital специалистов за 3 месяца получают ТОПовые офферы в ИТ в 7 направлениях (product / project management, аналитики, разработчики, 1С, С-level позиции: СРО, РМО, СТО, СОО, ССО) от таких компаний как AVI

🤣25🤔21🔥1

24 Jun 2026, 11:49 UTC≈6,350 views17 reactionsread 28 August 2026
Photo

Photo, posted without a caption

🔥12👏4😁1

Showing the 12 most recent of 22 posts we hold for @local_talent_developers. 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.

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.

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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“Local Talent | Developers” (@local_talent_developers), 7,919 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/local_talent_developers.

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.