Channel
@nlp_jobs
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,268subscribers
+30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001887930469 |
|---|---|
| Type | Channel |
| Username | @nlp_jobs |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/nlp_jobs |
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 16 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 09:37 | 2,268 | +1 |
| 8 Sept 2026, 10:36 | 2,267 | +12 |
| 2 Sept 2026, 20:36 | 2,255 | +4 |
| 30 Aug 2026, 08:44 | 2,251 | +3 |
| 27 Aug 2026, 12:34 | 2,248 | +2 |
| 24 Aug 2026, 19:24 | 2,246 | +7 |
| 20 Aug 2026, 23:14 | 2,239 | +2 |
| 17 Aug 2026, 17:47 | 2,237 | -1 |
| 14 Aug 2026, 21:16 | 2,238 | -1 |
| 11 Aug 2026, 16:26 | 2,239 | +1 |
| 7 Aug 2026, 09:02 | 2,238 | no change |
| 7 Aug 2026, 08:57 | 2,238 | first reading |
20 posts held, back to 28 December 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 2 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 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
273 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 15.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 43 | 15.8% | |
| 👎 | 39 | 14.3% | |
| ❤ | 37 | 13.6% | |
| 💩 | 36 | 13.2% | |
| 👍 | 28 | 10.3% | |
| 🥴 | 24 | 8.79% | |
| 😁 | 20 | 7.33% | |
| 🔥 | 15 | 5.49% | |
| 🤣 | 12 | 4.40% | |
| ⚡ | 9 | 3.30% | |
| 😢 | 4 | 1.47% | |
| ❤🔥 | 3 | 1.10% | |
| 🖕 | 3 | 1.10% |
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 17 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 273 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 28 December 2024 to 3 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.
#candidate Nachyn-Enkhedorzhu Oorzhak ML / NLP Engineer with 3 years of production experience in NLP, LLMs and applied ML. Contact: Telegram: @nachyn_enkhe 1) The job I'm looking for Positions: - NLP / LLM Engineer - AI Safety / LLM Security Engineer I'm looking for an engineering role — building, fine-tuning and shipping models Job type: Full-time Locations considered: Outside Russia only (open to relocation, migh…
😁12❤6🥴3👍2🤣2
#candidate About me: William Briggs Senior / Lead NLP & LLM Engineer with 8+ years of experience in ML/NLP and a PhD background. I build production-grade GenAI systems end-to-end: conversational AI, RAG pipelines, document intelligence, and LLM-based automation, with a strong focus on product impact and scalability. LinkedIn: https://www.linkedin.com/in/williambri/ Website: https://william-briggs.com 1) The job I’…
👍4😢4
#job #вакансия #nlp #ml #saas #cyprus #limassol #ITJobs #vacancy #ai 🔎 Senior NLP / ML-разработчик чат-ботов (Remote/Limassol) В быстрорастущий продуктовый SaaS-стартап с фокусом на AI-решения для бизнес-коммуникаций ищем Senior NLP-специалиста для разработки внутреннего текстового чат-бота под ключ и интеграции с существующими системами. Цель — снизить нагрузку на техническую поддержку и улучшить пользовательский …
👎7👍1
#job #vacancy Вакансия: Аналитик ИИ (Senior) Компания продуктовая: Элоконт Формат: Удаленно (в пределах РФ) Занятость: Полная, 5/2 Контакт: tg @aver89 Ищем аналитика с опытом работы в Data Science проектах (в текстовых задачах, рекомендательных и поисковых системах, компьютерном зрении, предиктивной аналитике и т.п.). Мы занимаемся развитием и внедрением ИИ-моделей (в т.ч. LLM). Задачи: • Сбор и анализ бизнес-требо…
#job at pheon.com Position: Lead Machine Learning Engineer (CV / NLP) Remote | Outside Russia & Belarus Pheon is looking for an experienced ML Engineer ready to take technical leadership and drive a fast-growing AI product. The platform hosts thousands of AI characters, works with text, images, and video, has 250k+ MAU, a high pace of experimentation, and real product impact from day one. Responsibilities R&D in Co…
#job Вакансия: Middle Data Scientist, NLP Компания: Ozon Банк Зарплата: 250 000 - 350 000 рублей net с учетом премий Локация: МСК, СПБ, Удаленка Ищем Middle Data Scientist в команду, которая решает все NLP-задачи Ozon Банка. Мы создаём RAG для бизнес-направлений и чат-бот поддержки, реализуем speech-to-text решения, OCR с использованием LLM, кодогенерацию. И ещё работаем с любыми запросами бизнеса, связанными с текс…
💩15❤2👍2
#vacancy #job #senior #python #developer #project 😊 Senior Python Backend Engineer (NLP & Microservices) 🥶 ⚫️Company: Veranto.tech + AZ Agency 🪐 Locations: Kazakhstan (preferred), Georgia, Moldova, Armenia, Azerbaijan, Turkey. English level: B2 and higher ⛩Hourly rate: 25 euro Project engagement: 6-12 months 📰 We are looking for an experienced Senior Python Backend Engineer to join our team and take a leading role …
👎22❤2
LLM Engineer (NLP / Generative AI) https://hyperspace.ai/ *Project: AI chatbot platform + multimodal scenarios (image and video generation)* --- about the project We’re building interactive AI partners that engage in meaningful conversations, remember context, manage media content, and adapt to the user's style. --- responsibilities Python utilities for LLMs * small scripts / CLI tools initially run locally, …
❤5
Вакансия: Head of AI / Кофаундер Зарплата: Доля до 20% Локация: удаленная работа по миру / Москва - идеально! Контакт: тг – @sputnik11 Компания: Innde О компании: - Сфера: чат-боты на ИИ (сейчас упор на магазины Авито/сайты/мессенджеры) - Продукт: чат-бот, который общается с заинтересованными покупателями (например, на Авито) и пытается взять у них телефон - Ценность продукта: снижает кост на менеджеров, увеличиваем…
🥴21🤡13😁6❤2👍2
Hi 👋 Our company is looking for 🦾AI ENGINEER https://innova-technology.com Requirements: ✔️Proficiency in Python ecosystem: FastAPI (or similar framework), pydantic, asyncio, pandas, NumPy, SQLAlchemy ✔️Hands-on expertise in building RAG Systems ✔️Hands-on expertise with AI/NLP ✔️Hands-on expertise in Fine-Tuning & Model Customization ✔️DevOps Experience ✔️Experience in writing & optimizing SQL queries ✔️Expe…
👎8
Всем привет. Я Python-разработчик с опытом в NLP (SpaCy), аналитике данных (Pandas, SQL) и веб-парсинге (Scrapy). Работал в Källkod OY, Utopia Analytics и других компаниях. Ищу работу в NLP/Data Science. Свободно владею английским, есть опыт с Azure и Git. Готов к интересным проектам. Нахожусь в РФ
🔥5❤1👍1
#job ML Engineer (NLP + RecSys), Tbilisi, onsite or remote. Neiro.ai, ChaChat About the Position: We are looking for a talented ML Engineer to enhance our products and user experience. In this role, you will work on developing and testing language models, building microservices, and solving interesting tasks in natural language processing. You will become part of a friendly and professional team where everyone can i…
❤🔥3💩2😁2👍1
Showing the 12 most recent of 20 posts we hold for @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.
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.
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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“NLP jobs” (@nlp_jobs), 2,268 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/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.