Telegram RegisterThe public register of Telegram
Telegram profile photo for BDY/WFH 远程技术、职能、业绩 - 招聘简章发布

Channel

BDY/WFH 远程技术、职能、业绩 - 招聘简章发布

@dongnanya_jobs

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

514subscribers

+5 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-1002524847610
TypeChannel
Username@dongnanya_jobs
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/dongnanya_jobs

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

509516512.57 August 2026 — 509 subscribers8 August 2026 — 509 subscribers14 August 2026 — 514 subscribers22 August 2026 — 516 subscribers8 September 2026 — 515 subscribers16 September 2026 — 514 subscribers5147 August 202616 September 2026
6 measurements spanning 40 days, net +5. 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 508–517 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 10:21514-1
8 Sept 2026, 21:37515-1
22 Aug 2026, 11:35516+2
14 Aug 2026, 03:37514+5
8 Aug 2026, 04:15509no change
7 Aug 2026, 17:03509first reading

Engagement

20 posts held, back to 21 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 7 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 2 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 21 July 2026 to 7 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

7 Aug 2026, 09:21 UTC71 viewsread 8 August 2026

技术支持专员 技术客服专员 1、有计算机专业或客服工作经验者优先 2、做事踏实可靠,学习能力强,有较好的团队合作精神 3、打字速度快。 4、工作认真负责,能吃苦耐劳、有奉献精神 5、福利:底薪1000USDT,转正1200USDT,试用期:1-3个月(可根据能力提前考核转正) 人员入职即可享有: 全勤:50(满勤出席,无迟到/早退/请假)即可享有 餐补:195 绩效:0-240,转正后享有 月休6,无节假日 福利, 满1年可以享有休年假8天,每一年叠加1天年假,最高上限11天 ☎️联系孟德☎️ @jishu_jobs #Java #Golang #Python #React #Flutter #NodeJS #Android #iOS #PHP #AI #DevOps #UI设计

6 Aug 2026, 05:29 UTC103 viewsread 8 August 2026

新加坡 (35岁以下) Cocos Creator 前端开发工程师 薪资面议 卡学历 本科起(要看学校,不然也是进不去)学历院校填写真实的 Cocos Creator 前端开发工程师岗位职责 基于 Cocos Creator​ 引擎,负责 Slots(老虎机)类休闲游戏的客户端功能开发与维护,重点参与主题项目的迭代; 与策划、美术、后端紧密配合,完成游戏 UI 交互、动画特效、数值表现、资源管理等模块的设计与实现; 优化游戏性能,解决不同机型上的适配、内存、帧率等问题,确保流畅体验; 参与游戏 SDK 接入(支付、统计、广告等),处理原生平台兼容性问题; 编写清晰的技术文档,参与代码 Review,推动团队开发规范落地。 任职要求 本科及以上学历,计算机相关专业优先; 5年以上 Cocos Creator 实际项目经验,至少完整参与过一款上线手游(有 Slots/棋牌/休闲类游戏经验者优先); 精通 Ty…

6 Aug 2026, 05:27 UTC99 viewsread 8 August 2026

新加坡坐班 (35岁以下) 数值策划(Slots 游戏方向) 薪资面议 卡学历 本科起(要看学校,不然也是进不去)学历院校填写真实的 数值策划(Slots 游戏方向) 岗位职责 负责 Slots(老虎机)类游戏的数值体系设计与维护,主导主题项目的数值配置工作; 设计并优化转轮符号权重、赔付线结构、赔率表、免费游戏触发概率、Bonus 奖励分布等核心数值模型; 运用 跑库算法​ 进行大规模模拟运算,验证数值模型的长期预期回报率(RTP)、波动性、玩家留存曲线等指标; 熟练使用 纸带算法(物理纸带/虚拟纸带)配置转轮停靠逻辑,确保游戏结果符合合规要求且体验流畅; 针对 官方牌照类游戏(如菲律宾 PAGCOR、英国 UKGC、马耳他 MGA 等监管标准),设计满足合规要求的数值方案,撰写相关技术文档; 与程序、美术、测试紧密协作,跟进数值实装后的表现,根据运营数据持续调优数值平衡; 参与新玩法、新功能的数值原型设计,输…

5 Aug 2026, 13:45 UTC114 viewsread 8 August 2026

