Telegram RegisterThe public register of Telegram

Channel

公司职位JD😊找工作请咨询人事 @RoseHRD1

@IntechJD

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

1,390subscribers

+26 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-1001606409393
TypeChannel
Username@IntechJD
CreatedBetween 1 December 2021 and 31 March 2023— 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/IntechJD

Growth

1,3641,3901,3777 August 2026 — 1,364 subscribers7 August 2026 — 1,364 subscribers7 August 2026 — 1,367 subscribers10 August 2026 — 1,379 subscribers13 August 2026 — 1,390 subscribers7 August 202613 August 2026
5 measurements spanning 6 days, net +26. 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 1,360–1,394 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:041,390+11
10 Aug 2026, 11:371,379+12
7 Aug 2026, 15:551,367+3
7 Aug 2026, 11:011,364no change
7 Aug 2026, 10:491,364first reading

Engagement

20 posts held, back to 10 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
43.0%
avg views ÷ 1,390 subscribers
Avg views / post
598
16 posts measured
Reaction rate
0.167%
reactions ÷ views · ER floor
Posts in window
16
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 8 of 16 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 7 August 2026
Posts held20 (10 July 20267 August 2026)
Views total9,569
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 11:01 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

10 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
880.0%
👍110.0%
🫡110.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 11 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 10reactions 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 10 July 2026 to 7 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

7 Aug 2026, 09:57 UTC101 views2 reactionsread 7 August 2026

运营助理(泰国) 年龄要求26以下 上班时间:9小时 月休7 薪资待遇1500-1800USD + 奖金 工作内容: 1. 协助负责线上线下活动,并针对运营工作或运营活动进行资料跟踪分析及总结, 根据数据效果,推进网站的改进和营销策略的改变; 2. 协助负责网站的运营规划,结合产品需求与市场调查分析, 制定一系列完善的产品整体运营规划并执行; 3. 协助各类活动/优化需求运营验收与开发、设计对接等; 4. 协助日常运营维护、线上问题即时处理,事故处理并即时反馈相应部门,降低事故损失; 5. 协助与其他部门有效沟通及共同完成项目策划及执行工作; 6. 协助交办的其他事宜。 岗位需求: 2. 良好的沟通能力,协调能力,做事清晰,做人简单; 3. 对数据敏感和日常运营维护能力; 4. 抗压能力强,责任心强,能接受KPI指标

1🫡1

7 Aug 2026, 09:56 UTC96 viewsread 7 August 2026

社区专员 薪资:2700U+ 房补+餐补:450U+300U 工作地点:亚美尼亚 岗位职责 1.主播管理与排班 负责论坛直播主播的招募、培训及日常管理,确保主播团队高效运作; 制定主播排班计划,协调直播时间,保障直播内容的稳定输出; 监督主播表现,定期反馈优化建议,提升直播质量与用户互动体验。 2.活动策划与执行 策划并组织论坛直播相关活动(如专题直播、节日活动、用户互动等),提升用户参与度和粘性; 跟踪活动数据,分析效果并优化后续方案,确保活动目标的达成; 协调内外部资源,推动活动顺利落地执行。 3.产品优化与验收 收集用户及主播反馈,提出直播产品功能优化建议,推动技术团队迭代改进; 参与新功能或改版测试,负责验收并反馈问题,确保产品体验符合预期; 监测直播平台运行状况,及时跟进并解决突发问题。 4.数据分析与运营优化 定期分析直播数据(如观看量、互动率、转化率等),制定运营策略调整方案; 结合行业动态和竞品分析,探

7 Aug 2026, 03:31 UTC208 viewsread 7 August 2026

安全系统维护工程师(1位) 🎯 工作内容 1,资安防护与监控系统维运: 负责 Ekran System(用户行为监控与审计)等资安系统的架设、管理、维护与权限控管。 2,伺服器与基础架构安全维护: 管理 Windows Server 与 Linux Server 之系统安全、补丁更新、漏洞修补、备份与灾害复原策略执行。 3,日志平台管理与数据对接: 负责 ELK Stack (Elasticsearch, Logstash, Kibana) 集群的搭建、维运、效能调优与资安告警规则设定。 4,云端资安日志整合: 负责 AWS / GCP / Azure 等公有云平台的 Cloud Audit Logs、Flow Logs 与安全日志对接至中央日志系统。 5,安全事件应变与分析: 负责系统与网路安全告警判定、障碍排除、事件纪录与应变处置。 📋 职务需求(必要条件) 1,伺服器与资安系统经验: 熟悉 Windows Se

6 Aug 2026, 05:42 UTC352 viewsread 7 August 2026

