Telegram RegisterThe public register of Telegram
Telegram profile photo for Jobs to be Loved | Вакансии для IT-специалистов

Channel

Jobs to be Loved | Вакансии для IT-специалистов

@jtbl_vacancy

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,441subscribers

+1,719 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-1002403817147
TypeChannel
Username@jtbl_vacancy
DescriptionJTBL Vacancies — Jobs to be Loved — Вакансии, в которые влюбляются ✦ ежедневные подборки вакансий из IT и Digital с прямыми контактами | РФ, СНГ, удаленно по всему миру ✦ от команды JTBL @jobstobeloved Предложить вакансию и задать вопрос: @jtbl_company
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/jtbl_vacancy

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 12 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 the other topics.

Growth

5,7227,4416,581.56 August 2026 — 5,722 subscribers6 August 2026 — 5,722 subscribers7 August 2026 — 5,728 subscribers9 August 2026 — 5,741 subscribers12 August 2026 — 5,764 subscribers15 August 2026 — 5,831 subscribers19 August 2026 — 5,881 subscribers22 August 2026 — 5,917 subscribers25 August 2026 — 5,950 subscribers28 August 2026 — 5,994 subscribers31 August 2026 — 6,011 subscribers3 September 2026 — 6,039 subscribers8 September 2026 — 6,098 subscribers12 September 2026 — 6,130 subscribers16 September 2026 — 6,158 subscribers30 September 2026 — 6,508 subscribers7 October 2026 — 6,631 subscribers13 October 2026 — 6,794 subscribers16 October 2026 — 6,879 subscribers19 October 2026 — 6,927 subscribers22 October 2026 — 7,061 subscribers25 October 2026 — 7,092 subscribers28 October 2026 — 7,125 subscribers31 October 2026 — 7,215 subscribers3 November 2026 — 7,249 subscribers6 November 2026 — 7,295 subscribers10 November 2026 — 7,338 subscribers14 November 2026 — 7,441 subscribers6 August 202614 November 2026
28 measurements spanning 100 days, net +1,719. 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 5,464–7,699 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
14 Nov 2026, 20:507,441+103
10 Nov 2026, 01:377,338+43
6 Nov 2026, 11:467,295+46
3 Nov 2026, 11:147,249+34
31 Oct 2026, 21:267,215+90
28 Oct 2026, 13:187,125+33
25 Oct 2026, 21:157,092+31
22 Oct 2026, 18:267,061+134
19 Oct 2026, 10:206,927+48
16 Oct 2026, 17:596,879+85
13 Oct 2026, 16:566,794+163
7 Oct 2026, 14:566,631+123
30 Sept 2026, 19:366,508+350
16 Sept 2026, 09:556,158+28
12 Sept 2026, 20:166,130+32
8 Sept 2026, 16:416,098+59
3 Sept 2026, 12:216,039+28
31 Aug 2026, 07:036,011+17
28 Aug 2026, 14:335,994+44
25 Aug 2026, 11:155,950first reading

Engagement

188 posts held, back to 5 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.94%
avg views ÷ 7,441 subscribers
Avg views / post
740
127 posts measured
Reaction rate
0.128%
reactions ÷ views · ER floor
Posts in window
127
of 188 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. It is computed over the 24 of 127 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held188 (5 August 2026 – 16 November 2026)
Views total93,942
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 02:02 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.

What this channel posts

Photos
≈4,800
Links
≈3,610

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

40 reactions across 22 posts, in 13 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1332.5%
👎717.5%
❤‍🔥37.50%
🔥37.50%
🤡37.50%
⚡25.00%
🐳25.00%
💊25.00%
👌12.50%
💯12.50%
😭12.50%
🤩12.50%
🤮12.50%

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

