Channel
@zhaopinyuancheng
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
451subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001562340666 |
|---|---|
| Type | Channel |
| Username | @zhaopinyuancheng |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/zhaopinyuancheng |
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 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 02:21 | 451 | -1 |
| 30 Aug 2026, 03:44 | 452 | -1 |
| 24 Aug 2026, 01:36 | 453 | -2 |
| 15 Aug 2026, 16:03 | 455 | +1 |
| 8 Aug 2026, 05:00 | 454 | no change |
| 7 Aug 2026, 10:22 | 454 | first reading |
20 posts held, back to 19 May 2023 — 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 26 February 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 63.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 63.3% | |
| 👍 | 10 | 33.3% | |
| 🎉 | 1 | 3.33% |
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 14 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 30 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 19 May 2023 to 26 February 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.
‼️紧急招聘岗位 岗位：渗透工程师（高级/资深/专家） 需求： 5人 工作地点： 非大陆远程（可香港、澳门、台湾远程） 薪资：面议 岗位职责 1.熟练使用（不限于Burp.AWVS.NMAP）等漏洞扫描工具，掌握常见Web.系统安全漏洞原理，对解决方案有所理解。 2.熟悉Web攻击方法,SQL注入.XSS攻击.命令注入.CSRF攻击.上传漏洞.解析漏洞等攻击的各类技术及方法，对各类操作系统.应用平台的弱点有较深入的理解。 3.熟悉Linux/Unix/Window操作系统常用命令。 4.熟悉常见的内网攻击思路和方法，域环境渗透等。 5.能制定方案并执行渗透，提供漏洞咨询与技术支持。 任职资格 1.五年以上的红队经验，有渗透案例并拿到结果 2.具备web渗透能力，owasp top10常规精通 3.具备主机信息快速收集能力，具备内网攻击能力 4.具备免杀以及社工攻击能力 5.脚本语言能力，可以编写常规工具 6.移动端能反编译…
岗位：渗透工程师（高级/资深/专家） 需求： 3人 工作地点： 第三国远程 薪资： Open，面谈 岗位职责 1.熟练使用（不限于Burp.AWVS.NMAP）等漏洞扫描工具，掌握常见Web.系统安全漏洞原理，对解决方案有所理解。 2.熟悉Web攻击方法,SQL注入.XSS攻击.命令注入.CSRF攻击.上传漏洞.解析漏洞等攻击的各类技术及方法，对各类操作系统.应用平台的弱点有较深入的理解。 3.熟悉Linux/Unix/Window操作系统常用命令。 4.熟悉常见的内网攻击思路和方法，域环境渗透等。 5.能制定方案并执行渗透，提供漏洞咨询与技术支持。 任职资格 1.具有3年及以上安全岗位或大型信息安全项目经验。 2.本科及以上学历；
IM移动端专家（安卓方向）✈️✈️ 工作地点： 远程 后期去日本 项目：IM（白项目） 薪资范围：55k-100k 任职资格 1. 专业技能要求 移动端开发经验： 精通iOS（Swift/Objective-C）或Android（Java/Kotlin）开发，至少有5年以上相关经验。 熟悉移动端开发中的UI设计、性能优化、跨平台开发等技术。 精通性能优化，对UI卡顿优化、线程优化、数据库优化有经验。 即时通讯相关技术： 熟悉即时通讯系统的基本原理与技术，如消息推送、实时数据传输、Socket、WebSocket等。 有IM类应用开发经验，能够设计和实现高效的消息传输和存储机制。 网络和数据处理能力： 深入理解TCP/IP、HTTP/HTTPS等网络协议，具备一定的网络优化经验。 熟悉数据存储和同步机制，能优化数据传输的效率与稳定性。 2. 经验要求 至少有5年以上即时通讯（IM）应用的开发经验，包括但不限于即时聊天、视频通话…
❤1
IM项目新增一个需求 岗位： 资深前端开发工程师 薪资范围： 40-60K 人民币 工作性质： 可先远程，然后出国（日本或菲） 工作时间： 9休4 任职资格 1、参与IM即时通讯产品规划设计，提供技术实现方案 2、负责核心架构设计，业务代码编写 3、根据项目安排工作安排和进度，按时完成指定模块的编码和调试工作 4、对现有项目的设计代码进行复核，根据业务部门的需求对现有系统进行调整、优化、功能扩展 5、与团队一起攻克例如高并发、高稳定性等带来的各种挑战及技术难关 任职要求： 本科及以上学历，计算机科学或相关专业。 8年以上前端开发经验 精通 Vue.js，熟悉 Vuex、Vue Router 等常用工具及框架，能基于 Vue 构建高质量的前端应用。 熟悉前端工程化，能够设计并实施前端构建工具链（如 Webpack 等）。 精通 HTML5、CSS3、JavaScript，理解浏览器工作原理，有较强的前端性能优化经验。 熟悉 …
香港高薪招聘各类技术，候选人需要有香港工作签证
高级前端， 高级java, 只要人在国外可以远程
❤7
远程go需要五名，有意者尽快联系我投简历哈
名称：UE用户体检官 远程 岗位要求： "1、本科以上学历： 具有相关领域的本科或以上学历，有人机交互、心理学、设计等相关专业背景者优先考虑。 2、用户研究经验： 有2年以上用户体验或用户研究工作经验，熟悉各类用户研究方法，能独立设计和执行用户调研项目。 3、竞品分析能力： 具备出色的竞品分析能力，能够对市场上的竞品进行深入剖析，提炼出关键竞争点，并能将分析结果转化为实际产品优化方案。 4、数据分析能力： 熟练使用数据分析工具，能够从大量数据中提取有价值的信息，为用户体验优化提供数据支持。 5、团队合作： 具备良好的团队合作精神，能够与多个团队紧密配合，推动项目的顺利进行。 6、沟通能力： 出色的沟通和表达能力，能够清晰地向团队传达用户需求和优化建议，推动团队行动。" 岗位职责： "1、竞品分析报告： 负责对竞品市场进行深入研究和分析，撰写详尽的竞品分析报告，包括但不限于界面设计、用户交互、功能特性等方面的比较和评估。 2、用户…
👍2❤1
交易所技术总监 （新加坡入职) 1、负责数字货币交易所系统的搭建，重点是合约交易系统的搭建及运维。 2、负责搭建和管理公司产品技术团队，结合公司发展战略，把握科技金融衍生品交易产品发展趋势，分析跟踪竞争对手，进行产品的发展规划，明晰定位、目标、策略并落实实施；根据业务需求及时调整产品系统功能重点，促进版本迭代更新，保证产品系统不断优化对整个团队工作结果负责；? 3、负责公司产品业务研发、规划、关键技术架构的制定；配合公司的业务发展需要，组织团队完成产品设计和研发工作；? 4、负责整体产品技术队伍建设、激励、培养，做好人员配置与协调，有效地监控项目进展，制定相应的考核/激励，持续提升团队工作热情、工作质量和工作效率；? 5、负责应用技术团队的管理工作，负责全局性和前瞻性的架构设计、规划平台未来技术架构方向； 6、结合外汇/大宗商品差价合约，美/港股差价合约，数字货币差价合约交易系统，CRM及渠道代理业务系统，数据分析及风控系统做集…
❤6
交易所新增远程岗位： #交易所 #远程 #web3 #币圈 技术总监：80-120k 运营总监：70-100k 业务总监：70-100k 商务BD:12-30K 市场主管：20-30k BD总监：40-300k BD经理：20-200k 策略研究员：20-50k 图像识别工程师：20-55k 机器学习高级工程师：20-55k AL算法工程师：20-55k 金融产品经理：20-40k python量化开发工程师：20-40k 场外期权定价&对冲&交易：20-40k
👍3
支付 技术总监 1）计算机相关专业统招本科及以上学历； 2）10年以上Java开发经验，熟练掌握多线程等基础类库，熟悉分布式缓存等技术； 3）3年以上互联网行业架构经验，熟悉微服务体系技术,有K8s实施经验优先； 4）熟练掌握Spring boot、Springcloud、Mybatis、MQ开发框架； 5）精通Rabbitmq、Kafka、Zookeeper、Zeromq等流行的分布式系统及其架构； 6）掌握分布式开源技术，包括分布式事物，分布式日志，MQ； 7）精通缓存等机制,熟悉高并发、高性能的分布式系统的设计及应用、调优； 8）精通数据库Mysq，NoSQL存储，Hbase、memcached、redis、mongodb等； 9）熟悉Linux系统，并能熟练掌握各种Linux命令及其工具，熟悉shell。 10）从事过中大型互利网项目及高并发等相关经验加分； 11）有支付行业加分 岗位职责 1）支付系统前瞻性技术储备，负…
远程 初中级运维3个 15-20k
Showing the 12 most recent of 20 posts we hold for @zhaopinyuancheng. 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.
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.
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.
“交易所 远程岗位” (@zhaopinyuancheng), 451 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/zhaopinyuancheng.
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.