活动运营(海外市场) 薪资:20K-35K 上班时间:12小时月休4 中国籍/马来籍贯 不超过35岁 base胡志明 岗位职责 负责美区、拉美、东南亚及印度市场的线上活动运营,结合当地用户特征、文化习惯及节庆热点,制定区域化活动策略。 独立策划并落地大型线上活动,包括方案设计、资源协调、上线执行、风险控制及效果复盘。 参与营收功能和付费玩法的设计与优化,如会员、订阅、虚拟道具、充值激励及用户付费成长体系等。 基于用户行为、付费数据及活动数据,搭建分析模型,持续优化活动机制、奖励结构和商业化效率。 制定活动核心指标并进行效果监控,推动用户活跃、留存、付费转化、ARPU及营收增长。 协同产品、研发、设计、市场及本地化团队,保障项目按期、高质量交付。 持续跟踪海外市场趋势、竞品动态及优秀案例,沉淀可规模化复用的活动运营方法论。 任职要求 本科及以上学历,3年以上互联网活动运营、用户运营或商业化运营经验。 对美区、拉美、东南亚及印度市…

5 Aug 2026, 10:34 UTC124 views1 reactionsread 8 August 2026

CRM 运营 亚美尼亚入职 薪资范围:3500u-4000u 工作职责: 1.⁠ ⁠生命周期自动化运营 负责用户全生命周期 CRM 自动化旅程的设计、搭建及持续优化,包括注册、首充、复充、留存、召回、VIP 等场景。 配置并维护 Email、Push、SMS、站内信等自动化触达流程。 2.⁠ ⁠CRM 策略支持与需求评估 与运营团队协作,评估 CRM 需求及营销方案的合理性。 基于用户行为数据、历史表现及业务目标,对活动目标、人群、触发条件、触达时机及长期运营策略提出建议。 推动 CRM 决策数据化,避免缺乏数据支撑的运营策略。 3.⁠ ⁠用户体验与运营治理 建立并持续优化 CRM 运营规范,包括频率控制、生命周期互斥、活动冲突管理及用户体验优化。 确保各生命周期及营销活动协同运行,避免重复触达和过度营销。 4.⁠ ⁠数据分析与持续优化 持续监控 CRM 核心指标,分析活动效果,并提出优化建议。 跟踪…

❤1

31 Jul 2026, 05:49 UTC226 viewsread 8 August 2026

高级产品经理(包网) 📌地点:马来西亚-吉隆坡居家办公 地点:马来8小时单休 岗位职责: 1.包网产品规划与设计 负责包网类产品的整体规划、功能设计与版本迭代 根据业务目标制定产品方案及产品路线图 2.需求分析与产品落地 深入理解业务需求与使用场景 独立输出高质量 PRD、原型图、流程图 等产品文档 3.项目推进与跨部门协作 协调技术、测试、运营等团队,推动产品按计划落地 跟进研发进度,确保需求准确实现 4.产品体验与持续优化 基于数据和实际使用反馈,持续优化产品功能与流程 对核心功能和整体产品体验负责 5.产品结果与复盘 跟踪产品上线后的效果与核心指标 进行产品复盘,持续提升产品质量与业务价值 二、 任职要求 1.基本条件(硬性要求) 统招本科及以上学历,35岁以内,3 年及以上互联网产品经理工作经验,必须具备包网相关产品经验,面试时需携带本人主导的产品作品。 2.专业能力要求 熟悉互联网产品从需求分析 → 设…

31 Jul 2026, 05:48 UTC198 viewsread 8 August 2026

运维值班工程师 📌地点:马来西亚-吉隆坡居家办公 岗位职责: 告警监控与响应 •实时监控系统、服务及业务告警,发现异常后第一时间响应。 •根据告警类型和影响范围,判断处理紧急程度。 •执行标准化操作流程,对可处理的基础问题进行处理;复杂问题及时通知运维专员。 •完整记录告警处理过程,确保问题可追溯。 合作方反馈处理 •及时接收合作方反馈的问题和异常请求,快速确认问题范围和影响。 •使用规范话术、保持专业耐心,向合作方说明处理步骤、预计处理时间及进度。 •协调内部运维团队进行问题处理配置域名、防封线路等,确保问题快速闭环。 •对问题处理结果进行跟踪确认,确保合作方满意度。 基础运维操作 •执行基础运维任务,如服务重启、日志检查、状态确认、数据核对等。 •按照标准操作手册进行操作,确保风险可控。 •协助运维专员进行突发问题的初步排查和数据收集。 系统与业务模块支持 •支付系统:监控支付交易状态,及时处理异常或通知运维专员。 •游…

31 Jul 2026, 05:39 UTC169 viewsread 8 August 2026

📌地点:马来西亚-吉隆坡居家办公 🔆 🔴🔴 Java - 资深大数据开发工程师 ✨ 性别: 男 ✨ 年龄 : 35周岁内 ✨ 薪资 : 35-50k RMB ⏰上班时间 : 9小时, 月休4天 📌办公地点:马来西亚-吉隆坡 📋 岗位职责(工作内容): 1、数仓架构与模型设计:负责海量数据环境下的数据仓库(D层次/DWD/DWS/ADS)架构设计、建模及核心研发,确保数仓的稳定性和高扩展性。 2、高性能 ETL 研发:负责百亿级核心业务数据的 ETL 流程设计与数据清洗,编写高效的实时(Flink/Spark Streaming)与离线(Spark/Hive)数据处理任务。 3、大容量存储与计算维护:负责 Doris、ClickHouse、TiDB 等 NewSQL/OLAP 数据库的开发与建设,支撑高并发、低延迟的业务多维分析需求。 4、SQL 性能调优(实战):针对复杂的分布式 SQL、多表关联及复杂聚合查询进行极致的…