Measured over the 188 most recent posts we hold, published 5 August 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 4 of 127 posts held from the last 30 days (3.15%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 13:32 UTC597 views4 reactionsread 17 November 2026
Photo

Говорят, счастье не в деньгах. 💴😎 Но почему-то ипотека, отпуск и доставка суши с этим не согласны.🙃 Поэтому мы подготовили свежую подборку вакансий. Ищите место, где ваша экспертиза наконец-то начнёт приносить не только моральное удовлетворение. Senior Backend Developer 📍Из любой точки мира (график по МСК, full-time). Senior BI / DWH Developer 📍Удалённо (любая). Full-time. Senior Python Developer 📍Удалённо. Часо…

❤2💯1🤩1

16 Nov 2026, 11:32 UTC649 viewsread 17 November 2026
Photo

Middle System Analyst #SystemAnalyst #SQL #JSON #SOAP #REST #BPMN #РФ #Москва #Офис Требования: Опыт от 3 лет. Законченное высшее образование. Общие знания продукта «счета и вклады». Составление ТЗ, расширенных БТ, инструкций. Проектирование и ТЗ по интеграции систем (SOAP / REST). Работа с JSON. Анализ бизнес-процессов + структурирование требований по автоматизации. Простые SQL-запросы + основы проектирования БД. Д…

16 Nov 2026, 11:04 UTC624 viewsread 17 November 2026
Photo

Senior DevOps Engineer #SeniorDevOps #DevOpsEngineer #DevOps #GitLabCI #CICD #PostgreSQL #Redis #SQL #NoSQL #Удаленно #РФ Требования: 3–5+ лет в DevOps / Infrastructure Engineer с production-нагрузкой. CI/CD на GitLab CI (построение и поддержка). Ansible для управления конфигурациями. AWS (развёртывание, настройка сервисов, управление ресурсами, безопасность). Docker и Kubernetes-практический опыт. Мониторинг и логи…

16 Nov 2026, 10:32 UTC655 views2 reactionsread 17 November 2026
Photo

Business Analyst #BusinessAnalyst #BPMN #UML #Jira #Confluence #Москва #РФ #Офис Требования: Опыт в роли Business Analyst от 3-х лет. Наличие законченного высшего образования (ПГС). Опыт в сфере IT (проектная или продуктовая разработка) от 3-х лет;- опыт разработки систем с функциональностью КСП. Глубокое понимание логики КСП - Календарно-сетевое планирование. Опыт в специализированном ПО, например MS Project или Pr…

👎2

16 Nov 2026, 10:02 UTC669 viewsread 17 November 2026
Photo

Senior MLOps Engineer #SeniorMLOpsEngineer #MLOps #MLOpsEngineer #Python #CICD #Удаленно #РФ Требования: Опыт: от 4 лет. Глубокое владение Python (от 5 лет), production-ready код. Docker, Kubernetes. Apache Airflow. CI/CD для ML (GitLab CI, GitHub Actions). Мониторинг (Prometheus, Grafana) и централизованное логирование. Опыт проектирования промышленных систем и участия в архитектуре. Понимание best practices разраб…

16 Nov 2026, 09:33 UTC659 viewsread 17 November 2026
Photo

В2В Sales Manager #B2BSales #B2BSalesManager #SalesManager #B2B #РФ #РБ #Удаленно #Fulltime Требования: Опыт работы с B2B продажами от года. Наличие компьютера и гарнитуры, а также стабильного интернета. Грамотная устная и письменная речь. Знание MS Office, Google Docs, amoCRM (будет преимуществом). Локация:📍РФ/РБ, удалённо. Full-time. Контакт для отклика: @diana_talent_hub +CV 👉 Узнать, какого хрена я всё ещё бе…

16 Nov 2026, 09:02 UTC681 viewsread 17 November 2026
Photo

Backend Developer (Java / AWS Migration) #BackendDeveloper #Developer #Java #AWS #ЕС #Удаленно Требования: Стек: Java, AWS, облачные архитектуры, микросервисы. Сильный бэкенд-опыт работы с Java + практический опыт работы с AWS. Обязателен опыт крупномасштабных миграций и модернизации. Локация:📍Удалённо, ЕС (требуются рабочие документы ЕС). Контакт для отклика: https://www.linkedin.com/in/dzmitry-bandarchuk/ +CV 👉…

16 Nov 2026, 08:33 UTC670 viewsread 17 November 2026
Photo

UA Lead (Web-to-Web) #UALead #UA #Удаленно Требования: 2+ года опыта в UA для B2C mobile apps. Опыт с подписочными продуктами. Опыт работы с Tier 1 (US, CA, AU, UK, DE, FR). Успешные кейсы за последний год. Аналитический и предпринимательский подход. Ищут человека, который умеет масштабировать трафик и строить прибыльные воронки. Локация:📍Удалённо. Контакт для отклика: @valentina_hr_mst +CV 👉 Узнать, какого хрена…

16 Nov 2026, 08:02 UTC706 viewsread 17 November 2026
Photo

Data Analyst (лабораторная информационная система) #DataAnalyst #SQL #PostgreSQL #Python #Москва #Офис Требования: Опыт работы с данными от 2 лет, сильный SQL и PostgreSQL, опыт массового изменения и удаления данных в базе, работа с таблицами от 500 тыс. строк. Python и опыт в биоинформатике или медтехе будут плюсом. Обязательно законченное высшее образование. Локация:📍Рассматривают кандидатов только из Москвы. Раб…

16 Nov 2026, 07:32 UTC697 viewsread 17 November 2026
Photo

Senior UX/UI Designer #SeniorUXDesigner #SeniorUIDesigner #UXDesigner #UXUI #Figma #FigmaAI Требования: Портфолио со сложными сценариями (B2B или высоконагруженные системы-большой плюс). Опыт работы в связке с BA и разработкой. Активное использование AI в работе (Figma AI, генерация контента, прототипирование). Экспертное владение Figma (Variables, токены, Auto Layout). Знание UX-базы и гайдлайнов iOS (HIG) / Androi…

16 Nov 2026, 07:03 UTC773 viewsread 17 November 2026
Photo

DevSecOps в BlackHub Games #DevSecOps #DevOps #CICDSecurity #GitLabCI #Ansible #Terraform #Гибрид #Москва #СанктПетербург #Удаленно #РФ Требования: Инженер с сильным DevOps-бэкграундом и опытом построения безопасности инфраструктуры. Ключевой стек и опыт: HashiCorp Vault: внедрение и управление секретами. Kubernetes Security: RBAC, Service Accounts, Network Policies. CI/CD Security: GitLab CI / Jenkins. Управление д…

13 Nov 2026, 11:31 UTC948 views2 reactionsread 17 November 2026
Photo

Senior MLOps Engineer #SeniorMLOpsEngineer #MLOps #Python #ApacheKafka #RESTAPI #GitLabCI #Удалённо #Москва #СанктПетербург Требования: Python 5+ лет, production-ready код, паттерны проектирования. Docker, Kubernetes. Apache Airflow. Apache Kafka, REST API. Базы данных, распределенные вычисления. GitLab CI / GitHub Actions. Prometheus, Grafana. Git. Будет плюсом: Понимание MLOps Lifecycle. Опыт с Feature Store, DVC.…

❤1👌1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 6 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.

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

“Jobs to be Loved | Вакансии для IT-специалистов” (@jtbl_vacancy), 7,441 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/jtbl_vacancy.

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.