#резюме #cv #resume #mobile #reactnative #expo #typescript #nodejs #go #senior #remote #удаленно 🎯 Позиция: Senior Software Engineer — React Native / Node.js / Go 🏢 Формат работы: удалённо ⌛️ Занятость: полная ⏰ Опыт: 5+ лет 💸 Ожидания по зарплате: от $4 000 📞 Контакты: @doubleaitch 👨 Обо мне: hayrapetian.dev ⚙️ Tech Stack: - TypeScript, JavaScript, Go - React Native, Expo, React, Next.js, Angular - Node.js, NestJS…

Channel
NodeJS Jobs канал вакансий и резюме
@nodejsjobsfeed
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,538subscribers
+57 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 | -1001621569402 |
|---|---|
| Type | Channel |
| Username | @nodejsjobsfeed |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/nodejsjobsfeed |
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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 04:16 | 3,538 | +8 |
| 15 Sept 2026, 18:16 | 3,530 | +15 |
| 11 Sept 2026, 18:15 | 3,515 | +18 |
| 6 Sept 2026, 21:38 | 3,497 | +4 |
| 30 Aug 2026, 11:04 | 3,493 | +2 |
| 24 Aug 2026, 10:18 | 3,491 | -4 |
| 20 Aug 2026, 20:15 | 3,495 | +3 |
| 17 Aug 2026, 13:59 | 3,492 | +1 |
| 14 Aug 2026, 06:19 | 3,491 | +8 |
| 8 Aug 2026, 00:47 | 3,483 | +2 |
| 7 Aug 2026, 05:47 | 3,481 | first reading |
Engagement
29 posts held, back to 4 August 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 29 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
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 2 of the 29 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 4 August 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
#резюме #Backend #NodeJS #NestJS #TypeScript #Remote #iGaming 👨💻 Backend Software Engineer (Node.js) Опыт: 3+ года Стек: Node.js / NestJS / TypeScript / PostgreSQL / Redis / RabbitMQ / Kafka / Docker Локация: Минск / Удалённо / Релокация Занятость: Полная Зарплата: 2000–3000$ 📌 О себе Backend-разработчик с экспертизой в высоконагруженных микросервисных системах, iGaming (интеграция провайдеров, игровые математики…
#резюме #backend #nodejs #nestjs #typescript Junior Backend Developer (Node.js, NestJS, TypeScript) - ищу стажировку Формат работы: удалёнка Занятость: полная / частичная Ожидания по зарплате: от 0 ₽ Контакты: @msminkyyyy Обо мне: 16 лет, за полгода прошёл путь от вёрстки до коммерческого full-stack проекта. Самостоятельно освоил NestJS, TypeScript, PostgreSQL, Redis, Docker. Ищу стажировку с менторством, чтобы раб…
#резюме #nodejs #nestjs #backend #senior #highload #microservices ⚡️ Senior Node.js Backend Developer — 5+ лет с Node.js Формат: удалённо / гибрид Локация: Москва, рассматриваю СПБ / Нижний Новгород / релокацию Занятость: полная Оформление: ТК РФ / ИП Ожидания: от 300 000 ₽ на руки Английский: B2 Telegram: @tgdmitr Backend-инженер с 4+ годами коммерческого опыта на Node.js/TypeScript. Фокус — highload, system desi…
#резюме #frontend #backend #fullstack #javascript #resume #удаленка #fulltime #parttime Позиция: Fullstack / Frontend Developer / Backend Developer Формат работы: удаленно Занятость: полная, частичная, проектная Коммерческий опыт: 6 лет Ожидания по зарплате: от 3500$ — Обо мне: T-shaped Software Engineer с 6 летним опытом разработки в стартапах и продуктовых компаниях. Специализируюсь на проектировании распреде…
#резюме #remote #fullstack #backend #typescript #nodejs #react #nextjs #nest #web3 #javascript #crypto #solana 👨💻 Позиция: Senior Fullstack / Backend Developer 📍 Формат работы: Удалённо ⏱️ Занятость: Полная / Частичная / Проектная 💰 Ожидания: от 4000 USD на руки 🧠 Опыт: 6+ лет 📞 Контакты: @viesto_rosa ⸻ Fullstack JavaScript / TypeScript | Backend-focused | Web3, Solana, FinTech, Automation Разработчик с продакшен…
#резюме #nodejs Позиция: Middle+ Node.js developer Формат работы: удаленно Ожидания по зарплате: 3000$ Занятость: партайм, проектная, полная Опыт работы: 4+ года Обо мне: Middle+ Node.js разработчик с 4+ годами опыта в микросервисной архитектуре и highload-системах. Самостоятельно реализовывал продукты полного цикла - от архитектуры до MVP. Беру ответственность за принятые решения, слежу за их результатом в проде. У…
#резюме #backend #nodejs #nestjs #typescript #remote #fulltime Senior Backend Engineer / Technical Lead (Node.js) Remote · Full-time · $4200+ Telegram: @norayryeghiazaryan Email: [email protected] Обо мне Senior Backend Engineer с 8+ годами опыта. 2+ года — Team Lead (команды до 10 человек). Фокус: Node.js / NestJS · микросервисы · high-load · AI/search backend Опыт Objet.art — Senior Backend Engineer (2025…
#resume #резюме #job #backend #middle #remote #javascript #typescript #nestjs #nodejs #frontend #fullstack ━━━━━━━━━━━━━━━━━━ 👨💻 Middle Fullstack Developer 📍 Ростов-на-Дону, Россия 🌎 Готов к удаленной работе 💼 Full-time / Contract / Part-time 💰 От 100 000 руб. / месяц 📩 Telegram: @microzavrik 🌐 https://microzavrik.xyz ━━━━━━━━━━━━━━━━━━ 👋 О себе Fullstack-разработчик: backend на Node.js / TypeScript / NestJS, front…
❤1
#резюме #nodejs #nestjs #backend #senior Senior Node.js Backend Developer — 5+ лет с Node.js Формат работы: удалённо; гибрид — Москва (приоритет), СПБ, Нижний Новгород (готов переехать в любой из этих), либо релокация в вашу страну Занятость: полная Оформление: ТК РФ или ИП Ожидания по зарплате: от 300 000 ₽ на руки Контакты: @tgdmitr Обо мне: Backend-разработчик с 4+ годами коммерческого опыта. Основной стек — No…
#резюме #backend #nodejs #nestjs #typescript Junior Backend Developer (Node.js, NestJS, TypeScript) - ищу стажировку Формат работы: удалёнка Занятость: полная / частичная Ожидания по зарплате: от 0 ₽ Контакты: @msminkyyyy Обо мне: 16 лет, за полгода прошёл путь от вёрстки до коммерческого full-stack проекта. Самостоятельно освоил NestJS, TypeScript, PostgreSQL, Redis, Docker. Ищу стажировку с менторством, чтобы раб…
#резюме #удалёнка #javascript #typescript #react #nodejs #fulltime #fullstack Формат работы: удаленно (полностью) Занятость: полная, частичная (20–30 ч/нед), проектная работа Ожидания по зарплате: от 120 000 ₽ (на полный день) / обсуждаемо для частичной занятости Контакты: Telegram: @RegTegHik Ключевые проекты: 🛒 Интернет-магазин лазерных аппаратов (WordPress + WooCommerce) — 2024 Разработал кастомную тему «с нуля» …
Showing the 12 most recent of 29 posts we hold for @nodejsjobsfeed. 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@itfreelancers · 25,645
Telegram ranks this channel #35 of 92 here — alongside 91 others — read 14 September 2026
@myresume_ru · 20,089
Telegram ranks this channel #98 of 98 here — alongside 97 others — read 29 September 2026
This channel appears in 2 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“NodeJS Jobs канал вакансий и резюме” (@nodejsjobsfeed), 3,538 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/nodejsjobsfeed.
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.