Telegram RegisterThe public register of Telegram
Telegram profile photo for Backend Job Offers

Channel

Backend Job Offers

@runello_rus_backend

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

14,097subscribers

+812 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001344577123
TypeChannel
Username@runello_rus_backend
DescriptionВакансии: Backend
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/runello_rus_backend

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

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 in near-verbatim form on 6 other registered channels. This entry also sits inside a group of 11 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@runello_rus_backend/4971 · this entry2 Nov 2026, 05:10 UTC@runello_rus_webdevelopment/58842 Nov 2026, 05:10 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@runello_rus_webdevelopment388 (8/8 hand-verifiable sample passed)1.003.0 hoursthis entry (386–2)
@runello_rus_c2061 (8/8 hand-verifiable sample passed)1.006.2 hours@runello_rus_c20 (61–0)
@runello_rus_c72 (8/8 hand-verifiable sample passed)1.004.2 hours@runello_rus_c (72–0)
@runello_rus_python68 (8/8 hand-verifiable sample passed)1.005.2 hours@runello_rus_python (68–0)
@runello_rus_php45 (8/8 hand-verifiable sample passed)1.003.6 hours@runello_rus_php (45–0)
@runello_rus_goland59 (8/8 hand-verifiable sample passed)1.004.9 hours@runello_rus_goland (59–0)

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. 37 of the 37 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 491 comparable posts for this entry, running 5 August 2026 to 15 November 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).

Of the group of 11 channels, the one whose matching posts we hold earliest is @runello_rus_html. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 16 November 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.

Channels linked by matching posts

This channel is in a group of 11 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

13,26614,15813,71214,0977 August 202613 November 2026
63 measurements spanning 98 days, net +812. 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 13,132–14,292 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
13 Nov 2026, 17:1014,097-35
11 Nov 2026, 03:5014,132+7
9 Nov 2026, 13:0614,125-12
8 Nov 2026, 07:4714,137-1
7 Nov 2026, 03:2114,138-13
6 Nov 2026, 06:3114,151-7
5 Nov 2026, 06:2814,158+22
4 Nov 2026, 04:5914,136+28
3 Nov 2026, 01:3414,108+18
2 Nov 2026, 03:1414,090-4
1 Nov 2026, 04:2914,094-2
31 Oct 2026, 01:3614,096-12
30 Oct 2026, 00:4614,108+35
29 Oct 2026, 00:1014,073+6
27 Oct 2026, 21:0614,067+18
27 Oct 2026, 00:0114,049-14
26 Oct 2026, 03:0614,063-18
25 Oct 2026, 01:2914,081-13
24 Oct 2026, 00:5614,094-10
23 Oct 2026, 02:5014,104first reading

Engagement

495 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 78 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.53%
avg views ÷ 14,097 subscribers
Avg views / post
216
151 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
151
of 495 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held495 (5 August 2026 – 16 November 2026)
Views total32,667
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 20:23 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
130
Links
13

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 151 posts held from the last 30 days (0%) 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, 18:03 UTC96 viewsread 16 November 2026

Он пропустил вакансию своей мечты.. Сергей искал работу неделю. Каждый день новые вакансии появлялись, но он видел только половину из них. Мы собрали папку с каналами, где публикуют все свежие вакансии. Теперь Сергей видит их первым и сразу откликается. Ты тоже можешь быть на шаг впереди! Сохрани папку и больше не пропускай возможности ➡️ https://t.me/addlist/sSZgEuLpcwU4MWJi

16 Nov 2026, 07:10 UTC199 viewsread 16 November 2026
Forwarded from @runello_rus_pythonPhoto

Forward Deployed Engineer (Python / AI) Стек: Python, AI, API, SQL, Databases, Docker, Cloud services, LLM Forward Deployed Engineer (Python / AI) at KOZ AI. Role involves transforming business tasks into AI solutions, developing AI agents, applications, and automations, and integrating them with client da… Откликнуться через Runello-бот ↓ #python #office

16 Nov 2026, 06:10 UTC198 viewsread 16 November 2026
Forwarded from @runello_rus_c20Photo

Embedded Software Engineer / Разработчик примеров кода Стек: C, Python, MicroPython, RISC-V, ARM, Microcontroller Programming, AVR C, UART Разработка примеров кода для микроконтроллеров и микропроцессоров, создание технической документации, отладка на реальном железе. Откликнуться через Runello-бот ↓ #cpp #c #office

16 Nov 2026, 05:10 UTC188 viewsread 16 November 2026
Forwarded from @runello_jobs_javaPhoto

Java Backend Developer Грейд: Middle/Senior Стек: Java, Groovy, Hibernate, SQL, Oracle Database, PostgreSQL, Apache Maven, Git Разработка и сопровождение серверной логики на основе Java / Groovy с использованием ORM-фреймворка Hibernate и SQL. Работа с проприетарным SDK вендора, интеграция с банковскими системами, работа в ср… Откликнуться через Runello-бот ↓ #java #middle #office

15 Nov 2026, 15:10 UTC211 viewsread 16 November 2026
Forwarded from @runello_jobs_javaPhoto

