Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚求职交流【远程/驻场】-日本新加坡马来泰国

Channel

东南亚求职交流【远程/驻场】-日本新加坡马来泰国

@BuzzTheJob

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

633subscribers

+43 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002379269347
TypeChannel
Username@BuzzTheJob
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/BuzzTheJob

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

590633611.57 August 2026 — 590 subscribers8 August 2026 — 590 subscribers15 August 2026 — 606 subscribers22 August 2026 — 612 subscribers30 August 2026 — 617 subscribers8 September 2026 — 626 subscribers15 September 2026 — 633 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net +43. 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 584–639 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:21633+7
8 Sept 2026, 14:16626+9
30 Aug 2026, 06:38617+5
22 Aug 2026, 09:16612+6
15 Aug 2026, 19:16606+16
8 Aug 2026, 03:18590no change
7 Aug 2026, 15:13590first reading

Engagement

20 posts held, back to 29 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 1 page 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 20 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

8 Aug 2026, 02:11 UTC29 viewsread 8 August 2026

📍【泰国🇹🇭包网运营专员】 大陆/越南籍 12-15K + KPI 9休6 要求:有包网经验,目前已在泰国,持有泰国长期签证。

7 Aug 2026, 11:16 UTC91 viewsread 8 August 2026

💜【越南-胡志明市-活动运营 】20K-35K 上班时间:12小时月休4 💜详情咨询 @Buzzwithagun

6 Aug 2026, 11:48 UTC127 viewsread 8 August 2026

💜第三国远程--后端开发工程师Java+go, 需要 精通两种开发语言JAVA+Golang都会,薪资30-50k 💜详情咨询 @Buzzwithagun

6 Aug 2026, 02:59 UTC141 viewsread 8 August 2026

💜【国内远程golang 5个空缺】简历投递 @Buzzwithagun 资深Go/主程级Go业务开发 ✅五年以上golang,Docker部署、有RPC服务器开发经验,其中2年架构经验 ✅精通数据结构和算法,深入理解多线程、net/http等相关技术,有大规模分布式系统的设计和开发经验,能独立完成系统的设计及开发 ✅精通MySQL数据库&索引优化。熟悉国际埋点sdk接入优先,拥有Adjust,AF,FB,谷歌广告s2s对接经验的优先 💜详情咨询 @Buzzwithagun

6 Aug 2026, 00:44 UTC142 viewsread 8 August 2026

📍【 亚美尼亚-财务助理】外籍 薪资13-18 需精通excel 并有基本运营经验,财务背景相关 💜详情咨询 @Buzzwithagun

5 Aug 2026, 12:11 UTC151 viewsread 8 August 2026

📍【 新加坡】 数值策划(Slots 游戏方向) Cocos Creator 前端开发工程师 💜详情咨询 @Buzzwithagun

4 Aug 2026, 10:39 UTC189 viewsread 8 August 2026

📌 财务专员(马来西亚 / 迪拜) 💰 马来西亚:RM6,000 – RM12,000(根据经验面议) 💰 迪拜:AED10,000 – AED18,000(根据经验面议) ✅ 开放外籍人士(马来西亚、台湾、越南、印尼、缅甸、泰国) 📌 前端开发工程师(马来西亚) 💰 薪资:面议 ✅ 开放中国籍和外籍 📌 产品经理(迪拜) 💰 薪资:面议 ✅ 开放中国籍 📌 会所女助理(马来西亚 / 迪拜) 💰 马来西亚:RM6,000 – RM8,000 💰 迪拜:RM7,000 – RM12,000(根据经验面议) ✅ 开放马来西亚籍、台湾籍 📌 会所男助理(日本 / 香港) 💰 RMB20,000 ✅ 开放马来西亚籍 📌 高级私厨(Base 马来西亚,可配合外派迪拜) 💰 RMB20,000 起(根据经验面议) ✅ 开放马来西亚籍 📮简历投递 @Buzzwithagun

4 Aug 2026, 06:17 UTC177 viewsread 8 August 2026

泰国新增两名 DBA,要求候选人目前已在泰国。📮简历投递 @Buzzwithagun

4 Aug 2026, 05:38 UTC165 views1 reactionsread 8 August 2026

日本技术公司岗位介绍(优先在日本有日本签证❗️) 💵 薪资 : 30-50k,特别优秀者可面议 🌎 国籍:不限 🎓 学历:全日制本科 📆 上班时间:9 小时!大小周 📍地点:日本 东京办公室 🎯 基本要求: ✅ 年龄38岁以下 ❗️ 计算机相关专业本科及以上❗️必须全日制统招学历 🎁 Benefits | 员工福利: 1. 公司提供住宿 2. 每日餐补 3. 薪资结构:各种激励奖金➕13薪 4. 年休假: 每年15天带薪年假 5. 每月至少一次团队日常活动 6. 工作签证 7. 公司报销入职所用单程机票 8. 节假日提供节日红包 9. 生日红包 🎯 【岗位: 前端开发工程师】 📣岗位职责📣 • 负责平台开发与迭代、第三方平台对接 • 负责平台网页端和移动端开发 📣任职要求📣 • 计算机相关专业,3 年及以上前端开发经验; • 深入理解React框架原理,熟练掌握React Hooks开发模式 • 熟练使用React生态常…

❤1

4 Aug 2026, 05:36 UTC148 viewsread 8 August 2026

📍【 日本东京 运维工程师-30K-40K】 要求:域名 + CDN + 服务器 + 数据运营方向,偏实施与维护) 💜详情咨询 @Buzzwithagun 岗位职责: 1. 负责公司域名管理、CDN加速配置及日常维护。 2. 熟悉主流CDN平台接入与配置(Cloudflare、阿里云、腾讯云、百度云加速等)。 3. 负责SSL证书申请、部署与续期,了解Let's Encrypt、ACME协议及Cloudflare API等。 4. 维护多CDN环境,支持不同平台间的配置切换、缓存策略调整及基础WAF管理。 5. 负责域名解析记录管理、批量操作及DNS更新。 6. 配合完成域名注册 → DNS配置 → CDN加速 → HTTPS启用的流程优化。 7. 参与服务器日常运维、监控及基础数据运营支持工作。 8. 处理日常故障响应、问题排查及优化工作。 任职要求: - 2年以上相关运维经验,熟悉Linux服务器基础操作。 - 有CDN配…

4 Aug 2026, 05:26 UTC149 viewsread 8 August 2026

💜泰国要一个测试 30-40k 💜详情咨询 @Buzzwithagun

Showing the 12 most recent of 20 posts we hold for @BuzzTheJob. 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 1 registered channel — 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.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“东南亚求职交流【远程/驻场】-日本新加坡马来泰国” (@BuzzTheJob), 633 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/BuzzTheJob.

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.