Telegram RegisterThe public register of Telegram

Channel

InfoSec Jobs — вакансии по информационной безопасности, infosec, pentesting, пентестингу, security engineer, инфобезу, DevSecOps

@hackdevjob

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

3,090subscribers

+8 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001747597265
TypeChannel
Username@hackdevjob
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/hackdevjob

Growth

3,0823,0903,0867 August 2026 — 3,082 subscribers7 August 2026 — 3,082 subscribers8 August 2026 — 3,083 subscribers11 August 2026 — 3,090 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net +8. 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 3,081–3,091 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:323,090+7
8 Aug 2026, 10:103,083+1
7 Aug 2026, 17:483,082no change
7 Aug 2026, 17:393,082first reading

Engagement

21 posts held, back to 21 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.5%
avg views ÷ 3,090 subscribers
Avg views / post
788
21 posts measured
Reaction rate
0.164%
reactions ÷ views · ER floor
Posts in window
21
of 21 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 6 of 21 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 7 August 2026
Posts held21 (21 July 20267 August 2026)
Views total16,548
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23: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

9 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤔888.9%
111.1%

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

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

7 Aug 2026, 18:03 UTC273 viewsread 7 August 2026

✂️ Главный специалист по кибербезопасности Офис (Москва) ООО ОТЭКО — крупнейший частный инвестор в портовую инфраструктуру Юга России, один из лидеров на рынке транспортных услуг России и стран СНГ. Требования: — имеете опыт работы с любыми из перечисленных систем: сканер уязвимостей, система управления безопасностью мобильных устройств, антивирусные решения; — имеете опыт проектирования и внедрения систем защиты и

6 Aug 2026, 18:01 UTC490 viewsread 7 August 2026

🫣 Специалист по реагированию и расследованию инцидентов ИБ от 300 000 ₽ Офис/гибрид (Москва) Alta Personnel — быстрорастущая российская фармацевтическая компания развивает процесс управления инцидентами информационной безопасности и планирует использовать гибридную модель. Требования: — Опыт работы в incident response, SOC L2/L3, расследовании инцидентов, ИБ-аналитике или смежных направлениях от 3 лет. — Понимание

5 Aug 2026, 18:03 UTC591 viewsread 7 August 2026

⌨️ Специалист по информационной безопасности Удаленно «Норникель Спутник» — это высокотехнологичный сервисный центр, выполняющий функции единого цифрового и операционного партнера для предприятий группы компаний «Норникель». Требования: • Понимание основных принципов и специфики работы АСУ ТП; • Понимание принципов построения систем защиты АСУ ТП; • Опыт работы и администрирования: Kaspersky Security Center, KICS f

4 Aug 2026, 13:50 UTC718 views2 reactionsread 7 August 2026

👅 Специалист по информационной безопасности Офис (Томск) ООО «РН-Проектирование Добыча» — один из ключевых Корпоративных институтов ПАО «НК «Роснефть», крупный исследовательский и проектный центр нефтегазовой отрасли страны, выполняющий широкий спектр научных и проектных работ для предприятий нефтегазового комплекса. Требования: — высшее профессиональное образование по специальности "Информационная безопасность", л

1🤔1

4 Aug 2026, 12:33 UTC603 viewsread 7 August 2026

Покупать новый курс каждый раз, когда меняется рабочая задача, — довольно странная механика. Нашли альтернативу 👇

4 Aug 2026, 12:33 UTC604 viewsread 7 August 2026
Forwarded from @proglib_academyPhoto

👅 Самое сложное — выбрать не курс, а направление Сегодня хочется разобраться в AI-агентах. Через пару недель появляется задача, где нужны алгоритмы. Потом понимаешь, что неплохо бы освежить Python или математику для Data Science. 🔜 Именно поэтому подписка на обучение многим оказывается удобнее отдельных курсов. Можно спокойно переключаться между темами, когда меняются задачи, а не покупать новую программу каждый ра

3 Aug 2026, 18:01 UTC680 viewsread 7 August 2026

🥳 Security Business Partner Удаленно Циан — крупнейший в России сервис для поиска недвижимости. Компания входит в топ-10 лучших сайтов по недвижимости в мире, ежемесячная аудитория сервиса — свыше 18 млн. человек. Наш будущий коллега: — Имеет опыт работы в области application/product security более 3 лет с фокусом на проектную деятельность и внедрение контролей; — Умеет вести проекты end-to-end и ориентирован на ре

31 Jul 2026, 18:05 UTC925 views4 reactionsread 7 August 2026

😧 Security Engineer от 200 000 до 250 000 ₽ Офис (Москва) АО «ТрансМашГазТокен» (ТМГТ) — российская технологическая компания, разрабатывающая программную платформу для рынка криптовалют и цифровых финансовых активов. Требования: — 5+ лет в application security / product security, из них опыт в финтехе или криптоиндустрии. — Понимание атак на инфраструктуру цифровых активов: blind signing, компрометация цепочки пост

🤔4

30 Jul 2026, 12:01 UTC950 views0 reactionsread 7 August 2026

🥳 Специалист по информационной безопасности от 160 000 до 200 000 ₽ Офис (Москва) М7.PRO — команда, которая реализует и сопровождает сложные цифровые системы для бизнеса. Мы работаем как технологический партнер: проектируем, разрабатываем и поддерживаем надежные IT-решения. Требования: — Опыт работы в ИБ или системном администрировании от 2 лет — Знание принципов информационной безопасности и сетевых технологий (TC

30 Jul 2026, 10:31 UTC735 viewsread 7 August 2026

Разработчик, DevOps-инженер или техлид — у каждого своя причина навести порядок в работе с AI-агентами. Разбираем, чем отличаются их задачи 😊

30 Jul 2026, 10:31 UTC802 viewsread 7 August 2026
Forwarded from @proglib_academyPhoto

🎯 У разработчика, DevOps-инженера и техлида разные причины задуматься о системной работе с AI-агентами Но цель одна: перейти от случайных удачных запусков к управляемому процессу на реальном проекте — с понятными правилами, ревью, контролем расходов и безопасности ✔️ На курсе «ИИ для разработчиков» участники выстраивают такой процесс на практике: подключают инструменты, задают границы для агента и учатся понимать,

29 Jul 2026, 18:03 UTC766 viewsread 7 August 2026

🚀 SRE-инженер Гибрид (Казань) Т-Банк — онлайн-экосистема, основанная на финансовых и лайфстайл-услугах. Клиентами Т‑Банка стали 50 млн человек по всей России. Требования: 1. Разработка процессов мониторинга и алертинга. 2. Улучшение стабильности и отказоустойчивость платформы. 3. Выстраивание CI/CD для платформы. 4. Разработка Self Service для пользователей платформы. 5. Поддержка платформы/ оперативная реакция на

Showing the 12 most recent of 21 posts we hold for @hackdevjob. 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 — 1,053,972 of 1,160,990entries 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

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

“InfoSec Jobs — вакансии по информационной безопасности, infosec, pentesting, пентестингу, security engineer, инфобезу, DevSecOps” (@hackdevjob), 3,090 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/hackdevjob.

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.