17 Mar 2025, 08:38 UTCviews —
DIGI PLUS 岗位简章 pinned a photo
Channel
DIGI PLUS 岗位简章
@DIGIPLUS_HR
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
20subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002262167532 |
|---|---|
| Type | Channel |
| Username | @DIGIPLUS_HR |
| Description | DigiPlus-BGC-本地市场-上市公司-周末双休+法定菲假, 目前只更新技术岗位职缺，更多岗位麻烦发送简历至HR @hrandrew188 为您匹配合适的岗位噢！祝愿各位在海外每天开心，赚更多更多的钱~ |
| Created | Between 1 October 2024 and 6 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DIGIPLUS_HR |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:00 | 20 | no change |
| 11 Aug 2026, 17:46 | 20 | first reading |
Engagement
20 posts held, back to 6 March 2025 — 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.
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 17 March 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 24
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👍 | 1 | 50.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 2reactions 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 6 March 2025 to 17 March 2025, 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 Mar 2025, 06:49 UTC360 viewsread 11 August 2026
🎨【UX设计师 | 高薪急招】🇨🇳 📍办公地点：菲律宾Makati ⏰工作时间：弹性制度 | 享集团标准假期 💵薪资：面议（3年+经验者优厚） ━━━━━━━━━━━━━━ 🔥【核心职责】 1️⃣ 主导BingoPlus平台全渠道UI体验设计 2️⃣ 优化产品视觉呈现，强化品牌认知度 3️⃣ 创新视觉思维，突破品牌平面设计瓶颈 4️⃣ 统筹页面风格设计&重点活动视觉落地 ━━━━━━━━━━━━━━ 🎓【任职要求】 ✅ 艺术类大专以上学历（视觉/动画/数字媒体优先） ✅ 3年+实战经验，成熟设计技法+系统理论 ✅ 精准品牌分析能力，逻辑思维清晰 ✅ 极致审美追求+艺术敏锐度 ✅ 强沟通力+创新意识+快速学习能力 ━━━━━━━━━━━━━━ 🌟【加分项】 ✔️ 有游戏/社交平台设计经验 ✔️ 熟悉用户体验研究流程 ✔️ 动效设计/3D建模能力 ✔️ 多语言能力（英/中文流利） ━━━━━━━━━━━━━━ 📮【应聘方式】…
6 Mar 2025, 06:49 UTC281 viewsread 11 August 2026
🎨【创意设计师 | 高薪急招】🇨🇳 📍办公地点：菲律宾Makati ⏰工作时间：弹性制度 | 享集团标准假期 💵薪资：面议（3年+经验者优厚） ━━━━━━━━━━━━━━ 🔥【核心职责】 1️⃣ 主导BingoPlus平台全渠道视觉体验设计 2️⃣ 优化产品视觉呈现，提升品牌认知度 3️⃣ 创新设计思维，突破品牌平面视觉瓶颈 4️⃣ 统筹整体页面风格&重点活动视觉设计 ━━━━━━━━━━━━━━ 🎓【任职要求】 ✅ 艺术类大专以上学历（视觉/动画/数字媒体优先） ✅ 3年+实战经验，成熟设计技法+系统理论 ✅ 精准品牌/产品分析能力，逻辑思维清晰 ✅ 极致审美追求+艺术敏锐度 ✅ 强沟通力+创新意识+高责任心 ━━━━━━━━━━━━━━ 🌟【加分项】 ✔️ 有游戏化产品/社交平台设计经验 ✔️ 熟悉品牌视觉系统搭建 ✔️ 插画/动态视觉设计能力 ✔️ 中英双语流畅沟通 ━━━━━━━━━━━━━━ 📮【应聘方式】 …
6 Mar 2025, 06:49 UTC235 viewsread 11 August 2026
🔧🌟 高级系统工程师/Senior System Engineer 🌐💻 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心职责 | 企业IT基石守护者】 ✅ 全域IT基础架构设计、运维与战略优化 ✅ 构建安全防线：系统监控/灾备方案/攻防演练 ✅ 🚨 重大故障应急响应与技术团队协作攻关 ✅ 推动流程标准化：安全加固/自动化升级/合规落地 ✅ 📚 知识库建设（项目文档/操作手册/FAQ全生命周期管理） ✅ 🎓 员工IT技能培训与新技术布道 ✅ 7×24关键业务系统护航 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【任职要求 | 硬核技术门槛】 🔹 5年+企业级IT运维经验（千人规模优先｜💎标杆案例加分） 🔹 微软生态专家：AD/Exchange/Office全栈掌控 🔹 云端混合架构实战：Hybrid Azure AD迁移/Exchange Online部署 🔹 Microsoft 365深度玩家｜Intune终端统一管理大师 🔹 …
6 Mar 2025, 06:48 UTC201 viewsread 11 August 2026
🛠🌟 系统工程师/System Engineer | 企业数字基座建造师 🌐🔒 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 智能运维指挥官】 ❶ 🌉 企业级IT基础架构全生命周期管理（规划→部署→优化） ❷ 🛡 系统安全三叉戟：实时监控/攻防演练/灾备方案实施 ❸ 🚨 7×24小时故障响应 & 跨团队技术攻坚协作 ❹ 📊 流程再造：持续推动自动化运维与合规升级 ❺ 📚 知识图谱构建：项目文档/操作手册/FAQ体系化管理 ❻ 🎓 员工IT赋能培训与技术布道 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【能力图谱 | 技术硬指标】 🔹 5年+企业IT运维实战（🌟千人规模企业经验优先） 🔹 微软生态专家：AD/Exchange/Office全栈掌控 🔹 ☁️ 混合云架构师：Hybrid Azure AD迁移/Exchange Online部署 🔹 Microsoft 365管家 & Intune终端管理达人 🔹 🖥 Vmw…
6 Mar 2025, 06:48 UTC173 views1 reactionsread 11 August 2026
🔄🌟 应用工程师/Application Engineer | 企业数字流程架构师 📈💼 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 业务系统指挥官】 ❶ 🛠 全生命周期维护企业核心业务系统（权限/流程/账号） ❷ 🚨 7×24 SLA保障 & 故障三级响应机制 ❸ 🔍 跨部门业务流程解构与数字化转型需求挖掘 ❹ 📊 解决方案可行性评估与业务目标精准匹配 ❺ 🌀 工作流持续优化引擎（BPMN建模/自动化升级） ❻ 🤝 端到端交付：从UAT测试到用户培训全链路管理 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【能力矩阵 | 技术+业务双驱动】 🔹 2年+企业级系统运维经验（🚀Larksuite深度使用者优先） 🔹 📌 人事系统专家：考勤/薪资/绩效模块全流程掌控 🔹 💰 财务系统能手（🌟Microsoft Dynamics经验加成） 🔹 ☁️ AWS云服务：IAM策略/EC2/RDS/S3精调大师 🔹 📊 Jira全栈…
❤1
6 Mar 2025, 06:48 UTC150 viewsread 11 August 2026
🔭🚨 高级业务运维/Senior SRE | 数字业务护航官 🌐⚡️ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 系统稳定性建筑师】 ❶ 🔍 全链路业务洞察：解构产品线+中后台架构，输出优化蓝图 ❷ 🏗 高可用架构设计：稳定性/安全/扩展性三位一体方案 ❸ 🚑 故障急救专家：疑难问题攻坚（MTTR缩短30%+） ❹ 📜 标准化体系构建：SRE文档库&自动化运维框架 ❺ 🌩 技术雷达：追踪混沌工程/可观测性/智能运维前沿 ❻ ⚙️ 性能调优大师：定位系统瓶颈，吞吐量提升实战 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【硬核准入标准】 🔹 3年+互联网运维经验（🌟混合云/百万QPS架构实战优先） 🔹 🌐 网络基石：TCP/HTTP/DNS精研（CCNA+认证标配） 🔹 ☁️ 多云指挥官：阿里云/华为云/AWS组件深度运维 🔹 ⚡️ 高阶技能树： 服务治理框架（Istio/Spring Cloud） 混沌工程演练（C…
6 Mar 2025, 06:48 UTC130 viewsread 11 August 2026
🛡⚙️ 业务运维/SRE | 数字业务守夜人 🌐🕒 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心职责 | 永不停机的守护者】 ❶ ⏰ 7×24业务哨兵：保障亿级流量业务零中断 ❷ 🚀 发布流水线指挥官：CI/CD部署优化+灰度发布策略 ❸ 🔍 架构侦探：容灾设计/性能调优/隐患清除专项 ❹ 🛠 标准化先锋：制定SLA规范&自动化运维手册 ❺ 🌩 云上作战专家：混合云资源调度与成本优化 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【能力图谱 | 硬核指标】 🔹 2年+Linux运维实战（🔥百台服务器集群管理经验） 🔹 🐧 Linux内核调优专家｜Nginx高可用架构师 🔹 🌐 网络协议全解析：TCP/HTTP/DNS（🌟CCNP认证加成） 🔹 ☁️ 多云运维：阿里云/华为云/AWS组件实战 🔹 🌍 CDN掌控者：流量调度/故障排查/供应商管理 🔹 🚦 Web业务护航：高并发场景SLA保障经验 🔹 🚨 7×24战备状态，5分钟应急…
6 Mar 2025, 06:48 UTC122 viewsread 11 August 2026
🖥🔧 Linux运维/Linux System Engineer | 基础设施架构师 🐧⚡️ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 系统中枢守护者】 ❶ 🌐 基础架构运维：DNS/NTP/SaltStack高可用集群调优 ❷ 🧩 中间件生态：RabbitMQ/Redis/Kafka集群性能压榨 ❸ ☁️ 云平台运维：OpenStack虚拟化+Ceph存储系统全栈掌控 ❹ 📊 监控体系构建：Zabbix/Prometheus/Grafana/ELK精准布控 ❺ 🛠 自动化武器库：从批量部署到故障自愈全链路设计 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【硬核能力矩阵】 🔹 3年+互联网运维实战（🔥千节点级集群管理经验） 🔹 🐧 Linux宗师：内核调优/故障排查/安全加固全精通 🔹 云原生专家： OpenStack组件深度运维（Neutron/Cinder/Nova） Ceph存储：CRUSH算法调优/故障…
6 Mar 2025, 06:47 UTC96 viewsread 11 August 2026
🔍💾 高级数据库管理员/DBA | 数据动脉守护者 🛡📈 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 数据生命线捍卫者】 ❶ 🏗 数据库架构设计与SLA护航（亿级TPS场景优化） ❷ 🚨 7×24应急响应：故障恢复/数据补入/性能调优 ❸ 🌉 跨版本升级大师：PSU补丁/MySQL大版本迁移 ❹ 🔄 数据迁徙专家：热迁移/容灾切换/OGG同步监控 ❺ 🧹 数据治理管家：空间管理/碎片整理/历史数据清理 ❻ 📊 监控生态：Zabbix+PMM+Grafana黄金监控三角 ❼ 🤖 自动化运维：备份策略/RMAN闪回/日常任务脚本化 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【硬核技术门槛】 🔹 3年+海量数据库运维经验（🔥PB级数据处理实战） 🔹 🐧 Linux内核级调优专家（CentOS深度玩家） 🔹 多数据库全栈掌控： Oracle（DG容灾/RMAN/OGG） MySQL（主从集群/性能压榨） TiDB分布…
6 Mar 2025, 06:47 UTC79 views1 reactionsread 11 August 2026
🔐🛡 安全工程师/Security Engineer | 云盾架构师 ☁️💻 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🚀 【核心使命 | 数字边疆守卫者】 ❶ ☁️ 云安全架构设计：AWS/华为云/阿里云全栈防护体系构建 ❷ 🔒 零信任实践：IAM策略/KMS加密/WAF规则深度调优 ❸ 🚨 攻防指挥官：7×24安全监控/APT攻击溯源/红蓝对抗 ❹ ⚙️ DevSecOps引擎：CI/CD管道安全左移（SAST/DAST集成） ❺ 📡 威胁狩猎者：蜜罐部署/异常流量分析/漏洞预判 ❻ 🌉 合规架构师：GDPR/等保2.0/金融级合规落地 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 🎯 【硬核能力矩阵】 🔹 5年+云安全实战（🔥3年架构设计经验 | 亿级流量场景） 🔹 ☁️ 云原生安全专家： AWS安全全家桶（GuardDuty/Shield/Inspector） 阿里云盾/华为云安全中心深度配置 🔹 🛡 网络防御体系： VPC流…
👍1
6 Mar 2025, 06:47 UTC73 viewsread 11 August 2026
运维架构师/Operations Architect "岗位职责： 负责基础设施的运维管理与维护，包含服务器管理，集群管理，存储管理，监控管理，SLA管理 ； 负责运维制度规范的梳理和制定，让运维操作和流程更加标准，可控 ； 负责与工具研发团队对接，推动运维操作与流程的平台化 ； 负责基础设施稳定性体系建设，包括系统/硬件/存储的故障预防，故障发现、故障应急、故障预案，故障演练等； 负责服务器，存储，备份的部署与维护，巡检，操作变更，升级，安全加固等； 负责linux/windows操作系统的维护管理，包含登录与权限管理，系统基线，系统服务，以及常规性能分析与系统问题排查； 负责运维自动化脚本的编写，部署，更新，管理； 负责运维行业前沿技术的调研与引入（如AIOps，DevOps，FinOps等）。 任职资格： 全日制大学本科以上学历，计算机、信息技术、软件工程等专业。 精通IaaS平台架构，精通分布式存储，熟悉分布式框架资…
Showing the 12 most recent of 20 posts we hold for @DIGIPLUS_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 — 1,309,982 of 1,478,351entries 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 3 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@DIGIPLUS_HR named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@hrandrew188
named in 19 posts, 12 August 2026 – 12 August 2026
named in 19 posts, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“DIGI PLUS 岗位简章” (@DIGIPLUS_HR), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/DIGIPLUS_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.