Telegram RegisterThe public register of Telegram
Telegram profile photo for QA Jobs - Вакансии

Channel

QA Jobs - Вакансии

@rabota_testirovshchike

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Cite this entry

5,700subscribers

-11 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001250796655
TypeChannel
Username@rabota_testirovshchike
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 live16 September 2026
Measurements held11
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/rabota_testirovshchike

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 98% 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 2 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
@rabota_testirovshchik/29212 Aug 2026, 09:07 UTC@rabota_testirovshchike/2828 · this entry2 Aug 2026, 12:00 UTC1.002.9 hours
@rabota_testirovshchik/29243 Aug 2026, 09:00 UTC@rabota_testirovshchike/2830 · this entry3 Aug 2026, 09:00 UTC1.00under a minute
@rabota_testirovshchik/29294 Aug 2026, 09:00 UTC@rabota_testirovshchike/2835 · this entry4 Aug 2026, 09:00 UTC1.00under a minute
@rabota_testirovshchik/29314 Aug 2026, 12:01 UTC@rabota_testirovshchike/2837 · this entry4 Aug 2026, 12:01 UTC1.00under a minute
@rabota_testirovshchik/29366 Aug 2026, 09:05 UTC@rabota_testirovshchike/2842 · this entry6 Aug 2026, 09:05 UTC1.00under a minute
@rabota_testirovshchik/29417 Aug 2026, 09:07 UTC@rabota_testirovshchike/2847 · this entry7 Aug 2026, 09:07 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@rabota_testirovshchik9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (81)
@rabota_testirovshchiko9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (72)

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 3 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 22 comparable posts for this entry, running 2 August 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 3, the earliest publisher we hold is @rabota_testirovshchik. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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 2 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

5,7005,7115,705.57 August 2026 — 5,711 subscribers7 August 2026 — 5,711 subscribers8 August 2026 — 5,710 subscribers11 August 2026 — 5,708 subscribers14 August 2026 — 5,707 subscribers17 August 2026 — 5,704 subscribers23 August 2026 — 5,700 subscribers27 August 2026 — 5,701 subscribers30 August 2026 — 5,703 subscribers2 September 2026 — 5,702 subscribers12 September 2026 — 5,700 subscribers7 August 202612 September 2026
11 measurements spanning 36 days, net -11. 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,698–5,713 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 13:005,700-2
2 Sept 2026, 17:465,702-1
30 Aug 2026, 13:045,703+2
27 Aug 2026, 05:345,701+1
23 Aug 2026, 21:175,700-4
17 Aug 2026, 16:585,704-3
14 Aug 2026, 01:065,707-1
11 Aug 2026, 03:425,708-2
8 Aug 2026, 08:125,710-1
7 Aug 2026, 13:025,711no change
7 Aug 2026, 12:555,711first reading

Engagement

31 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 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 31 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10s
Average length
5s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Advertising

Ad load
9.68%
3 of 31 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 2 distinct tokens
Median views · ads
9.0
over 3 measured posts
Median views · rest
8.0
over 28 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd726 August 202611 August 2026
5jtCeReNwxHpfQTDve31wmc17 August 20267 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 31 most recent posts we hold, published 2 August 2026 to 11 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

11 Aug 2026, 17:54 UTC4 viewsread 12 August 2026
Advertisementerid CQH36pWzJqVGXC5oLP8WVVNCNqJmbhiUPijGiu4zpwPd7Video

💛 Подработка курьером в вашем городе — доставка заказов Яндекс Еды и Яндекс Лавки Набор ведёт официальный партнёр сервиса. Условия: 📍 доход до 8 500 ₽ в день, выплаты каждый день (оформление как самозанятый) 📍 график выбираете сами — слоты свободные, заказы поступают 24/7 📍 все чаевые — ваши 📍 из документов — требуется только удостоверение личности + смартфон Бонусы для курьеров сейчас: 😍 велосипед Яндекс Байк — з

11 Aug 2026, 09:06 UTC5 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

10 Aug 2026, 10:40 UTC6 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

9 Aug 2026, 15:00 UTC5 viewsread 12 August 2026

