Channel
@non_nlp_jobs
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
146subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002047983052 |
|---|---|
| Type | Channel |
| Username | @non_nlp_jobs |
| Created | 2 February 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/non_nlp_jobs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 08:16 | 146 | -2 |
| 22 Aug 2026, 09:46 | 148 | +1 |
| 8 Aug 2026, 20:31 | 147 | no change |
| 7 Aug 2026, 10:43 | 147 | first reading |
13 posts held, back to 2 February 2024 — 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 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 13 posts for this entry, the most recent from 8 May 2025. An engagement rate over an empty window would be a number about nothing.
9 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 3 | 33.3% | |
| ❤ | 2 | 22.2% | |
| 🔥 | 2 | 22.2% | |
| 👍 | 1 | 11.1% | |
| 😐 | 1 | 11.1% |
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 7 of the 13 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 2 February 2024 to 8 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#вакансия #vacancy #job #senior #hybrid #poland #warsaw #bigdataengineer Vacancy: Big Data Engineer Location: Poland Format: Hybrid Type of Contract: B2B Orca Security is a leading cloud infrastructure security platform. If you like working with cutting-edge tech and solving real security challenges, this might be your perfect match! Key Responsibilities: - Design, develop, and maintain scalable and robust data pi…
#вакансия #удаленка #datascientist Data Scientist в Авито (Middle/Senior) Формат работы: удаленка или работа из офиса в Москве, Санкт-Петербурге, Самаре, Казани Занятость: полная ЗП: от 285.000 рублей В зависимости от выбранной команды вы будете: — развивать умный алгоритм проверки объявлений; — внедрять ML-модели в процессы монетизации; — писать микросервисы для улучшения поискового ранжирования; — оказывать DS-п…
#job data engineer, Warsaw (remote) We are looking for a Senior Data Engineer for Haptiq. Haptiq is a global technology company dedicated to delivering best-in-class software and digital solutions that drive profitable and scalable growth for our clients. As we expand our innovative offerings, we are looking for talented individuals to join our dynamic team! Skills and Experience: - 3+ years in Python coding. - 5+ …
Коммуникационный менеджер в сфере научных проектов и IT Я запаслась эльфийским хлебом и выхожу на тернистую тропу поиска full-time работы 🍀 Что я ищу — Удалённую или частично удалённую работу (потому что нужно ездить по опекунским делам) — Проект вне России, в идеале — немецкий (делаю визу Chancenkarte) или кипрский (чтобы легализоваться, есть туристическая виза) — В приоритете наука, tech или НКО Что я умею 🔴Разр…
❤2
File, posted without a caption
#job #startup Hey everyone, We at TensorSense are working on an exciting project: an AI agent that creates computer vision datasets. It's all about automating the heavy lifting in data collection, processing, and labeling for CV tasks using AI. We've got a working prototype and even have a few paid projects to put it through its paces. We're looking for 1-2 co-founders to join us—preferably based in the USA or Isra…
👍1
ML-инженер, РФ/РБ, гибрид #job #ТБанк #вакансия #ML #NLP #NaturalLanguageProcessing #LLM #RecSys #CV #senior #middle Ищем ML-engineer в Т-Банк 👋 Мы создаем и применяем AI-технологии для развития финансовой экосистемы Т-Банка: внедряем в продукты и внутренние процессы компании, делаем решения качественнее, безопаснее и удобнее для пользователей, вкладываемся в долгосрочные исследования. Кратко про работу в команде:…
😐1
#job Пачка вакансий по управлению кредитными рисками в Алматы и Ташкенте. ---------- Предлагаю 4 вакансии CRO or Deputy CRO (Retail or SME) or DS, в штат Solva Group, Алматы или командировки из Москвы – 70%. Первое видео-интервью будет с будущим руководителем. 1. CRO / Deputy CRO (Retail & SME) Solva Group, Казахстан, Алматы 2. Руководитель по управлению рисками Solva Group, Казахстан, Алматы 3. Р…
#job (начало поста) Условия: - Стабильная, высокая, белая зарплата, оклад + премия (годовая) - Руководящая позиция, в подчинении риск-аналитики, скорингисты - Международный коллектив и работа, связанная с бизнесом в разных странах - Работа в одной из самых быстрорастущих fintech компаний в мире - Оформление трудовых отношений в соответствии с ТК - Гибкий график работы - ДМС (Медстраховка) - Корпоративный фитнес - Оп…
🚀 ИЩУ РАБОТУ. В поиске следующего большого вызова в Product Management! 🌟 В Порту или удалённо. ---- Я – опытный специалист в области Product Management, с энтузиазмом подходящий к каждому проекту и стремящийся превращать инновационные идеи в успешные продукты. Мой опыт включает в себя не только запуск и развитие цифровых продуктов на всех этапах их жизненного цикла, но и глубокое понимание пользовательских потребнос…
⚡3
Non-NLP jobs pinned «A year ago, I started the channel @nlp_jobs, because I was frequently contacted by people who are looking for a job in natural language processing, or people who want to hire someone. Now, I realize that I am often contacted with similar requests, unrelated…»
A year ago, I started the channel @nlp_jobs, because I was frequently contacted by people who are looking for a job in natural language processing, or people who want to hire someone. Now, I realize that I am often contacted with similar requests, unrelated to NLP. What is an appropriate response? Right, to start a new channel, @non_nlp_jobs! The rules are the same: if you want to post a position or your CV, write t…
🔥2
Showing the 12 most recent of 13 posts we hold for @non_nlp_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.
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.
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.
@non_nlp_jobs named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Non-NLP jobs” (@non_nlp_jobs), 146 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/non_nlp_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.