Telegram RegisterThe public register of Telegram
Telegram profile photo for 集团直招

Channel

集团直招

@zhizhao8888666

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

10subscribers

-1 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-1003595353839
TypeChannel
Username@zhizhao8888666
CreatedBetween 1 December 2025 and 9 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live10 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 10 October 2026
On Telegramt.me/zhizhao8888666

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 2 October 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 why it has no browse page of its own yet.

Growth

101110.57 August 2026 — 11 subscribers12 August 2026 — 11 subscribers1 October 2026 — 10 subscribers7 August 20261 October 2026
3 measurements spanning 55 days, net -1. 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 10–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 11:0110-1
12 Aug 2026, 07:3011no change
7 Aug 2026, 18:1511first reading

Engagement

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

What this channel posts

Video runtime
30s
Average length
30s

Measured directly from 1 video 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.

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 9 April 2026 to 23 April 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

23 Apr 2026, 08:19 UTC251 viewsread 12 August 2026

岗位:财务专员 办公场地:柬 工作要求: 1、熟练使用财务软件、Excel 函数(VLOOKUP、数据透视表)、Office 办公软件。 2、耐心稳重,抗压能力强,能应当日当月的账目核对。 3、需要对平台账目内部账目核对流程熟悉有经验的 4、工作严谨细心,责任心强,保密意识高 工作职责: 核对每日每月的各部门往来账目。

23 Apr 2026, 08:19 UTC246 views1 reactionsread 12 August 2026

岗位:财务主管 办公场地:柬 工作要求: 1、完成平台账务处理、往来对账、月末结转、出具财务报表 2、熟练使用财务软件、Excel 函数(VLOOKUP、数据透视表)、Office 办公软件 3、定期做财务分析:经营数据、费用占比、盈亏分析 4、工作严谨细心,责任心强,保密意识高,沟通协调能力良好。 5、沟通协调能力好,执行力强,做事有条理 6、有多年bc数据报表管理经验。 工作职责: 整理核对每日的账目报表、内部账目梳理、统筹部门日常工作。

❤1

14 Apr 2026, 06:20 UTC218 viewsread 12 August 2026
Video

🏆 集团直招🏆所有岗位不限制任何人生自由!全透明~ 抓住2026世界杯让旅行的梦想回归~我在西港等你~ 🏝工作地点: 柬埔寨🇰🇭 西港 可以选择想做的岗位 |简历投放👍@mingyue000222 |更多岗位明细👍查看频道 ❤️‍🔥【职能岗】❤️‍🔥 |数据分析专员 | 红利专员 |运营专员 |客服主管 |客服专员 | 部门助理 |财务专员 |业务部助理 |HRBP组长 |培训专员 |薪酬组长 |审计组长 |审计专员 |风控专员 |风控助理 |总经办助理 |培训师 ❤️‍🔥【金流部】❤️‍🔥 |运营推广专员 |运营推广经理 |出入款 |BC游戏电子客服 |BC电子游戏运营 |财务专员 |缅籍客服 ❤️‍🔥【 IT岗位】❤️‍🔥 |中文网管专员 |中级网络工程师 |高级网络工程师 ❤️‍🔥【 …

14 Apr 2026, 05:42 UTC159 viewsread 12 August 2026

岗位名称:设计专家 入职地:吉隆坡 (能力好,前期可远程) 薪资待遇:面议 岗位职责 1.负责公司整体设计体系建设,统筹 UI、UX、视觉、品牌等设计方向,确保设计输出质量与风格统一。 2.深度参与公司核心产品与重点项目,从业务目标、用户体验、视觉表达等维度提供系统性设计方案。 3.搭建设计规范、组件体系、设计流程与协作机制,提升设计团队整体交付效率与标准化水平。 4.管理并带领设计团队,完成任务分配、过程把控、质量审核、人才培养与梯队建设。 5.与产品、研发、运营、市场等团队紧密协作,推动设计方案高质量落地,并对最终呈现效果负责。 6.关注行业趋势、竞品动态及用户体验变化,持续推动设计创新与设计能力升级。 7.参与公司品牌升级、重大活动、营销专题、核心页面改版等重点项目的设计策略制定与把控。 8.建立并优化设计评审机制,对关键项目进行设计把关,确保商业目标与用户体验平衡。 9.对团队产出结果负责,包括视觉品…

9 Apr 2026, 10:52 UTC146 viewsread 12 August 2026

