产品(彩票经验) 入职地点:马来西亚/居家 薪资范围:20-30k 工作时间:8小时/双休 岗位职责: 1、 独立负责平台APP项目产品调研、功能规划、需求定义、开发、测试和上线的全流程, 2、 保证产品上线质量,把控产品体验,并跟进产品上线后的用户反馈和数据指标,持续进行分析、总结、优化; 3、 深度参与业务,收集运营、产品、客服等相关业务需求,梳理出清晰的业务流程,形成产品方案; 4、 以提升转化率和用户体验为目标,持续优化产品体验和探索产品的玩法。 任职要求: 1.3年以上互联网行业产品经验,需1年以上完整APP项目产品策划经验 2.有过AI产品经验的应用类等行业经验,熟悉彩票和体育业务; 3.能够熟练运用Axure RP、Visio、MindManager等常用工具 4.有基础产品运营意识,对数据敏感,具有数据分析能力,并将分析结果用于产品改进; 5.年龄40岁以下

Channel
多个国家月休8天工作交流(每周更新)
@shuangxiugognzuo
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Telegram's recommendations · Cite this entry
6,687subscribers
+199 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001686889569 |
|---|---|
| Type | Channel |
| Username | @shuangxiugognzuo |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/shuangxiugognzuo |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 |
|---|---|---|
| 17 Sept 2026, 20:40 | 6,687 | +41 |
| 13 Sept 2026, 11:00 | 6,646 | +4 |
| 9 Sept 2026, 12:01 | 6,642 | -5 |
| 4 Sept 2026, 04:17 | 6,647 | +16 |
| 1 Sept 2026, 04:15 | 6,631 | +6 |
| 29 Aug 2026, 08:25 | 6,625 | +15 |
| 26 Aug 2026, 17:39 | 6,610 | +21 |
| 24 Aug 2026, 00:48 | 6,589 | +23 |
| 20 Aug 2026, 04:13 | 6,566 | +34 |
| 16 Aug 2026, 21:42 | 6,532 | +19 |
| 13 Aug 2026, 07:14 | 6,513 | +25 |
| 9 Aug 2026, 23:33 | 6,488 | no change |
| 9 Aug 2026, 03:45 | 6,488 | first reading |
Engagement
27 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 5 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 27 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
26 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 73.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 73.1% | |
| 🤣 | 5 | 19.2% | |
| 🤬 | 2 | 7.69% |
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 16 of the 27 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 29 July 2026 to 19 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
File, posted without a caption
❗️❗️日本--越南--斯里兰卡-新加坡-马来西亚--菲律宾--亚美尼亚--迪拜—知名集团月休6-8天 (周末双休),总有一个合适你的 ❤️⭕️远程职位:推广专员、推广专员、招商专员、SEO专员、电销专员、AI Agent 工程师 ❤️⭕️格鲁吉亚:外籍值班、财务经理 ❤️🇦🇲亚美尼亚:golang、 ❤️🇱🇰斯里兰卡:市场经理 ❤️⭕️新加坡:数值策划、cocos、 ❤️🇯🇵日本:财务专员、客服专员、golang、前端开发、Golang(web3)、运营专员、数据分析师、网络链路与分发安全运维工程师、财务专员、 ❤️🇻🇳越南职位:总监助理 、投放专员 、用户运营、 ❤️🇲🇾马来西亚:Golang工程师、Telegram流量操盘手、商务专员、娱乐主播、游戏玩家运营、UI/UX设计师、商务拓展、会计师、社交产品经理、财务专员、运营负责人、电销专员、运维工程师、产品经理、 ❤️🇦🇪迪拜:运营经理、数据开发、商务经理…
AI Agent 工程师 工作时间:9小时月休6 ⚠️试用期远程,试用期薪资25-30K 转正需马来现场办公,薪资35-50K ## 岗位职责 1. 负责公司 AI Agent 相关功能的开发和落地,重点探索 AI 在研发、运营、客服、风控、数据分析等场景的实际应用。 2. 前期直接在现有开发环境中开展工作,结合现有项目进行 AI Coding、代码理解、Bug 排查、测试、Code Review、代码维护等。 3. 根据实际需求开发 Agent、Workflow、工具调用等功能,把 AI 真正接入现有业务系统,而不是停留在 Demo 阶段。 4. 探索让 Agent 参与完整研发流程,包括: 需求分析 → 任务拆解 → 开发 → 测试 → Review → 发布 → 维护。** 5. 针对现有项目中重复、耗时的工作,寻找适合 AI 自动化的场景,并实际开发解决方案。 6. 后续逐步探索 Agent 在集团…
❤3🤬2
远程UI JD 合作模式: - 远程合作,工作时间配合团队 - 试用期:3个月 - 薪资待遇:面议 招聘|远程产品 UI 设计师(Web3 / 金融方向) 岗位方向: Web3 / 金融产品 设计范围: Web、移动端、浏览器插件 ▼ 岗位职责 ‧ 负责钱包、交易、支付、理财等核心产品的 UI / UX 设计。 ‧ 搭建及维护 Figma Design System,包括组件库、Variables、深浅色主题、响应式规范等。 ‧ 负责签名、授权、转账等高风险操作流程的交互及风险提示设计,降低用户误操作。 ‧ 与产品、前端协作,完成从需求到上线的设计闭环,并参与设计走查及还原度验收。 ▼ 任职要求 ‧ 3 年以上产品 UI / UX 设计经验。 ‧ 作品集至少包含 2 个完整项目案例,能够讲清楚设计思路、决策过程及最终效果。 ‧ 精通 Figma,熟悉 Auto Layout、Components / Variants、De…
upay 职位:运维工程师 💰 薪资福利: 薪资:25,000 CNY 起步 国籍:马来西亚、台湾、中国 学历:本科 地点:日本 - 大阪或者马来西亚-吉隆坡 🎁 Benefits | 员工福利: 1. 房补:2500~4000 CNY / 月 (可提供内宿) 2. 年休假:每年两次年休假,未使用年假者可获得一个月基本工资的补贴 3. 每周五提供员工下午茶时光。部门每月组织一次团队建设活动 4. 节假日提供过节红包 5. 薪资结构:13薪 6. 公司承担工作签证费用(服务满一年后公司不再追偿) 7. 公司报销入职所用单程机票(转正后,无需承担费用) ⏱️ 工时:每日10小时(包含用餐1小时)休4 🎯 Responsibilities | 工作职责 1. 负责公司系统的日常运维工作,包括系统部署、配置管理、监控和故障排除等。 2. 参与系统架构设计和优化,提高系统的性能和稳定性。 3. 设计和实施自动化工具,提高运维效率和…
❤1
一、全栈/前端/后端/cocos/运维开发工程师 负责以下一个或多个方向的工作: 工作地点:日本东京 工作时间:8 小时 / 日,周休 1 日 薪资:30-50K RMB / 月,保底13薪,表现优异者奖励期权和最多24月奖金 - 参与产品研发,围绕真实场景持续迭代。 - 打造可复用的Tools&Skills体系,提升扩展效率与规模化交付能力。 - 完善工程基建与效能体系(Telemetry、微服务质量、CI/CD DevOps、AI+研发流程)。 需要具备的能力: - 精通前端/服务端/COCOS Creator/K8S中任一技术栈 - Al-native,vibe coding重度使用者,能判断代码质量,有能力用大模型出色地完成任何项目 - 有精心维护的、你不断觉得它变成屎山然后重构/重写了的项目 - 精通Java/TypeScript/Golang/Python中的任一语言,并能说出有趣细节 - 能够说出任意软件的任…
❤3
ak资深UI设计师 工作地点:日本东京 工作时间:8 小时 / 日,周休 1 日 薪资:25K –35K RMB / 月,保底13薪,表现优异者奖励期权和最多24月奖金 负责以下工作: - 参与产品研发,围绕真实场景持续迭代。 - 学习竞品,取长补短,不断优化产品。 - 持续塑造品牌感 需要具备的能力: - 精通Photoshop/Figma等常用软件 - 有精心设计的作品,并可以在面试时直接show off 你的作品 - 对当前主流的AI绘画、AI视频生成工具有深入的了解和丰富的实践经验 我们希望你: - 不墨守陈规:敢于质疑权威,敢于引领而非跟随; - 有品味:对产品的美感有追求 - 有强烈的好奇心和学习能力 硬性要求 - 年龄:28-38岁 - 学历:统招本科及以上有学位可认证 薪资与福利: - 正规公司,不压护照 - 生活补贴(3000JPY/D) + 住宿补贴(100000/M) - 无限量提供AI To…
File, posted without a caption
❗️❗️日本--越南--斯里兰卡-柬埔寨-马来西亚--菲律宾--亚美尼亚--迪拜—知名集团月休6-8天 (周末双休),总有一个合适你的 ❤️⭕️远程职位:推广专员、推广专员、招商专员、SEO专员、电销专员、UI设计师 ❤️⭕️格鲁吉亚:外籍值班、财务经理 ❤️🇦🇲亚美尼亚:golang、 ❤️⭕️新加坡:数值策划、cocos、 ❤️🇯🇵日本:财务专员、客服专员、golang、前端开发、Golang(web3)、运营专员、产品调研专员、数据分析师、网络链路与分发安全运维工程师、财务专员、cocos creator、java后端、前端、资深UI设计师、 ❤️🇭🇰香港:运营总监、高级秘书(香港/台湾护照)、海外增长经理 、投后管理总监 、发⾏总监 (海外⽅向) ❤️🇻🇳越南职位:总监助理 、投放专员 、用户运营、 ❤️🇱🇰斯里兰卡:市场经理、财务专员、运营助理、直播运营组长/主管、代理主管(招商资源+管理团队)、代理招…
❤1
upay财务专员 - 日本 国籍:马来、台湾 地点:大阪 薪资:1600u 转 1800~2200u区间 工作时间:周休一、10:00-19:00 1. 需要会计毕业生(大专或本科) 2. 可以接受无经验、部门可以带(Fresh Graduate) 3. 入职费用转正后报销 4. 转正满半年有14天年假、放弃年假有一个月底薪 5. 提供宿舍 6. 宿舍离办公室10分钟步行 7. 宿舍2人一间 8. 餐补 4万日元 额外条件:需要财务相关专业毕业 & 博彩小白
❗️❗️最新招聘的职位可以点击频道置顶查看
Showing the 12 most recent of 27 posts we hold for @shuangxiugognzuo. 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
@shuangxiugognzuo edited 5 posts 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
- 10 August 2026
- Most recent edit
- 20 August 2026
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.
@bnzhaopingmnl · 142,493
Telegram ranks this channel #3 of 84 here — alongside 83 others — read 15 August 2026
@XCRLZP · 108,649
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 13 August 2026
@remote_cn · 25,016
Telegram ranks this channel #22 of 85 here — alongside 84 others — read 15 September 2026
@abetterpathxyz · 33,176
Telegram ranks this channel #28 of 90 here — alongside 89 others — read 4 September 2026
@DeJob_official · 46,726
Telegram ranks this channel #37 of 94 here — alongside 93 others — read 27 August 2026
@zii33 · 105,071
Telegram ranks this channel #52 of 78 here — alongside 77 others — read 16 August 2026
@qzzpfabu888 · 636,574
Telegram ranks this channel #63 of 72 here — alongside 71 others — read 9 August 2026
@XMZPK · 92,960
Telegram ranks this channel #67 of 76 here — alongside 75 others — read 16 August 2026
This channel appears in 8 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 September 2026 — this entry's latest reading, not the date you are reading this.
“多个国家月休8天工作交流(每周更新)” (@shuangxiugognzuo), 6,687 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/shuangxiugognzuo.
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.