Channel
@naumen_job
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,261subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001779083876 |
|---|---|
| Type | Channel |
| Username | @naumen_job |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/naumen_job |
Technology — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 14:20 | 2,261 | -7 |
| 15 Sept 2026, 02:15 | 2,268 | -1 |
| 11 Sept 2026, 14:17 | 2,269 | -3 |
| 7 Sept 2026, 08:18 | 2,272 | -5 |
| 2 Sept 2026, 21:14 | 2,277 | -5 |
| 30 Aug 2026, 13:38 | 2,282 | -3 |
| 27 Aug 2026, 19:04 | 2,285 | +1 |
| 21 Aug 2026, 06:03 | 2,284 | -3 |
| 18 Aug 2026, 00:11 | 2,287 | -1 |
| 14 Aug 2026, 21:55 | 2,288 | +3 |
| 11 Aug 2026, 12:33 | 2,285 | +5 |
| 8 Aug 2026, 04:51 | 2,280 | +1 |
| 7 Aug 2026, 16:17 | 2,279 | first reading |
6 posts held, back to 23 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
65 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 35.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 35.4% | |
| 👍 | 13 | 20.0% | |
| 🔥 | 9 | 13.8% | |
| ❤🔥 | 6 | 9.23% | |
| 💯 | 6 | 9.23% | |
| ✍ | 5 | 7.69% | |
| 👏 | 2 | 3.08% | |
| 😁 | 1 | 1.54% |
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 6 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 23 July 2026 to 6 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.
Бывает, что ИИ выдает совсем не тот результат, который мы ожидали. И дело не всегда в возможностях самой модели: даже хороший инструмент может отвечать хуже, если смешать контекст, нечетко поставить задачу или передать лишние данные. Пообщались с Константином, экспертом по ИИ в Naumen, и собрали несколько частых ошибок, которые встречаются в работе с нейросетями. В первой части нашего материала говорим о контексте,…
❤5👍3💯1
С обратной связью мы сталкиваемся постоянно: на встрече с руководителем, после презентации или просто при обсуждении задачи. Но даже полезный комментарий не всегда приводит к результату. Может не хватать конкретики, стороны могут по-разному понимать ситуацию, а разговор — закончиться без ясного следующего шага. Задача обратной связи — не определить, кто прав. Она помогает понять, что уже работает, что стоит изменить…
❤5✍2👍2
Встречи 1:1 — базовый инструмент взаимодействия сотрудника и руководителя. На них можно обсудить не только текущие задачи, но и нагрузку, развитие, сложности в команде и идеи, на которые не всегда хватает времени в рабочей переписке. При этом результат встречи зависит не только от руководителя. Собрали рекомендации наших коллег, которые помогут подготовиться к разговору и получить от него больше пользы. 6️⃣ Определ…
❤🔥6👍3💯3
В работе с клиентами участвуют сразу несколько команд. Клиентский сервис знает о текущих сложностях и запросах, а продуктовая команда решает, как будет развиваться сервис. Но эта информация не всегда складывается в общую картину: обратная связь теряет контекст, продукту сложно оценить реальную значимость запроса, а клиент не понимает, что происходит с его предложениями. Команде Скорозвона решить эту проблему помогли…
❤6👍3👏2🔥1
Интерфейсы с каждым годом становятся только удобнее: часть задач, например, сейчас можно решить с голосовым помощником. Но новые технологии не всегда делают взаимодействие с системой проще. Пользователи по-прежнему теряются в меню, тратят время на поиск нужных функций и устают от необходимости постоянно принимать лишние решения. Поговорили об этом с Динарой — владельцем продукта Naumen Service Desk и аналитиком в ко…
❤7💯2🔥2
Эффективная работа в команде строится на «трех китах»: доверии, четких целях и умении конструктивно общаться. Именно продуктивное взаимодействие с коллегами позволяет быстрее и качественнее достигать общих результатов. Собрали подборку книг, которые помогут отработать эти навыки на практике.
🔥6✍3👍2😁1
Showing the 6 most recent of 6 posts we hold for @naumen_job. 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Naumen | Карьера” (@naumen_job), 2,261 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/naumen_job.
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.