Telegram RegisterThe public register of Telegram
Telegram profile photo for Data Engineer Jobs UZ

Channel

Data Engineer Jobs UZ

@datajobsuzb

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

168subscribers

+16 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003662699042
TypeChannel
Username@datajobsuzb
CreatedBetween 1 December 2025 and 11 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/datajobsuzb

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@datajobsuzb/25 · this entry11 May 2026, 11:45 UTC@datajobs_kz/1711 May 2026, 11:46 UTC1.00under a minute
@datajobsuzb/26 · this entry14 May 2026, 10:51 UTC@datajobs_kz/1814 May 2026, 10:53 UTC1.002 minutes
@datajobsuzb/27 · this entry14 May 2026, 10:51 UTC@datajobs_kz/1914 May 2026, 10:53 UTC1.002 minutes
@datajobs_kz/215 Jun 2026, 15:52 UTC@datajobsuzb/33 · this entry5 Jun 2026, 15:53 UTC1.00under a minute
@datajobsuzb/39 · this entry6 Jul 2026, 04:06 UTC@datajobs_kz/266 Jul 2026, 04:06 UTC1.00under a minute
@datajobs_kz/2810 Jul 2026, 13:29 UTC@datajobsuzb/41 · this entry10 Jul 2026, 13:29 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
@datajobs_kz7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (5–2)
@datajobskg5 (5/5 hand-verifiable sample passed)1.00under a minute@datajobskg (4–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. None of the 6 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 11 May 2026 to 3 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @datajobsuzb — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 11 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 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

15016815910 August 2026 — 152 subscribers11 August 2026 — 152 subscribers18 August 2026 — 150 subscribers1 September 2026 — 154 subscribers11 September 2026 — 156 subscribers18 September 2026 — 165 subscribers4 October 2026 — 164 subscribers20 October 2026 — 166 subscribers28 October 2026 — 167 subscribers13 November 2026 — 168 subscribers10 August 202613 November 2026
10 measurements spanning 95 days, net +16. 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 147–171 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 01:26168+1
28 Oct 2026, 18:09167+1
20 Oct 2026, 23:05166+2
4 Oct 2026, 02:57164-1
18 Sept 2026, 14:59165+9
11 Sept 2026, 04:16156+2
1 Sept 2026, 21:13154+4
18 Aug 2026, 08:22150-2
11 Aug 2026, 00:15152no change
10 Aug 2026, 00:47152first reading

Engagement

20 posts held, back to 11 May 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 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥375.0%
👎125.0%

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

Measured over the 20 most recent posts we hold, published 11 May 2026 to 3 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.

Recent posts

3 Aug 2026, 05:33 UTC62 viewsread 10 August 2026

Что говорят участники курса Data Human Первый отзыв - от человека, который в IT 15 лет. Сопровождение, ETL на Oracle/MSSQL/Talend, потом 6 лет системным аналитиком в банке. Сейчас переходит в современный DE: «Я проходил разные курсы, и есть те, от которых прям чувствуется value: понятно объяснено, покрыто основное, материал про то, что реально используется на практике. Этот курс ощущается как раз таким.» Второй - …

23 Jul 2026, 14:17 UTC114 viewsread 10 August 2026

Ucell, ищем в команду IT инфраструктуры Cloud Engineer и Database administrator (DBA) Ucell — это один из крупнейших ⁠мобильных операторов Узбекистана, предоставляющий услуги сотовой связи и интернета. если вы в поиске новых возможностей или знаете подходящих специалистов — пишите! ☁️ Cloud Engineer Стек: Linux, Windows Server, Huawei Cloud, Azure, OpenShift, VMware, KVM, Docker, Kubernetes, Terraform, Ansible, CI…

21 Jul 2026, 09:09 UTC115 viewsread 10 August 2026

#vacancy #jobs #вакансия #офис #fulltime Должность: Data Engineer / DWH Developer Локация: Ташкент Компания: партнер HaaS Platform Занятость: Полная Формат: Офис ЗП: от 3000$ net (обсуждается по результатам интервью) Data Engineer DWH Мы ищем опытного Data Engineer / DWH-разработчика для работы над аналитическими системами в финансовом домене. Нам нужен практичный специалист, который сможет быстро погрузиться в пр…

15 Jul 2026, 09:57 UTC86 viewsread 10 August 2026
Forwarded from @data_engineer_jobsPhoto

Директор по данным (CDO, Chief Data Officer) APEXBANK приглашает Chief Data Officer (CDO) — руководителя, который сформирует и реализует стратегию управления данными и превратит данные в контролируемый корпоративный актив, которому доверяют бизнес и регулятор. Роль подотчётна Правлению; CDO возглавляет Data Office и Комитет по управлению данными. Что предстоит делать: • Разработать и реализовать Data Strategy как ч…

10 Jul 2026, 13:29 UTC187 views0 reactionsread 10 August 2026

🚀 𝐖𝐞'𝐫𝐞 𝐡𝐢𝐫𝐢𝐧𝐠 𝐃𝐚𝐭𝐚 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬! We have 2 𝒉𝒐𝒕 𝑫𝒂𝒕𝒂 𝑬𝒏𝒈𝒊𝒏𝒆𝒆𝒓 𝒐𝒑𝒆𝒏𝒊𝒏𝒈𝒔 and are looking for talented professionals to join our team. 📍 𝐎𝐩𝐞𝐧 𝐩𝐨𝐬𝐢𝐭𝐢𝐨𝐧𝐬: 🔗 𝐃𝐚𝐭𝐚 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫 (𝐌𝐮𝐬𝐭 𝐡𝐚𝐯𝐞: AWS, Kafka, Airflow) 🔗 𝐃𝐚𝐭𝐚 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫 🌍 𝐋𝐨𝐜𝐚𝐭𝐢𝐨𝐧: Georgia • Kazakhstan • Uzbekistan • Azerbaijan • Kyrgyzstan • Serbia • Moldova. 🏡 𝐖𝐨𝐫𝐤 𝐟𝐨𝐫𝐦𝐚𝐭: Remote / Hybrid / Office. 𝐖𝐡𝐲 𝐣𝐨𝐢𝐧 𝐀𝐧𝐝𝐞𝐫𝐬𝐞𝐧? ✅ Work with global clients such as Samsung, Siemens,…

7 Jul 2026, 22:20 UTC168 viewsread 10 August 2026

🚀 В поисках Data Governance Manager в TBC Uzbekistan. Сейчас мы строим Data Governance как полноценную функцию: catalog, glossary, DQ, Data Ownership, процессы, политики и культуру работы с данными. Масштаб большой, задач много, влияния – еще больше. Что важно: • Опыт в Data Governance / Data Management; • Понимание жизненного цикла данных; • Уверенный SQL; • Опыт внедрения DG-решений, работы с DWH/Data Lake и опыт …

6 Jul 2026, 04:06 UTC156 viewsread 10 August 2026
Photo

Представь, ты - junior DE в нейротех-стартапе Sign System. Продукт DataVision - носимый датчик, который ловит момент, когда человек начинает засыпать, и будит его до микросна. Клиент - Kingsroad, автоперевозчик с 12000 фур. Боль клиента: дальнобойщик засыпает за рулём, и это стоит жизней. Разбудить - не твоя задача, это делает само устройство мгновенно. Твоя задача начинается дальше: данные с каждого датчика улетают…

28 Jun 2026, 08:00 UTC200 viewsread 10 August 2026

Team Lead Data Engineer в Alif Uzbekistan Локация: Ташкент Формат: офис/гибрид/удалённо Доход: при собеседовании Опыт: 3-6 лет Задачи: проектирование архитектуры данных и ETL/ELT-пайплайнов, развитие Data-платформы, контроль качества данных и производительности процессов, проведение code review и менторство команды. Требуется глубокое знание SQL и СУБД, опыт работы с Airflow и Kafka, уверенное владение Python, пон…

26 Jun 2026, 18:26 UTC106 viewsread 10 August 2026
Forwarded from @data_engineer_jobs

⚙️ Junior Data Engineer — Ташкент В команду Core Technology ищут Junior Data Engineer. Обязательные требования: - Базовые знания SQL - Понимание основ DWH, ETL/ELT и работы с данными - Понимание принципов построения и обработки данных - Интерес к сфере Data и готовность развиваться - Русский язык — рабочий язык команды Рассматриваются кандидаты уровня Junior с базовыми знаниями и/или минимальным коммерческим опыто…

24 Jun 2026, 13:43 UTC185 viewsread 10 August 2026

📍 Data Hunter — TBC Uzbekistan, Ташкент Дата-команда TBC Uzbekistan расширяется и ищет Data Hunter. Чем предстоит заниматься: — Поиск новых источников данных (behavioral, digital signals) для улучшения кредитного скоринга и фрод-превенции — Тесная работа с командами Risk, Product и Data Engineering — Тестирование и интеграция новых потоков данных Что нужно: — Опыт в Data Sourcing, Risk Analytics или Fintech — Опыт п…

23 Jun 2026, 13:43 UTC163 views1 reactionsread 10 August 2026

🚀 CORE TECHNOLOGY расширяет команду и приглашает специалистов в офис в Ташкенте! Открытые вакансии: 🔹 Head of Data / CDO 🔹 Junior Data Engineer 🔹 Junior Data Analyst / Младший аналитик данных 🔹 Data Engineer 🔹 DevOps Engineer 📍 Локация: Ташкент, Узбекистан ❗️ Обязательные требования для всех позиций: • Работа в офисе (удаленный формат не рассматривается); • Нахождение на территории Ташкента; • Обязательное владение р…

👎1

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

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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.

“Data Engineer Jobs UZ” (@datajobsuzb), 168 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/datajobsuzb.

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.