Java developer (СФС) Стек: Java, Spring framework, Jenkins, Gradle, REST, gRPC, OpenAPI, SQL Сбер Банк — крупнейший российский финансовый конгломерат, предоставляющий широкий спектр банковских услуг для частных лиц, малого бизнеса и корпоративных клиентов. Откликнуться через Runello-бот ↓ #java #hybrid

15 Nov 2026, 14:10 UTC178 viewsread 16 November 2026
Forwarded from @runello_rus_cPhoto

Game Development Workshop Leader / Преподаватель разработки игр Грейд: Middle Стек: Unity, C#, Visual Studio Code, Game Development, 2D game development, 3D game development, UI integration, Animation Международный центр искусственного интеллекта, занимающийся разработками и образовательными инициативами в сфере ИИ. Откликнуться через Runello-бот ↓ #csharp #unity #middle #office

15 Nov 2026, 13:10 UTC179 viewsread 16 November 2026
Forwarded from @runello_jobs_javaPhoto

Senior Java-разработчик Грейд: Senior Стек: Java, Java Core, Concurrency, Spring Framework, Spring Boot, Spring Data, Spring Web, JPA Сбер Банк — крупнейший российский финансовый конгломерат, предоставляющий широкий спектр банковских услуг для частных лиц, малого бизнеса и корпоративных клиентов. Откликнуться через Runello-бот ↓ #java #senior #hybrid

15 Nov 2026, 12:10 UTC183 viewsread 16 November 2026
Forwarded from @runello_rus_cPhoto

C#/.NET-разработчик Стек: C#, .NET, ASP.NET Core, Web API, Background Services, Consumers, REST API, SQL Строительство и продажа недвижимости в Москве и области. Каталог проектов от застройщика. Откликнуться через Runello-бот ↓ #csharp #c #remote #global

15 Nov 2026, 11:10 UTC188 viewsread 16 November 2026
Forwarded from @runello_jobs_javaPhoto

Middle Java разработчик (Сервисы и безопасность) Грейд: Middle Стек: Java, Java Core, JCF, Spring Core, Spring MVC, Spring Data JPA, Spring AOP, Hibernate Сбер Банк — крупнейший российский финансовый конгломерат, предоставляющий широкий спектр банковских услуг для частных лиц, малого бизнеса и корпоративных клиентов. Откликнуться через Runello-бот ↓ #java #middle #hybrid

15 Nov 2026, 10:10 UTC188 viewsread 16 November 2026
Forwarded from @runello_rus_pythonPhoto

Middle python-разработчик Грейд: Middle Стек: Python, LangGraph, LlamaIndex, RAG, PostgreSQL, OpenSearch, Kafka, FastAPI Сбер Банк — крупнейший российский финансовый конгломерат, предоставляющий широкий спектр банковских услуг для частных лиц, малого бизнеса и корпоративных клиентов. Откликнуться через Runello-бот ↓ #python #middle #hybrid

15 Nov 2026, 09:10 UTC189 viewsread 16 November 2026
Forwarded from @runello_rus_phpPhoto

Старший Backend-разработчик PHP (лидер команды) Грейд: Lead Стек: PHP, MySQL, PostgreSQL, Go, JavaScript, TypeScript, Python, Symfony Строительство и продажа недвижимости в Москве и области. Каталог проектов от застройщика. Откликнуться через Runello-бот ↓ #php #lead #remote #global

15 Nov 2026, 08:10 UTC176 viewsread 16 November 2026
Forwarded from @runello_rus_cPhoto

NET Trainee Грейд: Trainee Стек: C#, .NET, OOP, SOLID, Algorithms, Data structures, Relational databases, SQL Орион Софт — российский разработчик ИТ-решений, специализирующийся на создании продуктов для виртуализации и управления ИТ-инфраструктурой, таких как zVirt. Откликнуться через Runello-бот ↓ #csharp #c #trainee #hybrid

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

Fullstack / Software Job Offers
@runello_rus_webdevelopment · 24,125
Telegram ranks this channel #2 of 93 here — alongside 92 others — read 17 September 2026
Вакансии айти IT 💻
@vakansii_it · 27,601
Telegram ranks this channel #17 of 88 here — alongside 87 others — read 10 September 2026
Python Job | Вакансии | Стажировки
@job_python · 23,499
Telegram ranks this channel #33 of 96 here — alongside 95 others — read 19 September 2026
IT Jobs | Вакансии в IT
@devs_it · 19,575
Telegram ranks this channel #38 of 93 here — alongside 92 others — read 5 October 2026
Horst Lüning (UnterBlog)
@UnterBlogg · 42,110
Telegram ranks this channel #40 of 46 here — alongside 45 others — read 24 September 2026
Вакансии и Стажировки от MyResume
@myresume_ru · 20,328
Telegram ranks this channel #49 of 98 here — alongside 97 others — read 29 September 2026
Remote IT (Inflow)
@Remoteit · 52,225
Telegram ranks this channel #50 of 95 here — alongside 94 others — read 25 August 2026
Get IT
@Getitrussia · 22,083
Telegram ranks this channel #76 of 97 here — alongside 96 others — read 24 September 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“Backend Job Offers” (@runello_rus_backend), 14,097 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/runello_rus_backend.

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.