Telegram RegisterThe public register of Telegram

Channel

Data Engineer Jobs UZ

@datajobsuzb

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

152subscribers

+0 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 live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/datajobsuzb

Growth

15210 Aug 2026, 00:47 — 152 subscribers11 Aug 2026, 00:15 — 152 subscribers10 Aug 2026, 00:4711 Aug 2026, 00:15
2 measurements taken within a single day. 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 151–153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:15152no change
10 Aug 2026, 00:47152first reading

Engagement

20 posts held, back to 11 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
63.8%
avg views ÷ 152 subscribers
Avg views / post
97.0
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (11 May 20263 August 2026)
Views total291
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 00:47 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.

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 4reactions 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.

Citation-graph rank

Citation-graph rank — 1,144,607 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“Data Engineer Jobs UZ” (@datajobsuzb), 152 subscribers as measured 11 August 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.