Posted without readable text
👍11👎4

Channel
@refer_me_it
On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
30,925subscribers
+769 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002139675468 |
|---|---|
| Type | Channel |
| Username | @refer_me_it |
| Description | Канал сообщества Осознанная Меркантильность: @om_assistant_robot Задать вопрос: @m0rtymerr_support Предложка — @refer_me_it_bot Буст канала — https://t.me/boost/refer_me_it |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/refer_me_it |
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 9 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.
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 05:01 | 30,925 | +28 |
| 16 Sept 2026, 00:18 | 30,897 | +62 |
| 14 Sept 2026, 06:41 | 30,835 | +36 |
| 12 Sept 2026, 12:55 | 30,799 | +44 |
| 10 Sept 2026, 08:38 | 30,755 | +85 |
| 7 Sept 2026, 03:37 | 30,670 | +21 |
| 4 Sept 2026, 08:40 | 30,649 | +36 |
| 2 Sept 2026, 20:15 | 30,613 | +22 |
| 1 Sept 2026, 18:46 | 30,591 | +15 |
| 31 Aug 2026, 19:04 | 30,576 | +17 |
| 30 Aug 2026, 22:24 | 30,559 | +14 |
| 30 Aug 2026, 00:23 | 30,545 | +4 |
| 29 Aug 2026, 01:45 | 30,541 | -11 |
| 27 Aug 2026, 06:34 | 30,552 | +22 |
| 26 Aug 2026, 05:02 | 30,530 | +36 |
| 25 Aug 2026, 01:52 | 30,494 | +27 |
| 23 Aug 2026, 13:37 | 30,467 | +34 |
| 21 Aug 2026, 21:27 | 30,433 | +30 |
| 20 Aug 2026, 17:12 | 30,403 | +31 |
| 19 Aug 2026, 20:36 | 30,372 | first reading |
75 posts held, back to 25 June 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 69 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 75 (25 June 2026 – 22 September 2026) |
| Views total | 147,200 |
| Reactions total | 648 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 08:48 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.
Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,890 reactions across 71 posts, in 2 distinct kinds. The most used accounts for 72.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 1,372 | 72.6% | |
| 👍 | 518 | 27.4% |
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 71 of the 75 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,890 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 75 most recent posts we hold, published 25 June 2026 to 22 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @refer_me_it. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 75 most recent posts we hold for this entry, published 25 June 2026 to 22 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Posted without readable text
👍11👎4
Почему ты откликаешься, а на собеседования все еще не зовут? https://www.youtube.com/watch?v=J9zNT0xgRpc Можно отправлять десятки откликов, переписывать резюме и все равно получать автоотказы еще до первого разговора с HR. Мало просто подходить под вакансию — сначала нужно пройти алгоритмы HH, ATS-фильтры и другие этапы современного найма. Мы собрали большой гайд, который поможет разобраться, что происходит с твои…
👍4
Область и стек: Big Data/Data Engineering Должность: ✨ Junior Data Scientist (Python) Компания: Coperto Зарплатная вилка: 90 000 — 105 000 ₽/мес Формат работы: Удаленка Страна работы: Россия Опыт: Без опыта Обязанности • Подготовка данных: выгрузки из PostgreSQL и POS, очистка, пропуски, выбросы • Прогнозные модели: поток гостей, спрос на позиции меню, потребность в закупках • Признаки предметной области: сез…
👎10👍9
Область и стек: Системная аналитика Должность: System Analyst/Business Analyst Компания: Paynet Зарплатная вилка: 3000$-3500$ Формат работы: В офисе Страна работы: Ташкент ,Узбекистан О позиции Мы ищем опытного Senior бизнес-/системного аналитика, который будет заниматься проектированием интеграций, описанием API, анализом требований и разработкой технических заданий для команд разработки. Вы станете связующим …
👎12👍1
Что продают рекрутеры в своих курсах / Кира Кузьменко упаковывает резюме за 90к https://youtu.be/fsD5DPwa1PI https://youtu.be/fsD5DPwa1PI https://youtu.be/fsD5DPwa1PI Продолжаем погружаться в курсы от "белых" HR, чтобы узнать, как все таки устроиться в IT без серых схем. Сегодня в студии Кира Кузьменко — видный эксперт в мире HR и сжигания половичков. Узнаем, какие советы получает новичок для поиска новой работы, …
👍1👎1
Область и стек: Бэкенд Должность: Java Lead Компания: Дом.РФ Зарплатная вилка: 500к+ Формат работы: Удаленка Страна работы: Россия ЧЕМ ПРЕДСТОИТ ЗАНИМАТЬСЯ: • Руководить кросс-функциональной продуктовой командой интернет-банка • Организовывать работу команды: участвовать в планировании, распределять задачи, контролировать сроки и качество результата • Заниматься backend-разработкой Java-приложений на Spring Bo…
👍9👎4
Связи реально работают / Гайд по осознанному нетворкингу Нетворкинг часто сводят к простому обмену контактами: познакомились на мероприятии, добавили ники друг друга и разошлись. Но если спустя месяц ты не понимаешь, кому из этих людей можно написать по работе, обратиться за советом или предложить совместный проект, то сама по себе такая база контактов ничего не дает. Для меня связи — это один из самых сильных карь…
👍9👎9
Область и стек: Фронтенд Должность: Junior Fullstack Developer (React + Express) Компания: Coperto Зарплатная вилка: 120 000 -- 135 000 ₽/мес Формат работы: Удаленка Страна работы: Россия Обязанности • REST API на Node.js и Express: маршруты, сервисный слой, middleware, валидация • Схема данных в PostgreSQL, запросы и миграции через Prisma • Аутентификация и авторизация по ролям, интеграции с кассами, Telegr…
👎35👍7
Область и стек: Фронтенд Должность: Middle Frontend Developer (React, Next.js) Компания: Coperto Зарплатная вилка: 150 000 — 190 000 ₽/мес Формат работы: Удаленка Страна работы: Россия Обязанности • Разработка ui на Next.js (App Router): серверные и клиентские компоненты, стриминг, границы загрузки и ошибок • Проектирование архитектуры фичи - слои, переиспользуемые модули, понятные контракты компонентов • Стро…
👎26👍2
Область и стек: Машинное обучение Должность: Machine Learning Engineer (Agentic AI) Компания: Cognizant Зарплатная вилка: 6-10к + премия Формат работы: Удаленка Страна работы: Не РФ (но в целом похуй не чекают). Есть офис коворкинг в Ташкенте Machine Learning Engineer (Agentic AI) About the Role As a Machine Learning Engineer, you will make an impact by designing, developing, deploying, and optimizing Agentic A…
👍16👎4
Область и стек: QA Должность: Инженер нагрузочного тестирования Компания: InfoWatch Зарплатная вилка: 200 000 - 250 000 Формат работы: Удаленка Страна работы: Россия Задачи, которые предстоит решать: - проводить нагрузочное тестирование и тестирование производительности продуктов компании; - анализировать результаты тестирования и представлять их коллегам в удобной и доступной форме; - настраивать стенды для на…
👎6👍1
Область и стек: React Native Должность: Junior React Native Developer Компания: Coperto Зарплатная вилка: 95 000 — 110 000 ₽/мес Формат работы: Удаленка Страна работы: Россия Обязанности • Разработка экранов приложения на React Native + Expo • Типизация компонентов, пропсов и API-ответов на TypeScript • Работа с состоянием через Redux Toolkit / Zustand • Интеграция REST API и кэширование запросов на React Quer…
👍14👎6
Showing the 12 most recent of 75 posts we hold for @refer_me_it. 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 4 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Рефералки в IT | Вакансии и резюме” (@refer_me_it), 30,925 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/refer_me_it.
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.