Telegram RegisterThe public register of Telegram
Telegram profile photo for 技术全岗-远程-到岗-朱莉😘

Channel

技术全岗-远程-到岗-朱莉😘

@Jolie_HR

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

2,627subscribers

+6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001175182640
TypeChannel
Username@Jolie_HR
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Jolie_HR

Growth

2,6212,6292,6257 August 2026 — 2,621 subscribers7 August 2026 — 2,621 subscribers7 August 2026 — 2,622 subscribers10 August 2026 — 2,629 subscribers13 August 2026 — 2,627 subscribers2,6277 August 202613 August 2026
5 measurements spanning 6 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 2,620–2,630 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:272,627-2
10 Aug 2026, 10:432,629+7
7 Aug 2026, 15:002,622+1
7 Aug 2026, 13:332,621no change
7 Aug 2026, 12:512,621first reading

Engagement

20 posts held, back to 24 July 2026the 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
33.7%
avg views ÷ 2,627 subscribers
Avg views / post
884
18 posts measured
Reaction rate
0.116%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 9 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (24 July 20266 August 2026)
Views total15,916
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 13:33 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

8 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8100.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 9 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 8reactions 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 24 July 2026 to 6 August 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

6 Aug 2026, 11:44 UTC438 views1 reactionsread 7 August 2026

#远程 #长期远程 #高级前端 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 🥺2名:高级前端 🥰 薪资范围:20-30K(具体面谈) 🥰 上班时间:8休4(09:30-18:30)午休1小时 🥰 试用期间:1-3个月(能力好可提前转正) 🥰 办公地点:远程办公/不限制地区 👌 岗位要求: 技术栈一览:Vue 3 + Vite + TypeScript(Composition API)、Pinia、Vue Router、Module Federation(微前端)、SignalR + SSE(实时订单推送)、AES/RSA/SHA256/MsgPack/Gzip(请求体加解密与压缩)、Dexie(IndexedDB)、Docker 多架构构建部署、Vitest + Husky(测试与提交卡点)。 一、核心职责 • 负责收银台充值/提现核心链路的开发与维护,保障下单、金额、汇率、优惠计算的绝对正确。 • 处理会话生命周期与各类异

1

Signed 人事直招-HR E ( 朱莉 )

5 Aug 2026, 15:49 UTC578 views1 reactionsread 7 August 2026

#IOS #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 #双休 #双休 长期远程 #不限制地区 😊1名:iOS开发工程师(含App Store上架) ❤️上班时间:10:00-20:00 (双休) ❤️薪资范围:20-25k ❤️学历要求:本科以上 🌟职位概述 负责公司iOS App的功能开发与迭代,并全流程负责App Store上架、审核沟通、版本发布及合规管理,确保产品稳定、合规、高效地触达用户。 工作职责 负责iOS App核心功能的设计、开发、调试与维护,保证代码质量与性能。 独立负责App Store Connect后台管理,包括应用信息配置、证书与描述文件管理、版本提交。 跟进App Store审核全流程,及时响应苹果审核团队的驳回意见并完成整改,控制上架周期。 熟悉并落实App Store审核指南(Guideline 2.x/3.x/4.x等),提前排查隐私合规、支付合规(IAP)、UI规范等风险点。

1

Signed 人事直招-HR E ( 朱莉 )

4 Aug 2026, 09:29 UTC626 views1 reactionsread 7 August 2026
Photo

2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 #远程 #ios #第三国远程 ➡️4名:iOS开发/架构 📍第三国远程办公 30~50k 📍马来西亚/泰国 40~80k 1、5年及以上iOS开发经验,具备完整项目开发及上线经验; 2、熟练掌握Swift,熟悉Objective-C,能够维护历史项目; 3、熟悉UIKit、SwiftUI,能够独立完成复杂业务开发; 4、熟悉网络通信、数据存储、多线程、内存管理、性能优化等核心技术; 5、熟悉MVC、MVVM等常见架构模式,具有良好的代码设计能力; 6、熟悉Git等版本管理工具,具备良好的编码规范和团队协作能力; 7、具备较强的分析问题和解决问题能力,能够独立负责业务模块开发; 优先录用条件(重点) • 拥有海外互联网公司或海外项目工作经验。 • 具有数字货币交易所、Web3、区块链、钱包、DeFi等相关项目开发经验。 • 具有棋牌、BC、游戏、社交等高并发、高性能项目开发经验者

