Python Develeper Компания: ПАО Сбербанк Гео: Москва Формат: гибрид Условия: не указаны Нужно: опыт коммерческой разработки на Python от 3-х лет, хорошее знание FastAPI, опыт работы с SQL и одной из СУБД (PostgreSQL, ClickHouse, S3 и др.), понимание REST... Стек: fastapi · prometheus · grafana · victoriametrics · swagger/openapi · docker · git · postgresql rabota.sber.ru · открыть вакансию 🤖 job_ftch

Channel
AI Engineers Jobs
@ai_engineer_jobs
On this record: Growth · Engagement · Posts · Citations · Cite this entry
543subscribers
+53 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003939680219 |
|---|---|
| Type | Channel |
| Username | @ai_engineer_jobs |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/ai_engineer_jobs |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:14 | 543 | +46 |
| 6 Aug 2026, 21:56 | 497 | +7 |
| 6 Aug 2026, 18:48 | 490 | no change |
| 6 Aug 2026, 04:32 | 490 | first reading |
Engagement
20 posts held, back to 6 August 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.25%
- avg views ÷ 543 subscribers
- Avg views / post
- 50.3
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 6 August 2026) |
| Views total | 1,005 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 18:48 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.
Recent posts
Senior ML Engineer (ИИ-агенты для бизнеса) Компания: ПАО Сбербанк Гео: Москва Формат: гибрид Условия: не указаны Нужно: опыт разработки и продакшен-внедрения ML-сервисов от 3х лет, уверенные технические навыки, глубокие знания NLP и уверенная база в классическом ML, опыт... Стек: python · langgraph · llamaindex · fastapi · flask · tornado · bash · docker rabota.sber.ru · открыть вакансию 🤖 job_ftch
⚠️ Требует проверки Разработчик полного цикла с AI Компания: не указана Гео: Россия, Санкт-Петербург Формат: не указан Условия: не указаны getmatch.ru · открыть вакансию 🤖 job_ftch
ML-разработчик в команду автоматизаций в клиентском сервисе Yandex Crowd Компания: Yandex Crowd Гео: не указано Формат: не указан Условия: не указаны Нужно: Практический опыт в разработке агентов и внедрении RAG, Отличное понимание GenAI, Хорошее знание python, Опыт продакшн-разработки, Опыт MLOps/LLMOps Стек: python · rag · mlops · llmops t.me/ITjobsFeed · открыть пост 🤖 job_ftch
Technical Project Manager Компания: ПАО Сбербанк Гео: Москва Формат: гибрид Условия: не указаны Нужно: опыт управления проектами от 4 лет, из них не менее 2 лет — в сложных кросс-командных проектах с большим числом стейкхолдеров, уверенное владение инструментами... Стек: roadmap planning and visualization tools (unspecified) · status meetings / issue registry (process) rabota.sber.ru · открыть вакансию 🤖 job_ftch
Agent SRE (Site Reliability Engineer for AI Agents) (Blockchain) Компания: ПАО Сбербанк Гео: Москва, пр. Кутузовский 32к1 Формат: гибрид Условия: не указаны Нужно: опыт в роли SRE/DevOps от 3 лет коммерческого опыта эксплуатации высоконагруженных распределенных систем, глубокое понимание Kubernetes (архитектура... Стек: kubernetes · helm · jenkins · bitbucket · prometheus · grafana · loki · opentelemetry rabota.sb…
AI Product Analyst Компания: ПАО Сбербанк Гео: Москва Формат: не указан Условия: не указаны Нужно: опыт от 1,5 лет на ролях продуктового / стратегического / IT-аналитика, бизнес-консультанта, BA в IT-продукте или presale-аналитика в Enterprise-софте... Стек: excel · google sheets · sql · python · pandas · jupyter · anthropic · openai rabota.sber.ru · открыть вакансию 🤖 job_ftch
Инженер по ИИ/AI Agent Engineer (LLM & Agentic Systems) Компания: Градиент Гео: Москва, Россия Формат: гибрид Условия: не указаны Нужно: Опыт создания агентов на современных фреймворках (LangChain, LangGraph, LlamaIndex и тд), Знания стратегий планирования AI-агентов (ReAct, Plan-and-Execute... Стек: langchain · langgraph · llamaindex · weaviate · pinecone · qdrant · milvus · ragas hh.ru · открыть вакансию 🤖 job_f…
Fullstack Developer (AI) Компания: NDA Гео: Санкт-Петербург Формат: гибрид Условия: не указаны Нужно: Опыт самостоятельной разработки на React., Владение Python, фреймворками Django и FastAPI., Знание ML и опыт работы с языковыми моделями (LLM), RAG и... Стек: react · python · django · fastapi · cursor · claude code · codex hirify.me · открыть вакансию 🤖 job_ftch
Project Manager (AI) Компания: Yandex Гео: Россия Формат: гибрид Условия: не указаны Нужно: Опыт работы в проектном менеджменте от 3 лет., Опыт администрирования и внедрения систем для оптимизации бизнес-процессов., Навыки эффективного взаимодействия... Стек: sql · airflow · etl · dashboards hirify.me · открыть вакансию 🤖 job_ftch
AI / LLM Inference Engineer Компания: Ключевые ИТ Решения Гео: Москва, Россия Формат: гибрид Условия: не указаны Нужно: практический опыт запуска и оптимизации моделей на GPU, опыт работы хотя бы с одним inference engine: vLLM, Triton Inference Server, TensorRT-LLM, TGI или... Стек: openstack · kubernetes · linux · docker · nvidia gpu · vllm · triton inference server · tensorrt-llm hh.ru · открыть вакансию 🤖 job_f…
Agent SRE (Site Reliability Engineer for AI Agents) (Blockchain) Компания: Сбер. IT Гео: Москва, Россия Формат: гибрид Условия: не указаны Нужно: опыт в роли SRE/DevOps от 3 лет коммерческого опыта эксплуатации высоконагруженных распределенных систем, глубокое понимание Kubernetes (архитектура... Стек: kubernetes · helm · jenkins · bitbucket · git · groovy · python · postgresql hh.ru · открыть вакансию 🤖 job_ftch
Showing the 12 most recent of 20 posts we hold for @ai_engineer_jobs. 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 — 150,880 of 1,548,671entries 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.
Mentions
Named by 3 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“AI Engineers Jobs” (@ai_engineer_jobs), 543 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ai_engineer_jobs.
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.