Telegram RegisterThe public register of Telegram
Telegram profile photo for 海外招聘技术-远程或到岗

Channel

海外招聘技术-远程或到岗

@jishubumen123

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

412subscribers

+3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001676041469
TypeChannel
Username@jishubumen123
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/jishubumen123

Growth

409412410.57 August 2026 — 409 subscribers8 August 2026 — 409 subscribers14 August 2026 — 412 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +3. 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 409–412 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 16:46412+3
8 Aug 2026, 05:35409no change
7 Aug 2026, 13:33409first reading

Engagement

20 posts held, back to 18 June 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
24.5%
avg views ÷ 412 subscribers
Avg views / post
101
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 July 2026
Posts held20 (18 June 202631 July 2026)
Views total101
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:35 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.

What this channel posts

Video runtime
14s
Average length
14s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 3 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 3reactions 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 18 June 2026 to 31 July 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

31 Jul 2026, 08:34 UTC101 viewsread 8 August 2026

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

17 Jul 2026, 13:47 UTC165 viewsread 8 August 2026
Forwarded from @Jolie_HRVideo

#越南胡志明 #二郡 #产品经理 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 ♈️不压护照 ♈️不压护照♈️ 💖 1名: 高级产品经理 🔘有包网经验的 🔘产品画原型图要利索,快。 ➕学历本科以上 ➕年龄限制:36岁以内 ✅ 工作地点:🇻🇳越南/胡志明 第二郡 【不压护照】 ✅ 薪资范围:5000U-8000U ✅ 上班时间:10休4 单休 ✅ 运营项目:包网项目 ➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

9 Jul 2026, 02:54 UTC217 viewsread 8 August 2026

SEO 负责人(海外 · 自然流量获客) ❤️上班时间:10:00-20:00 (双休) ❤️工作地点:前期远程后期到岗 ❤️学历要求:本科以上 岗位职责 负责公司出海产品的 Google SEO 整体策略与增长,通过行业词、竞品词拦截等策略,获取高商业价值的自然搜索流量与线索转化。 统筹三大方向落地:内容 SEO(基于用户搜索意图的关键词研究、内容集群规划、落地页优化)、技术 SEO(站点结构、收录、页面速度、Schema、多语言 hreflang 等)、站外 SEO(高质量外链建设)。 熟悉谷歌关键词投放与分析工具,结合付费搜索(SEM)数据反哺 SEO 选词与内容策略,实现搜索协同获客。 制定 SEO 路线图,管理并带领内部团队、海外写手及外包资源高效落地。 搭建数据监控体系(GSC / GA4 / Ahrefs / Semrush),跟踪排名、流量、收录、转化及 ROI 并持续优化。 与产品、研发协作推动 SEO 需

9 Jul 2026, 02:53 UTC165 viewsread 8 August 2026

产品经理(多渠道群发 SaaS) ❤️上班时间:10:00-20:00 (双休) ❤️工作地点:前期远程后期到岗 ❤️学历要求:本科以上 岗位职责 负责多渠道群发 SaaS 产品(WhatsApp / Instagram / Line / Email / SMS)的规划、设计与迭代,服务外部企业 / 商家客户 深入理解出海商家的营销触达场景,输出 PRD,设计批量发送、联系人分组、消息模板、定时 / 自动化、数据看板等核心功能 跟进各平台 API 与政策(WhatsApp Business API、Line OA、Instagram 等),在功能与平台风控、合规之间做平衡 搭建产品数据指标体系(送达率、打开率、回复率、转化、留存),用数据驱动迭代 关注竞品与海外市场动态,参与商业化设计(定价、套餐、计费逻辑) 协同研发、设计、运营、客户成功,推进版本落地 任职要求 3-5 年 B 端 / SaaS 产品经验,有营销触达 /

9 Jul 2026, 02:47 UTC155 viewsread 8 August 2026

游戏系统策划(真金游戏|印度市场) ❤️上班时间:10:00-20:00 (双休) ❤️工作地点:前期远程后期到岗 ❤️学历要求:本科以上 岗位职责: 负责真金游戏平台系统策划,覆盖棋牌、Slots(电子)、体育及综合娱乐平台等业务模块。 负责平台核心系统设计,包括: 充值 / 提现 钱包系统 VIP成长体系 活动系统 签到系统 任务系统 返利系统 邀请裂变 用户成长体系 围绕付费转化、留存率、ARPU、流水等核心指标,持续优化商业化与运营系统。 深入研究印度市场用户行为、支付习惯及竞品运营策略,制定符合当地市场的产品方案。 编写PRD、流程图、状态图、功能说明等策划文档,并推动研发落地。 配合运营团队完成活动规划、版本迭代及数据复盘,持续优化产品体验。 任职要求: 硬性要求(必须满足) 3年以上真金游戏系统策划经验。 具有印度市场真金游戏平台项目经验(必须)。 熟悉印度本地真金游戏平台运营模式及商业体系。 专业能力:

1 Jul 2026, 02:19 UTC208 viewsread 8 August 2026

#越南胡志明 #二郡 #产品经理 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 ♈️不压护照 ♈️不压护照♈️ 💖 1名: 高级产品经理 ➕学历本科以上 ➕年龄限制:36岁以内 ✅ 工作地点:🇻🇳越南/胡志明 第二郡 【不压护照】 ✅ 薪资范围:5000U-8000U ✅ 上班时间:10休4 单休 ✅ 运营项目:包网项目 ➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

1 Jul 2026, 02:19 UTC196 views1 reactionsread 8 August 2026

