Telegram RegisterThe public register of Telegram
Telegram profile photo for QA тестирование Pабота Вакансии

Channel

QA тестирование Pабота Вакансии

@qa_rab

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

3,797subscribers

+478 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001294226314
TypeChannel
Username@qa_rab
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/qa_rab

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 14 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qa_rab/1194 · this entry25 Jul 2026, 07:55 UTC@devs_it/558727 Jul 2026, 10:00 UTC1.002 days
@qa_rab/1197 · this entry28 Jul 2026, 07:19 UTC@devs_it/559830 Jul 2026, 15:00 UTC1.002 days
@qa_rab/1200 · this entry31 Jul 2026, 07:26 UTC@devs_it/56031 Aug 2026, 05:00 UTC1.0022 hours
@qa_rab/1191 · this entry22 Jul 2026, 07:53 UTC@devs_it/563811 Aug 2026, 15:10 UTC1.0020 days
@qa_rab/1202 · this entry3 Aug 2026, 07:25 UTC@devs_it/56124 Aug 2026, 05:00 UTC0.9722 hours
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
@devs_it5 (5/5 hand-verifiable sample passed)0.992 daysthis entry (5–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. None of the 0 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @qa_rab — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 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 2 registered channels linked by matching posts. 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

3,3173,7973,5576 August 2026 — 3,319 subscribers6 August 2026 — 3,317 subscribers10 August 2026 — 3,339 subscribers12 August 2026 — 3,346 subscribers16 August 2026 — 3,357 subscribers19 August 2026 — 3,354 subscribers23 August 2026 — 3,355 subscribers26 August 2026 — 3,359 subscribers29 August 2026 — 3,405 subscribers1 September 2026 — 3,413 subscribers5 September 2026 — 3,435 subscribers10 September 2026 — 3,465 subscribers14 September 2026 — 3,481 subscribers18 September 2026 — 3,496 subscribers29 September 2026 — 3,521 subscribers6 October 2026 — 3,562 subscribers12 October 2026 — 3,619 subscribers15 October 2026 — 3,645 subscribers18 October 2026 — 3,668 subscribers22 October 2026 — 3,702 subscribers24 October 2026 — 3,717 subscribers27 October 2026 — 3,743 subscribers30 October 2026 — 3,768 subscribers2 November 2026 — 3,772 subscribers5 November 2026 — 3,795 subscribers9 November 2026 — 3,797 subscribers6 August 20269 November 2026
26 measurements spanning 95 days, net +478. 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 3,245–3,869 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
9 Nov 2026, 11:063,797+2
5 Nov 2026, 20:493,795+23
2 Nov 2026, 19:573,772+4
30 Oct 2026, 23:543,768+25
27 Oct 2026, 18:293,743+26
24 Oct 2026, 23:493,717+15
22 Oct 2026, 01:583,702+34
18 Oct 2026, 13:073,668+23
15 Oct 2026, 19:193,645+26
12 Oct 2026, 21:563,619+57
6 Oct 2026, 04:383,562+41
29 Sept 2026, 08:163,521+25
18 Sept 2026, 23:003,496+15
14 Sept 2026, 20:583,481+16
10 Sept 2026, 21:363,465+30
5 Sept 2026, 19:163,435+22
1 Sept 2026, 15:273,413+8
29 Aug 2026, 17:043,405+46
26 Aug 2026, 12:173,359+4
23 Aug 2026, 10:163,355first reading

Engagement

21 posts held, back to 17 July 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 3 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

16 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 68.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1168.8%
🤔425.0%
🔥16.25%

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 12 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 16 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:29 UTC485 views0 reactionsread 7 August 2026

QA-cпециалист в VK AdBlogger, Москва #удаленка #senior Компания: VK 🔹Задачи -Тестировать новые фичи и изменения в продукте: функциональные возможности, интеграции, статусы, негативные сценарии -Участвовать в грумингах/планировании: помогать формулировать критерии приёмки, выявлять риски, предлагать планировать тестирование -Проводить smoke/регресс перед релизами и участвовать в релизных активностях (фичефлаги, раска…

6 Aug 2026, 07:41 UTC383 viewsread 7 August 2026

QA-инженер в ecom-сценарии Поиска #гибрид Компания: Яндекс 🔹Какие задачи вас ждут -Отвечать за функциональное и UI-тестирование Вам предстоит тестировать выдачу Поиска для сценариев выбора и покупки товаров, искать неконсистентности и исследовать сложные проблемы. -Повышать качество продакшна Мы серьёзно относимся к состоянию прода и багам. Ожидаем от вас такой же подход и постоянную работу над качеством прода. -Улу…

5 Aug 2026, 07:46 UTC537 views0 reactionsread 7 August 2026

QA Auto в Wildberries Банк #удаленка Компания: Wildberries ☑️Что нужно делать -Проведение функционального, регрессионного, интеграционного тестирования; -Работа с SQL, написание запросов средней сложности; -Тестирование API; -Написание тестовой документации; -Написание и поддержка автотестов на Python. ☑️Какой опыт и знания нужны -Понимание микросервисной архитектуры; -Опыт работы с Postman, Swagger; -Умение работа…

4 Aug 2026, 07:47 UTC≈1,030 views1 reactionsread 7 August 2026

Junior auto QA-инженер (Java) #офис #гибрид #junior Москва Компания: Сбер ☑️Обязанности -проводить ручное тестирование (функциональное, интеграционное, регрессионное), создавать и развивать тестовую модель -писать автотесты на Java -работать с логами, API, SQL-запросами -подготавливать артефакты для процедуры тестирования -работать с баг-трекингом (Jira и другие системы) -вести коммуникацию с контрагентами ☑️Требов…

❤1

3 Aug 2026, 07:25 UTC≈1,050 viewsread 7 August 2026

Инженер по автоматизированному тестированию backend (Python) #гибрид #middle Москва Компания: Иви ☑️В команде Иви тебе предстоит: -Функционально и интеграционно тестировать микросервисы -Покрывать автотестами новый функционал и беклог автоматизации -Поддерживать, дорабатывать существующие фреймворки тестирования микросервисов и разрабатывать их с нуля -Активно участвовать в жизни команды: планировать, разбирать и оц…

1 Aug 2026, 07:01 UTC≈1,080 viewsread 7 August 2026

Руководитель службы QA в Яндекс Роботикс #гибрид Компания: Яндекс 🔹Какие задачи вас ждут -Стратегия тестирования и качество релизов Вы будете развивать стратегию тестирования от отдельных компонентов до end-to-end-сценариев, отвечать за качество релизов: тестирование на этапе CI/CD, автотесты, acceptance-тестирование на реальных роботах. Также предстоит формировать единый подход к качеству на уровне всей платформы. …

31 Jul 2026, 07:26 UTC≈1,160 views1 reactionsread 7 August 2026

Стажер QA Manual [Discovery Portal] #гибрид #intern Москва Компания: МТС 🔹Чем предстоит заниматься -Разработка тестовых сценариев, проведение ручного тестирования; -Написание автотестов; -Выявление и документирование дефектов; -Взаимодействие с командой разработки для улучшения качества продукта. 🔹Что мы ожидаем -Студенты 3 - 6 курсов бакалавриата, специалитета или магистратуры -Знание DevTools браузеров: умение ан…

🤔1

30 Jul 2026, 07:10 UTC≈1,140 views1 reactionsread 7 August 2026

Senior Fullstack QA #удаленка #senior Компания: Золотое Яблоко 🔹ЧТО НУЖНО ДЕЛАТЬ: -Проводить ручное функциональное и нефункциональное тестирование (веб/мобильные устройства/апи) -Проводить регрессионное тестирование -Составлять документацию для проведения функционального и нефункционального тестирования, поддерживать её актуальность -Заниматься автоматизацией тестирования нового функционала -Проводить автоматизацию …

🔥1

29 Jul 2026, 07:02 UTC630 viewsread 7 August 2026

Инженер по автоматизации тестирования, Заказы в ЛК покупателя #удаленка #middle Компания: OZON 🔹Что предстоит делать? -Все проекты проходят ручную приемку, часть приемки тестируем автоматически, сверкой скриншотов и json-данных. -Автотесты пишем на Typescript и немного на Python и Go. -Многие проекты мы делаем сразу с несколькими соседними командами, поэтому нужно будет подготавливать тестовые данные совместно. -Для…

28 Jul 2026, 07:19 UTC≈1,100 views4 reactionsread 7 August 2026

Функциональный тестировщик / QA инженер #удаленка #Офис #senior Компания: Лоция 🔹Чем предстоит заниматься -участием в процессах и решениях сложных и средних задач; -формированием обратной связи по задачам/функционалу/методикам; -тестированием функционала собственного программного продукта компании; -написанием тестовой документации: тест-кейсы, планы-тестирования, стратегии тестирования, программы методики испытаний…

❤4

27 Jul 2026, 07:55 UTC≈1,070 viewsread 7 August 2026

SDET / AQA Python #удаленка Компания: Arenadata ☑️Что нужно делать: -Автоматизировать тестирование компонентов Arenadata Hyperwave (ADH) и Arenadata Hyperwave Cloud (ADHC): Spark, Impala, Trino, Kyuubi, Hive, HBase, Ozone, HDFS, YARN, Airflow, Flink; -Тестировать развёртывание и эксплуатацию платформы на bare metal, VM и в Kubernetes; -Разрабатывать и развивать тестовые фреймворки на Python для распределённых Big Da…

26 Jul 2026, 07:15 UTC≈1,200 viewsread 7 August 2026

Инженер по тестированию в Сервисы продуктивности VK Tech, Москва #офис #гибрид #middle #senior Компания: VK 🔹Задачи -Ручное тестирование (70%): фича-тестирование и регресс кросс-платформенного приложения (Mobile, Desktop, Web) -Тестирование клиент-серверных взаимодействий и поведения приложения в различных сетевых условиях -Написание тест-кейсов, разработка тест-планов -Автоматизация (30%): поддержка и развитие суще…

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

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.

Job for QA
@forallqa · 22,906
Telegram ranks this channel #10 of 95 here — alongside 94 others — read 20 September 2026
Работа для тестировщиков. QA
@qajoboffer · 20,811
Telegram ranks this channel #17 of 92 here — alongside 91 others — read 27 September 2026
IT Jobs | Вакансии в IT
@devs_it · 19,514
Telegram ranks this channel #45 of 93 here — alongside 92 others — read 5 October 2026

This channel appears in 3 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“QA тестирование Pабота Вакансии” (@qa_rab), 3,797 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/qa_rab.

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.