Telegram RegisterThe public register of Telegram
Telegram profile photo for Go jobs — вакансии по Go

Channel

Go jobs — вакансии по Go

@godevjob

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

11,548subscribers

+661 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-1001295906671
TypeChannel
Username@godevjob
DescriptionЛучшие вакансии по Go. Наши курсы: https://clc.to/sfRQ4w По рекламе: @tproger_sales_bot Для обратной связи: @proglibrary_feeedback_bot Наши каналы: https://t.me/proglibrary/9197 Покажем, как запустить своего ии-агента: https://clc.to/tvpmDQ
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/godevjob

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 99% 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

10,88711,55211,219.56 August 2026 — 10,887 subscribers7 August 2026 — 10,889 subscribers8 August 2026 — 10,898 subscribers9 August 2026 — 10,906 subscribers10 August 2026 — 10,918 subscribers11 August 2026 — 10,933 subscribers12 August 2026 — 10,947 subscribers13 August 2026 — 10,963 subscribers15 August 2026 — 11,008 subscribers16 August 2026 — 11,011 subscribers17 August 2026 — 11,008 subscribers18 August 2026 — 11,012 subscribers19 August 2026 — 11,025 subscribers20 August 2026 — 11,029 subscribers21 August 2026 — 11,047 subscribers23 August 2026 — 11,051 subscribers24 August 2026 — 11,052 subscribers25 August 2026 — 11,063 subscribers26 August 2026 — 11,070 subscribers27 August 2026 — 11,079 subscribers28 August 2026 — 11,090 subscribers29 August 2026 — 11,101 subscribers30 August 2026 — 11,107 subscribers31 August 2026 — 11,115 subscribers1 September 2026 — 11,133 subscribers2 September 2026 — 11,147 subscribers4 September 2026 — 11,156 subscribers6 September 2026 — 11,166 subscribers9 September 2026 — 11,207 subscribers12 September 2026 — 11,244 subscribers13 September 2026 — 11,254 subscribers15 September 2026 — 11,277 subscribers17 September 2026 — 11,278 subscribers27 September 2026 — 11,360 subscribers4 October 2026 — 11,401 subscribers9 October 2026 — 11,408 subscribers13 October 2026 — 11,422 subscribers14 October 2026 — 11,432 subscribers15 October 2026 — 11,456 subscribers17 October 2026 — 11,483 subscribers18 October 2026 — 11,490 subscribers19 October 2026 — 11,491 subscribers20 October 2026 — 11,495 subscribers22 October 2026 — 11,508 subscribers23 October 2026 — 11,514 subscribers25 October 2026 — 11,518 subscribers26 October 2026 — 11,512 subscribers27 October 2026 — 11,514 subscribers28 October 2026 — 11,513 subscribers29 October 2026 — 11,526 subscribers30 October 2026 — 11,530 subscribers31 October 2026 — 11,535 subscribers1 November 2026 — 11,527 subscribers2 November 2026 — 11,534 subscribers3 November 2026 — 11,542 subscribers4 November 2026 — 11,552 subscribers5 November 2026 — 11,548 subscribers11,5486 August 20265 November 2026
57 measurements spanning 91 days, net +661. 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 10,787–11,652 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
5 Nov 2026, 16:3611,548-4
4 Nov 2026, 14:1011,552+10
3 Nov 2026, 15:1011,542+8
2 Nov 2026, 12:2811,534+7
1 Nov 2026, 10:3711,527-8
31 Oct 2026, 12:4611,535+5
30 Oct 2026, 10:0211,530+4
29 Oct 2026, 12:1511,526+13
28 Oct 2026, 14:1711,513-1
27 Oct 2026, 11:2111,514+2
26 Oct 2026, 09:3511,512-6
25 Oct 2026, 12:0511,518+4
23 Oct 2026, 13:0511,514+6
22 Oct 2026, 14:0511,508+13
20 Oct 2026, 05:0011,495+4
19 Oct 2026, 02:3811,491+1
18 Oct 2026, 00:5611,490+7
17 Oct 2026, 02:1811,483+27
15 Oct 2026, 22:5011,456+24
14 Oct 2026, 20:4911,432first reading

Engagement

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

ERR · 30 days
24.9%
avg views ÷ 11,548 subscribers
Avg views / post
2,870
24 posts measured
Reaction rate
0.223%
reactions ÷ views · ER floor
Posts in window
24
of 46 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 23 of 24 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 5 November 2026
Posts held46 (24 July 2026 – 5 November 2026)
Views total68,990
Reactions total146
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 07:46 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
≈201
Videos
≈8
Links
≈2,240

Lifetime counters from Telegram’s own channel header, read 6 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.

Reaction mix

329 reactions across 39 posts, in 3 distinct kinds. The most used accounts for 70.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤔23370.8%
❤5817.6%
👍3811.6%

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

Measured over the 46 most recent posts we hold, published 24 July 2026 to 5 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
4.35%
2 of 46 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,260
over 2 measured posts
Median views · rest
3,420
over 44 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
2VtzqvpnJQs11 September 20261 September 2026
2VtzqvwpJCn15 November 20265 November 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 46 most recent posts we hold, published 24 July 2026 to 5 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 24 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).

