Telegram RegisterThe public register of Telegram
Telegram profile photo for 核心-招聘渠道

Channel

核心-招聘渠道

@job_999999

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

125subscribers

-6 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003796576748
TypeChannel
Username@job_999999
CreatedBetween 1 February 2026 and 11 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/job_999999

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

1251311288 August 2026 — 131 subscribers9 August 2026 — 131 subscribers9 August 2026 — 130 subscribers16 August 2026 — 129 subscribers30 August 2026 — 127 subscribers7 September 2026 — 126 subscribers14 September 2026 — 125 subscribers8 August 202614 September 2026
7 measurements spanning 37 days, net -6. 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 124–132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 17:59125-1
7 Sept 2026, 04:20126-1
30 Aug 2026, 05:57127-2
16 Aug 2026, 17:18129-1
9 Aug 2026, 02:11130-1
9 Aug 2026, 01:00131no change
8 Aug 2026, 06:31131first reading

Engagement

20 posts held, back to 11 March 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 10 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

10 reactions across 6 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10100.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 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 10 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 11 March 2026 to 10 June 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

10 Jun 2026, 07:22 UTC508 views2 reactionsread 9 August 2026

SEO专员 胡志明居家 2K – 15K(后续看能力调涨)+提成 提成: 日均2wip=150rmb/wip 日均5wip=250rmb/wip 日均10wip=350rmb/wip 日均2wip以下只有底薪 ,没有提成 算法如下:当月60万ip/当月实际天数(30天)/两万日均ip,达到发放标准一万ip奖金150RMB,以此类推 1.按照SEO策略要求执行关键词布局、内页优化、内容优化等日常SEO工作; 2.负责站内内容更新、伪原创文章处理、页面结构优化等基础优化任务; 3.协助进行外链建设,包括文章外链、资源平台外链、友情链接拓展等; 4.对网站数据进行监控与整理,如OP、UV、PV、关键词排名等,并输出简易分析报告; 5.收集并研究竞争对手网站的优化策略,提供优化建议; 6.配合内容部门、技术部门完成SEO相关需求的落地执行; 7.完成领导布置的其他SEO相关任务。 .硬性需求,有色流经验 2.对市场上大厂热门播…

❤2

21 May 2026, 04:22 UTC719 viewsread 9 August 2026

X站运营负责人 胡志明(居家办公) 试用期:25,000 RMB(两个月) 转正后:35,000 RMB + 项目分成 上班时间: 配合领导 负责X站整体运营规划与落地执行 2. 统筹团队管理(运营 / 技术 / 客服 / 推广等),搭建组织架构 3. 制定项目 KPI 与营收目标,把控核心数据(留存 / 转化 / ARPU 等) 4. 协调上游流量、支付通道及外部合作资源 5. 监控项目风险,处理重大事件并持续复盘优化 6. 向高层汇报项目进展,参与战略与商业决策 1. 3 年以上互联网项目 / 产品运营管理经验 2. 有成人项目 / 直播 / 社交 / 短视频 / 流量变现 等相关行业经验者优先 3. 具备团队管理与跨部门协作能力,能独立带团队从 0 到 1 4. 熟悉用户增长、付费转化、内容审核与合规风险控制 5. 对数据敏感,具备较强的分析与决策能力 6. 抗压能力强,责任心强,具备高度保密意识

21 May 2026, 04:20 UTC649 views0 reactionsread 9 August 2026

