Telegram RegisterThe public register of Telegram
Telegram profile photo for ITvacancy KZ & UZ

Channel

ITvacancy KZ & UZ

@itvacancykz

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

13,657subscribers

+1,690 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002321256587
TypeChannel
Username@itvacancykz
Description🚀 Вакансии IT и Маркетинга в Казахстане и Узбекистане. 🎯 Поиск талантливых специалистов в свою команду Здесь: ✅ Актуальные вакансии и резюме ✅ Полезные советы для соискателей По вопросам публикации своих CV и вакансии: @Kira_BK
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/itvacancykz

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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@itvacancykz/1979 · this entry27 Aug 2026, 06:29 UTC@itcom_kz/722127 Aug 2026, 06:56 UTC1.0028 minutes
@itvacancykz/2163 · this entry9 Nov 2026, 12:29 UTC@itcom_kz/76509 Nov 2026, 12:30 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@itcom_kz19 (8/8 hand-verifiable sample passed)1.0013 minutesthis entry (18–1)

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. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 119 comparable posts for this entry, running 25 July 2026 to 13 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @itvacancykz — 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 14 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

11,96713,65712,8126 August 202613 November 2026
66 measurements spanning 98 days, net +1,690. 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,714–13,911 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
13 Nov 2026, 08:2013,657+28
10 Nov 2026, 20:3513,629+24
9 Nov 2026, 07:5113,605+5
8 Nov 2026, 02:2913,600+2
6 Nov 2026, 21:0713,598+20
5 Nov 2026, 23:3113,578+13
4 Nov 2026, 21:1813,565+10
3 Nov 2026, 17:1913,555+4
2 Nov 2026, 17:3613,551+22
1 Nov 2026, 14:3613,529+7
31 Oct 2026, 12:0613,522+8
30 Oct 2026, 13:3013,514+21
29 Oct 2026, 11:5613,493+33
28 Oct 2026, 08:3913,460+30
27 Oct 2026, 08:1713,430+22
26 Oct 2026, 10:0113,408+15
25 Oct 2026, 11:0813,393+29
24 Oct 2026, 12:4613,364+9
23 Oct 2026, 15:5113,355+30
22 Oct 2026, 18:5713,325first reading

Engagement

126 posts held, back to 25 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 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
32.7%
avg views ÷ 13,657 subscribers
Avg views / post
4,470
50 posts measured
Reaction rate
0.255%
reactions ÷ views · ER floor
Posts in window
54
of 126 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. It is computed over the 47 of 50 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held126 (25 July 2026 – 14 November 2026)
Views total223,530
Reactions total540
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 20:35 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
≈35
Links
≈1,020

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

935 reactions across 108 posts, in 13 distinct kinds. The most used accounts for 60.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤56360.2%
👍15416.5%
🥱869.20%
🤔373.96%
🤨293.10%
😐242.57%
😁171.82%
🔥80.856%
🌭60.642%
🥴50.535%
👏40.428%
👀10.107%
💔10.107%

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

Measured over the 126 most recent posts we hold, published 25 July 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 0 of 54 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 09:00 UTC≈2,120 views1 reactionsread 14 November 2026

AI engineer/LLM engineer во вторую команду По задачам: • Проектирование RAG-архитектур: разработка и оптимизация пайплайнов извлечения данных (chunking strategies, embedding selection, re-ranking) • Prompt Engineering & Optimization: создание сложных системных инструкций, использование техник Chain-of-Thought, Few-shot, ReAct. Работа над воспроизводимостью ответов • Разработка AI-агентов: создание автономных систем …

💔1

13 Nov 2026, 12:38 UTC≈3,010 views11 reactionsread 14 November 2026

Full Stack разработчик - Офис в центре Ташкента, здание Федерации профсоюзов Узбекистана (ориентир — ГАБТ) Основные задачи: - Разработка и техническая поддержка сайта; - Работа с Django и Backend; - Разработка интеграций с государственными информационными системами и внешними сервисами через API; - Оперативное устранение технических проблем сайта; - Доработка существующего функционала и внедрение новых решений. Тре…

😐9❤1🥱1

13 Nov 2026, 12:01 UTC≈2,990 views5 reactionsread 14 November 2026

IT Project Manager – Digital Transformation 📍 Location: Abu Dhabi, UAE Project Type: Yearly Renewable Contract Experience: 8+ Years Notice Period: Immediate to 15 Days 📌 Candidates currently based anywhere within the UAE are welcome to apply. Key Responsibilities: Lead end-to-end IT and digital transformation projects, ensuring delivery within scope, budget and timelines. Manage project plans, milestones, budgets, r…

🤔4👍1

13 Nov 2026, 10:09 UTC≈3,510 views48 reactionsread 14 November 2026

СТО Астана Нужно будет менеджерить разработку 3 команд 50+ человек (разработчики бэкенд и фронт, аналитики, qa, девопсы, мобильная разработка). Две команды software, третья - hardware. Нужен человек, который умеет выстраивать процессы разработки в кросс-функциональных командах, знает и понимает как внедрять ИИ в разработку, без слепого фанатизма "мы сейчас всё отдадим ИИ агентам", не брезгует засучить рукава и затра…