31 Jul 2026, 05:39 UTC161 viewsread 8 August 2026

📌地点:马来西亚-吉隆坡居家办公 🔆 🔴🔴 高级UI设计师 ✨ 性别: 男 ✨ 年龄 : 35周岁内 ⏰上班时间 : 9小时, 月休4天 岗位职责: 1、主要负责包网平台的UI/UX设计和创意工作;包括APP、官网、后台等多终端应用。 2、负责公司产品的整体模块UI、视觉设计工作,对产品的整体美术风格、基础动效设计、界面结构、操作流程等做出视觉设计; 3、参与优化制定产品UI界面设计稿色值、文字规格、组件规格及间距等界面规格定义,使整个产品设计保持风格统一,提高团队的协作效率与产出质量; 4、Ul设计方案实现还原度把控与项目组成员沟通,推进界面及交互设计的最终实现,确保产品实现效果一致及交互可行性; 5、规划指导团队产品体验优化,灵活提供设计解决案,做好对应的设计沉淀,协同项目不断地提升产品的视觉与体验; 6、输出成熟的设计方法论,开展对应的经验分享和讨论,提高团队的专业能力。 任职要求: 1、5年以上UI相关经验,设计相…

30 Jul 2026, 11:34 UTC159 viewsread 8 August 2026

印度客服 需要会:中文+英文 薪资:800U(次月递增50U*4,封顶1000U) 岗位职责 一、用户咨询与服务: 1.通过在线聊天、电话、社交媒体等渠道,解答玩家关于彩金、优惠、账户等方面的咨询。 2.帮助用户理解彩金规则、领取条件与使用方式。 3.提供友好、准确的服务,提升用户体验。 二、问题处理与跟进 1.记录用户反馈和问题,及时处理彩金异常、优惠纠纷等情况。 2.对复杂问题进行调查,并在必要时升级至上级或其他部门。 三、账户与流程支持 1.协助用户办理账户相关事务,如登录异常、充值/提款问题、彩金发放状态等。 2.保持对平台各类优惠活动、彩金政策的熟悉,以便提供准确解答。 四、推广与活动支持 1.向用户介绍当前有效的优惠活动和彩金福利,适当引导用户参与。 2.协助用户完成活动参与流程。 五、服务质量与记录维护 1.将用户沟通内容、处理结果等录入客服系统或数据库,确保数据完整。 2.跟踪用户满意度、收集优化建议,提…

28 Jul 2026, 12:53 UTC151 viewsread 8 August 2026
Forwarded from @vieclamphilippinesnhansu01Photo

CRM 高级运营 薪资范围:3500u-4000U 地点:亚美尼亚 工作职责: 1.⁠ ⁠生命周期自动化运营 负责用户全生命周期 CRM 自动化旅程的设计、搭建及持续优化,包括注册、首充、复充、留存、召回、VIP 等场景。 配置并维护 Email、Push、SMS、站内信等自动化触达流程。 2.⁠ ⁠CRM 策略支持与需求评估 与运营团队协作,评估 CRM 需求及营销方案的合理性。 基于用户行为数据、历史表现及业务目标,对活动目标、人群、触发条件、触达时机及长期运营策略提出建议。 推动 CRM 决策数据化,避免缺乏数据支撑的运营策略。 3.⁠ ⁠用户体验与运营治理 建立并持续优化 CRM 运营规范,包括频率控制、生命周期互斥、活动冲突管理及用户体验优化。 确保各生命周期及营销活动协同运行,避免重复触达和过度营销。 4.⁠ ⁠数据分析与持续优化 持续监控 CRM 核心指标,分析活动效果,并提出优化建议。 跟踪 A/B Test …

28 Jul 2026, 05:04 UTC136 views0 reactionsread 8 August 2026
Forwarded from @vieclamphilippinesnhansu01Photo

【游戏后端开发工程师】(老HU机 / 休闲游戏) 【高级数学工程师】 地点:新加坡 ☎️联系孟德☎️ @jishu_jobs #Java #Golang #Python #React #Flutter #NodeJS #Android #iOS #PHP #AI #DevOps #UI设计

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“BDY/WFH 远程技术、职能、业绩 - 招聘简章发布” (@dongnanya_jobs), 514 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/dongnanya_jobs.

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.