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

Channel

Data Engineer Jobs KZ

@datajobs_kz

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

243subscribers

+25 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003967820412
TypeChannel
Username@datajobs_kz
CreatedBetween 1 April 2026 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/datajobs_kz

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

218243230.57 August 2026 — 218 subscribers8 August 2026 — 218 subscribers16 August 2026 — 227 subscribers23 August 2026 — 229 subscribers6 September 2026 — 236 subscribers14 September 2026 — 243 subscribers7 August 202614 September 2026
6 measurements spanning 38 days, net +25. 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 214–247 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 23:38243+7
6 Sept 2026, 12:19236+7
23 Aug 2026, 10:56229+2
16 Aug 2026, 08:47227+9
8 Aug 2026, 10:45218no change
7 Aug 2026, 20:50218first reading

Engagement

20 posts held, back to 30 April 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

14 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎750.0%
428.6%
👍321.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 10 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 14 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 30 April 2026 to 7 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

7 Aug 2026, 16:01 UTC80 views1 reactionsread 8 August 2026

Привет👋 Новая вакансия Data Engineer для работы в офисе, в Алматы. Стек: Airflow, Python, MSSQL, Postgre. Локация: Алматы (строго). Формат работы: FULL-TIME Задачи на проекте: Интеграция и добавление источника данных из системы 1С в корпоративное хранилище. Обязательные требования к кандидатам: Опыт коммерческой разработки на Python от 2 лет. Уверенная работа с Apache Airflow (написание DAG-ов, настройка расписаний,

👎1

3 Aug 2026, 05:34 UTC136 viewsread 8 August 2026

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

16 Jul 2026, 18:38 UTC238 views1 reactionsread 8 August 2026

🔥 Вакансия: Data Engineer в inDrive Гео: Казахстан или Грузия Команда inDrive ищет сильного инженера по данным! Ребята не просто настраивают конвейеры, а строят с нуля современную платформу на передовом облачном стеке. 🛠 Стек проекта: • BigQuery, Databricks, Airflow • Kafka с Debezium CDC • Dataflow, Kubernetes на GCP 🎯 Кого ищут: • Сильный практический Python: написание чистого, хорошо спроектированного и протест

👍1

15 Jul 2026, 11:07 UTC341 viewsread 8 August 2026

Теперь в Казахстане официально разрешено брать на работу без диплома. https://designer.kz/2026/07/the-economics-of-real-skills/ Если у вас не профильного ИТ образования и хотите работать DE, двери открыты еще шире!

10 Jul 2026, 13:29 UTC259 views1 reactionsread 8 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,

👎1

7 Jul 2026, 03:00 UTC194 viewsread 8 August 2026
Forwarded from @data_engineer_jobs

🚀 Ищем Data Engineer в Центр Цифрового Развития Национального Банка Казахстана! 📍 Локация: Астана (офис / гибрид) 💰 Вилка: до 900 000 ₸ + прозрачные премии (ежемесячные, годовые) ПРОСЬБА направлять CV только в случае, если указанный уровень заработной платы вас устраивает. 💼 Формат: Full-time За полгода наша команда вывела в прод более 10 AI-продуктов. Сейчас усиливаем направление Data Engineering под новый проект

6 Jul 2026, 04:06 UTC218 viewsread 8 August 2026
Photo

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

15 Jun 2026, 07:55 UTC294 viewsread 8 August 2026

Всем привет 🙋‍♀️ Я в поиске Data Architect в направление Data Governance для развития корпоративной архитектуры данных и построения единого информационного пространства компании. Важен опыт разработки доменной моделей данных, миграции с DWH на Lakehouse, интеграции корпоративных систем и источников данных, а также построения процессов консолидации и унификации данных. Роль предполагает участие в формировании целевой

12 Jun 2026, 00:24 UTC322 views2 reactionsread 8 August 2026

Freedom Bank ищет DWH Support Engineer / DevOps 📍 Локация: Алматы 🏢 Формат: офис / гибрид Ищем инженера, который поможет поддерживать стабильность, автоматизацию и развитие инфраструктуры DWH (Data Warehouse). Если тебе близки задачи оптимизации, CI/CD, мониторинга и ETL — присоединяйся к нашей команде 💡 🔹 Основная роль: Поддержка, координация и оптимизация процессов сопровождения DWH. 🔹 Твои задачи: • Анализ и у

2

10 Jun 2026, 03:18 UTCviews —

Data Engineer Jobs KZ pinned «Что должен знать Junior Data Engineer, чтобы его взяли на работу? Один из самых частых вопросов новичков: «а что вообще учить, чтобы получить первый оффер в DE?». Стек огромный, и легко потратить месяцы не на то. Я собрал карту навыков для junior-дата-инженера…»

10 Jun 2026, 03:17 UTC250 viewsread 8 August 2026

Что должен знать Junior Data Engineer, чтобы его взяли на работу? Один из самых частых вопросов новичков: «а что вообще учить, чтобы получить первый оффер в DE?». Стек огромный, и легко потратить месяцы не на то. Я собрал карту навыков для junior-дата-инженера - что реально нужно и до какой глубины. Без воды - только то, что нужно на старте. Это часть моего курса по Data Engineering для новичков. Веду канал, где де

Showing the 12 most recent of 20 posts we hold for @datajobs_kz. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“Data Engineer Jobs KZ” (@datajobs_kz), 243 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/datajobs_kz.

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.