客户撮合钱包负责人 (需自带资源) 年龄:20-35 到岗(马来吉隆坡) 试用:28000RMB 正式:33000RMB 9休2(配合公司运营) 一、 职位目标 负责平台 P2P/C2C 交易的流动性管理、风险控制与用户生态增长,确保撮合效率与资金安全。 二、 核心职责 1. 撮合管理: 优化订单撮合机制,监控交易深度与成交效率。 2. 商家管理: 开发并维护优质商家(做市商),建立分层管理与激励制度。 3. 风控体系: 制定 AML(洗钱防制)与交易安全规则,处理订单纠纷与欺诈预警。 4. 数据运营: 分析交易数据,根据市场变化调整运营策略与手续费模型。 三、 加分项 • 自带商家或做市商资源。 • 熟悉海外市场支付环境或合规政策。 行业经验: 3 年以上交易所、P2P 平台或 FinTech 相关运营经验。 • 专业能力: 熟悉区块链钱包运作机制、资产撮合原理及风控逻辑。 • 核心素质: 具备极强的逻辑分析能力,能…

23 Apr 2026, 10:42 UTC752 viewsread 9 August 2026

推广专员 马来( 居家) 试用期:12000RMB ( 两个月) 转正后:每个月加500 RMB. 第一年 15000绩效 利润提成5% 1、投流模式,懂数据分析 2. 无需跟客户一对一开发维护 福利: 满勤奖:500RMB 生活补贴:100美金 /月(如遇中国法定节日会增加) 生日礼金:100美金 (转正后享有,试用期间生日转正后补)

7 Apr 2026, 14:37 UTC848 views1 reactionsread 9 August 2026

风控组长 试用13k转正16k 1.带领风控团队执行日常审核工作(如账户审核、异常行为识别等) 2.复核重点风控案例,确保处理结果准确合理 3.监控日常数据变化,识别异常行为及潜在风险 4.协助优化风控流程,提高团队执行效率 5.负责团队排班、工作分配及基础管理工作 2年以上风控或相关经验,有团队管理经验优先 熟悉基础风控逻辑及常见风险行为 具备一定数据分析能力与判断能力 执行力强,责任心高

❤1

7 Apr 2026, 14:37 UTC775 views1 reactionsread 9 August 2026

风控主管 试用20k转正23k 10休4 1.统筹风控团队日常工作,制定并优化执行流程 2.审核高风险案例(如异常资金、大额操作等) 3.监控核心数据指标,识别异常趋势并制定应对策略 4.管理团队绩效,提升整体执行力与稳定性 5.协调运营、技术等部门,完善风控体系 3年以上风控相关经验,有团队管理经验 熟悉各类风险行为及识别逻辑 具备较强数据分析能力与逻辑判断能力 具备团队管理与跨部门沟通能力

❤1

7 Apr 2026, 14:36 UTC735 viewsread 9 August 2026

风控总监 远程( 台湾 /马来) 面议 (10休4) 1.制定并优化整体风控策略及体系架构 2.监控平台整体风险水平,制定风险应对机制 3.统筹风控团队管理(组长/主管),建立高效组织架构 4.分析核心业务数据(如用户行为、资金流动等),识别系统性风险 5.主导重大风险事件处理及复盘,持续优化风控能力 6.与高层协作,参与业务决策与风险评估 5年以上风控或相关领域经验,具备团队管理经验 熟悉复杂风险模型及风控体系搭建 具备极强的数据分析能力与战略思维 具备优秀的管理能力与决策能力 抗压能力强,具备高度责任感与保密意识

6 Apr 2026, 11:01 UTC703 viewsread 9 August 2026

客服主管 (0-1搭建客服部门) 居家远程 台湾 试用期:20000RMB ( 两个月) 转正后:综合薪资范围 25000- 30000 RMB含绩效 10休4 轮班 1.负责客服团队的日常管理、工作安排与运营统筹; 2.监督客服服务质量,定期进行质检抽查与服务反馈优化; 3.处理客户投诉、重大问题升级,协调跨部门资源解决问题; 4.组织培训与考核,提升团队专业能力与服务意识; 5.分析客户需求与数据,定期优化客服话术与工作流程; 6.协助上级领导制定客服管理制度与绩效标准,推动团队绩效目标达成。 1.具备 1 年以上客服主管或团队管理经验(平台/盘口类优先) 2.熟悉 体育、真人、棋牌、彩票、电竞等综合盘口业务 为佳 3.擅长排班管理、数据分析、培训辅导与问题处理 4.熟练使用办公软件(Excel、Word、表格公式) 5.抗压能力强,能在快节奏下维稳团队士气与服务质量