Egret前端 办公地址:塞尔维亚 工作时间:9小时,周末双休+当地法定节假日 薪资面议 工作职责: 1. 使用Egret进行项目相关功能模块任务的开发; 2. 根据项目需求,进行游戏程序设计及开发工作; 3、与服务器后端工程师沟通网络数据通信等; 4、与项目组策划、美术人员共同讨论开发需求及设计游戏实现细节,保证产品质量和进度,优化前端页面性能。 任职要求: 1.egret至少独立完整开发过一款游戏而且上过线 2.必备技术 • 熟练掌握 TypeScript、JavaScript、ES6 • 熟悉 HTML5、Canvas、WebGL • 熟练使用 Egret Engine5版本 • 熟悉egret整套工具 • 掌握 Git版本管理 • http和WebSocket 长连接等网络请求 • 会用chrome快速调试和查找问题。 加分项目: 1.

6 Aug 2026, 05:38 UTC347 viewsread 7 August 2026

推广专员 办公地点:远程 薪资范围: 转正2000USD➕提成 工作时间:10小时双休 岗位空缺:3名 职责: 1、通过技术手段或媒体内容手段进行引流 2、可批量通过论坛/自媒体/视频/信息流/社区等进行推广 3、掌握最新的推广渠道以及方法,能够带来流量和用户 4、对推广数据进行分析,并对推广方案进行优化 5、可有效发展并维护外部代理或拓展流量合作渠道 要求: 1、1年以上行业经验,有激情,有推广思路和渠道 2、善于利用各种引流、推广手段,有多种技术手段引流者优先,如脚本引流,群控群发,视频裂变 3、拥有各种流量合作资源者优先 4、有团队精神及高度的责任感,够承担一定压力

27 Jul 2026, 05:24 UTC908 views1 reactionsread 7 August 2026

OracleDBA 岗位职责: 1、负责Oracle或TIDB(包含容器化)数据库日常运维操作,确保数据库服务高效稳定运行; 2、负责Oracle或TIDB(包含容器化)数据库设计方案的审核及实施,性能分析和调优,故障应急处理,自动化运维等工作; 3、负责Oracle或TIDB(包含容器化)数据库升级、扩容、备份、数据迁移、灾难恢复和管理等工作; 4、参与技术文档梳理相关工作,为数据库维护的标准化、流程化提供合理建议,并形成规范文档; 5、能够提前发现潜在问题并给出解决方案; 6、负责系统架构设计与优化改良,新方案的调研上线" 任职要求: 1、3年以上大型数据库维护经验 2、熟悉Linux操作系统工作原理,熟练使用Linux操作系统。 3、熟悉shell/python等至少一种语言,可以使用脚本完成相关工作。 4、熟悉Oracle,mysql,postgresql,TiDB 安装、备份、故障处理、在线升级等日常任务。 5、熟

👍1

20 Jul 2026, 06:23 UTC≈1,140 views1 reactionsread 7 August 2026

