Telegram RegisterThe public register of Telegram
Telegram profile photo for BackEnd Работа вакансии

Channel

BackEnd Работа вакансии

@back_rabota

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,963subscribers

+68 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001147870425
TypeChannel
Username@back_rabota
CreatedBetween 1 July 2016 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/back_rabota

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@p_rabota/175518 Jul 2026, 07:44 UTC@back_rabota/1769 · this entry18 Jul 2026, 07:46 UTC1.0072 seconds
@back_rabota/1773 · this entry22 Jul 2026, 07:16 UTC@p_rabota/176123 Jul 2026, 07:16 UTC1.0024 hours
@p_rabota/176325 Jul 2026, 07:37 UTC@back_rabota/1777 · this entry26 Jul 2026, 07:37 UTC1.0024 hours
@back_rabota/1778 · this entry27 Jul 2026, 07:05 UTC@p_rabota/176729 Jul 2026, 07:04 UTC1.0048 hours
@back_rabota/1779 · this entry28 Jul 2026, 07:08 UTC@p_rabota/176830 Jul 2026, 07:08 UTC1.002 days
@back_rabota/1780 · this entry29 Jul 2026, 07:21 UTC@p_rabota/176931 Jul 2026, 07:21 UTC1.002 days
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@p_rabota10 (8/8 hand-verifiable sample passed)1.0036 hoursthis entry (73)
@rabotapython5 (5/5 hand-verifiable sample passed)1.0048 hours@rabotapython (32)
@job_python5 (5/5 hand-verifiable sample passed)1.0010 daysthis entry (41)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 7 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 17 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 4, the earliest publisher we hold is @p_rabota. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,8951,9631,9296 August 2026 — 1,895 subscribers6 August 2026 — 1,895 subscribers9 August 2026 — 1,905 subscribers13 August 2026 — 1,907 subscribers17 August 2026 — 1,913 subscribers20 August 2026 — 1,916 subscribers23 August 2026 — 1,917 subscribers26 August 2026 — 1,921 subscribers29 August 2026 — 1,932 subscribers1 September 2026 — 1,941 subscribers4 September 2026 — 1,963 subscribers6 August 20264 September 2026
11 measurements spanning 29 days, net +68. 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 1,885–1,973 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 23:211,963+22
1 Sept 2026, 03:361,941+9
29 Aug 2026, 06:041,932+11
26 Aug 2026, 16:071,921+4
23 Aug 2026, 13:231,917+1
20 Aug 2026, 00:431,916+3
17 Aug 2026, 09:371,913+6
13 Aug 2026, 09:141,907+2
9 Aug 2026, 23:321,905+10
6 Aug 2026, 18:531,895no change
6 Aug 2026, 15:371,895first reading

Engagement

21 posts held, back to 17 July 2026the 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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

Measured over the 21 most recent posts we hold, published 17 July 2026 to 7 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

7 Aug 2026, 07:53 UTC238 viewsread 7 August 2026

Junior Python-разработчик (стажировка) #офис #junior Москва Компания: Сбер ☑️Обязанности -разработка и поддержка Python-скриптов и микросервисов для интеграции AI-инструментов в банковские процессы -исследование и пилотирование AI-платформ (OpenClaw, Claude Code, LangChain и аналоги) для автоматизации задач разработки и бизнес-процессов -участие в проектировании бэкенд-компонентов для взаимодействия с LLM (совместно

6 Aug 2026, 07:21 UTC618 viewsread 7 August 2026

Python разработчик #офис Пенза,Уфа Компания: ИнфоТеКС ☑️Обязанности: -Участие в разработке новых возможностей продукта. -Сопровождение предыдущих версий продукта: доработки и исправление ошибок. -Проведение review кода других программистов в команде. -Участие в проектировании архитектуры продукта (при соответствующем уровне квалификации). -Взаимодействие с другими сотрудниками: аналитиками, разработчиками, тестировщи

5 Aug 2026, 07:22 UTC204 views1 reactionsread 7 August 2026

Главный разработчик Python (Gen AI) #удаленка Компания: Альфа-Банк ☑️Чем предстоит заниматься -Разработка и развитие backend-компонентов и микросервисов на Python (FastAPI, asyncio). -Разработка и развитие интеграционных решений для взаимодействия с внутренними и внешними сервисами посредством REST API. -Разработка и развитие компонентов, связанных с применением технологий Generative AI и AI-агентов. -Разработка и р

1

4 Aug 2026, 07:19 UTC649 viewsread 7 August 2026

Стажёр AI разработчик в дирекцию развития казначейства #гибрид #intern Москва Компания: Альфа-БАнк ☑️Обязанности •Участвовать в разработке ИИ-агента •Взаимодействовать в составе команды со специалистами по анализу данных и специалистами по развитию инфраструктуры •Проводить функциональное тестирование •Работать в Jira и Confluence ☑️Требования •Понимание общих принципов реляционных баз данных (таблица данных, перви