6 Apr 2026, 05:40 UTC644 views0 reactionsread 9 August 2026

ZX1B 岗位:风控/运营 国籍:中国籍 上班地点:印度尼西亚 人数 : 不限 薪资待遇: 上班时间:12小时(两班倒)月休二 试用:13000R 转正:20000R-30000R(看能力) 试用期:2个月 "签证机票到岗报销" 岗位职责 有较强学习能力,能较快掌握财务风控基本的数据排查、异常资金审核、异常风控问题及时处理等工作 岗位要求 完成财务风控中心工作;处理异常风控问题,查询异常套利玩家;协助完成撤诉等工作。

28 Mar 2026, 12:26 UTC674 views1 reactionsread 9 August 2026

ZX2B 数据分析专员 *2 工作时间:9小时休4(需轮班) 早班:8:00-17:00 晚班:14:00-23:00 薪资:试用12000RMB转正14000Rmb(转正后绩效1000Rmb) 试用期:2个月 国籍:外籍(不要在中国境内) 性别:女性优先 任职要求: 1. 行业背景:具备 BC 行业相关数据分析经验者优先,熟悉行业核心指标(如留存、转化、损益等)。 2. 熟悉工具: • 精通 Excel(函数、透视表、VBA/Power Query 加分); • 熟悉 SQL 数据库操作,能够独立编写复杂查询语句; • 了解 Python(Pandas, NumPy)进行数据处理或自动化; • 能够使用至少一种主流 BI 工具(如 Tableau, PowerBI, FineBI 等)。 3. 综合素质:具备逻辑思维能力,对数字敏感,能够从海量数据中发现潜在规律。 岗位职责: 1. 数据监控与提取:负责日常业务数据的提…

❤1

27 Mar 2026, 05:37 UTC632 viewsread 9 August 2026

出款专员 - 直招 国籍:越南/缅甸 上班地点:除中国大陆以外地区 上班时间:9休2 (需轮班) 上班型态:远程居家 薪资待遇:试用期5000转正6000+全勤500+绩效1000 转正早班实拿7500 转正中班实拿8000 转正晚班实拿8500 岗位要求: 具备WG包网系统或波音直播出款相关工作经验者优先录用 工作细心、责任感强,具备基本风险意识 岗位职责: 负责平台用户出款审核及处理 按照流程进行资金操作,确保准确无误 监控异常出款情况,及时上报处理 配合风控及财务完成相关工作

27 Mar 2026, 05:20 UTC640 viewsread 9 August 2026

ZX2B 彩金专员 预计需求人数 : 5 办公地点 : 远程居家 国籍 : 外籍 上班时间 : 12小时 月休1 需倒班 薪资待遇 底薪8000,试用期三个月,15000封顶 第三个后开始递增,两个月递增500元, 试用期15天 岗位职责 - WG包网后台经验者优先 1.负责日常活动彩金的审核、发放及记录管理 2.核对用户参与活动资格,确保彩金发放符合规则要求 3.跟进彩金使用情况,处理相关异常问题 4.协助检查活动执行效果,反馈异常数据或问题 5.配合运营及风控部门,确保活动安全及合规进行 岗位要求 1.工作认真细致,责任心强,执行力高 2.具备基础数据核对能力,对数字敏感 3.熟悉电脑操作及办公软件(Excel 优先) 4.具备良好的沟通能力,能与相关部门协作 5.有相关经验或远程办公经验者优先 6.完成上级安排的其他相关工作

Showing the 12 most recent of 20 posts we hold for @job_999999. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“核心-招聘渠道” (@job_999999), 125 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/job_999999.

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.