Telegram RegisterThe public register of Telegram
Telegram profile photo for Секретные вакансии в IT и Digital — Sparkles

Channel

Секретные вакансии в IT и Digital — Sparkles

@sparklesjobs

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

8,258subscribers

+167 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002140214987
TypeChannel
Username@sparklesjobs
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/sparklesjobs

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 12 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

8,0908,2588,1746 August 2026 — 8,091 subscribers6 August 2026 — 8,091 subscribers6 August 2026 — 8,090 subscribers9 August 2026 — 8,094 subscribers12 August 2026 — 8,101 subscribers16 August 2026 — 8,158 subscribers19 August 2026 — 8,178 subscribers22 August 2026 — 8,181 subscribers25 August 2026 — 8,185 subscribers28 August 2026 — 8,192 subscribers1 September 2026 — 8,199 subscribers4 September 2026 — 8,211 subscribers9 September 2026 — 8,228 subscribers13 September 2026 — 8,244 subscribers16 September 2026 — 8,258 subscribers6 August 202616 September 2026
15 measurements spanning 41 days, net +167. 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 8,065–8,283 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:578,258+14
13 Sept 2026, 08:568,244+16
9 Sept 2026, 13:198,228+17
4 Sept 2026, 12:208,211+12
1 Sept 2026, 02:168,199+7
28 Aug 2026, 15:088,192+7
25 Aug 2026, 06:228,185+4
22 Aug 2026, 01:388,181+3
19 Aug 2026, 04:558,178+20
16 Aug 2026, 02:148,158+57
12 Aug 2026, 06:028,101+7
9 Aug 2026, 14:128,094+4
6 Aug 2026, 16:088,090-1
6 Aug 2026, 14:158,091no change
6 Aug 2026, 14:088,091first reading

Engagement

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

ERR · 30 days
12.0%
avg views ÷ 8,258 subscribers
Avg views / post
994
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 32 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 August 2026
Posts held32 (17 July 202626 August 2026)
Views total2,981
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18:26 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

7 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 71.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
571.4%
👍114.3%
🔥114.3%

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

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

26 Aug 2026, 07:39 UTC861 viewsread 28 August 2026

❤️ Ведущий бренд-менеджер в Яндекс Пэй 📍 Москва, гибрид 💎 Построение маркетинговой стратегии бренда: календарь запусков на полугодие, промоподдержка с учётом ЦА, проработка CJM и распределение бюджета по каналам, поиск креативных идей для wow-промо и кросс-сервисных коллабораций. Управление проектами от брифа до отчётности. 💼 5+ лет в маркетинге на самостоятельных позициях, опыт запуска омниканальных рекламных кампа

25 Aug 2026, 08:48 UTC≈1,060 viewsread 28 August 2026

