Telegram RegisterThe public register of Telegram
Telegram profile photo for IT вакансии для всех

Channel

IT вакансии для всех

@zizu_IT_RU

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry

3,932subscribers

-761 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002365337337
TypeChannel
Username@zizu_IT_RU
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/zizu_IT_RU

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zizu_IT_RU/721 · this entry27 Jan 2026, 14:28 UTC@java_c_net_golang_jobs/38927 Jan 2026, 14:28 UTC1.00under a minute
@zizu_IT_RU/724 · this entry27 Jan 2026, 15:42 UTC@java_c_net_golang_jobs/39027 Jan 2026, 15:42 UTC1.00under a minute
@zizu_IT_RU/725 · this entry27 Jan 2026, 15:47 UTC@java_c_net_golang_jobs/39127 Jan 2026, 15:47 UTC1.00under a minute
@zizu_IT_RU/726 · this entry29 Jan 2026, 07:59 UTC@java_c_net_golang_jobs/39229 Jan 2026, 07:59 UTC1.00under a minute
@zizu_IT_RU/729 · this entry29 Jan 2026, 08:02 UTC@java_c_net_golang_jobs/39429 Jan 2026, 08:02 UTC1.00under a minute
@zizu_IT_RU/739 · this entry4 Feb 2026, 11:52 UTC@java_c_net_golang_jobs/3974 Feb 2026, 11:53 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@java_c_net_golang_jobs6 (6/6 hand-verifiable sample passed)1.00under a minutethis entry (60)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 27 January 2026 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @zizu_IT_RU — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.

Growth

3,9324,6934,312.57 August 2026 — 4,693 subscribers8 August 2026 — 4,691 subscribers11 August 2026 — 4,687 subscribers15 August 2026 — 4,684 subscribers17 August 2026 — 4,676 subscribers20 August 2026 — 4,673 subscribers23 August 2026 — 4,665 subscribers26 August 2026 — 4,656 subscribers29 August 2026 — 4,649 subscribers1 September 2026 — 4,650 subscribers4 September 2026 — 4,645 subscribers10 September 2026 — 4,408 subscribers13 September 2026 — 4,039 subscribers18 September 2026 — 3,932 subscribers7 August 202618 September 2026
14 measurements spanning 41 days, net -761. 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,818–4,807 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 03:193,932-107
13 Sept 2026, 15:014,039-369
10 Sept 2026, 02:014,408-237
4 Sept 2026, 09:364,645-5
1 Sept 2026, 02:274,650+1
29 Aug 2026, 12:144,649-7
26 Aug 2026, 18:564,656-9
23 Aug 2026, 15:254,665-8
20 Aug 2026, 09:024,673-3
17 Aug 2026, 19:144,676-8
15 Aug 2026, 02:264,684-3
11 Aug 2026, 17:134,687-4
8 Aug 2026, 17:414,691-2
7 Aug 2026, 19:184,693first reading

Engagement

20 posts held, back to 27 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages 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 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Aug 2026, 16:23 UTC60 viewsread 12 August 2026

👩‍💻 Вакансия Frontend-разработчик (Vue.js) 🟢Удаленно🟢Полная занятость 🟢ЗП обсуждается на собеседовании 🟢В компанию Aston 🟦Задачи – разрабатывать, поддерживать и запускать многостраничные сайты и промо-страницы на Vue.js; – создавать адаптивные, интерактивные и кроссбраузерные интерфейсы по макетам из Figma; – интегрировать сайты с внешними REST API, CRM-системами и сервисами аналитики; – оптимизировать скорость заг

4 Aug 2026, 16:22 UTC58 viewsread 12 August 2026

🖥 Вакансия Python-разработчик 🟢Удаленно🟢Полная занятость 🟢ЗП обсуждается на собеседовании 🟢В компанию Т-Банк 🟦Задачи – Писать код и проводить код-ревью – Писать тесты на свой код – Наставлять и менторить младших коллег 🟦Требования – У вас есть опыт промышленной разработки на Python от 3 лет – Отлично знаете Python 3 – Есть опыт многопоточного и асинхронного программирования – Умеете работать с фреймворками FastApi

4 Aug 2026, 09:54 UTC62 viewsread 12 August 2026

