Telegram RegisterThe public register of Telegram
Telegram profile photo for HighTech Israel Jobs - вакансии и резюме

Channel

HighTech Israel Jobs - вакансии и резюме

@israjobs

On this record: Topic · Growth · Engagement · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

12,847subscribers

-1 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-1001337182164
TypeChannel
Username@israjobs
Created4 June 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/israjobs

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

12,79612,85112,823.56 August 2026 — 12,848 subscribers7 August 2026 — 12,847 subscribers8 August 2026 — 12,849 subscribers9 August 2026 — 12,848 subscribers10 August 2026 — 12,847 subscribers11 August 2026 — 12,850 subscribers12 August 2026 — 12,845 subscribers13 August 2026 — 12,846 subscribers14 August 2026 — 12,848 subscribers17 August 2026 — 12,851 subscribers18 August 2026 — 12,849 subscribers19 August 2026 — 12,846 subscribers22 August 2026 — 12,847 subscribers24 August 2026 — 12,846 subscribers25 August 2026 — 12,845 subscribers26 August 2026 — 12,840 subscribers27 August 2026 — 12,838 subscribers28 August 2026 — 12,831 subscribers29 August 2026 — 12,826 subscribers30 August 2026 — 12,824 subscribers31 August 2026 — 12,823 subscribers1 September 2026 — 12,822 subscribers2 September 2026 — 12,818 subscribers3 September 2026 — 12,813 subscribers5 September 2026 — 12,805 subscribers9 September 2026 — 12,796 subscribers11 September 2026 — 12,823 subscribers13 September 2026 — 12,829 subscribers15 September 2026 — 12,842 subscribers17 September 2026 — 12,845 subscribers19 September 2026 — 12,847 subscribers12,8476 August 202619 September 2026
31 measurements spanning 44 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 12,788–12,859 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
19 Sept 2026, 16:3612,847+2
17 Sept 2026, 02:5612,845+3
15 Sept 2026, 02:1612,842+13
13 Sept 2026, 11:1512,829+6
11 Sept 2026, 15:1612,823+27
9 Sept 2026, 03:1912,796-9
5 Sept 2026, 22:1612,805-8
3 Sept 2026, 17:1612,813-5
2 Sept 2026, 07:2412,818-4
1 Sept 2026, 07:4412,822-1
31 Aug 2026, 06:4712,823-1
30 Aug 2026, 06:5512,824-2
29 Aug 2026, 09:1212,826-5
28 Aug 2026, 08:5312,831-7
27 Aug 2026, 10:4712,838-2
26 Aug 2026, 14:0412,840-5
25 Aug 2026, 11:4512,845-1
24 Aug 2026, 10:4312,846-1
22 Aug 2026, 19:2912,847+1
19 Aug 2026, 14:0212,846first reading

Engagement

29 posts held, back to 13 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 48 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.77%
avg views ÷ 12,847 subscribers
Avg views / post
870
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 29 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held29 (13 July 20261 September 2026)
Views total1,739
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 20:53 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.

Advertising

Ad load
3.45%
1 of 29 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
2,650
over 1 measured post
Median views · rest
1,770
over 28 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.

Measured over the 29 most recent posts we hold, published 13 July 2026 to 1 September 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

1 Sept 2026, 08:42 UTC810 viewsread 2 September 2026
File

#резюме Всем привет! Ищу работу и буду рада фидбэку или рекомендациям. Направляю свое общее резюме (под конкретные вакансии готова оперативно его адаптировать). Я Technical Business & System Analyst / QA Engineer с бэкграундом в FinTech (кредитные конвейеры) и e-commerce ритейле. Полный цикл работы с требованиями, BPMN/UML, REST API (Postman/Swagger), SQL + тест-дизайн и QA. Свободно владею английским (C1) и франц

31 Aug 2026, 18:01 UTC929 viewsread 2 September 2026

Публикатор: Kido Barao Обсуждение: @TechRabbits #вакансия Ищу гофера! По вопросам в ЛС, дам реферал Upwind Security https://t.me/kido_barao whatsapp - +97254-513-2710 About the role We are looking for a Senior Software Engineer to join our engineering team and work on a cross-platform security product. The role combines backend development, systems programming, and operating-system integrations, with a strong foc

18 Aug 2026, 11:28 UTC≈1,850 viewsread 2 September 2026

Публикатор: Tanichev Vitaly Обсуждение: @TelRan Разработчики севера! Есть #вакансия и даже не одна 1. Embedded Linux Tech Lead 2. Cloud & DevOps Engineer 3. Senior Robotics Algorithm Engineer 4. Embedded Software Engineer Ведётся разработка робота на новой платформе, нужны специалисты. Maytronics. Территориально недалеко от Афулы. Есть возможность работать 2 дня в неделю из дома. Компенсация дороги или автомобил

18 Aug 2026, 03:21 UTC≈1,850 viewsread 2 September 2026
File