1

Signed 人事直招-HR E ( 朱莉 )

2 Aug 2026, 12:24 UTC843 viewsread 7 August 2026

#运营 #远程 1️⃣2名:运营专员 😛有经营国内盘网站的经验 工作目标:不打广告的情况下,使用活动或是其他方式让网站营业数据提升 😛台湾籍女性或中国籍女性为主 可远程办公 年紀37以下 薪资:20000~面议 ➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

Signed 人事直招-HR E ( 朱莉 )

1 Aug 2026, 06:05 UTCviews —

技术全岗-远程-到岗-朱莉😘 pinned «#安卓 #远程 1️⃣【招聘】高级 Android 开发工程师(海外产品) 😛薪酬范围:18-30k 😛双休 上午10点到晚上8点,中午休息2小时 😁岗位要求: 😁岗位职责 * 负责公司海外 Android 产品的客户端开发、架构设计及版本迭代。 * 负责核心业务模块开发,包括用户系统、任务系统、钱包、消息、支付、奖励发放等功能。 * 负责 Android 客户端性能优化,持续提升应用启动速度、流畅度、稳定性及用户体验。 * 负责第三方 SDK 接入与维护,包括 Firebase、AppsFlyer、Adjust、Google…»

1 Aug 2026, 06:00 UTC903 views1 reactionsread 7 August 2026

#安卓 #远程 1️⃣【招聘】高级 Android 开发工程师(海外产品) 😛薪酬范围:18-30k 😛双休 上午10点到晚上8点,中午休息2小时 😁岗位要求: 😁岗位职责 * 负责公司海外 Android 产品的客户端开发、架构设计及版本迭代。 * 负责核心业务模块开发,包括用户系统、任务系统、钱包、消息、支付、奖励发放等功能。 * 负责 Android 客户端性能优化,持续提升应用启动速度、流畅度、稳定性及用户体验。 * 负责第三方 SDK 接入与维护,包括 Firebase、AppsFlyer、Adjust、Google Play Billing、广告 SDK 等。 * 负责应用在 Google Play 的版本发布、维护及线上问题排查。 * 与产品、UI、后端、测试团队密切协作,完成需求分析、开发、测试及上线。 * 参与客户端架构设计、公共组件建设及技术方案制定,不断提升研发效率和代码质量。 任职要求 基本要求 *

1

Signed 人事直招-HR E ( 朱莉 )

31 Jul 2026, 09:00 UTC840 views1 reactionsread 7 August 2026

2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 #技术主管 #马来西亚 🎃急招|Java 开发主管(Java Team Lead)薪资面议 工作地点:马来吉隆坡 工作时间:10休4 🥺10 年以上 Java 开发经验 🥺有团队管理经验,带过研发团队 🥺熟悉 Java 主流技术栈、微服务架构 🥺能独立负责项目并带领团队交付 ➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

1

Signed 人事直招-HR E ( 朱莉 )

31 Jul 2026, 08:24 UTCviews —

技术全岗-远程-到岗-朱莉😘 pinned «#远程 #长期远程 #测试 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 1️⃣2 名:测试 远程 薪资范围:15k-20k 工作时间:9休4 😛工作内容: 1. 依产品/专案设计之功能项目,拟定 Test Plan 和设计 Test Case 2. 和相关人员沟通,确认设计、功能需求和规格 3. 进行API测试、功能测试、使用者体验、UI测试、APP测试(ios/Android) 4. 问题回馈、问题追踪,协助各端人员确认 Issue 并加以验证 5. 分析测试结果且清楚回报,协助开发团队解决问题,并持续追踪回归测试…»