3 Aug 2026, 07:14 UTC709 viewsread 7 August 2026

Junior Python-разработчик (стажировка) #офис #junior Москва Компания: Сбер ☑️Обязанности -разработка и поддержка Python-скриптов и микросервисов для интеграции AI-инструментов в банковские процессы -исследование и пилотирование AI-платформ (OpenClaw, Claude Code, LangChain и аналоги) для автоматизации задач разработки и бизнес-процессов -участие в проектировании бэкенд-компонентов для взаимодействия с LLM (совместно

2 Aug 2026, 07:19 UTC685 viewsread 7 August 2026

Tech lead C/C++ [MWS Cloud Platform] #офис #lead Москва Компания: МТС 🔹Чем предстоит заниматься -Лидировать процесс разработки команды: декомпозировать и ставить задачи, контролировать сроки выполнения, распределять ресурсы; -Участвовать в найме разработчиков: делиться экспертизой, менторить; -Проектировать архитектуру и составлять план реализации; -Самостоятельно решать технические задачи и писать код; -Измерять пр

1 Aug 2026, 07:01 UTC710 views0 reactionsread 7 August 2026

Младший Python разработчик, Отдел разработки аналитических инструментов и управления данными #удаленка #офис #junior Компания: OZON ☑️Вы будете: -Внедрять AI-инструменты, агентов и сценарных ботов в продукты и сервисы. -Разрабатывать микросервисы для обработки данных. -Проектировать и оптимизировать ETL-процессы. -Поддерживать и развивать потоковые и пакетные системы обработки данных. -Повышать производительность, о

30 Jul 2026, 07:55 UTC743 viewsread 7 August 2026

Go-разработчик, Delivery #Удаленка #гибрид #middle Компания: OZON 🔹Вы будете -Разрабатывать и совершенствовать логику CI/CD процессов и их автоматизацию. -Развивать инструменты, обеспечивающие контроль качества и унификацию процессов разработки для тысяч микросервисов. -Проектировать и развивать архитектуру существующих и новых сервисов нашей экосистемы. -Участвовать в полном цикле разработки — от проектирования и р

29 Jul 2026, 07:21 UTC795 viewsread 7 August 2026

Backend Developer (Middle/Senior) - Москва #офис #middle #senior Москва Компания: ВкусВилл ☑️Чем предстоит заниматься: -Разрабатывать и поддерживать высоконагруженный бэкенд корпоративного портала на Python и FastAPI (async/await, dependency injection, middleware); -Проектировать схемы и работать с PostgreSQL (SQL) и MongoDB (NoSQL), а также с объектными хранилищами (S3). Интегрировать локальные LLM, работать с вект

28 Jul 2026, 07:08 UTC787 viewsread 7 August 2026

Junior Python Developer [Маркетолог ] #гибрид #junior Москва Компания: МТС ☑️Чем предстоит заниматься -Разрабатывать API для взаимодействия с продуктами рекламной вертикали (backend, python/go); -Разрабатывать модули обработки задач: сбор/выгрузка сегментов (в т.ч. near-real-time), построение отчетов и т.п. (python/go); -Разрабатывать систему категоризации страниц в интернете. Основные функции: краулинг/парсинг стра

27 Jul 2026, 07:05 UTC790 viewsread 7 August 2026

Python разработчик цифровых продуктов #Офис Москва Компания: Мегафон ☑️Какие задачи необходимо решать -Разрабатывать сервисы под NLP и LLM -Разрабатывать AI-тренажеры, работа с RAG, интеграция с голосовым движком (ASR/TTS) -Проводить PoC по новым инициативам -Проводить code review ☑️Для решения этих задач требуется -Уверенные знания Python -Стек: FastAPI, asyncio, PostgreSQL, Redis, Docker/Kubernetes -Опыт работы с

26 Jul 2026, 07:37 UTC793 viewsread 7 August 2026

Разработчик на Python #гибрид Компания: Яндекс ☑️Какие задачи вас ждут -Совершенствовать сервис Разрабатывать продуктовую и бизнес-логику. Реализовывать интеграции с сервисами базовой инфраструктуры. Улучшать observability и архитектуру решения. ☑️Мы ждём, что вы -Разрабатывали на Python от трёх лет -Знакомы с классическими алгоритмами и структурами данных -Знакомы с Tortoise ORM или другой ORM -Работали с многопот

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

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.

Удаленная работа - Фриланс
@rabotay · 84,407
Telegram ranks this channel #43 of 68 here — alongside 67 others — read 18 August 2026

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.

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

“BackEnd Работа вакансии” (@back_rabota), 1,963 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/back_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.