Telegram RegisterThe public register of Telegram
Telegram profile photo for Java jobs — вакансии для java-разработчиков

Channel

Java jobs — вакансии для java-разработчиков

@javadevjob

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

14,080subscribers

+402 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001470492937
TypeChannel
Username@javadevjob
DescriptionЛучшие вакансии для джавистов. По рекламе: @proglib_adv Учиться у нас: https://proglib.io/w/8fbbd3be Для обратной связи: @proglibrary_feeedback_bot Наши каналы: https://t.me/proglibrary/9197 РКН: https://gosuslugi.ru/snet/679b8fb7dad2d930d2eb5cb5
Created23 December 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/javadevjob

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 10 September 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 the other topics.

Growth

13,67814,08013,8796 August 2026 — 13,678 subscribers7 August 2026 — 13,687 subscribers8 August 2026 — 13,691 subscribers9 August 2026 — 13,694 subscribers10 August 2026 — 13,691 subscribers11 August 2026 — 13,705 subscribers12 August 2026 — 13,709 subscribers13 August 2026 — 13,721 subscribers14 August 2026 — 13,731 subscribers17 August 2026 — 13,737 subscribers19 August 2026 — 13,736 subscribers20 August 2026 — 13,735 subscribers21 August 2026 — 13,737 subscribers22 August 2026 — 13,742 subscribers24 August 2026 — 13,752 subscribers26 August 2026 — 13,757 subscribers27 August 2026 — 13,765 subscribers28 August 2026 — 13,770 subscribers29 August 2026 — 13,782 subscribers31 August 2026 — 13,787 subscribers1 September 2026 — 13,795 subscribers2 September 2026 — 13,805 subscribers4 September 2026 — 13,820 subscribers6 September 2026 — 13,831 subscribers9 September 2026 — 13,847 subscribers12 September 2026 — 13,893 subscribers13 September 2026 — 13,899 subscribers15 September 2026 — 13,909 subscribers17 September 2026 — 13,923 subscribers27 September 2026 — 13,934 subscribers5 October 2026 — 13,966 subscribers9 October 2026 — 13,974 subscribers13 October 2026 — 13,986 subscribers14 October 2026 — 13,972 subscribers15 October 2026 — 13,982 subscribers16 October 2026 — 13,979 subscribers17 October 2026 — 13,981 subscribers18 October 2026 — 13,984 subscribers20 October 2026 — 13,994 subscribers21 October 2026 — 14,000 subscribers23 October 2026 — 14,005 subscribers24 October 2026 — 14,003 subscribers25 October 2026 — 14,000 subscribers26 October 2026 — 13,992 subscribers27 October 2026 — 13,991 subscribers28 October 2026 — 13,997 subscribers29 October 2026 — 14,003 subscribers30 October 2026 — 13,998 subscribers31 October 2026 — 14,002 subscribers1 November 2026 — 14,001 subscribers2 November 2026 — 14,006 subscribers3 November 2026 — 14,019 subscribers4 November 2026 — 14,025 subscribers5 November 2026 — 14,032 subscribers6 November 2026 — 14,040 subscribers7 November 2026 — 14,044 subscribers8 November 2026 — 14,046 subscribers9 November 2026 — 14,052 subscribers11 November 2026 — 14,073 subscribers14 November 2026 — 14,080 subscribers6 August 202614 November 2026
60 measurements spanning 100 days, net +402. 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,618–14,140 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
14 Nov 2026, 19:4714,080+7
11 Nov 2026, 20:3614,073+21
9 Nov 2026, 22:3614,052+6
8 Nov 2026, 13:4614,046+2
7 Nov 2026, 04:3614,044+4
6 Nov 2026, 06:5014,040+8
5 Nov 2026, 08:5414,032+7
4 Nov 2026, 07:0114,025+6
3 Nov 2026, 03:1714,019+13
2 Nov 2026, 04:0814,006+5
1 Nov 2026, 07:1914,001-1
31 Oct 2026, 08:5014,002+4
30 Oct 2026, 11:2913,998-5
29 Oct 2026, 12:3514,003+6
28 Oct 2026, 14:2613,997+6
27 Oct 2026, 12:0513,991-1
26 Oct 2026, 13:0713,992-8
25 Oct 2026, 11:0014,000-3
24 Oct 2026, 08:1014,003-2
23 Oct 2026, 09:4914,005first reading

