10 Aug 2026, 15:41 UTC≈1,120 views6 reactionsread 12 August 2026
Posted without readable text
🤔6
Channel
Data Engineer Работа Вакансии
@de_rabota
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,920subscribers
+175 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001378035988 |
|---|---|
| Type | Channel |
| Username | @de_rabota |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/de_rabota |
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 13 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 04:57 | 4,920 | +26 |
| 9 Sept 2026, 15:39 | 4,894 | +23 |
| 4 Sept 2026, 14:00 | 4,871 | +22 |
| 1 Sept 2026, 09:36 | 4,849 | +16 |
| 29 Aug 2026, 11:49 | 4,833 | +15 |
| 26 Aug 2026, 12:14 | 4,818 | +14 |
| 23 Aug 2026, 09:48 | 4,804 | +8 |
| 19 Aug 2026, 13:32 | 4,796 | +17 |
| 16 Aug 2026, 22:28 | 4,779 | +7 |
| 13 Aug 2026, 08:52 | 4,772 | +14 |
| 10 Aug 2026, 16:53 | 4,758 | +13 |
| 7 Aug 2026, 11:33 | 4,745 | no change |
| 6 Aug 2026, 15:37 | 4,745 | first reading |
Engagement
25 posts held, back to 17 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 8 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 25 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
116 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 65.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤔 | 76 | 65.5% | |
| ❤ | 23 | 19.8% | |
| 👍 | 9 | 7.76% | |
| 🔥 | 8 | 6.90% |
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 22 of the 25 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 17 July 2026 to 10 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
10 Aug 2026, 10:40 UTC≈1,180 views2 reactionsread 12 August 2026
Data Engineer #удаленка #senior Компания: BGStaff ☑️Ключевые задачи -Проектирование, разработка и сопровождение ETL/ELT-пайплайнов с использованием Snowflake и SQL -Управление облачной инфраструктурой на AWS (S3, Glue, Lambda, CloudWatch, IAM) -Написание чистого и поддерживаемого кода на Python -Автоматизация развертывания и настройки инфраструктуры через Terraform -Оркестрация рабочих процессов с помощью Apache Air…
❤2
9 Aug 2026, 10:40 UTC≈1,240 views0 reactionsread 12 August 2026
Data Engineer #гибрид Москва Компания: Облако.ру 🔹ОБЯЗАННОСТИ -Проектирование и развитие data-пайплайнов для обработки событий кибербезопасности; -Нормализация и обогащение событий безопасности; -Проектирование и оптимизация аналитического хранилища данных (ClickHouse / StarRocks / аналоги); -Подготовка витрин данных под быстрые запросы и аналитику; -Эксплуатация data сервисов в Kubernetes: деплой, ресурсы, отказоус…
8 Aug 2026, 10:40 UTC≈1,200 views1 reactionsread 12 August 2026
Data Engineer в команду SMT #удаленка Компания: 2ГИС 🔹Что предстоит делать -Разрабатывать с нуля MVP новой дата‑платформы и инфраструктуры для ingest/transform. -Мигрировать существующие пайплайны с Hadoop/HDFS на новую архитектуру (S3, Kafka, Spark, ClickHouse). -Работать с большими объёмами данных и высоконагруженными Kafka‑топиками. -Строить отказоустойчивые пайплайны обработки и доставки данных. -Участвовать в а…
❤1
7 Aug 2026, 10:40 UTC≈1,190 views1 reactionsread 12 August 2026
Data Engineer, Подготовка офлайн-факторов ранжирования #удаленка #middle Компания: OZON ☑️Примеры задач -Подготовка витрин и датасетов для команд, аналитики, DS и ML. -Оптимизация Spark-задач, SQL-запросов и процессов поставки данных. Настройка регулярных процессов подготовки витрин данных и контроль их качества. -Разбор инцидентов в процессах подготовки витрин и повышение их надежности. ☑️Нам важно -Опыт разработк…
❤1
6 Aug 2026, 10:40 UTC≈1,760 views4 reactionsread 12 August 2026
Data Engineer #удаленка Компания: Авиасейлс 🔹Что нужно делать -активно участвовать в командном чате: отслеживать запросы, оперативно реагировать на вопросы и задачи в рабочее время; -мониторить системы и решать возникающие инциденты вместе с дежурными дата инженерами; -оптимизировать текущие процессы обработки данных; -модернизировать текущую дата платформу вместе с Core командой дата инженеров. 🔹Чего ждём от тебя …
❤4
5 Aug 2026, 10:40 UTC≈1,720 views14 reactionsread 12 August 2026
Data Engineer в Корпоративное хранилище #удаленка Компания: Wildberries 🔹Что нужно делать -Обеспечивать стабильную, производительную и безопасную работу Data Platfrorm на базе Trino, Spark, S3 и Apache Iceberg, включая администрирование и управление ролевой моделью доступа, документирование изменений в проекте -Настраивать, обновлять, мониторить и тюнить кластера Trino -Настраивать коннекторы (Iceberg, S3) -Оптимизи…
🤔8🔥4❤2
4 Aug 2026, 11:15 UTC≈1,620 views15 reactionsread 12 August 2026
🚀 Вакансия: Data Engineer (удаленно/гибрид) Компания: ООО "ОДСС" https://odsscompany.ru (аккредитованная IT-компания) Локация Москва Зрплата от 150 до 170 т.р. Оформление по ТК РФ Мы ищем в свою команду инициативного Data Engineer для разработки и поддержания инфраструктуры данных для большого проекта озера данных, включающего себя сложные сценарии приема и обработки данных из разных источников. Что предстоит: • ра…
🤔13❤2
4 Aug 2026, 10:40 UTC≈1,560 viewsread 12 August 2026
Data Engineer #офис #гибрид #senior Компания: CINIMEX ☑️Задачи: -Разработка ETL-пайплайнов (Apache Spark on java, HDFS (parquets), ClickHouse, Hive, Greenplum); -Разработка витрин данных в Greenplum и ClickHouse; -Оркестрация ETL-процессов; -Оптимизация ETL-процессов (батчинг, ретраи, SLA-контроль); -Взаимодействие с BI-разработчиками и DevOps для своевременной доставки данных в Superset. ☑️Ожидаем от Вас: -Глубок…
3 Aug 2026, 14:00 UTC≈1,670 views2 reactionsread 12 August 2026
Data Engineer в команду CDP #удаленка Компания: 2Гис 🔹Тебе предстоит -Повысить эффективность пайплайнов для расчета с daily-признаков на основе batch процессинга. -Создать эффективный пайплайн для расчёта realtime-признаков на основе Kafka‑топиков. -Проектировать и разрабатывать сервисы, обрабатывающие миллиарды событий пользователей. -Решать сложные инженерные задачи: расчеты метрик, построение витрин. -Работать с …
🤔2
1 Aug 2026, 10:40 UTC≈1,820 views1 reactionsread 12 August 2026
Инженер данных #гибрид Москва Компания: Альфа-Банк 🔹Чем предстоит заниматься -Реализация высоконагруженных конвейеров обработки данных для обеспечения надежной и бесперебойной репликации данных из ИТ-систем Банка. -Реализация комплексных задач по подготовке данных в целевых аналитических хранилищах (DataLake, SandBox, FeatureStore) для построения признаков, необходимых для разработки моделей машинного обучения. -Раз…
🤔1
31 Jul 2026, 10:40 UTC≈1,930 viewsread 12 August 2026
Data-инженер в команду SQL-SWAT #удаленка Компания: Авито ☑️Какие задачи вас ждут: -разрабатывать сервисы, CLI-инструменты и LLM-инструменты для ускорения и упрощения процесса миграции; -самостоятельно мигрировать объекты с помощью созданных инструментов: -транслировать код; -верифицировать данные; -переносить историю; -переключать зависимости; -обучать и поддерживать пользователей при работе с селф-сервис-инструмен…
Showing the 12 most recent of 25 posts we hold for @de_rabota. 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.
Mentions
Named by 4 registered channels — 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Job for Analysts & Data Scientists
@foranalysts · 36,592
Telegram ranks this channel #17 of 96 here — alongside 95 others — read 1 September 2026
@foranalysts · 36,592
Telegram ranks this channel #17 of 96 here — alongside 95 others — read 1 September 2026
Data Engineering Zoomcamp
@dezoomcamp · 30,361
Telegram ranks this channel #25 of 69 here — alongside 68 others — read 15 September 2026
@dezoomcamp · 30,361
Telegram ranks this channel #25 of 69 here — alongside 68 others — read 15 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Data Engineer Работа Вакансии” (@de_rabota), 4,920 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/de_rabota.
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.