AI应用层开发工程师(高级) 技术栈要求 1.5年以上 Java 开发经验 2.熟悉 Spring Boot、MyBatis、MySQL、Redis 3.具备 Vue 开发能力(Vue3优先) 4.具备良好的系统设计及问题排查能力 AI能力要求 1.有真实 AI 应用层项目经验 2.熟悉大模型(LLM)应用开发 3.熟悉 RAG 技术方案 4.熟悉向量数据库(Milvus、Qdrant 等) 5.了解知识图谱相关技术 6.具备 Prompt Engineering(提示词工程)经验 7.熟悉 Cursor、Codex、Claude Code 等 AI 编程工具 8.具备 AI 功能测试与评测能力,能够设计测试数据集并评估模型效果 优先考虑 1.有已上线 AI 项目经验 2.有 Agent 或 Multi-Agent 项目经验 3.熟悉 MCP(Model Context Protocol) 4.有私有化大模型部署经验(vLL

1

17 Jul 2026, 09:28 UTC≈1,090 viewsread 7 August 2026

运维自动化开发工程师 岗位定位:平台开发 / 系统优化 核心技术:Python · Django · Celery 重点经验:CMDB / 运维平台 岗位职责 1. 负责公司运维自动化平台、CMDB、发布系统、监控告警、任务调度、资源管理等系统的设计、开发、维护与优化。 2. 基于 Python + Django 进行后端服务开发,包括资产管理、权限管理、任务管理、接口服务、数据同步、自动化操作等功能。 3. 独立负责 CMDB 或运维平台核心模块 的需求分析、方案设计、数据库设计、接口开发、联调测试及上线交付。 4. 使用 Celery、RabbitMQ、Redis 构建异步任务、定时任务、批量任务、任务状态追踪、缓存及后台任务处理能力。 5. 参与 Kubernetes 相关自动化平台功能开发,包括集群资源查询、应用发布、服务状态展示、日志检索、巡检任务、异常告警等能力建设。 6. 负责平台系统优化,包括接口性能优化、

17 Jul 2026, 09:25 UTC762 views1 reactionsread 7 August 2026

高级运维安全工程师 办公地址:塞尔维亚 岗位职责 1. 负责公司基础设施(云 / 主机 / K8s)的安全架构设计与加固。 2. 建立并推动 IT 安全体系落地(访问控制、数据安全、安全基线等)。 3. 负责权限管理(IAM / RBAC)及网络安全策略(防火墙 / WAF)。 4. 建设安全监控与日志审计体系,进行告警分析与风险评估。 5. 负责漏洞管理(扫描、修复闭环)及安全事件响应。 6. 推动 DevSecOps,将安全能力融入 CI / CD 流程。 7. 参与云平台(AWS / 阿里云)安全治理。 任职要求 1. 5 年以上运维 / 安全经验,有 IT 安全体系建设经验优先。 2. 扎实的 Linux 与网络基础,熟悉常见运维架构。 3. 熟悉云平台(AWS / 阿里云)及容器技术(Docker / K8s)。 4. 具备以下至少 2–3 个方向的实践经验: • 身份与权限管理(IAM / RBAC) • 主机

1

17 Jul 2026, 09:24 UTC704 viewsread 7 August 2026

高级运维网络工程师 办公地址:塞尔维亚 岗位职责 1. 负责数据中心、云平台及办公网络的规划、部署、优化和日常运维。 2. 管理路由器、交换机、防火墙、VPN、负载均衡等设备,保障网络稳定与高可用。 3. 负责 IDC、云平台及跨地域网络互联,快速排查路由、链路、丢包和延迟等问题。 4. 维护防火墙、ACL、WAF、IPS/IDS、VPN及零信任等网络访问与安全策略。 5. 管理域名、DNS和SSL证书,处理解析异常、DNS污染及跨境访问问题,完善多DNS和线路分流策略。 6. 使用 tcpdump、Wireshark、MTR 等工具分析 TCP/IP、TLS、DNS、HTTP(S) 及异常流量。 7. 维护办公网络、网络隔离、VDI及多地办公接入,完善网络监控、告警和技术文档。 8. 复盘重大网络事件,输出故障分析与优化方案。 任职要求 1. 5年以上网络运维或网络工程经验。 2. 熟悉 TCP/IP、BGP/OSPF、V

17 Jul 2026, 09:10 UTC690 viewsread 7 August 2026

网络工程师 办公地址:塞尔维亚 岗位职责 1,负责 GCP 云网络架构设计、部署及优化,包括 VPC、Subnet、Cloud Router、Cloud NAT、Cloud DNS、Load Balancer 等网络资源管理。 2,负责企业混合云网络建设,完成本地 IDC 与 GCP 的网络互联(VPN、Interconnect、BGP 等)。 3,负责 GCP Network Connectivity Center(NCC)架构规划、部署及维护。 4,负责 GCP 网络安全建设,包括 Firewall、Cloud Armor、VPN、NAT 等网络安全策略配置。 5,负责 GKE 网络相关支持,包括 Ingress、Load Balancer、Network Policy 等。 6,负责生产环境网络运维、故障排查、网络优化及技术文档编写。 7,参与网络自动化建设,持续提升网络运维效率。 任职要求 1,本科及以上学历,计算机、

17 Jul 2026, 08:49 UTC635 views1 reactionsread 7 August 2026

游戏交互设计师 办公地址:塞尔维亚 岗位职责: 一.负责真人视讯百家乐产品的交互设计,包括: 1.游戏大厅 2.房间列表 3.游戏桌面 4.下注区域 5.筹码交互 6.路单展示 7.结算界面 8.历史记录 9.活动页面 10.VIP专区 二.根据产品需求,输出完整的交互设计方案,包括: 1.用户流程 2.信息架构 3.页面流程图 4.Wireframe(线框图) 5.高保真交互原型 6.交互说明文档 三.优化真人游戏核心操作体验,包括: 1.快速下注 2.重复下注 3.双击下注 4.撤销下注 5.多筹码组合下注 6.倒计时交互 7.动效反馈 8.下注确认机制 四.设计直播互动体验,包括: 1.荷官视频展示 2.聊天互动 3.玩家排行榜 4.礼物互动(如产品需要) 5.公告与系统消息 6.游戏提示与引导 五.与产品经理、UI设计师、开发、测试团队协作,推动交互方案落地,并跟进开发实现效果。 六.基于用户反馈和数据分析,

1

Showing the 12 most recent of 20 posts we hold for @IntechJD. 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 — 278,291 of 1,151,006entries 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.

Mentions

Named by 5 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.

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.

“公司职位JD😊找工作请咨询人事 @RoseHRD1” (@IntechJD), 1,390 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/IntechJD.

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.