高级运营(数据分析+活动策划) 仅要中国籍或马来籍 不超过35岁 📍 工作地点:越南胡志明 📍 上班时间:12小时休4 📍 试用期间:3个月 📍 薪资范围:面议 一 岗位职责: 1.用户分层与精细化数据运营:负责构建CRM基础体系及用户RFM分层模型,基于用户行为数据建立精准标签体系,实现差异化精准触达,提升单用户价值(ARPU)及留存率 。 2.活动策划与流失用户召回:定期策划并执行高转化的用户激励活动(如充值激励、排名赛等) ;针对流失与沉睡用户制定分层召回机制,有效提升用户复活率与留存表 。 3.数据监控与策略迭代:负责日常运营核心指标的监控与看板建设,能熟练运用SQL/Python等工具进行用户行为数据分析,通过数据复盘持续优化运营路径 。 二 任职要求: 1.学历经验:大专及以上学历 ,具备3年以上海外菠菜运营经验,有扎实的用户增长及数据分析复合背景者优先 。 2.技术加分项:掌握基础的SQL、Pyth…

Channel
海外岗位招聘-现场/远程
@globaljob814
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
435subscribers
+3 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 | -1002223953323 |
|---|---|
| Type | Channel |
| Username | @globaljob814 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/globaljob814 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:58 | 435 | +3 |
| 8 Aug 2026, 05:17 | 432 | no change |
| 7 Aug 2026, 19:38 | 432 | first reading |
Engagement
20 posts held, back to 15 October 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 76.8%
- avg views ÷ 435 subscribers
- Avg views / post
- 334
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 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 22 July 2026 |
|---|---|
| Posts held | 20 (15 October 2025 – 22 July 2026) |
| Views total | 334 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:17 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
7 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 85.7% | |
| 👍 | 1 | 14.3% |
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 7 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 7reactions 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 15 October 2025 to 22 July 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
🔥迪拜 #待招岗位 Vue/H5游戏前端开发 #上班时间 8小时 #薪资范围 35,000-45,000RMB #岗位职责 -负责公司棋牌游戏 Web 前端开发,提供高效、稳定的前端开发工作。 -基于 Vue、HTML5、JavaScript / TypeScript 进行前端页面开发,实现游戏界面、交互逻辑、动画效果和业务流程开发。 -负责棋牌游戏、视频游戏等核心玩法的前端开发,包括牌桌界面、座位管理、下注操作、筹码动画、发牌动画、结算展示、倒计时、聊天互动等。 -负责与游戏服务端进行 WebSocket / HTTP 通信对接,实现实时消息推送、状态同步、断线重连、异常恢复等功能。 -负责 H5 游戏在 PC、移动端、不同浏览器和不同分辨率下的适配与性能优化。 参与游戏前端架构设计,优化项目结构、组件封装、资源加载机制和动画渲染性能。 -配合 UI、产品、后端、测试团队完成需求开发、联调测试、上线发布和版本迭代。 -负责前…
❤1
🔥迪拜-资深运维 基础薪资:30k-55k(13薪) 个人季度奖金:基础薪资30~60% 公司季度奖金:根据公司增长目标,享受对应岗位奖金 其他要求: 中国籍男性,年龄35岁以下优先无BC行业相关经历,不接受有缅甸和柬埔寨高风险地区经历的人选,必须接受到现场,公司根据实际情况决定 人选若有BC经验(不接受有柬埔寨和缅甸经历),年龄35以下,简历背景清晰靠谱的人选也可以。 按照公司精英化战略,本岗位为一线岗位,需全心投入项目,没有那么多分心的事 岗位职责 运维体系搭建:负责公司项目运维侧落地,负责公司项目的运维体系、安全体系和管理规范的搭建和一线实施; 技术难题解决:负责解决运维侧中存在的难点并进行有效优化,保障系统性能、可用性与稳定性,降低运维成本; 运维风险管理:负责把握数据、服务器、网络等各层面风险,制定风险管理策略,建立事故处理和应急机制; 项目管理和协调:参与项目的规划和管理,配合各技术团队和运营的工作,为其他…
👍1
🔥远程:安卓逆向工程师 要求无BC经验 🤩TG:@niki0828
亚美尼亚需要一名Golang(支付经验),单休,不压护照。 🤩TG:@niki0828
#迪拜🇦🇪 高级 测试 ‼️🚨 技术客服 高级产品经理 安卓逆向 #亚美尼亚🇦🇲 高级 点net (着急) ‼️🚨 高级 UI (着急) ‼️🚨 高级 DBA‼️🚨 技术客服‼️🚨 高级 前端 高级 测试 🤩TG:@niki0828
🔥曼谷居家远程 🤩Java架构师 🤩Java研发主管 🤩前端主管 🤩测试主管 🔥远程岗位 🤩高级游戏UI设计师 🤩高级游戏2D动画师 🤩高级游戏特效师 🤩游戏原画师 曼谷居家到岗 🤩Web前端架构师 🤩Java主管 🤩Java架构师 🤩TG:@niki0828
❤1
高级测试工程师 薪资:25-30+绩效 工作时间:10小时,月休8天 办公:马来西亚—办公室办公(不接受远程,勿问) 餐补:12600P 房补:22000P (不属于原属国办公补贴正常) 岗位职责: 1、1参与互联网客户端产品测试全流程,包括需求分析、设计评审、测试方案制定、测试用例设计与执行、缺陷跟踪及质量分析; 2、负责客户端(iOS / Android / Web / H5)功能测试、兼容性测试、稳定性测试,保障版本质量; 3、独立承担项目测试工作,推动测试进度,协同产品、研发定位并推动问题闭环; 4、参与接口联调测试,分析客户端与服务端交互问题; 5、执行客户端相关的性能、弱网、异常场景测试,评估潜在风险; 6、持续优化客户端测试方法和测试规范,提升整体测试效率和质量。 任职要求: 1、3 年及以上软件测试经验,有互联网客户端测试经验者优先; 2、熟悉客户端测试流程,精通功能测试、兼容性测试、异常场景测试及测试用例…
❤2
吉隆坡居家-双休-UI设计师 🔛TG:@niki0828 ✅更多职缺:@globaljob814
吉隆坡补一位DBA
亚美尼亚 埃里温 9休4 1.UI/UX 2.产品经理 3.Flutter 4.测试工程师 5.React 前端开发工程师— Next.js方向 🔛TG:@niki0828 ✅更多职缺:@globaljob814
开放几个远程岗位: 高级Java Java架构师 后台产品经理 棋牌数值策划 🔛TG:@niki0828 ✅更多职缺:@globaljob814
Showing the 12 most recent of 20 posts we hold for @globaljob814. 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.
Citation-graph rank
Citation-graph rank — 1,274,544 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“海外岗位招聘-现场/远程” (@globaljob814), 435 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/globaljob814.
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.