Channel
@Technical168
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
164subscribers
-9 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001895029059 |
|---|---|
| Type | Channel |
| Username | @Technical168 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/Technical168 |
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 25 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 06:14 | 164 | -5 |
| 2 Sept 2026, 07:23 | 169 | -1 |
| 26 Aug 2026, 22:13 | 170 | -1 |
| 19 Aug 2026, 15:07 | 171 | -2 |
| 13 Aug 2026, 05:06 | 173 | no change |
| 13 Aug 2026, 01:17 | 173 | first reading |
20 posts held, back to 9 March 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 1 page of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 reactions 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 9 March 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.
【更新】6/8 目前我们开放以下招聘岗位： • AIGC（远程） • 产品经理（远程/驻场）- 支付平台经验(熟悉USDT支付流程) / 包网经验 • 安卓逆向工程师（远程/驻场） 以上岗位需求紧急，请优先推荐合适候选人并加快推进流程。感谢大家的支持与配合！ 备注： • 提交简历时，请务必确认岗位类别准确匹配。 • 除远程岗位外，其他岗位将先远程工作约1个月，之后转为驻场办公。 • 请根据上述招聘需求投递相关岗位的简历，除列明岗位外，当前暂无其他招聘需求。 地点：马来西亚 @xiaoxiong333
JAVA高级开发【远程】：1名 基础薪资：20k-35k（13薪） 个人月奖金：基础薪资10% 公司季度奖金：根据公司增长目标，享受对应岗位奖金 其他要求： 1. 按照公司精英化战略，本岗位为一线岗位，需全心投入项目，没有那么多分心的事 岗位职责 1. 参与公司saas项目的建设工作，致力于帮助业务提升用户产品体验，实现快速用户增长 2. 负责相关系统功能的设计与代码编写，保证业务需求的高效、高质量实现； 3. 参与各系统的架构规划、性能优化、稳定性保障、安全等工作； 4. .解决系统开发和运行过程中的技术缺陷和线上问题，持续优化系统质量和性能。 任职要求 1. 5年以上互联网一线开发经验 2. 熟练掌握Java开发技术栈，对分布式架构组件有实践经验，熟悉设计模式、高可用性与容错保障等知识体系; 3. 具备优秀的业务分析能力、方案整合能力和解决问题能力，能够将复杂的业务问题转变为清晰的系统需求 4. 做事有责任感和主动性，…
新增岗位： 远程 安卓逆向工程师 岗位职责 1、负责 Android APK、SDK 的静态反编译与动态调试，梳理业务逻辑、接口协议、签名校验、防篡改机制。 2、对梆梆、乐固、爱加密等加固应用进行脱壳，对抗反调试、内存检测、环境检测。 3、Java 层与 SO 原生层逆向分析，还原加密算法（AES/RSA/ 自定义加密），还原网络请求协议。 4、使用 Frida、LSPosed 完成 Hook 开发，编写 Python 脚本复现接口，开发自动化工具。 5、研究客户端安全防护方案，完成攻防对抗，输出技术文档与工具。 任职要求 1、熟练使用 Jadx、Apktool、IDA、Frida、Charles 等全套逆向工具，独立完成 APK 分析。 2、精通 Dex 层逆向，掌握 ARM64 汇编，能够分析 so 库逻辑，修复校验代码。 3、拥有各类商业加固脱壳实战经验，能够处理花指令、混淆、VMP 虚拟化壳。 4、熟练 Python，…
高级架构师（Java / 分布式系统） Java技术主管 / Java研发主管 前端主管 前端总监 测试主管 测试总监 ➡️ 先远程后到岗泰国 @xiaoxiong333
（资深测试工程师 ） 国籍：越南，马来籍优先， 大陆籍 要求人在第三国+有稳定长期签证 综合薪资：15-20k，远程岗位，没有补贴 ✅【任职要求】 1. 行业背景： 具备 3-5 年软件测试或开发相关岗位经验，拥有博弈类游戏产品及其管理后台的实战经验，具有棋牌、老虎机测试经验者优先。 2. 核心工具能力： 掌握 Chrome 开发者工具，能运用 Console、Network、Application 等面板进行问题定位与数据分析。 3. 独立交付能力： 具备文档编写能力，能独立交付测试计划、测试案例及测试报告。 4. 业务洞察力： 对博弈类游戏的结算、账变、功能逻辑有理解，能拆解业务并进行风险预判。 5. 沟通与素质： - 具备简体中文书面与口头表达能力，反馈结果清晰。 - 熟悉主流 Bug 管理系统的使用及工作流。 6. 软技能： 具备问题分析能力与主动提问意识，能在压力环境下确保测试工作的轻重缓急。 ✅【岗位职责】 …
❤1
@xiaoxiong333
密码打开：abc@1230. @xiaoxiong333
急招！ —————————————— 技术总监-2位 运维总监-2位 —————————————— 薪资面议 地点：菲律宾 @xiaoxiong333
项目经理 (包网） ——————————————- 到岗泰国 薪资范围：25-40k ——————————————— ✅ 职责: 1.项目整体的立项、规划等工作 2.项目风险控制、跟踪解决影响项目进度相关问题 3.项目团队管理及计划 4.项目会议组织 5.项目资料的收集、整理、建档、保存 6.项目需求承接等 ✅ 要求: 1.任何行业，专业项目管理经验至少3年 2.对jira、conf等同类软件的熟悉 3.对于项目管理具备一定的专业知识 4.对于人力规划利用有自己的实验案例 5.具备一定的风险评估能力 6.良好的沟通，协调能力 7.良好的抗压能力 @xiaoxiong333
密码打开：abc@1230. @xiaoxiong333
Java主管 (包网项目） 国籍不限 泰国办公 薪资50-70k ✅ 要求： 1、计算机科学、软件工程或相关专业本科及以上学历。 2、8年以上Java开发经验，3年以上系统架构设计经验、3年以上管理经验。 3、有大规模分布式系统设计和开发经验。 4、精通Java编程，熟悉Spring、Spring Boot、mybatis-plus等主流框架。 5、深入理解微服务架构、分布式系统设计及实现。 6、熟悉数据库技术，包括SQL和NoSQL数据库（如MySQL、ES等）。 7、具备出色的系统分析和解决问题能力，能够处理复杂系统中的技术难题。 8、有性能调优、故障排查和问题解决的实战经验。 9、良好的沟通能力和团队协作能力，能够与团队成员和其他部门有效合作。 10、具备良好的学习能力和技术敏感性，能够快速掌握和应用新技术。 ✅ 职责： 1、负责公司核心系统的架构设计和优化，确保系统的高性能、高可用性和高扩展性。制…
马来西亚-吉隆坡市区 ✔️Java 开发工程师（加急） ✔️产品经理（加急） ✔️运维工程师 ✔️安卓逆向工程师 ✔️架构师 ✔️AIGC人工智能自动生成内容（远程/驻场） 备注： • 除运维岗位需直接驻场外，其余岗位将先进行约1个月远程工作，随后转为驻场。 • 30-55k 单休 @xiaoxiong333
Showing the 12 most recent of 20 posts we hold for @Technical168. 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.
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.
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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“（技术岗位）招聘！” (@Technical168), 164 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/Technical168.
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.