🇲🇱🇲🇱🇲🇱频道里的兄弟姐妹,如果你们公司你们团队有需求IT技术岗位可以随时联系我们,我们深耕海外招聘市场8年,积累了大量的技术资源,或者你们要直接购买源码也可以联系我们,我们这边可以帮你们找到各类产品的源码,欢迎各位老板前来洽谈合作,推荐给我们合作的奖励丰厚红包。 https://t.me/HHJason123

Channel
海外技术招聘/远程/驻场/🌱
@HHJason123
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Telegram's recommendations · Cite this entry
9,073subscribers
+944 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001548855145 |
|---|---|
| Type | Channel |
| Username | @HHJason123 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/HHJason123 |
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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 06:58 | 9,073 | +42 |
| 11 Nov 2026, 21:59 | 9,031 | +21 |
| 8 Nov 2026, 09:46 | 9,010 | +41 |
| 4 Nov 2026, 19:51 | 8,969 | +38 |
| 1 Nov 2026, 18:20 | 8,931 | +23 |
| 30 Oct 2026, 04:06 | 8,908 | +36 |
| 26 Oct 2026, 20:00 | 8,872 | +21 |
| 23 Oct 2026, 10:05 | 8,851 | +46 |
| 20 Oct 2026, 07:36 | 8,805 | +29 |
| 17 Oct 2026, 16:40 | 8,776 | +20 |
| 14 Oct 2026, 22:35 | 8,756 | +20 |
| 11 Oct 2026, 13:36 | 8,736 | +78 |
| 5 Oct 2026, 06:41 | 8,658 | +59 |
| 26 Sept 2026, 14:37 | 8,599 | +60 |
| 17 Sept 2026, 23:57 | 8,539 | +58 |
| 13 Sept 2026, 14:58 | 8,481 | +31 |
| 10 Sept 2026, 02:01 | 8,450 | +71 |
| 4 Sept 2026, 16:41 | 8,379 | +51 |
| 1 Sept 2026, 11:53 | 8,328 | +34 |
| 29 Aug 2026, 14:33 | 8,294 | first reading |
Engagement
61 posts held, back to 28 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 40 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 35.9%
- avg views ÷ 9,073 subscribers
- Avg views / post
- 3,250
- 20 posts measured
- Reaction rate
- 0.163%
- reactions ÷ views · ER floor
- Posts in window
- 20
- 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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 61 (28 July 2026 – 16 November 2026) |
| Views total | 65,088 |
| Reactions total | 106 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 01:21 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.
Reaction mix
207 reactions across 43 posts, in 8 distinct kinds. The most used accounts for 93.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 193 | 93.2% | |
| 👍 | 4 | 1.93% | |
| ✍ | 3 | 1.45% | |
| 🌚 | 3 | 1.45% | |
| 👏 | 1 | 0.483% | |
| 🤔 | 1 | 0.483% | |
| 🤝 | 1 | 0.483% | |
| 🤣 | 1 | 0.483% |
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 207 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 28 July 2026 to 16 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.
Recent posts
Telegram’s own ‘edited’ marker: 11 of 20 posts held from the last 30 days (55.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).
胡志明招聘: 麻烦请知悉以下急招岗位: 一、A8 1. 总监助理1名 2. 高级运营经理1名 3. 资深用户运营1名 4. 海外运营主管1名 5. 社媒运营专员1名 6. 活动运营专员1名 7. 客维主管1名(入职亚美) 8. 培训专员1名(入职亚美) 9. 商务专员2名 (入职亚美,有菲律宾,印度,墨西哥市场代投资源优先) 10. 运营管培生 (华人不限国籍,前期迪拜/格鲁吉亚学习,后期越南) 二、BRC团队 1. 远程商务专员/组长5名(10K-15K) 2. 资深广告投放(18K-30K,主做菲律宾,有菲律宾代投资源优先) 3. 素材组长1名(12-15K+➕提成) 4. 户管组长1名(12-15K+➕提成) 5. 短…
🔥高阶渗透工程师 薪资:300k-500k/每月 工作地点:远程办公不限制地区 工作时间:完成交代的任务即可..(其他时间自由安排) 工作要求:完成指定网站的渗透提取数据即可(既然开这么高的薪资项目肯定是有难度,如果不是一般专家估计是做不了,需要非常丰富的渗透网站的经验)胆子要大,心要细 项目来源:提供稳定且持续的固定业务,无需个人或团队自行拓展客户/找项目。 薪资支付:只证明有这个实力,哪怕是提前支付都行,主要是看能力能不能达到要求,一切都好谈,可以商量。 任职要求: 1、男女不限;年龄 21-不限制 2、5-10 年以上渗透测试经验或安全行业工作经验,熟悉 OWASP10漏洞挖掘及利 用,及常规CVE利用。熟悉常见Web安全漏洞分析,包括SQL注入、XSS、CSRF;越权.. 3、熟悉常见安全攻防技术和安全漏洞,熟悉常用渗透测试工具;熟悉国内主流 安全检测系统、工具,如AWVS,Burpsuit,sqlmap,nmap,m…
❤3👏1
前端开发工程师(Vue / Android 混合应用) 工作性质:前期远程(后期新加坡) · 薪酬范围:15-25k 双休 任职要求 - 3 年及以上前端开发经验,有实际上线并持续维护的移动端项目。 - 熟练掌握 JavaScript、TypeScript、HTML、CSS,熟悉 Vue 及其生态。 - 熟悉 Android WebView 或其他混合应用开发模式,有 H5 与原生交互经验。 - 理解异步编程、事件机制、状态管理及网络请求,能处理重复点击、重复回调、页面切换和状态不同步等问题。 - 具备接口联调、性能优化和线上故障排查能力,能够独立完成模块交付。 - 具备基本安全意识,理解登录凭证保护、敏感信息脱敏及日志边界。 - 沟通清晰,有责任心,能主动发现问题并推动解决。 加分项 - 能阅读或编写 Java / Kotlin,具备 Android 原生开发经验。 - 熟悉 Android 权限、短信能力、多 SIM 卡…
❤9
前期远程后期入职格鲁吉亚 go开发 高并发,im,微服务,kafka,经验加分 薪资 30-60k https://t.me/HHJason123
❤5
远程招聘: 马甲包上架 移动端觉得自己马甲包上架很牛逼的都可以来,入职后会有马甲包数量考核的。 没有jd,以上就是甲方要求,其余的面试聊细节 远程薪资: 20k + 一个包100U https://t.me/HHJason123
❤3
远程Android架构师(远控方向) 国籍与工作地点不限, 英文能沟通即可。 这个职位是远程兼职 核心要求: 5 年以上 Android,…
❤1
格鲁吉亚 运维(30-60K) 单休 一、岗位职责 负责公司生产、测试环境的日常运维、稳定性建设及性能优化,保障业务系统的高可用性、安全性和可扩展性。 负责 Linux 服务器、网络、存储及基础设施的部署、维护、故障排查和性能调优。 负责 Kuber…
❤10
远程招聘: 马甲包上架 移动端觉得自己马甲包上架很牛逼的都可以来,入职后会有马甲包数量考核的。 没有jd,以上就是甲方要求,其余的面试聊细节 远程薪资: 20k + 一个包100U http…
❤5
🇦🇪🇹🇼🇦🇪🇹🇼远程:前端开发工程师(Vue / Android 混合应用),服务端开发(PHP优先),公司双休,8小时,包含国内所有假期,公司目前入职人选反馈都是非常不错的,经验符合的欢迎投递简历,有朋友的也可推荐朋友,远程职位现在不多,绝对靠谱的公司https://t.me/HHJason123
❤9
🇮🇲🇮🇲🇮🇲双休公司紧急招聘前期远程,后期入职新加坡职位, 早10 晚7,月休息8天,包含国内所有节假期 服务端开发工程师-PHP优先(前期远程后期入职新加坡) 前端开发工程师(vue-Android混合开发) SEO负责人(远程) 海外广告投放业务主管(远程接受偶尔出差) 私欲运营经理(入职越南胡志明) https://t.me/HHJason123
❤5
曼谷要高级运维 越南要财务和运营
❤4
Showing the 12 most recent of 61 posts we hold for @HHJason123. 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 edited after publishing
@HHJason123 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 7 November 2026
- Most recent edit
- 7 November 2026
Posts recorded as deleted after publishing
We recorded 1 post on @HHJason123 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
- 6 November 2026
- Most recent seen missing
- 6 November 2026
- Median time before seen missing
- 30 hours
- Seen missing in the last 30 days
- 1
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.
@remote_cn · 25,947
Telegram ranks this channel #8 of 85 here — alongside 84 others — read 15 September 2026
@XCRLZP · 104,460
Telegram ranks this channel #11 of 82 here — alongside 81 others — read 13 August 2026
@abetterpathxyz · 32,809
Telegram ranks this channel #22 of 90 here — alongside 89 others — read 4 September 2026
@DeJob_official · 48,023
Telegram ranks this channel #22 of 94 here — alongside 93 others — read 27 August 2026
@bnzhaopingmnl · 106,536
Telegram ranks this channel #26 of 84 here — alongside 83 others — read 15 August 2026
@dubaiuuu · 85,317
Telegram ranks this channel #53 of 67 here — alongside 66 others — read 17 August 2026
@zii33 · 104,625
Telegram ranks this channel #58 of 78 here — alongside 77 others — read 16 August 2026
This channel appears in 7 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“海外技术招聘/远程/驻场/🌱” (@HHJason123), 9,073 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/HHJason123.
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.