5 Nov 2026, 09:58 UTC≈1,260 views2 reactionsread 6 November 2026
Advertisementerid 2VtzqvwpJCnVideo

Бэкендеры, 17 ноября AvitoTech усаживает вас за игровые столы 🔥 Backend Roulette — вечеринка для бэкенд- и Go-разработчиков и архитекторов System Design. Инженерные задачи там раскладываются как партия в покер, а вместо докладов будут практика, обмен опытом и немного азарта. Роль крупье за каждым столом играет эксперт AvitoTech: выдаёт команде вводные и по ходу игры подкидывает новые обстоятельства, под которые при…

🤔2

5 Nov 2026, 09:19 UTC≈1,510 views6 reactionsread 6 November 2026

🎬 Go-разработчик в VK Video Live Зарплата не указана Санкт-Петербург, удалёнка допускается. Географию найма нужно уточнить Команда развивает прямые эфиры и Live SDK. Предстоит разрабатывать чаты с модерацией и ботами, инструменты монетизации и сервисы для работы с потоковыми данными, снижать сетевые задержки. Требования: — Знание Go и опыт проектирования приложений на нём — REST/gRPC, отладчик и профайлеры Go — Pos…

🤔5❤1

4 Nov 2026, 09:20 UTC≈2,020 views3 reactionsread 6 November 2026

🛰 Middle Go-разработчик в Базис Зарплата не указана Удалённо. В карточке указана Москва, географию найма нужно уточнить Команда Basis SDN развивает управление виртуальными сетями на Open vSwitch и OVN. Предстоит писать Go-бэкенд, проектировать схемы PostgreSQL, разрабатывать ETL для загрузки сетевой телеметрии в ClickHouse и REST/gRPC API, писать тесты. Требования: — Go от 2 лет — Высшее образование, желательно зак…

🤔3

3 Nov 2026, 09:16 UTC≈2,250 views28 reactionsread 6 November 2026

💻 Senior Fullstack-разработчик в Most AI 180 000–220 000 ₽ в месяц, до или после налогов — не уточнено Удалённо, МСК ±2 часа, полный рабочий день В Most AI предстоит развивать React-интерфейс и Go/Python-бэкенд AI-платформы, работать над LLM-чатами и агентами. Требования: — От 4 лет коммерческого fullstack-опыта — React/TypeScript — от 2 лет — Go — от 2 лет, сейчас как основной язык — Python на бэкенде — Linux CLI,…

🤔27❤1

2 Nov 2026, 08:42 UTC≈2,600 views5 reactionsread 6 November 2026

💳 Руководитель отдела разработки в Wildberries Банк Зарплата не указана Удалённо, опыт от 5 лет по карточке работодателя Wildberries Банк ищет руководителя для разработки банковской платформы. Предстоит проектировать ПО, ставить задачи команде, планировать работы и отвечать за качество и надёжность продуктов. Требования: — Опыт руководства командой разработки — Коммерческая разработка на Java, Kotlin или Go — Опыт …

🤔3❤1👍1

1 Nov 2026, 08:46 UTC≈2,780 views5 reactionsread 6 November 2026

💻 Golang backend developer в Platform Backend Services, 2ГИС Зарплата не указана Удалённо или гибрид. Офисы: Москва, Санкт-Петербург, Новосибирск Команда направления Mobile поддерживает серверы обновлений приложений 2ГИС и собирает ключевые бэкенды внутри направления. Задачи: интеграции с мобильными клиентами, доставка через CI/CD в Kubernetes в несколько ЦОД, тестирование и соблюдение SLO. Требования: — От 5 лет п…

👍4🤔1

31 Oct 2026, 09:15 UTC≈2,830 views3 reactionsread 6 November 2026

💻 Golang-разработчик в команду ГеоПоток, 2ГИС Зарплата не указана Удалённо или гибрид. Офисы: Москва, Санкт-Петербург, Новосибирск ГеоПоток — система мониторинга персонала и транспорта. Предстоит развивать высоконагруженный backend, участвовать в проектировании архитектуры, проводить ревью и улучшать надёжность продукта. Требования: — От 4 лет командной разработки на стеке команды и хорошее знание Go — KISS, DRY, S…

🤔2❤1

30 Oct 2026, 09:07 UTC≈2,940 views6 reactionsread 6 November 2026

💻 Golang-разработчик в команду CDP, 2ГИС Зарплата не указана Удалённо, географию найма стоит уточнить CDP в 2ГИС объединяет пользовательские данные для персонализации. Предстоит разрабатывать сервисы обработки миллиардов событий, склейку идентификаторов, real-time агрегации и витрины. Требования: — Опыт backend-разработки от 3–5 лет — Понимание распределённых систем и микросервисов — Самостоятельная проработка реше…

❤4👍1🤔1

29 Oct 2026, 09:01 UTC≈3,000 views12 reactionsread 6 November 2026