#远程 #长期远程 #第三国远程 2️⃣0️⃣2️⃣6️⃣ 🇨🇭🇸🇾 第三国远程—需要苹果电脑办公 🐈‍⬛架构师 (30-40k+绩效) 🐈‍⬛服务端开发 (30+50k+绩效) 🐈‍⬛风控产品经理 (30-50k+绩效) 🐈‍⬛高级产品经理(30-50k+绩效 🐈‍⬛运维值班 (面议+绩效) 🐈‍⬛测试工程师 (25-45K+绩效) 🐈‍⬛产品经理(AI应用经验优先) 🐈‍⬛AI智能应用开发(30-45K+绩效) 🐈‍⬛JAVA开发 (30-45K+绩效) ➖薪资范围:30-45K(具体面谈) ➖上班时间:9休4 ➖ 试用期间:1-3个月(能力好可提前转正) ➖ 办公地点:远程办公/第三国 ➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

1

30 Jun 2026, 09:43 UTC208 viewsread 8 August 2026

职位名称:测试总监 办公地点:菲律宾 薪资待遇:试用期:60K-96K,转正:80K-120K +绩效 上班时间:9小时工作制,周休一天 岗位要求: 具备一线或二线金融科技(FinTech)、大型互联网、加密货币或交易所行业5年以上测试或质量管理经验。 熟悉高并发、高可用、高安全性系统的测试体系及质量保障。 具备优秀的业务理解能力,能够从业务及用户角度分析需求。 具备复杂问题分析、故障定位及生产环境问题处理经验。 熟悉分布式系统、微服务架构、性能测试、安全测试及自动化测试。 熟悉 Python、Java、Go 等至少一种编程语言,可进行自动化框架或测试工具开发。 具备优秀的团队管理、跨部门沟通及项目协调能力。 有大型金融项目全链路测试经验,擅长自动化测试者优先。 岗位职责: 负责20人以内测试团队的组建、管理、绩效考核及人才培养。 制定测试策略、测试计划及测试流程,覆盖功能、性能、安全及自动化测试。 组织团队完成测试工作,确

30 Jun 2026, 09:42 UTC191 viewsread 8 August 2026

职位名称:技术总监 (精通AI的技术专家) 办公地点:菲律宾 薪资待遇:面议 上班时间:9小时工作制,周休一天 岗位要求: 计算机相关专业本科及以上学历。 10年以上 Java 开发经验,熟悉多线程及Java核心技术。 5年以上互联网架构设计经验,熟悉微服务架构,具备 K8s 实施经验优先。 精通 Spring Boot、Spring Cloud 技术体系。 熟悉 RabbitMQ、Kafka、Zookeeper、ZeroMQ 等分布式中间件。 熟悉分布式事务、分布式日志、MQ 等技术。 精通高并发、高性能分布式系统设计、优化及缓存机制。 熟悉 MySQL、Redis、MongoDB、HBase、Memcached 等数据库及缓存技术。 熟悉 Linux 系统及 Shell 脚本开发。 至少完整负责过2个大型系统从0到1的架构设计、开发、上线及运维。 曾从0到1组建50人以上技术团队,并拥有2年以上团队管理经验,总监岗位经验不

29 Jun 2026, 08:08 UTC136 views1 reactionsread 8 August 2026
Forwarded from @Jolie_HR

#远程 #长期远程 #高级前端 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

18 Jun 2026, 06:46 UTC269 viewsread 8 August 2026

#斯里兰卡 ⭐️ 岗位 测试工程师 🔣语言要求:中文 🔣年龄 : 21-38 🔣薪资待遇 : 面议 🔣工作时间 : 9小时 🔣工作地点 : 斯里兰卡 * 不要有13A签证的,不要返聘,强烈要求面试需要开视频面试 🇭🇹 岗位需求 : 1、统招大专以上学历;3年及以上功能测试经验 2、掌握软件测试基本理论和方法、测试需求分析及测试用例设计方法。 3、熟悉软件测试流程及行业规范、能够熟练使用JIRA,禅道等缺陷管理工具优先; 4,熟悉软件抓包工具 如 fiddler、Charles、proxyman等 5,熟练掌握至少一种大型数据 库,熟练运用基本sql语句 6,熟练使用接口测试工具 如:postman jmeter 等 7、具有良好的沟通能力,强烈的责任心与团队合作精神,具有较强自驱性和拿结果能力优先; 🇭🇹 岗位职责 : 1、负责产品的全流程测试,包括参与需求分析和评审、制定测试计划、编写测试方案

18 Jun 2026, 06:42 UTC197 viewsread 8 August 2026

#迪拜 ⭐️岗位 :DBA工程师 🔣语言要求:中文/English 🔣年龄 : 21-35 🔣薪资待遇 : 面议 🔣工作时间 : 9小时 🔣工作地点 : 迪拜 🇭🇹 岗位需求 : 1.有Linux 操作经验,或计算机专业毕业,热爱IT行业 2 有oracle sql server mysql TIDB 等任意一种数据库维护经验 3 有AI操作经验优先,有自动化维护数据库经验者" 🇭🇹 岗位职责 : 1 负责各类型数据库日常维护,管理 2 排查服务故障,分析和解决疑难问题 3 监控,告警,漏洞,调优,负载均衡 入职DB,请避开以下人员 1.斯坦籍 2.俄罗斯籍 3.蒙古籍 4.新疆籍 5.穆斯林 6.回民 ➖➖➖➖➖➖➖➖➖ 🔥🔥🔥🔥🔥🔥 🥰详细请咨询以下联系方式: ⚡️:@smile686868

Showing the 12 most recent of 20 posts we hold for @jishubumen123. 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 — 41,086 of 1,481,346entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

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

“海外招聘技术-远程或到岗” (@jishubumen123), 412 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jishubumen123.

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.