泰国/迪拜/菲律宾/马来西亚/斯里兰卡/柬埔寨等多个国家直招 更多--职能岗/业绩岗/技术岗 请关注:@wangnvshizhizhao
Signed 热心市民小蟹(招技术)

Channel
@zhaopinkanzhe
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
436subscribers
-30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001872980557 |
|---|---|
| Type | Channel |
| Username | @zhaopinkanzhe |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/zhaopinkanzhe |
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 21 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 03:14 | 436 | -7 |
| 30 Oct 2026, 17:58 | 443 | -6 |
| 16 Oct 2026, 00:28 | 449 | -2 |
| 9 Oct 2026, 21:18 | 451 | +2 |
| 30 Sept 2026, 11:58 | 449 | -9 |
| 16 Sept 2026, 20:40 | 458 | -3 |
| 9 Sept 2026, 19:00 | 461 | +2 |
| 31 Aug 2026, 01:05 | 459 | -2 |
| 24 Aug 2026, 05:35 | 461 | -3 |
| 16 Aug 2026, 20:35 | 464 | -2 |
| 8 Aug 2026, 04:47 | 466 | no change |
| 7 Aug 2026, 16:28 | 466 | first reading |
20 posts held, back to 30 April 2025 — 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 10 July 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
22 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 59.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 59.1% | |
| 👍 | 8 | 36.4% | |
| 🥰 | 1 | 4.55% |
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 8 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 22 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 30 April 2025 to 10 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
泰国/迪拜/菲律宾/马来西亚/斯里兰卡/柬埔寨等多个国家直招 更多--职能岗/业绩岗/技术岗 请关注:@wangnvshizhizhao
Signed 热心市民小蟹(招技术)
BX·交易所: 薪资:30K-100K(优秀可谈)+绩效 高级产品 产品专家 高级运维 高级前端/架构 高级后端/架构 双休+节假日+年假20天+年底13薪 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
👍8
Signed 热心市民小蟹(招技术)
柬埔寨金边/迪拜 安卓开发 测试管理 产品经理 紧急‼️ 前端/前端架构 Java /Java架构 紧急‼️ python 运营 马来吉隆坡 测试 web前端 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
❤5
Signed 热心市民小蟹(招技术)
太可爱了 我的哈基米👌 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
🥰1
Signed 热心市民小蟹(招技术)
U3d 高级游戏开发工程师(日本) 岗位职责: 1、使用Unity3D引擎开发3D游戏; 2、与策划、美术、产品人员讨论开发需求及技术实现细节; 3、编写高效、稳定、安全的代码; 4、负责游戏上线后的优化与迭代开发。 任职要求: 1.3年及以上Unity3D移动端游戏开发经验,熟练使用C#及Lua语言;有完整上线项目经验者优先; 2. 熟悉常用数据结构和算法;了解常用设计模式; 3. 熟练掌握系统开发,可以独立承担过核心模块的开发任务;熟悉UI系统框架及性能优化者优先; 4. 熟悉客户端架构者优先;有3D图形学经验者优先; 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
Signed 热心市民小蟹(招技术)
资深游戏主策划 / 制作人 (试用期泰国转正日本) 岗位职责 1. 全面负责游戏核心玩法、系统框架与内容设计,提升游戏体验 2. 主导战斗、关卡、系统、数值等核心模块的设计与落地执行 3.对美术品质非常敏感,注重在世界观下的内容表达 4. 深入研究市场热门产品与用户需求,持续输出创新方向与调整建议 45 梳理游戏体验与数值模型,推动项目从立项到上线的完整闭环 任职要求 1. 5年及以上工作经验,统招本科及以上学历 2. 有成功游戏项目完整研发、上线和运营经验 3. 精通(肉鸽/TCG/SLG)品类,对其发展趋势有深刻的思考和独到的见解 4. 善于团队协作与沟通,具备带领团队完成复杂系统设计的能力 5. 热爱游戏,具备丰富的网游体验,能够抽象分析核心玩法机制 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
Signed 热心市民小蟹(招技术)
📍马来吉隆坡 (双休) 🔴web前端 (直播项目) 🍙薪资待遇:35-45K 🍙餐补:12600P 🍙房补:22000P-32000P 🍙工作时间:9:30-18:30(周六日双休) 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
Signed 热心市民小蟹(招技术)
西港现场或者远程 岗位需求 1、两名中级Java 开发程序员(现场) 2、flutter 开发一名,能独立开发,会iOS 或者安卓更好 3、前端开发一名,主要以vue为主 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
❤1
Signed 热心市民小蟹(招技术)
菲/马来 居家 要Golang 高级测试 DBA K8s运维 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
Signed 热心市民小蟹(招技术)
马来/迪拜/菲/台湾 远程办公(双休) PHP(社区、论坛、优化) 薪资待遇:25-35K 餐补:12600P 房补:22000P-32000P 工作时间:9:30-18:30(周六日双休) 入职联系✈️:@HRxiexiexie 💕简介目录(顶端) 💕职能岗位大全 💕业绩岗位大全 💕技术岗位大全
❤2
Signed 热心市民小蟹(招技术)
家人们 谁能给我分享几个技术交流群哇 入职联系✈️:@HRxiexiexie
Signed 热心市民小蟹(招技术)
有没有flutter
Signed 热心市民小蟹(招技术)
Showing the 12 most recent of 20 posts we hold for @zhaopinkanzhe. 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.
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.
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.
“海外高薪技术岗招聘求职” (@zhaopinkanzhe), 436 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/zhaopinkanzhe.
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.