Engagement

61 posts held, back to 20 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 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.3%
avg views ÷ 14,080 subscribers
Avg views / post
3,280
33 posts measured
Reaction rate
0.101%
reactions ÷ views · ER floor
Posts in window
33
of 61 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. It is computed over the 27 of 33 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held61 (20 July 2026 – 17 November 2026)
Views total108,323
Reactions total90
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 09:34 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
≈240
Videos
≈11
Links
≈3,060

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
19s
Average length
19s

Measured directly from 1 video 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.

Reaction mix

188 reactions across 44 posts, in 3 distinct kinds. The most used accounts for 49.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤔9349.5%
❤7238.3%
👍2312.2%

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

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

Advertising

Ad load
1.64%
1 of 61 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
2,430
over 1 measured post
Median views · rest
3,640
over 60 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
2Vtzqw8Jxi7120 August 202620 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 61 most recent posts we hold, published 20 July 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 33 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).

17 Nov 2026, 09:04 UTC603 viewsread 17 November 2026

💻 МТС Банк ищет старшего Java-разработчика в новую команду платежей Команда создаёт платёжный продукт с нуля. Предстоит писать интеграционные сервисы на микросервисной платформе в Kubernetes, тестировать их, проводить ревью и участвовать в релизах. Пригодится опыт с Java, Spring, PostgreSQL или Oracle. Удалённо, гибрид или офис в Москве. Трудовой договор. Откликнуться ➡️ База знаний • Задачи • Собеседования 🐸 Би…

16 Nov 2026, 09:01 UTC≈1,680 views3 reactionsread 17 November 2026

💻 Uzum Technologies ищет Senior Java-разработчика в Uzum Bank В продуктовой команде предстоит проектировать банковские сервисы вместе с техлидом и архитектором, писать новые функции и тесты и развивать уже работающие сервисы. В стеке Java 11+, Spring Boot, Hibernate, Liquibase, PostgreSQL и Oracle. Удалённо. Откликнуться ➡️ База знаний • Задачи • Собеседования 🐸 Библиотека программиста

❤2🤔1

15 Nov 2026, 09:01 UTC≈2,070 views3 reactionsread 17 November 2026

💻 Ай-Теко ищет Senior Java-разработчика для проектирования сервисов В работе — проектирование новых сервисов, интеграции по REST и SOAP и обмен событиями через Kafka. Нужно будет описывать технические решения и согласовывать контракты со смежными командами. Ждут от пяти лет коммерческой разработки на Java, знания Java 17+ и Spring Boot 3. Удалённо или гибрид в Москве. Откликнуться ➡️ Навигация: База знаний • Зада…

❤3

14 Nov 2026, 09:05 UTC≈2,340 views16 reactionsread 17 November 2026

💻 VK ищет Senior/Lead Java-разработчика в MAX Предстоит проектировать новые серверные сервисы мессенджера и работать над их производительностью и отказоустойчивостью. Нужно от пяти лет бэкенд-разработки на Java, знание многопоточности, алгоритмов и структур данных. Опыт с Cassandra, ScyllaDB или PostgreSQL будет плюсом. Москва или Санкт-Петербург. Откликнуться ➡️ Навигация: База знаний • Задачи • Собеседования 🐸…

🤔14❤1👍1

13 Nov 2026, 09:04 UTC≈2,580 views3 reactionsread 17 November 2026

💻 Лига Цифровой Экономики ищет Junior Java для биометрической системы В команде нужно развивать микросервисы для поиска по биометрическим шаблонам, собирать контейнеры и писать модульные тесты. Ждут понимания JVM и байткода, основ ООП, алгоритмов и структур данных. Удалённо. Компания предоставляет технику и ДМС со стоматологией. Откликнуться ➡️ Навигация: База знаний • Задачи • Собеседования 🐸 Библиотека програм…

🤔3

12 Nov 2026, 16:11 UTC≈2,520 views1 reactionsread 17 November 2026
Photo

💥 Три IT-курса по цене одного — только до 15 ноября! Хорошая техническая база - вот что, что помогает разработчику расти и переходить к более сложным задачам. В Proglib Academy можно забрать такую комбинацию для мощной прокачки за 45 990 ₽: 🧠 Алгоритмы и структуры данных — для развития алгоритмического мышления, решения технических задач и подготовки к собеседованиям. 🐍 Python — для практического программирования…

