Telegram RegisterThe public register of Telegram

Channel

CareerStation | Вакансии для продактов и проджектов

@careerstation_pm

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

12,117subscribers

+98 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002672170872
TypeChannel
Username@careerstation_pm
DescriptionВакансии с прямыми контактами CPO и рекрутеров Разместить ваку https://goo.su/GBltzUz Зарплаты продактов/проджектов @salary_pm Интенсив поиск работы https://goo.su/mCG7io Кейс клуб @careerstation_bot Автор @vladislav_noskovets РКН https://clck.ru/3Tq2wM
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/careerstation_pm

Growth

12,01912,11712,0687 August 2026 — 12,019 subscribers8 August 2026 — 12,028 subscribers9 August 2026 — 12,041 subscribers10 August 2026 — 12,043 subscribers11 August 2026 — 12,063 subscribers12 August 2026 — 12,097 subscribers14 August 2026 — 12,117 subscribers7 August 202614 August 2026
7 measurements spanning 6 days, net +98. 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 12,004–12,132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:5512,117+20
12 Aug 2026, 18:0712,097+34
11 Aug 2026, 17:1612,063+20
10 Aug 2026, 13:5112,043+2
9 Aug 2026, 16:0612,041+13
8 Aug 2026, 14:0312,028+9
7 Aug 2026, 18:0312,019first reading

Engagement

40 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.0%
avg views ÷ 12,117 subscribers
Avg views / post
2,550
40 posts measured
Reaction rate
0.463%
reactions ÷ views · ER floor
Posts in window
40
of 40 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 14 August 2026
Posts held40 (1 August 202614 August 2026)
Views total101,800
Reactions total471
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 02:23 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
62
Links
1,220

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

471 reactions across 40 posts, in 5 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16234.4%
👎15532.9%
👍10121.4%
🔥408.49%
🤔132.76%

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

Measured over the 40 most recent posts we hold, published 1 August 2026 to 14 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

14 Aug 2026, 15:45 UTC950 views10 reactionsread 15 August 2026

⚡️ Senior Продакт менеджер в SkyСoach Задачи: • Лидировать основной продукт Skycoach.gg и его направления • Определять цели и доводить их до результата • Выстраивать понятные процессы: от выбора приоритетов до контроля сроков и качества • Быть ответственным за продукт и координировать задачи команды разработки • Отслеживать ключевые метрики продукта • Проводить CustDev, запускать A/B-тесты и анализировать данные Тр

👎5👍32

14 Aug 2026, 11:01 UTC≈1,500 views11 reactionsread 15 August 2026

⚡️ Продакт менеджер в Лабараторию Касперского Задачи: • Формировать и развивать продуктовую стратегию платформы • Управлять roadmap платформенных компонентов • Собирать и анализировать требования от SIEM, KEDR, XDR, NGFW, VM, KSC и других продуктов • Готовить бизнес-требования, описания сценариев • Приоритизировать backlog платформы Требования: • Опыт управления B2B Enterprise-продуктом • Понимание платформенного п

5👍3🔥3

14 Aug 2026, 07:04 UTC≈1,840 views18 reactionsread 15 August 2026

⚡️ Продакт менеджер в Higgsfield AI Требования: • продуктовый вкус • опыт запуска продуктов с нуля до релиза • реальная практика работы с AI. Условия: • Офис в Алматы, on-site, релокация за счёт компании. • Через год возможна релокация в Сан-Франциско по визе L1 • Компенсация в долларах по верхней границе рынка 📎Как откликнуться? Рекрутер: [LinkedIn], @Da6ka #Product #международка 🤖 Кейс-клуб для продактов 🤖

🤔7👍4👎43

13 Aug 2026, 15:15 UTC≈1,990 views13 reactionsread 15 August 2026

⚡️ Продакты, встречаемся на ProductSense'26! Всем привет, на связи Влад Носковец, автор этого канала 👋 10-11 сентября я буду в Москве на ProductSense'26 и хочу позвать вас с собой. Вы точно слышали про эту конференцию – она проходит каждый год и собирает вокруг себя большое сообщество продактов и экспертов. Тема этого года – «Фундамент и эволюция: как меняется продуктовая работа». Будут обсуждать, что в менеджмен

7🔥4👎2

13 Aug 2026, 11:00 UTC≈2,030 views18 reactionsread 15 August 2026

⚡️ Подборка вакансий на роль Продакт менеджера в Авито 🔹Продакт-менеджер Задачи: • Оптимизировать механизмы показа рекламы, проводить A/B-тесты форматов • анализировать трафик и точки роста • работать с ключевыми метриками и контрметриками направления • проводить регулярное дискавери 📎Как откликнуться? Вакансия: [ссылка] Нанимающий: [LinkedIn] отклики через сайт 🔹Senior Менеджер продукта Задачи: • управлять одно