Всем привет! Ищу работу в качестве Backend / AI Engineer. Мой основной стек: • Python (FastAPI), Java (Spring Boot), TypeScript • PostgreSQL, Redis, Docker, Kubernetes • PyTorch, OpenCV, AI Agents, LLM-интеграции • Оптимизация и алгоритмы (OR-Tools CP-SAT, ALNS, графовые модели) Есть опыт разработки production-систем: • AI Agent платформы с оркестрацией задач, workflow management и интеграцией LLM • Backend для ло

17 Aug 2026, 15:57 UTC≈1,610 viewsread 2 September 2026

Публикатор: Genady Обсуждение: @TelRan Работа. На частичную или полную ставку требуется программист (web разработчик клиентской части, frontend developer). Обязательны знания Angular 8+ , html, css , bootstrap. Возможна удалённая форма работы. Присылать резюме на электронную почту с указанием телефона([email protected]) #вакансия

16 Aug 2026, 10:46 UTC≈1,660 viewsread 2 September 2026
Photo

🔐 מוביל/ת תחום תקשורת ואבטחת מידע | Hands-On 📍 ראשון לציון 🏢 משרה מלאה מהמשרד | ללא היברידיות לחברת Enterprise מובילה דרוש/ה מוביל/ת תחום תקשורת ואבטחת מידע לתפקיד מקצועי עם אחריות מקצה לקצה. דרישות • 3–5 שנות ניסיון בתקשורת ואבטחת מידע • ניסיון בסביבת Enterprise מרובת משתמשים ואתרים • ניסיון עם Cisco ISE / NAC • יכולות Troubleshooting גבוהות • הסמכות CCNP, CCNP Security, Check Point CCSA/CCSE, CISSP או CISM – יתרון

15 Aug 2026, 09:11 UTC≈1,540 viewsread 2 September 2026

Публикатор: jewelxxet Обсуждение: @TelRan @barm1shka - связь Ищу работу / проекты по разработке лендингов Привет! Меня зовут Егор. Основное мое направление, где уже есть опыт — разработка лендингов от задачи до готового запуска Что могу: — анализ продукта и целевой аудитории; — структура и пользовательский сценарий; — дизайн и разработка адаптивного лендинга; — формы заявок, Telegram и другие интеграции; — доработк

11 Aug 2026, 06:24 UTC≈1,950 viewsread 2 September 2026

Публикатор: Elena Z Обсуждение: @TelRan #вакансия Netanya We are looking for an experienced Senior DevOps / Platform Engineer to support and enhance a cloud-native SaaS platform. 6-8 month contract position Responsibilities: * Manage and optimize infrastructure in Microsoft Azure * Support and maintain Kubernetes (AKS) and Docker environments * Automate infrastructure and operational processes using Terraform and P

10 Aug 2026, 12:09 UTC≈1,790 viewsread 2 September 2026

Публикатор: Genady Обсуждение: @TelRan Работа. На частичную или полную ставку требуется программист (web разработчик клиентской части, fronted developer). Обязательны знания Angular 8+ , html, css , bootstrap. Возможна удалённая форма работы. Присылать резюме на электронную почту с указанием телефона([email protected]) #вакансия

10 Aug 2026, 11:47 UTC≈1,770 viewsread 2 September 2026

Публикатор: K K Обсуждение: @TelRan Всем привет! Arad Technologies ищет Senior Embedded Engineer Мы — R&D-центр Arad Group, разрабатывающий умные IoT-решения для измерения воды. Ищем опытного Senior Embedded Engineer в команду Embedded Software для разработки следующего поколения smart water meters и IoT-устройств. Что предстоит делать: • Разрабатывать embedded software для микроконтроллеров • Работать с low-powe

8 Aug 2026, 19:25 UTC≈1,620 viewsread 2 September 2026

Публикатор: Мария Пелевина Обсуждение: @TelRan C#/.NET Software Developer | Misgav Area A company in the Misgav area is looking for a Software Developer with experience in systems that combine software and hardware. Full-time | Office-based, not hybrid Key Responsibilities: • Develop and maintain applications using C#/.NET • Develop and support WinForms-based user interfaces • Work with hardware components and s

6 Aug 2026, 05:48 UTC≈1,820 viewsread 2 September 2026

Публикатор: Daria Обсуждение: @TelRan Всем привет! GREEN-API - API провайдер популярных мессенджеров WhatsApp, Telegram, MAX. Мы уже более 10 лет на рынке, поэтому создаем не только новые продукты, но и поддерживаем старые. Мы в поисках менеджера по работе с клиентами в нашу команду, важно владение ивритом и проживание в Израиле. Чем предстоит заниматься: • Работа с действующими клиентами(отработка заявок, консульт

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

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.

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.

Работа в Израиле | WORK.co.il
@BROOTTO_Jobs · 40,173
Telegram ranks this channel #53 of 88 here — alongside 87 others — read 30 August 2026
Репатриация в Израиль | OLE HADASH
@olehadash_com · 31,871
Telegram ranks this channel #54 of 89 here — alongside 88 others — read 5 September 2026
Библиотека Иврит
@hebrew_library · 30,917
Telegram ranks this channel #83 of 92 here — alongside 91 others — read 6 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“HighTech Israel Jobs - вакансии и резюме” (@israjobs), 12,847 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/israjobs.

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.