❤1

12 Nov 2026, 09:01 UTC≈2,400 views1 reactionsread 17 November 2026

💻 YADRO ищет технического лидера Java для цифровых сервисов Команда развивает корпоративные порталы, личные кабинеты и электронный документооборот. Лиду предстоит принимать архитектурные решения, разбирать проблемы производительности и работать с инфраструктурой. Нужны от пяти лет Java, опыт проектирования систем и работы с Kubernetes. Удалённо. Откликнуться ➡️ Навигация: База знаний • Задачи • Собеседования 🐸 Б…

🤔1

11 Nov 2026, 09:04 UTC≈2,690 views2 reactionsread 17 November 2026

💻 NAUKA ищет Senior Java для промышленной ERP Предстоит развивать коробочный продукт и решения для предприятий: писать код и тесты, обсуждать технические решения и поддерживать внедрения у заказчиков. Нужны Java Core, Spring, JPA и SQL. В стеке Java 17, Hibernate, PostgreSQL, Docker и Kubernetes. Опыт ускорения Java-приложений будет плюсом. Офис в Петербурге, после испытательного срока — гибрид. Официальное оформл…

❤1👍1

10 Nov 2026, 09:04 UTC≈2,950 views1 reactionsread 17 November 2026

💻 BSS ищет Java-разработчика для банковских сервисов в Ташкенте Предстоит разрабатывать переводы, операции с картами, кредиты и депозиты, подключать банковские системы и обеспечивать устойчивость сервисов при сбоях. Обязателен опыт в финтехе, банках или платёжных продуктах. Нужны Java 17+, Spring Boot 3, PostgreSQL, Kafka и понимание безопасности финансовых операций. Работа в офисе в Ташкенте, 5/2 с 9:00 до 18:00.…

🤔1

9 Nov 2026, 09:00 UTC≈3,280 views6 reactionsread 17 November 2026

💻 ЛАНИТ ищет Middle Java для корпоративных информационных систем Предстоит писать бизнес-логику, интегрировать сервисы, покрывать код тестами и улучшать производительность приложений. Нужны от 3 лет разработки, Java Core, Spring Boot, Hibernate, SQL и понимание распределённой архитектуры. В стеке также RabbitMQ, Docker и Kubernetes. Работа в московском офисе у метро «Марьина Роща». Официальное оформление, ДМС со с…

👍3🤔3

8 Nov 2026, 09:00 UTC≈3,530 views4 reactionsread 17 November 2026

💻 МТС Банк ищет Java-разработчика для внутреннего портала Команда автоматизирует заявки на отпуска и командировки, развивает мониторинг и интеграции. Предстоит писать микросервисы на Java 17+ и Spring Boot, участвовать в архитектурных решениях и разборе инцидентов. Нужны знание внутреннего устройства Spring, опыт микросервисной разработки и от 2 лет опыта профилирования Java-приложений. В стеке Kafka, PostgreSQL и …

❤3👍1

7 Nov 2026, 09:04 UTC≈3,420 views0 reactionsread 17 November 2026

💻 Extyl ищет Senior Java-разработчика для проектной работы Предстоит подключиться к команде заказчика. Нужны от 3 лет разработки на Java, опыт со Spring, Hibernate, REST API и Kafka. В требованиях также есть Camunda, Oracle или PostgreSQL, Docker и Kubernetes. Пригодятся навыки тестирования и работы с микросервисами. Полная занятость, удалённая работа. Оформление через ИП или самозанятость. Откликнуться ➡️ Навиг…

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

Posts recorded as deleted after publishing

We recorded 3 posts on @javadevjob as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 August 2026
Most recent seen missing
16 November 2026
Median time before seen missing
39 hours
Seen missing in the last 30 days
1

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

Senior Java Developer
@seniorjavist · 20,341
Telegram ranks this channel #44 of 89 here — alongside 88 others — read 26 September 2026
Java библиотека
@javalib · 30,273
Telegram ranks this channel #55 of 84 here — alongside 83 others — read 7 September 2026
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 21,756
Telegram ranks this channel #57 of 88 here — alongside 87 others — read 21 September 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Java jobs — вакансии для java-разработчиков” (@javadevjob), 14,080 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/javadevjob.

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.