Лид продуктовых маркетологов в Фоксфорд 📍 Удалёнка по РФ / офис в Москве 💎 Ответственность за план продаж и бизнес-метрики сегмента «Помощь по школе» (LTV, CAC, конверсия, retention), управление командой из 3 продуктовых маркетологов, разработка стратегии развития сегмента, работа с воронкой на всех этапах — от привлечения до прогрева базы и direct-коммуникаций. 💼 3+ года в продуктовом маркетинге (желательно EdTech

25 Aug 2026, 07:46 UTC≈1,060 viewsread 28 August 2026

Lead Marketing Analyst в Social Discovery Group 📍 Удалёнка 💎 Управлять процессами маркетинговой аналитики: построение отчётности, дашбордов и стандартов качества данных, мониторинг ключевых метрик с root cause анализом, дизайн и оценка маркетинговых экспериментов и A/B-тестов, развитие аналитических и предиктивных моделей (атрибуция, прогнозирование, сегментация, распределение бюджета). 💼 Высшее техническое, математ

24 Aug 2026, 08:41 UTC≈1,310 viewsread 28 August 2026

🦤 Product Manager в Дринкит (Dodo Brands) 📍 Города с Дринкитом 💎 Развитие киосков для заказа в кофейнях: создание отличной первой сессии новичка и рост доли заказов через приложение. 💼 Сильный senior B2C IT-опыт продакта, умение и желание работать руками самому. Подробное описание Дринкит — сеть цифровых кофеен от Dodo Brands. Свобода в принятии решений, все нужные инструменты, культура Додо. Откликнуться: @tatatl

24 Aug 2026, 07:39 UTC≈1,290 views0 reactionsread 28 August 2026

Client Partner (Lifestyle) в TikTok 📍 Дубай 🇦🇪 💎 Развитие бизнеса в Apps-экосистеме региона METAP: анализ рынка и трендов, построение отношений с ключевыми клиентами и агентствами, работа над retention и upsell, ведение регулярных бизнес-ревью, помощь клиентам в достижении результатов через рекламные продукты TikTok. 💼 Опыт в продажах на платформах social media рекламы или в user acquisition, сильный бэкграунд в dig

18 Aug 2026, 09:12 UTC≈1,960 views2 reactionsread 28 August 2026

Software Engineer в Lyft 💵 CAD $108,000-135,000 в год 📍 Торонто 🇨🇦 гибрид (есть релок) 💎 Поддержка и развитие инфраструктуры логирования и метрик: разработка инструментов для надёжности и масштабируемости платформы, помощь командам в определении SLO, анализ метрик для обнаружения сбоев, автоматизация рутинных операций, участие в on-call дежурствах. 💼 3+ года опыта в разработке и системном инжиниринге, production-код

2

18 Aug 2026, 08:32 UTC≈1,780 views1 reactionsread 28 August 2026

Product Owner (Audacity) в Muse Group 📍 Удалёнка (Европа) 💎 Руководство трансформацией Audacity из аудиоредактора в полноценную DAW: определение стратегии и роадмапа, управление бэклогом, ведение релизов от планирования до пост-релизных отчётов, работа с ключевыми метриками, управление командой из 8 человек (разработка, дизайн, QA). 💼 Опыт Product Owner/Manager со сложным софтом и большой пользовательской базой, глу

🔥1

14 Aug 2026, 08:49 UTC≈2,120 viewsread 28 August 2026

Product Analyst в Weltrade 📍 Удалёнка (Европа) 💎 Владение event tracking и instrumentation для сайта и мобильных приложений (GTM, mobile SDKs), анализ воронок, retention, когорт и feature adoption, дизайн и проведение A/B-тестов со статистической строгостью, построение дашбордов и метрик как единого источника правды, ad-hoc анализы для стейкхолдеров. 💼 Опыт с product/event analytics платформами (GA4, PostHog, Hotjar

14 Aug 2026, 07:49 UTC≈1,940 viewsread 28 August 2026

Product Designer в глобальную security платформу 💵 ¥6,000,000-9,000,000 в год 📍 Удаленка / Гибрид Токио 🇯🇵 (японский язык НЕ требуется) 💎 Дизайн сложных security workflows: alert management, incident response, investigation timelines и операционные дашборды, создание data visualizations для обработки больших объёмов security данных, проектирование AI-powered experiences для автономных и ассистируемых workflows, разв

11 Aug 2026, 07:23 UTC≈2,240 views0 reactionsread 28 August 2026

💳 Руководитель продукта (семейный банкинг) в Т-Банк 📍 Москва, гибрид (м. Белорусская) 💎 Рост прибыли через развитие монетизации и увеличение проникновения, развитие направления шаринга и созаемного кредитования, активация спящей клиентской базы, формирование планов развития на 2027 год, защита KPI перед топ-менеджментом. 💼 Опыт управления портфелем или клиентским сегментом в финтехе, управление командой от 10 челове

10 Aug 2026, 08:37 UTC≈2,110 viewsread 28 August 2026

Product Manager в Findmykids 📍 Удалёнка / офисы в СПб, Перми, Белграде 🇷🇸 (часовой пояс МСК) 💎 Улучшение ключевых пользовательских сценариев с фокусом на рост Retention, MAU и LTV, поиск точек где пользователь теряет ценность и превращение их в продуктовые улучшения, ответственность за пользовательский опыт целиком: навигация, ключевые разделы, look & feel. 💼 5+ лет в product management, опыт с B2C mobile продуктом,

10 Aug 2026, 07:19 UTC≈1,960 viewsread 28 August 2026

🛍 Руководитель группы продуктового дизайна (B2C) в Lamoda 📍 Москва 💎 Руководство командой из 5 дизайнеров с фокусом на развитие их экспертизы, дизайн-ревью и разбор сложных кейсов (программа лояльности, гардероб, корзина и чекаут), формирование стандартов качества дизайна, участие в масштабировании дизайн-системы. 💼 Опыт управления командой дизайнеров от 3 человек, сильная экспертиза в UI-дизайне с продуктовым мышле

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

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

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

“Секретные вакансии в IT и Digital — Sparkles” (@sparklesjobs), 8,258 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/sparklesjobs.

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.