💡 Go Architect / Solution Architect в финтех Условия оплаты — уточнить у рекрутера Удалённо, гибрид или офис. Кандидаты из РФ и РБ не рассматриваются Рекрутер Vital Partners ищет архитектора для неназванной международной финтех-организации. Задачи: распределённая платформа на Go, технические планы с продактами, ревью senior-инженеров и защита архитектурных решений. Требования: — От 7 лет разработки, из них от 4 лет…

🤔10❤2

28 Oct 2026, 08:42 UTC≈3,200 views7 reactionsread 6 November 2026

🛰 Golang-разработчик в БЮРО 1440 Зарплата не указана Москва, офис, гибрид или удалённо БЮРО 1440 ищет разработчика PaaS. Предстоит писать компоненты платформы и внутренние инструменты на Go, автоматизировать развёртывание БД, Kafka и Redis. Требования: — От 5 лет разработки, из них от 2 лет на Go — Чистый тестируемый код и работа с Linux — Высокая доступность, балансировка нагрузки и rate limiting — Распределённые …

❤5👍1🤔1

27 Oct 2026, 09:08 UTC≈3,240 views3 reactionsread 6 November 2026

💳 Senior Engineer, Crypto Cards & Smart Contracts в AlemX Зарплата не указана Удалённо, ежедневное пересечение с UTC+4 AlemX ищет инженера для криптокарт: интеграции эмитентов, авторизация платежей и сверка с on-chain балансами. В стеке Python/FastAPI, Go и Anchor/Rust, роль не ограничена Go. Требования: — Запущенная в production интеграция криптокарт или card issuing и знание карточного цикла — Production-контракт…

🤔2❤1

26 Oct 2026, 09:10 UTC≈2,960 views3 reactionsread 6 November 2026

🛰 Senior Software Engineer (Go/Python) — МТС Web Services Зарплата не указана Можно удалённо, полный рабочий день МТС Web Services ищет инженера для автоматизации операторского сетевого оборудования. Предстоит писать агентов, контроллеры и оркестраторы, интегрировать их с мониторингом и инвентаризацией, хранить состояние сети в PostgreSQL и проверять решения на эмуляторах и реальном оборудовании. Требования: — от 5…

🤔2❤1

Showing the 12 most recent of 46 posts we hold for @godevjob. 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 4 posts on @godevjob 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
20 August 2026
Most recent seen missing
1 September 2026
Median time before seen missing
13 days
Seen missing in the last 30 days
0

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

Библиотека Go-разработчика | Golang
@goproglib · 23,909
Telegram ranks this channel #4 of 91 here — alongside 90 others — read 17 September 2026
Golang
@Golang_google · 40,479
Telegram ranks this channel #6 of 90 here — alongside 89 others — read 30 August 2026
Fullstack / Software Job Offers
@runello_rus_webdevelopment · 24,248
Telegram ranks this channel #36 of 93 here — alongside 92 others — read 17 September 2026
IT Jobs | Вакансии в IT
@devs_it · 19,442
Telegram ranks this channel #46 of 93 here — alongside 92 others — read 5 October 2026
IT Вакансии Казахстан
@workitkz · 36,880
Telegram ranks this channel #66 of 85 here — alongside 84 others — read 2 September 2026
Remote Junior (INFLOW)
@remotejun · 26,799
Telegram ranks this channel #72 of 98 here — alongside 97 others — read 12 September 2026
Dev KZ | Vacancy
@devkz_jobs · 25,747
Telegram ranks this channel #74 of 86 here — alongside 85 others — read 15 September 2026
Библиотека программиста
@proglibrary · 77,704
Telegram ranks this channel #75 of 82 here — alongside 81 others — read 19 August 2026
Remote IT (Inflow)
@Remoteit · 51,943
Telegram ranks this channel #76 of 95 here — alongside 94 others — read 25 August 2026
DevOps
@DevOPSitsec · 23,872
Telegram ranks this channel #79 of 90 here — alongside 89 others — read 18 September 2026
Python Job | Вакансии | Стажировки
@job_python · 23,412
Telegram ranks this channel #80 of 96 here — alongside 95 others — read 19 September 2026
Ozon Tech
@ozon_tech · 30,150
Telegram ranks this channel #82 of 98 here — alongside 97 others — read 8 September 2026
Avito Career
@avito_career · 67,427
Telegram ranks this channel #82 of 98 here — alongside 97 others — read 21 August 2026
AvitoTech
@avitotech · 25,787
Telegram ranks this channel #86 of 96 here — alongside 95 others — read 14 September 2026
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs · 33,135
Telegram ranks this channel #88 of 96 here — alongside 95 others — read 5 September 2026
Артём Шумейко
@artemshumeiko · 19,793
Telegram ranks this channel #90 of 92 here — alongside 91 others — read 29 September 2026
Get IT
@Getitrussia · 22,008
Telegram ranks this channel #94 of 97 here — alongside 96 others — read 24 September 2026

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

“Go jobs — вакансии по Go” (@godevjob), 11,548 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/godevjob.

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.