5👍5👎5🔥3

13 Aug 2026, 07:01 UTC≈2,190 views9 reactionsread 15 August 2026

⚡️ Продакт менеджер во ВкусВилл Задачи: • Искать и реализовывать точки роста в направлении лояльности, удержания и развития покупателей • Развивать механики программы лояльности, промо, рекомендательные алгоритмы • Выстраивать системный discovery совместно с аналитиками, исследователями и дизайнерами • Поддерживать и усиливать маркетинговые инициативы с помощью продуктовых инструментов • Следить за продуктовыми и би

5👍3👎1

12 Aug 2026, 11:04 UTC≈2,170 views13 reactionsread 15 August 2026

⚡️ Проджект менеджер в The Budnik Agency Задачи: • Управление проектами и координация работы команды • Решение проблемных и спорных ситуаций как внутри команды, так и с клиентами • Ведение большого количества задач, контроль сроков и качества выполнения Требования: • Опыт работы Project Manager от 1 года (опыт в маркетинговом агентстве будет большим преимуществом) • Понимание основ digital-маркетинга • Высокий уров

7👍3🔥3

12 Aug 2026, 07:03 UTC≈2,220 views7 reactionsread 15 August 2026

⚡️ Product Lead в игровую платформу Продукт – игровая экосистема, объединяющая десятки казуальных игр. Требования: • Продуктовый лидер с гейм-дизайнерским мышлением - мыслит не фичами, а механиками и циклами роста • Принимает решения на основе данных, работает с аналитикой и A/B‑тестами • Отвечает за Retention, User Journey и ключевые метрики: DAU/MAU, LTV, ARPU, конверсию в игровые механики и рекламную монетизацию

3👍2👎2

11 Aug 2026, 16:36 UTC≈2,270 views12 reactionsread 15 August 2026
Photo

Если вы устали от безрезультатных откликов – этот пост для вас! 👌 Мы в Career Station видели много историй, когда люди с совершенно разным бэкграундом не могли найти работу, а после смены стратегии у них на руках был оффер. Вот несколько примеров 👇 👱‍♀️ Даша – оффер с х2 ростом зарплаты Перешла в бигтех (Озон Банк) и сменила домен практически без опыта в финтехе. 👨‍🦱 Фёдор - 3 оффера на Senior продакта Давно не в

6👍4👎2

11 Aug 2026, 11:04 UTC≈2,360 views17 reactionsread 15 August 2026

⚡️ Подборка вакансий Продакт менеджеров в VK 🔹 Product Manager Задачи: • Развитие рекламного инструментария VK • Формирование и реализация стратегии, управление KPI, управление продуктовой командой, взаимодействие со стейкхолдерами и смежными командами. 🔹 ML Product Manager Задачи: • Создание и развитие рекламных моделей на основе машинного обучения в рекомендательных системах (лента, клипы, Discover и др.) 📎Ка

👎86🔥3

11 Aug 2026, 07:02 UTC≈2,440 views20 reactionsread 15 August 2026

⚡️ Продакт менеджер в Яндекс Ищем менеджера продукта в команду биллинга Yandex Cloud. Задачи: • Управление продуктовой разработкой калькулятора и тарификации • Анализ данных и работа с продуктовыми метриками • Проектирование сценариев As Is и To Be • Коммуникация и фасилитация рабочих групп • Презентация результатов Требования: • Управляли продуктами более трёх лет • Работали с CJM • Можете согласовывать требовани

👎153👍2

10 Aug 2026, 17:00 UTC≈2,440 views16 reactionsread 15 August 2026
Photo

Хватит быть удобным 😠 Прямой эфир с бизнес-психологом! Знакомы ли вам такие ситуации: • Соглашаетесь взять еще одну задачу, хотя команда уже перегружена; • Не спорите с руководителем, хотя понимаешь, что решение не сработает; • Смягчаете обратную связь, хотя проблема не решается? 👉 Кажется, что вы просто хороший менеджер: умеете договариваться, не конфликтуете и сохраняете отношения. На деле же такие ситуации сильн

👍87🔥1

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

Posts edited after publishing

@careerstation_pm edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 August 2026
Most recent edit
15 August 2026

Citation-graph rank

Citation-graph rank — 306,815 of 1,345,403entries 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

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

“CareerStation | Вакансии для продактов и проджектов” (@careerstation_pm), 12,117 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/careerstation_pm.

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.