Telegram RegisterThe public register of Telegram
Telegram profile photo for CareerStation | Вакансии для продактов и проджектов

Channel

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

@careerstation_pm

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

12,973subscribers

+954 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
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 live19 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/careerstation_pm

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

12,01912,97312,4967 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 subscribers15 August 2026 — 12,136 subscribers16 August 2026 — 12,146 subscribers17 August 2026 — 12,189 subscribers18 August 2026 — 12,214 subscribers19 August 2026 — 12,258 subscribers21 August 2026 — 12,282 subscribers22 August 2026 — 12,314 subscribers24 August 2026 — 12,324 subscribers25 August 2026 — 12,354 subscribers26 August 2026 — 12,388 subscribers27 August 2026 — 12,428 subscribers28 August 2026 — 12,476 subscribers29 August 2026 — 12,538 subscribers30 August 2026 — 12,545 subscribers31 August 2026 — 12,552 subscribers1 September 2026 — 12,581 subscribers2 September 2026 — 12,609 subscribers3 September 2026 — 12,648 subscribers5 September 2026 — 12,692 subscribers8 September 2026 — 12,767 subscribers11 September 2026 — 12,816 subscribers13 September 2026 — 12,828 subscribers14 September 2026 — 12,870 subscribers16 September 2026 — 12,920 subscribers19 September 2026 — 12,973 subscribers7 August 202619 September 2026
32 measurements spanning 43 days, net +954. 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 11,876–13,116 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
19 Sept 2026, 07:2212,973+53
16 Sept 2026, 20:5612,920+50
14 Sept 2026, 21:1812,870+42
13 Sept 2026, 09:1912,828+12
11 Sept 2026, 14:4012,816+49
8 Sept 2026, 21:3812,767+75
5 Sept 2026, 11:5712,692+44
3 Sept 2026, 13:3712,648+39
2 Sept 2026, 09:3312,609+28
1 Sept 2026, 08:5312,581+29
31 Aug 2026, 10:4612,552+7
30 Aug 2026, 09:4312,545+7
29 Aug 2026, 07:2412,538+62
28 Aug 2026, 07:5312,476+48
27 Aug 2026, 05:2312,428+40
26 Aug 2026, 08:1712,388+34
25 Aug 2026, 05:3512,354+30
24 Aug 2026, 02:1312,324+10
22 Aug 2026, 10:1312,314+32
21 Aug 2026, 02:1212,282first reading

Engagement

90 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 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.0%
avg views ÷ 12,973 subscribers
Avg views / post
2,720
28 posts measured
Reaction rate
0.589%
reactions ÷ views · ER floor
Posts in window
28
of 90 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 2 September 2026
Posts held90 (1 August 20262 September 2026)
Views total76,230
Reactions total449
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 21:24 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

1,262 reactions across 90 posts, in 7 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎45936.4%
35928.4%
👍25119.9%
🔥876.89%
🤔554.36%
😢372.93%
🤯141.11%

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

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

Recent posts

2 Sept 2026, 15:00 UTC≈1,180 views9 reactionsread 2 September 2026

⚡️ Продакт менеджер в EdTech Задачи: • смотреть на программы как на продукт • анализировать, что работает, а что пора менять • тестировать образовательные гипотезы • продумывать MVP новых программ для рынка Германии и Европы • развивать синхронные, асинхронные и AI-powered форматы • управлять командой методистов Требования: • 3+ годами опыта в EdTech / L&D / Learning Product / Curriculum Development и минимум 2 год

7👍1👎1

2 Sept 2026, 11:02 UTC≈1,580 views11 reactionsread 2 September 2026

⚡️ Продакт менеджер в Createx Задачи: • Управлять мобильным продуктом end-to-end: от бэклога до релиза • Вместе с командой формировать продуктовый roadmap и определять приоритеты • Анализировать продуктовые и бизнес-метрики и находить возможности для роста • Принимать решения на основе данных и превращать аналитику в конкретные задачи • Работать на стыке Product × Development × Marketing Требования: • 3+ года опыта

5👎5👍1

2 Sept 2026, 07:04 UTC≈1,870 views3 reactionsread 2 September 2026

⚡️ Продакт менеджер в Magnit OMNI Задачи: • Отвечать за развитие продукта от идеи до бизнес-результата • Переосмысливать и трансформировать бизнес-процессы Магнит Косметик • Bсследовать поведение пользователей, искать барьеры, тестировать гипотезы и запускать решения • Работать на стыке продукта, коммерции, маркетинга, аналитики и технологий • Управлять продуктовым бэклогом Требования: • Опыт работы над продуктами

👍2👎1

1 Sept 2026, 14:03 UTC≈2,130 views11 reactionsread 2 September 2026

⚡️ Product Owner в Aston Требования: • опыт работы Product Owner, управление проектами в IT от 3-х лет • наличие законченного высшего образования • опыт развития ИИ-решений в клиентской поддержке • опыт работы с NLP: интенты, классификация текста, эмбеддинги, векторные базы, RAG, когда LLM vs классификатор • знания и умение применять ключевые метрики оценки качества моделей машинного обучения • понимание жизненного

