Telegram RegisterThe public register of Telegram
Telegram profile photo for Вакансии для Senior разработчиков, аналитиков, дизайнеров

Channel

Вакансии для Senior разработчиков, аналитиков, дизайнеров

@senior_job_it

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

619subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001544449680
TypeChannel
Username@senior_job_it
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/senior_job_it

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 2 other registered channels. They sit inside a group of 7 channels that share the same post bodies 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@middle_job_it/54975 Mar 2026, 12:57 UTC@senior_job_it/4130 · this entry5 Mar 2026, 12:57 UTC1.00under a minute
@middle_job_it/55079 Apr 2026, 06:52 UTC@senior_job_it/4134 · this entry9 Apr 2026, 06:53 UTC1.00under a minute
@middle_job_it/550824 Apr 2026, 11:53 UTC@senior_job_it/4137 · this entry24 Apr 2026, 11:53 UTC1.00under a minute
@middle_job_it/551022 May 2026, 14:31 UTC@senior_job_it/4141 · this entry22 May 2026, 14:31 UTC1.00under a minute
@middle_job_it/55111 Jun 2026, 07:18 UTC@senior_job_it/4142 · this entry1 Jun 2026, 07:18 UTC1.00under a minute
@remote_job_it_geeklink/56489 Apr 2026, 06:52 UTC@senior_job_it/4134 · this entry9 Apr 2026, 06:53 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@middle_job_it5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (41)
@remote_job_it_geeklink5 (5/5 hand-verifiable sample passed)1.00under a minutethis 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 2 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 20 comparable posts for this entry, running 18 February 2026 to 11 June 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 7, the earliest publisher we hold is @product_project_job. 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 6 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

619620619.57 August 2026 — 620 subscribers7 August 2026 — 620 subscribers14 August 2026 — 619 subscribers7 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 619–620 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 21:08619-1
7 Aug 2026, 21:33620no change
7 Aug 2026, 01:18620first reading

Engagement

20 posts held, back to 18 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 11 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍450.0%
337.5%
🔥112.5%

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 7 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 8reactions 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 18 February 2026 to 11 June 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

11 Jun 2026, 12:28 UTC44 viewsread 7 August 2026

👤 РЕЗЮМЕ: Senior Legal Advisor | IT, GameDev & Digital Опыт: более 11 лет Зарплата: по договоренности Навыки: IP, IT Law, GameDev, Corporate Law, SHA, Venture Deals, Software Licensing, International Contracts, EULA, Privacy Policy, Contract Negotiation, Legal Due Diligence Привет! Меня зовут Андрей. Более 11 лет сопровождаю IT, GameDev и digital-проекты. Основной профиль — сопровождение игровых и IT-команд: догов

1 Jun 2026, 07:18 UTC48 viewsread 7 August 2026

💼 ВАКАНСИЯ: Technical Owner / Lead Developer Компания: DV Зарплата: от $2500 - $3500+ Локация/Format: Польша, удаленный Ищем сильного backend/fullstack разработчика (Middle+/Senior) с базой в DevOps, который в перспективе возьмет на себя всю техническую функцию внутри команды. Это не классический Team Lead и не CTO крупной компании. Скорее роль "CTO небольшой команды", где 70-80% времени — это самостоятельная работ

22 May 2026, 14:31 UTC58 viewsread 7 August 2026

💼 ВАКАНСИЯ: Middle+ - Senior Kotlin Multiplatform-разработчик для VPN-приложения Компания: Atlanta Зарплата: 2000$-4500$ Локация/Format: Удаленно График: Удалённо · full-time · фичи и доработки + иногда срочный хотфикс Стек и требования: - Уверенный Kotlin + опыт с KMP (shared-модули, expect/actual, общая логика под Android + Desktop) - Реальный прод-опыт: UI (Compose Multiplatform или нативный), навигация, сеть,

22 May 2026, 05:08 UTC40 viewsread 7 August 2026

