Channel
@TPzhaopin
On this record: Growth · Engagement · Posts · Citations · Cite this entry
64subscribers
+4 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002038817803 |
|---|---|
| Type | Channel |
| Username | @TPzhaopin |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/TPzhaopin |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 13:04 | 64 | +4 |
| 14 Aug 2026, 07:16 | 60 | first reading |
20 posts held, back to 5 August 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 pageof Telegram’s post history, 20 posts per page.
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 13 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 13 August 2026) |
| Views total | 762 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 07:16 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.
⭐️ 拓英猎头 · 在招岗位总目录 ⭐️ 致力成为国际人力资源服务领域的领航者 🏠拓英人力资源股份有限公司 Topin Recruitment 🌐官网 topinhongkong.com 💎当前在招 226 个岗位 · 16 家企业 · 14 个国家和地区 💵覆盖行业 资讯科技 / 金融服务 / 游戏娱乐 / 公关媒体 / 专业行销 / 房地产 / 软件开发 想怎么找？选一个 👇 📱金牌HR：@JSDom 🇪🇸直招岗位：@KMzhaopin 🗓猎头岗位：@TPzhaopin
⭐️ 应用系统产品经理 ⭐️ 🏠公司：BD 📍工作地点：远程 💵薪资/待遇：面议 🌐国籍要求：不限 💎岗位职责 1. 负责公司产品的需求调研、需求分析、产品规划、方案设计及持续迭代，能够独立完成从需求提出到产品上线的完整产品流程。 2. 负责后台管理平台、业务应用平台等B端产品的功能规划和产品设计，能够结合不同角色、权限及使用场景，设计合理的业务流程和操作方案。 3. 重点参与自动化测试平台的产品化建设，结合测试团队实际工作流程，对现有平台能力进行梳理、规划和持续优化。 4. 参与埋点系统的产品规划和建设，结合业务及使用场景，对埋点管理流程、功能体系和平台能力进行梳理，推动埋点系统逐步实现规范化、平台化和可视化。 5. 能够深入理解测试、研发及业务团队的实际使用场景，将研发及测试过程中存在的效率问题转化为平台化、产品化解决方案。 6. 负责产品需求文档、业务流程、产品原型、功能说明及验收标准的编写，并组织需求评审，确保产品需…
⭐️ 风控产品经理 ⭐️ 🏠公司：BD 📍工作地点：远程 💵薪资/待遇：面议 🌐国籍要求：台湾 💎岗位职责 1. 负责交易风控系统平台产品的设计规划，明确产品定位、业务边界、功能架构、版本路线与阶段目标。 2. 梳理业务流程与风险场景，将需求抽象为标准化产品能力，建立数据、指标、策略、决策、处置和复盘管理闭环。 3. 建设风险敞口、交易对手、会员/商户、潜在赔付、风险集中度、风险量化、损益分析、绩效归因、情境分析等风险计量能力及应用体系。 4. 设计实时及日终风险看板，支持平台、商户、事件、会员和订单多维分析、逐层下钻及异常预警能力建设。 5. 建设会员风险画像、标签、分层和名单管理，识别异常盈利、价格优势、套利对冲、自动化、团伙及关联账户行为风险。 6. 建设商户风险画像、评级及驾驶舱，从损益、会员结构、异常集中度和策略命中等维度实施分层管理与持续监控。 7. 负责规则引擎、模型接入、策略编排和决策流程设计，支持回测、灰度…
⭐️ 大数据开发工程师 ⭐️ 🏠公司：BD 📍工作地点：远程 💵薪资/待遇：面议 🌐国籍要求：不限 💎岗位职责 1. 负责公司大数据平台相关需求的开发与维护，包括实时数据处理、离线数据处理、数据同步、数据清洗及数据加工等工作。 2. 负责基于Flink / Flink SQL的实时数据任务开发，根据业务需求完成数据采集、转换、聚合、关联及实时指标计算。 3. 参与Flink集群及实时任务的日常维护，包括任务发布、监控、异常排查、性能优化Checkpoint/Savepoint管理、资源使用分析等。 4. 负责Doris相关数据模型设计、表结构设计、数据导入及查询开发，并参与Doris集群的日常维护、性能分析和问题排查。 5. 参与Kafka、RocketMQ等消息中间件的数据链路建设，处理实时数据消费、数据积压、延迟及异常数据等问题。 6. 参与大数据平台的数据链路建设和优化，包括数据接入、数据同步、实时计算、数据存储及数据…
⭐️ 数据分析师 ⭐️ 🏠公司：BD 📍工作地点：远程 💵薪资/待遇：面议 🌐国籍要求：不限 💎岗位职责 1. 基于用户、账户、设备、订单、交易、资金、渠道及操作行为等数据，识别异常特征、风险模式及潜在关联关系。 2. 负责现有风险规则、策略及模型的效果分析，建立命中量、命中率、风险确认率、准确率、召回率、误判率、漏判率、覆盖率及拦截效果等评价指标。 3. 对策略命中样本进行回溯分析和结果核验，判断策略是否准确有效，识别误判、漏判、重复命中及规则失效等问题。 4. 根据数据分析结果，完成风险指标设计、规则逻辑优化、参数及阈值调整、策略组合优化和适用范围调整。 5. 负责策略上线前的历史数据回测、样本分析、阈值验证、效果模拟及风险评估，并跟踪策略上线后的实际表现。 6. 承担策略日常运营工作，包括策略监控、异常排查、效果复盘、版本管理、灰度发布、策略回滚、停用及持续迭代。 7. 针对异常交易、批量操作、多账户关联、自动化行为、…
⭐️ 高级 go 开发工程师 ⭐️ 🏠公司：RDL 📍工作地点：第三国远程 💵薪资/待遇：试用期薪资34k以上 转正后薪资40k以上 🌐国籍要求：不限 💎岗位职责 1. 参与公司支付、IM、三方对接相关系统的开发和维护，负责核心业务模块的设计与实现。 2. 负责支付订单、回调通知、退款、对账、消息投递、三方接口接入等模块开发。 3. 参与系统性能优化和稳定性建设，包括慢 SQL 优化、缓存优化、接口 RT 优化、MQ 积压治理等。 4. 参与微服务治理，包括限流、熔断、降级、链路追踪、监控告警、异常重试和补偿机制建设。 5. 与产品、测试、运维等团队协作，保障项目交付质量和线上系统稳定性。 6. 参与代码 Review、技术方案评审和工程规范落地，提升团队研发效率和代码质量。 💎任职要求 1. 9小时/ 周休一 2. 专科及以上学历，计算机相关专业，至少 5 年以上后端开发经验，3 年以上 Go 开发经验。 3. 熟悉 G…
⭐️ 拓英猎头 · 在招岗位总目录 ⭐️ 🏠拓英人力资源股份有限公司 Topin Recruitment 致力成为国际人力资源服务领域的领航者 🌐官网 topinhongkong.com 💎当前在招 221 个岗位 16 家企业 14 个国家和地区 💵覆盖行业 资讯科技 金融服务 游戏娱乐 公关媒体 专业行销 房地产 软件开发 想怎么找？选一个 👇
⭐️ 资深UI设计师 ⭐️ 🏠公司：KA 📍工作地点：东京 💵薪资/待遇：薪资：25K –35K RMB / 月，保底13薪，表现优异者奖励期权和最多24月奖金 🌐国籍要求：无 💎岗位职责 负责以下工作： 1. 参与产品研发，围绕真实场景持续迭代。 2. 学习竞品，取长补短，不断优化产品。 3. 持续塑造品牌感 💎任职要求 需要具备的能力： 1. 精通Photoshop/Figma等常用软件 2. 有精心设计的作品，并可以在面试时直接show off 你的作品 3. 对当前主流的AI绘画、AI视频生成工具有深入的了解和丰富的实践经验 我们希望你： 4. 不墨守陈规：敢于质疑权威，敢于引领而非跟随； 5. 有品味：对产品的美感有追求 6. 有强烈的好奇心和学习能力 硬性要求 7. 年龄：28-38岁 8. 学历：统招本科及以上有学位可认证 9. 英语：CET-4及以上 📱金牌HR：@JSDom 🇪🇸直招岗位：@KMzhao…
⭐️ 高级猎头客户经理 ⭐️ 🏠公司：KM 📍工作地点：日本 东京 💵薪资/待遇：面议 🌐国籍要求：日本籍 💎岗位职责 1. 负责日本市场企业客户开发与业务拓展，建立并维护长期稳定的客户合作关系。 2. 深入理解客户的人才战略与招聘需求，为客户提供专业的中高端人才招聘及人才咨询解决方案。 3. 独立负责客户拜访、商务洽谈、职位需求分析、项目管理及招聘交付，确保项目顺利完成。 4. 与猎头顾问团队紧密合作，高效推进招聘项目，持续提升客户体验及服务质量。 5. 持续挖掘市场机会，拓展客户资源，实现业务增长及销售目标。 6. 参与日本猎头业务的筹建，为业务流程、客户管理体系及市场拓展提供专业建议。 💎任职要求 1. 日本国籍，日语为母语，并具备商务水平的英语或中文沟通能力。 2. 五年以上猎头行业工作经验，具备企业客户开发及客户管理经验。 3. 熟悉中高端人才招聘流程，具备优秀的商务拓展、咨询服务及客户关系管理能力。 4. 具备…
⭐️ 拓英猎头 · 在招岗位总目录 ⭐️ 🏠拓英人力资源股份有限公司 Topin Recruitment 致力成为国际人力资源服务领域的领航者 🌐官网 topinhongkong.com 💎当前在招 221 个岗位 16 家企业 14 个国家和地区 💵覆盖行业 资讯科技 金融服务 游戏娱乐 公关媒体 专业行销 房地产 软件开发 想怎么找？选一个 👇
🌐 其他 💎 共 4 个在招岗位，点岗位名看完整 JD 👇 📌 其他 🔹 前端开发（React Native） 📌 经理级 🔹 品牌经理 📌 专员级 🔹 运营专员 📌 助理 / 初级 🔹 行政助理 📱金牌HR：@JSDom 🇪🇸直招岗位：@KMzhaopin 🗓猎头岗位：@TPzhaopin
🇦🇪 迪拜 💎 共 1 个在招岗位，点岗位名看完整 JD 👇 📌 其他 🔹 高管秘书 📱金牌HR：@JSDom 🇪🇸直招岗位：@KMzhaopin 🗓猎头岗位：@TPzhaopin
Showing the 12 most recent of 20 posts we hold for @TPzhaopin. 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 — 623,061 of 1,480,975entries 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.
Named by 9 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“拓英猎头招聘” (@TPzhaopin), 64 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/TPzhaopin.
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.