⌨️ Вакансия PHP Developer 🟢Удаленно🟢Полная занятость 🟢ЗП обсуждается на собеседовании 🟢В компанию Aston 🟦Требования – опыт работы в роли PHP Developer от 3-х лет; – экспертное владение PHP 8+, принципами ООП и рефакторингом кода; – знание одного из фреймворков: Laravel, YII2 или Symfony; – опыт работы с реляционными БД (PostgreSQL/MySQL); – опыт работы с Redis/Memcached и очередями (RabbitMQ, Kafka или Redis как бр

28 Feb 2026, 15:41 UTC432 viewsread 12 August 2026

👨‍💻 Frontend (React) 🔥 Требования • React (hooks, performance), TypeScript • Vite / Webpack, пакетные менеджеры, линтеры, Git • Понимание HTTP, CORS, JWT, кеширования • REST / GraphQL (обработка ошибок, пагинация) • Компонентный подход, дизайн-системы, адаптив • HTML/CSS (Flex/Grid, анимации) • React Query / SWR + Redux Toolkit / Zustand • Jest / Vitest + Testing Library • Знание XSS, CSRF, безопасное хранение токе

27 Feb 2026, 14:37 UTC269 viewsread 12 August 2026

🧴 Руководитель отдела разработки и поддержки 1С (производство + логистика) 📍 Москва / удаленка 💰 от 350 000 ₽ на руки 🏢 Крупный производитель косметики О компании Российский производитель косметики с собственным производством, складами и полным контуром учета. Бизнес растет — автоматизация становится драйвером эффективности. В команде уже 10+ специалистов 1С, ищем сильного лидера, который выведет инфраструктуру на н

19 Feb 2026, 13:35 UTC285 viewsread 12 August 2026

#vacancy #работа #1C #консультант #Junior Вакансия: Консультант 1С:ЗУП Компания: аккредитованная IT компания Формат работы: офис, Москва (район Таганская) Вилка: 100 000 – 130 000 net в месяц 🔹Чем предстоит заниматься: - Поддержка пользователей 1С:ЗУП в офисе заказчика - Консультирование пользователей по работе в 1С:ЗУП 3.1 - Создание пользователей в базах 1С, настройка прав доступа - Исправление ошибок в данных (

18 Feb 2026, 05:56 UTC282 viewsread 12 August 2026

• Вакансия: UVM Verification Engineer • Компания: YADRO • Грейд: junior/middle/senior • Формат работы: удаленка, гибридный, офис: Москва, Санкт-Петербург, Нижний Новгород, Екатеринбург, Минск • Уровень ЗП: от 150 000 до 400 000 gross (зависит от грейда) Основные задачи: • Разработка и реализация верификационных планов. • Разработка, интеграция и поддержка автоматизированных тестовых окружений на UVM для IP/SoC. • П

4 Feb 2026, 11:52 UTC238 viewsread 12 August 2026

#вакансия #junior #go #golang #удаленка #fulltime Junior Golang разработчик Локация: РФ Формат работы: удаленка Занятость: полная Вилка: 100-125 тыс. руб. На руки Контакт: Аделя @Adelia021 Требования: • Понимание работы с реляционными базами данных (PostgreSQL). • Умение писать SQL-запросы, включая простые транзакции, JOIN и оптимизацию запросов. • Опыт работы с Redis (базовые знания). • Уверенные зна

29 Jan 2026, 08:15 UTC147 viewsread 12 August 2026

IOS разработчик middle Локация: Удалённо Компания: БИФИТ ЗП: от 285 000 до 335 000 р. Занятость: Полная Компания "БИФИТ" - аккредитованная продуктовая IT-компания один из лидеров на рынке разработки ПО для бизнеса, финансов, систем информационной, сетевой безопасности. Основное направление деятельности компании – разработка, внедрение и сопровождение системы электронного банкинга - ДБО «iBank». Приглашаем в команд

29 Jan 2026, 08:02 UTC152 viewsread 12 August 2026

C# .NET разработчик Локация: Удалённо Компания: Way to Win ЗП: от 250 000 до 300 000 р. Занятость: Полная Arigami — инновационная компания в сфере 3D-визуализации и дополненной реальности. Мы создаем интерактивные решения, которые помогают ритейлу продавать эффективнее: 3D-виджеты для сайтов, AR-приложения для шоу-румов и собственный AR-маркетплейс. Чем предстоит заниматься Разрабатывать и поддерживать высоконагру

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

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

“IT вакансии для всех” (@zizu_IT_RU), 3,932 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/zizu_IT_RU.

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.