🤔28🤨7😁6❤5😐2

13 Nov 2026, 07:38 UTC≈3,580 viewsread 14 November 2026

𝗗𝗮𝘁𝗮 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 📍 Ташкент, Узбекистан | Офис, полная занятость ЗАДАЧИ • Подключение источников данных (БД, файлы, CDC), инкрементальные загрузки • Трансформации между слоями хранилища и проектирование аналитических витрин • Разработка и поддержка пайплайнов в оркестраторе • Контроль качества данных: тесты, полнота, идемпотентность загрузок • Оптимизация производительности: партиционирование, форматы таблиц, планы вып…

12 Nov 2026, 17:15 UTC≈3,740 views1 reactionsread 14 November 2026

Middle Data Engineer and Senior Data Engineer. 📍 On-site • Full-time • Tashkent, Uzbekistan Both roles are for engineers who are comfortable working beyond isolated development tasks: building and improving data pipelines, dealing with performance and reliability, maintaining data quality, and contributing to migration and modernization work. Python and SQL are important for both positions, as is English at B2+ leve…

🤨1

12 Nov 2026, 14:10 UTC≈4,540 views10 reactionsread 14 November 2026

Senior System Developer (C++ / HFT) Формат: Full-time, Remote (пересечение с европейскими часовыми поясами) Зарплата: $6 000–10 000 Компания развивает высокопроизводительную торговую инфраструктуру для криптовалютного рынка и ищет Senior C++ Developer с опытом разработки HFT-систем и Market Making для централизованных криптобирж. Обязателен практический опыт работы с Binance в контексте алгоритмической торговли или…

❤10

12 Nov 2026, 10:52 UTC≈4,130 views6 reactionsread 14 November 2026

Solva Technology | System / Network Administrator (Middle+/Senior) 📍 Алматы | Только офис | 5/2 | Full-time Усиливаем IT-команду Solva Technology специалистом с глубокой экспертизой в корпоративных сетях и сетевой безопасности. Ключевые требования (Must-have): • FortiGate — самостоятельное администрирование Firewall Policies, NAT, VPN, маршрутизации. • Site-to-site IPsec VPN — настройка и диагностика. • Корпорати…

😁4❤2

12 Nov 2026, 09:44 UTC≈5,000 views232 reactionsread 14 November 2026

Уважаемые участники канала, Самое важное правило при отклике на вакансию - читайте полное описание вакансии и подавайтесь только если вы на 100% подходите! Последнее время много жалоб от HR, что отклики не релевантны, если пишут город и написано офлайн, сотни людей пишут, можно ли удаленно, если позиция Мидл - пишут сотни джунов, если написано Дубай, значит отклик только если вы там, не нужно писать - вы сделаете ви…

❤103🥱64🤨21👍11🔥8🌭6😁6🤔5

11 Nov 2026, 16:10 UTC≈1,860 views3 reactionsread 11 November 2026

АО «Bereke Bank» ищет Senior Data Scientist — человека, который ведёт модель от постановки задачи до мониторинга и не теряет к ней интерес после релиза. Для кредитных рисков (розница и корпоративный бизнес), портфельные модели, взыскание (soft/hard collection) и антифрод. Что предстоит: ▪️ самостоятельно вести DS-решения от идеи до production ▪️ вместе с бизнесом формулировать и проверять гипотезы ▪️ разбираться, по…

❤2🥱1

11 Nov 2026, 13:20 UTC≈3,890 views2 reactionsread 12 November 2026

RAKETA ищут Product Manager / Technical Product Manager. Запускают новый продукт в сфере e-commerce и SaaS и ищем сильного продакта, который возьмет на себя его развитие — от MVP до достижения бизнес-показателей и масштабирования. Что важно: Опыт работы в e-commerce и технический бэкграунд. Опыт запуска и развития цифровых продуктов. Системное мышление и ориентация на бизнес-результат. Навыки автоматизации, особенн…

❤2

11 Nov 2026, 13:18 UTC≈3,270 views0 reactionsread 12 November 2026

Andersen Lab 𝐢𝐬 𝐡𝐢𝐫𝐢𝐧𝐠: 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭 We're looking for an experienced Solution Architect to join a project developing an automated corporate lending platform with ML-based credit scoring and predictive analytics. 📍 𝐋𝐨𝐜𝐚𝐭𝐢𝐨𝐧: Uzbekistan 🏢 𝐖𝐨𝐫𝐤 𝐟𝐨𝐫𝐦𝐚𝐭: On-site in Tashkent 𝐓𝐞𝐜𝐡 𝐬𝐭𝐚𝐜𝐤: Microservices, APIs, Message Bus, Event-Driven Architecture, Kubernetes, ML Integration, Loan Origination Systems (LOS), Decisio…

Showing the 12 most recent of 126 posts we hold for @itvacancykz. 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 recorded as deleted after publishing

We recorded 1 post on @itvacancykz as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 November 2026
Most recent seen missing
10 November 2026
Median time before seen missing
30 hours
Seen missing in the last 30 days
1

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

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

“ITvacancy KZ & UZ” (@itvacancykz), 13,657 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/itvacancykz.

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.