Fullstack QA engineer (Platform V MDC) Заработная плата по договоренности Обязанности: • обеспечивать функциональное тестирование, строить тестовую модель с учётом ручного, авто и нагрузочного тестирования • управлять тестовыми средами для обеспечения бесперебойного процесса • осуществлять гибридный процесс тестирования (ручное + автоматизация) • осуществлять поиск дефектов и проводить их анализ • менторить, обменив

9 Aug 2026, 12:03 UTC6 viewsread 12 August 2026

Middle FullStack Python QA Engineer (HR платформа) Заработная плата по договоренности Обязанности: • ручное функциональное, регрессионное и интеграционное тестирование web, backend-сервисов и AI-агентов • разработка и поддержка тестовой модели (тест-кейсы по новому функционалу и регрессионной модели, чек-листы) • написание и поддержка Api и Web автотестов на Python (в т.ч. smoke, интеграционные, e2e) • анализ allure

9 Aug 2026, 09:05 UTC5 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

9 Aug 2026, 09:03 UTC4 viewsread 12 August 2026

QA Lead (SEAF.ArchTool) Заработная плата по договоренности Обязанности: • формировать и развивать стратегию тестирования SEAF.ArchTool • организовывать процессы ручного, автоматизированного, интеграционного, регрессионного и нагрузочного тестирования • внедрять автоматические проверки пользовательских сценариев, UI, API, сервисов и интеграций с внешними системами • обеспечивать тестирование работы с архитектурными д

8 Aug 2026, 09:05 UTC4 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

8 Aug 2026, 09:05 UTC7 viewsread 12 August 2026
Photo

🛑ПУНКТ ОТБОРА НА ВОЕННУЮ СЛУЖБУ ПО КОНТРАКТУ Министерства Обороны РФ ✅МОСКВА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА : 2️.3️0️0️.0️0️0️₽💰 Ежемесячные: Министерство Обороны РФ от 2️6️0️.0️0️0️₽ ✅КОСТРОМА 💰ЕДИНОВРЕМЕННАЯ ВЫПЛАТА: 1️.4️0️0️.0️0️0️₽-Ежемесячные Министерства Обороны РФ от 2️1️0️.0️0️0️₽ 🇷🇺Принимаются граждане РФ (прописка в любом регионе) и других СТРАН 📌Условия: ✅Оплачиваем Вам проезд ( авиа, ж/д ) ✅Оплачиваем Вам пр

7 Aug 2026, 17:05 UTC9 viewsread 12 August 2026
Advertisementerid 5jtCeReNwxHpfQTDve31wmcPhoto

🌎 До 23 августа любой курс Практикума на 7% дешевле. Яндекс Практикум — это курсы, где учат цифровым профессиям с нуля: программирование, анализ данных, дизайн, маркетинг, менеджмент. Учёба на реальных рабочих задачах, с трудоустройством помогает карьерный центр — работу находят 78% выпускников. Схема простая: 🟠 Начинаете с бесплатного вводного курса — без карты и обязательств 🟠 Подошло — берёте полный курс с пром

7 Aug 2026, 15:03 UTC8 viewsread 12 August 2026

Product Owner (B2B, Эквайринг, AI-ассистент) Заработная плата по договоренности Обязанности: • анализировать клиентские пути, обращения в поддержку, CSI, жалобы — находить точки роста • генерировать и валидировать гипотезы по оптимизации сценариев (от простых FAQ до сложных транзакционных действий) • проектировать сценарии и логику работы AI-агентов (чат-ботов, ассистентов) для корпоративных клиентов • совместно с и

7 Aug 2026, 12:07 UTC8 viewsread 12 August 2026

QA инженер Заработная плата по договоренности Обязанности: • составлять тестовую документацию: тест-кейсы, чек-листы, баг-репорты, протоколы тестирования • обнаруживать и отслеживать баги • изучать и оценивать требования, составленные аналитиками на предмет полноты и однозначности, участвовать в проработке задач • читать логи приложений для локализации багов • взаимодействовать с внутренними и смежными командами Тр

Showing the 12 most recent of 31 posts we hold for @rabota_testirovshchike. 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 2 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 12 September 2026 — this entry's latest reading, not the date you are reading this.

“QA Jobs - Вакансии” (@rabota_testirovshchike), 5,700 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/rabota_testirovshchike.

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.