👤 РЕЗЮМЕ: Senior DevOps Engineer / SRE / Lead Infrastructure Engineer Опыт: 7 Зарплата: 350000 Навыки: Kubernetes RKE2 Docker Helm ArgoCD GitOps Terraform Ansible GitLab CI/CD GitHub Actions Yandex Cloud Proxmox VE Linux Prometheus + Grafana Loki PostgreSQL ClickHouse HashiCorp Vault Nginx BGP / VLAN / VPN Ключевые навыки и технологии Kubernetes и контейнеризация: Managed K8s (Yandex Cloud Managed Service for Kube

21 May 2026, 12:45 UTC44 viewsread 7 August 2026

👤 РЕЗЮМЕ: Senior Technical Project Manager / Product Manager Опыт: 6+ лет в e-commerce, fintech, blockchain. Яндекс → Р-Фарм → RadianceTeam (Head of Projects, fintech/iGaming) → Monncashmere (Lead IT PM, руководитель отдела 15+ человек, бюджет 3.5 млн/мес) Зарплата: От 400000 Навыки: Agile, Scrum, Jira, Confluence, REST API, Docker, PostgreSQL, A/B тесты, LTV/CAC, retention, CRM, BI-аналитика, Python (основы), SQL

28 Apr 2026, 09:06 UTC52 views1 reactionsread 7 August 2026

👤 РЕЗЮМЕ: C# .NET / Python Разработчик Опыт: 5 лет 7 месяцев Зарплата: от 180 000 руб. мес. Навыки: C#, Python, C++, .NET Core, ASP.NET Core, MVC, WPF, Async/Await, Multithread Programming, ООП, SOLID, DRY, KISS, YAGNI, Design Patterns, Алгоритмы и структуры данных, Technical Lead, Управление командой, Entity Framework, REST, Git, Agile, SQL, PostgreSQL, Kubernetes, Unit Testing, Scrum, Agile Project Management, Red

👍1

24 Apr 2026, 11:53 UTC46 viewsread 7 August 2026

👤 РЕЗЮМЕ: Senior DevSecOps Опыт: 5 лет Зарплата: $2500 Навыки: Vault, Sast, Dast, Sca, Owasp, IaC, Shift Left Security Разработка и поддержание практик DevSecOps, включая управление секретами, тестирование безопасности приложений (DAST/SAST/SCA), управление уязвимостями и генерацию SBOM на протяжении всего жизненного цикла безопасной разработки программного обеспечения (S-SDLC). Ответственность за внедрение ASPM, о

23 Apr 2026, 09:40 UTC46 viewsread 7 August 2026

👤 РЕЗЮМЕ: Senior .NET Engineer / .NET Architect Опыт: 10 лет Зарплата: от 250000 RUB Навыки: .NET, ASP.NET, C#, Kafka, Redis, EF Core, PostgreSQL, MSSQL, Docker, xUnit, Moq, DDD, TDD, .NET Aspire, CI/CD, Event-Driven Architecture, TPL, Архитектура ПО, Распределенные системы, Высоконагруженные системы, Clean Architecture, Domain-Driven Design, Техническое лидерство Опыт 10+ лет в разработке сложных распределенных си

9 Apr 2026, 16:43 UTC61 viewsread 7 August 2026

💼 ВАКАНСИЯ: Senior Solidity developer Компания: KA Career Зарплата: 1200000 Локация/Format: Удаленная работа/ Гибрид из США 🔹Требования Английский разговорный от уровня B2+ От 5 л

9 Apr 2026, 06:53 UTC50 viewsread 7 August 2026

👤 РЕЗЮМЕ: Project manager Опыт: 5 Зарплата: От 250 000р Навыки: Jira, Confluence, Postman, DevTools, TestFlight, Bitbucket, Firebase, Figma, Ganttpro, Notion, Miro, HelpDesk Services. Всем привет! Я Елена, IT Project Manager с 5+ годами опыта. Вела веб и мобильные проекты с командами до 18 человек и бюджетами 10+ млн руб. Работала с рынками Европы, США и Латинской Америки, запускала продукты для Coca-Cola, Tesla, N

17 Mar 2026, 14:08 UTC99 views2 reactionsread 7 August 2026

👤 РЕЗЮМЕ: Unity Developer Опыт: 4 + года Зарплата: 150000 Навыки: Unity Addressables URP C# Async/Await DOTWEEN RPC Unity Test Runner UniRx UniTask OOP SOLID Алгоритмы и структуры данных MVC MVP MWM Git GitFlow CI/CD Agile AI GPT JavaScript TypeScript REST API PostgreSQL 👩‍💻Опытный Unity Разработчик с глубоким пониманием сетевой части и архитектурных паттернов. Моя специализация - создание сложных игровых систем, м

👍2

10 Mar 2026, 13:24 UTC39 viewsread 7 August 2026
Forwarded from @geeklink_ruPhoto

✨ AI-подбор каналов для постинга вакансий и резюме Теперь в боте https://t.me/it_jobs_resumes_bot AI помогает подбирать подходящие каналы для публикации вакансий и резюме. Как это работает: 📝 вы заполняете форму вакансии или резюме 🤖 AI анализирует текст 📢 сервис сразу отмечает подходящие каналы ✍️ при желании выбор можно изменить вручную Это быстрее, удобнее и помогает не тратить время на ручной подбор. Попробов

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

Citation-graph rank

Citation-graph rank — 159,147 of 1,481,346entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“Вакансии для Senior разработчиков, аналитиков, дизайнеров” (@senior_job_it), 619 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/senior_job_it.

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.