4👍4👎3

1 Sept 2026, 11:02 UTC≈2,240 views10 reactionsread 2 September 2026

⚡️ Проджект менеджер в Xmethod XMethod — студия разработки, которая создает цифровые продукты для бизнеса. Задачи: • Вести предпроектную подготовку (пресейл) • Выступать главным связующим звеном для клиентов из DACH-региона — свободно и уверенно общаться на немецком языке • Тесно взаимодействовать с командами разработки, дизайна и тестирования на протяжении всего цикла реализации Требования: • Опыт управления IT-п

4👍3👎3

31 Aug 2026, 16:10 UTC≈2,500 views10 reactionsread 2 September 2026
Photo

Хотите оффер в БигТех? Плохая новость: его хотят почти все 😰 Яндекс, Авито, Т-Банк и другие крупные компании получают тысячи откликов. Вакансии бигтех-компаний привлекают брендом, зарплатами, масштабом задач и условиями, поэтому желающих туда попасть хватает всегда. И среди них точно будут кандидаты с сильным опытом, нужным стеком и громкими компаниями в резюме – конкуренция бешеная. Чтобы пробиться, придется прикл

👎5👍3🔥2

31 Aug 2026, 11:01 UTC≈2,480 views10 reactionsread 2 September 2026

⚡️ Проджект менеджер в Dogma Задачи: • Формировать и поддерживать в актуальном состоянии CJM • Вести и контролировать актуальность бизнес-процессов • Управлять бэклогом • Проводить первичный анализ задач Битрикс24 × web-продукты / AI-решения • Контролировать полный жизненный цикл задач Требования: • Опыт работы Project Manager в ИТ или digital-проектах • Опыт самостоятельного ведения кросс-функциональных задач • Си

👍43🔥2👎1

31 Aug 2026, 07:01 UTC≈2,470 views4 reactionsread 2 September 2026

⭐️ Подборка актуальных вакансий за неделю Собрали активные вакансии прошлой недели, чтобы вы успели откликнуться! Продакт менеджер • Продакт менеджер в Дринкит • Продакт менеджер в Сбер • Senior Продакт менеджер в VK Video • Менеджер продукта в Яндекс • Подборка вакансий менеджера продукта в Mail.ru Проджект менеджер • Проджект менеджер в Navio Auto • Проджект менеджер в GBagency • Проджект менеджер в Magnit Ads

3👍1

30 Aug 2026, 15:45 UTC≈2,500 views27 reactionsread 2 September 2026

⚡️ Middle/Senior Продакт менеджер в IT-стартап Cтартап-студия, более 10 лет создающая успешные IT продукты в сфере браузерных технологий, веб-автоматизации и AI. Задачи: • Ведение полного цикла работы над фичами • Управление бэклогом продукта • Помощь команде в визуализации результатов и поддержании фокуса на достижении MVP • Планирование и координация продуктовых релизов • Взаимодействие с разными командами для ре

👎164🤔4👍3

30 Aug 2026, 11:04 UTC≈2,440 views8 reactionsread 2 September 2026

⚡️ Продакт менеджер в JanaPost Задачи: • развитие продукта курьерской доставки end-to-end • улучшение процессов назначения и распределения заказов • развитие Express, Same Day, Next Day и других сценариев доставки • повышение количества заказов на одного курьера • снижение cost per delivery • построение аналитики и продуктовых метрик Требования: • опыт работы Product Manager • обязательный практический опыт в курье

4👍3👎1

29 Aug 2026, 15:45 UTC≈2,450 views15 reactionsread 2 September 2026

⚡️ Growth Продакт менеджер в Делимобиль Задачи: • Искать точки роста в текущих пользовательских сценариях • Формировать и проверять продуктовые гипотезы • Работать с воронками, conversion, retention, DAU/MAU, LTV • Проводить и анализировать A/B-тесты • Приоритизировать гипотезы • Формировать и вести бэклог • Работать со стейкхолдерами, дизайном и разработкой Требования: • опыт от 3 лет в B2C-продукте • умеет самост

6👍6👎2🔥1

29 Aug 2026, 11:02 UTC≈2,510 views19 reactionsread 2 September 2026

⚡️ Head of Growth в Kukolschool.ru Задачи: • находить перспективные сегменты, понимать их мотивацию и причины покупки • формировать под них предложение, быстро проверять способы привлечения и превращать подтверждённые гипотезы в системные каналы роста. Требования: • стартап-опыт и предпринимательский способ мышления • важно уметь: разговаривать с клиентами и понимать причины покупок и отказов • быстро запускать экс

👎74👍3🤯3🤔2

Showing the 12 most recent of 90 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 4 posts 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
27 August 2026

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

“CareerStation | Вакансии для продактов и проджектов” (@careerstation_pm), 12,973 subscribers as measured 19 September 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.