31 Jul 2026, 08:21 UTC843 views1 reactionsread 7 August 2026

#远程 #长期远程 #测试 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 1️⃣2 名:测试 远程 薪资范围:15k-20k 工作时间:9休4 😛工作内容: 1. 依产品/专案设计之功能项目,拟定 Test Plan 和设计 Test Case 2. 和相关人员沟通,确认设计、功能需求和规格 3. 进行API测试、功能测试、使用者体验、UI测试、APP测试(ios/Android) 4. 问题回馈、问题追踪,协助各端人员确认 Issue 并加以验证 5. 分析测试结果且清楚回报,协助开发团队解决问题,并持续追踪回归测试 6. 跨部门沟通/合作 确保产品或专案之设计&需求的功能项目正确 加分条件: 1.具备自动化测试工具使用经验 (如Selenium、Appium、JMeter、POSTMAN等)。 2.熟悉敏捷开发与测试或专案管理工具等(如GitLab、JIRA)。 3.具备基础程式开发能力,可协助撰写测试脚本。 4.良好的问题

1

Signed 人事直招-HR E ( 朱莉 )

30 Jul 2026, 04:24 UTC890 viewsread 7 August 2026

#产品 #UI #亚美尼亚 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 ♈️亚美尼亚♈️埃里温♈️技术直招♈️ 🐳UI设计师 (30-45k) 🐳项目经理 (40-55k) 🐳高级运维 (35-50k) 🐳高级前端 (35-50k) 🐳高级UX (60-80k) ❤️‍🩹 办公地点:亚美尼亚/埃里温 ❤️‍🩹 上班时间: 8休4 单休(09:00-17:00) ❤️‍🩹 试用期间:1-3个月 ❤️‍🩹 薪资范围:30K-60K+绩效(具体面谈) ➖➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

Signed 人事直招-HR E ( 朱莉 )

29 Jul 2026, 14:41 UTC874 viewsread 7 August 2026

#双休 #长期远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 1️⃣ 游戏策划 (真金游戏 · 印度市场) 🥺薪资范围:20-30k 🥺了解slot/棋牌 / 电子 / 体育多品类玩法者优先 ➖➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

Signed 人事直招-HR E ( 朱莉 )

29 Jul 2026, 12:34 UTC840 views1 reactionsread 7 August 2026

#菲律宾 #运维 #卡加延 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 🎃 ⾼级/资深 K8S系统运维⼯程师 😢工作地点:菲律宾 (卡加延 - Cagayan) 😢工作时间:每天 8 小时 😢薪资:薪资面议 😢休假:周休1(按星期日计算) 😢国籍:不限 (台湾籍优先) 😢年龄:21-40岁 1️⃣招聘条件 学历:本科以上 语言:中文为主,能熟练英文或其它语言更佳。 经验 : ⾄少 5 年以上系统运维相关⼯作经验,具备⼤规模⽣产环境的管理与实务的经验。 技术能力要求: ◦ 理解 Linux 操作系统、Nginx、TCP/IP 协议,具备⽹络诊断、排查能⼒。 ◦ 能使⽤容器技术(如 Docker、Kubernetes),具有实务经验,并且担任专案内的主要⻆⾊ ◦ 熟练使⽤云计算平台常⽤服务(如 AWS、GCP、Azure、腾讯云、阿⾥云等)。 ◦ 熟悉常⻅数据库(如 MySQL、Redis , MongoDB , PostgreSQ

1

Signed 人事直招-HR E ( 朱莉 )

Showing the 12 most recent of 20 posts we hold for @Jolie_HR. 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 — 38,472 of 1,481,217entries 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.

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.

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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“技术全岗-远程-到岗-朱莉😘” (@Jolie_HR), 2,627 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Jolie_HR.

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.