❤️‍🔥产品体验师 / 高级产品体验专家(可远程) 岗位职责: 1.负责对公司多个产品进行系统性体验评估,输出体验报告,包括优势分析、问题清单、优化逻辑、改进方案及竞品交互参考。 2.从需求阶段提前介入产品设计,对PRD中的交互流程、页面逻辑、操作路径、异常场景等提出优化建议,降低开发返工与后期调整成本。 3.结合现有产品问题与行业优秀案例,建立并持续完善公司产品交互规范、体验标准及评审机制,并推动各团队落地执行。 4.深度研究字节、腾讯及其他头部互联网产品的交互设计思路、用户适配逻辑和体验亮点,沉淀为可复用的方法论、规范文档和通用方案,赋能各研发团队。 5.跟进体验优化需求从提出到落地的全过程,推动产品、设计、研发、测试、运营协同执行,对延期、偏差和落地质量进行跟踪、复盘和总结。 6.监督测试团队对交互体验相关问题的验证结果及修复落实情况,确保优化项真正闭环。 7.参与部门内产品、交互、测试、运营等相关专项调研任…

9 Apr 2026, 10:50 UTC117 viewsread 12 August 2026
Photo

❤️‍🔥业务部 岗位:推广培训师 需求:1人 薪资待遇:1.5W转1.8W+kpi 12休2 要求:懂体育,熟练规则,一定要懂业绩和转化!!!

9 Apr 2026, 10:46 UTC117 viewsread 12 August 2026
Photo

🌸业务部 岗位:引流渠道专员 需求:数名 国籍:中国籍 薪资:3个月试用期1万,转正1.2,3个月有业绩了可以谈点位 岗位职责要求: 1.有自己的渠道或者有独立的开发经验的薪资可谈 2.不限制年龄 3.证件齐全,有综合盘经验优先, 有自己的渠道或者有独立的开发经验的薪资可谈 4.不要赔付的 只要证件齐全的 5.要会打字,懂体育。熟悉做过体育盘的优先!

9 Apr 2026, 03:26 UTC97 viewsread 12 August 2026

🌸金流部 岗位:财务专员 需求:2人 国籍:国籍不限 中国籍 (福建,山东和河南除外) 薪资待遇:2000U+KPI(0-3000) 工作时间10休2 •有过财务管理或会计工作经验 •精通Excel、PPT等办公工具,具备数据处理与报表制作能力 大专及以上学历

9 Apr 2026, 03:16 UTC89 viewsread 12 August 2026
Photo

🌸人资部 岗位:薪酬组长 需求:1人 国籍:中国籍优先,其他国籍要求中文流利;(不要缅籍、越南籍、斯坦籍和非洲籍) 薪资:18-20k转正后有kpi ;9休4 岗位职责 1-统筹部门薪酬核算工作,确保薪资发放准确及时。 2-优化薪酬体系,开展市场薪酬调研,制定合理绩效\调薪方案。 3-管理薪酬数据,完成薪酬报表编制与分析。 4-针对行业特性,对目前薪酬政策及实施作出不定期调整,优化各项薪酬制度。 4-解答员工薪酬疑问,配合完成薪酬审计。 任职要求: 1-本科及以上学历,人力资源、财务等相关专业。 2-2年以上薪酬工作经验,1年团队管理经验。 3-一定的公文写作水平,快速行文和成表的能力;对数字敏感 员工福利:年、节日礼金、生日礼金、半年假 (仅限职能岗)

9 Apr 2026, 03:14 UTC82 views0 reactionsread 12 August 2026

❤️‍🔥人资部 岗位:培训专员 需求:1人 国籍:中国籍优先,其他国籍要求中文流利;(不要缅籍、越南籍、斯坦籍和非洲籍) 薪资:12k-15k;转正后有kpi;9休4 岗位职责 1-制定培训计划,组织实施员工培训; 2-培训课件制作,管理培训资源; 3-评估培训效果,优化培训体系。 任职要求 1-本科及以上学历; 2-1年以上行业内培训工作经验; 3-具备良好的沟通组织能力,熟悉培训流程。 员工福利:年、节日礼金、生日礼金、半年假 (仅限职能岗)。

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 registered channels — 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 1 October 2026 — this entry's latest reading, not the date you are reading this.

“集团直招” (@zhizhao8888666), 10 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/zhizhao8888666.

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.