#工作地点:日本京东 ☺️岗位:运维 #薪资:35K 包吃住13薪

Channel
海外IT技术招聘群
@siss67888
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
6,487subscribers
+698 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001735748156 |
|---|---|
| Type | Channel |
| Username | @siss67888 |
| Description | 选对平台,走对路,遇见更好的自己! @siss6788 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/siss67888 |
Topic
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 16:49 | 6,487 | +22 |
| 6 Nov 2026, 18:29 | 6,465 | +27 |
| 4 Nov 2026, 00:28 | 6,438 | +19 |
| 31 Oct 2026, 20:26 | 6,419 | +26 |
| 28 Oct 2026, 19:08 | 6,393 | +18 |
| 25 Oct 2026, 20:18 | 6,375 | +19 |
| 22 Oct 2026, 17:00 | 6,356 | +22 |
| 19 Oct 2026, 07:34 | 6,334 | +11 |
| 16 Oct 2026, 15:16 | 6,323 | +14 |
| 13 Oct 2026, 16:59 | 6,309 | +58 |
| 7 Oct 2026, 13:36 | 6,251 | +67 |
| 30 Sept 2026, 18:00 | 6,184 | +91 |
| 16 Sept 2026, 02:38 | 6,093 | +26 |
| 12 Sept 2026, 03:59 | 6,067 | +27 |
| 7 Sept 2026, 20:57 | 6,040 | +44 |
| 2 Sept 2026, 18:16 | 5,996 | +56 |
| 30 Aug 2026, 10:24 | 5,940 | +30 |
| 27 Aug 2026, 01:35 | 5,910 | +34 |
| 23 Aug 2026, 23:27 | 5,876 | +10 |
| 20 Aug 2026, 13:26 | 5,866 | first reading |
Engagement
55 posts held, back to 15 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 29.9%
- avg views ÷ 6,487 subscribers
- Avg views / post
- 1,940
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 55 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.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 55 (15 July 2026 – 14 November 2026) |
| Views total | 38,801 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 17: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.
What this channel posts
- Photos
- 8
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 14 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 4 of 20 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
远程成人aigc
#工作地点:马来新山_不压护照 ☺️岗位:产品专员岗位要求(BC 行业) #岗位职责 1. 协助研究同类产品,进行竞品调研与分析,每月按时输出行业内的竞品报告。 2. 能顺利将业务需求整理为清晰的功能说明、业务流程及产品需求文档(PRD)。 3. 负责前台及运营后台的交互原型设计,明确页面逻辑、操作流程、业务规则与异常状态。 4. 跟进设计、研发、测试及上线流程,及时处理需求疑问,参与功能验收,确保交付符合需求。 5. 协助维护产品文档规范及需求清单,保证信息准确、可追溯。 #任职要求 1. 具备 3年及以上互联网产品相关经验,有 BC、游戏、线上娱乐或支付类产品经验者优先;优秀产品助理亦可考虑。 2. 熟悉产品需求从收集、分析、设计到上线验收的基本流程,能够独立跟进范围明确的功能模块。 3. 熟练使用 Figma、Axure等至少一种原型工具,能够清晰表达页面结构、交互逻辑和状态变化。 4. 具备良好的文档能力,能写清…
#岗位:审计专员 (不要中国籍) #薪酬范围:15,000 RMB起 #工作地点:菲或迪 #工作时间:9小时 月休6 #岗位详情: 1. 财务专业毕业,有会计经验, 2. 有流程,风险管理经验的优先考虑 3. 沟通能力好,抵抗能力强和管理团队能力 4. 从事或有以上相关工作经验的优先考虑 5. 有审核财务报表和内控流程的相关经验 6. 要求外籍,英文沟通流利优先
#工作地点:泰国_月休6天 ☺️岗位:产品经理(AI向) #薪资:53-67K #要求:做过大模型效果评测、能自己核对 AI 输出并解释误判、简历头衔与实际一致"筛选;AI 工具用得熟不能替代判断能力 🤩咨询: @siss6788
#工作地点:泰国居家 #招聘岗位:产品经理(区块链 / 钱包 / C2C 方向) #薪資:面議 我们正在寻找一位熟悉区块链、数字资产钱包及 C2C 撮合业务的产品经理,负责钱包、交易撮合及法币入金相关产品的规划与迭代,推动需求落地,提升交易体验与资金安全。 一、岗位职责 产品规划与需求设计 深入理解用户需求及业务场景,制定产品规划与迭代方案,梳理业务流程,独立输出产品原型、需求文档(PRD)及验收标准。 钱包产品建设 负责数字资产钱包及 Web3 热钱包相关功能设计,覆盖多链资产展示、充值提现、转账收款、交易记录及私钥管理方案等核心模块。 C2C 交易与撮合设计 挂单、订单撮合、付款确认、放币、取消及申诉等流程设计,完善交易规则、额度控制与异常处理机制。 法币入金通道建设 深入调研并对接全球主流法币入金渠道(如Simplex, MoonPay, Banxa, Mercuryo等第三方服务商,或银行API),设计流畅…
远程外籍客服、远程Flutter #35岁以下视频面试 #愿意发护照首页和身份证证件照片的再投简历
远程Java架构师 国籍:不限 薪资:30-60K RMB/月 工作地点:不限 岗位职责 1、负责公司核心系统的开发和架构工作 2、参与制定系统开发规范,确保开发过程符合规范要求,并跟踪业界新技术动态,推动技术创新和落地。 3、负责解决系统架构中的关键问题,确保系统稳定运行。 任职要求 1、统招本科及以上学历。 2、5年以上使用JAVA开发的经验,对于用过的开源框架,能了解到它的原理和机制。 3、对Elasticsearch、Kafka、canal、rocketMQ、redis等有源代码分析问题经验,并实际解决业务问题。 4、熟悉 Docker、Kubernetes 、Service Mesh 等云原生相关技术。 5、具有较强的独立发现问题、解决问题的能力,具有高度的技术热情和责任感。 6、擅长系统分析与架构设计,至少有一个大型项目基础及应用架构完整设计经验。 7、能够熟练的使用各种AI开发工具,能够使用AI解决项目中的…
#工作地点:菲律宾(居家/写字楼) #要求:外籍非中国籍(会中文/越南语) #岗位:人事(居家办公)、翻译(居家办公)、客服(可不用会中文)、推广 🤩咨询: @siss6788
#工作地点:泰国/日本 (可以先远程一个月后来泰国) ☺️岗位:JAVA主管 (高并发互联网项目的经验 & 管理经验) #工作职责: 1 技术战略与架构规划:参与公司核心系统的应用架构、技术架构与数据架构的整体规划与设计,制定清晰、可演进的技术路线图,主导核心系统的微服务架构演进与落地。 2 领域建模与架构攻坚:深入理解公司业务架构进行领域建模,主导关键系统的架构重构、技术选型与核心组件设计,攻克高并发、大数据量、高可用、高一致等核心场景的技术难题。 3 工程效率与研发效能提升:负责研发效能体系的规划与建设,建立覆盖需求、开发、测试、发布的全流程效能度量指标体系;推动 CI/CD、自动化测试、代码质量门禁等工程基础设施建设,主导 AI 辅助研发(代码生成、智能评审等)工具链的引入与落地,持续提升团队交付效率与工程质量。 4 系统稳定性与性能治理:建立可观测性、SLI/SLO、容量管理、故障响应与复盘改进机制,持续优化…
远程数值策划 #35岁以下视频面试
#工作地点:曼谷办公/压护照 ☺️岗位:运维工程师(IM即时通讯方向) #岗位职责 负责 IM 即时通讯系统的部署、维护、监控及性能优化,保障系统 7×24 稳定运行。 负责 Kafka、Redis、Zookeeper、etcd、MinIO、MySQL 等组件的部署、升级及故障处理。 负责 Kubernetes 生产环境的部署、维护、升级、扩容及故障排查。 处理线上故障、性能瓶颈及高并发场景下的系统优化。 负责 CI/CD、自动化脚本及运维流程优化。 负责系统监控、容量规划、告警及应急预案建设。 任职要求 大专及以上学历,5年以上运维经验,2年以上 IM 或大型分布式系统运维经验。 Linux 系统基础扎实,网络基础良好,具备较强的系统及网络故障排查能力。 熟练掌握 Linux、Shell,熟悉 Python。 熟练掌握 Kafka、Redis、Zookeeper、etcd、MinIO 等分布式组件。 熟练掌握 Kubern…
Showing the 12 most recent of 55 posts we hold for @siss67888. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @siss67888 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 7 August 2026
- Most recent seen missing
- 7 August 2026
- Median time before seen missing
- 3 days
- Seen missing in the last 30 days
- 0
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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@remote_cn · 25,947
Telegram ranks this channel #14 of 85 here — alongside 84 others — read 15 September 2026
@XCRLZP · 92,416
Telegram ranks this channel #18 of 82 here — alongside 81 others — read 13 August 2026
@qiuzhi0999 · 55,454
Telegram ranks this channel #22 of 34 here — alongside 33 others — read 29 August 2026
@abetterpathxyz · 32,809
Telegram ranks this channel #24 of 90 here — alongside 89 others — read 4 September 2026
@DeJob_official · 47,995
Telegram ranks this channel #29 of 94 here — alongside 93 others — read 27 August 2026
@zii33 · 100,154
Telegram ranks this channel #44 of 78 here — alongside 77 others — read 16 August 2026
@qiuzhi008 · 231,891
Telegram ranks this channel #44 of 72 here — alongside 71 others — read 11 August 2026
@qzzpfabu888 · 606,835
Telegram ranks this channel #45 of 72 here — alongside 71 others — read 9 August 2026
@feixingzhe_qzzz · 610,591
Telegram ranks this channel #50 of 67 here — alongside 66 others — read 9 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“海外IT技术招聘群” (@siss67888), 6,487 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/siss67888.
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.