职位名称:#安卓逆向 – 薪资待遇:面议 工作时间:9小时 / 月休4天 工作地点:远程(不限地区) 办公模式:#远程办公 #安卓 #安卓逆向 岗位职责: 1、负责 Android 逆向、反编译、破解工作; 2、负责加固产品脱壳分析,VMP 加固分析研究; 3、跟踪和调研行业实践和最新的技术. 岗位要求: 1、有较强的 App 逆向分析能力,熟悉 Smali,so 汇编; 2、掌握常用的 apk 逆向工具,熟悉静态分析; 3、熟练进行反编译,了解 Android 打包流程; 4、熟悉各种 Hook 技术的原理,以及 hook 框架的使用; 5、熟悉 dex 动态调试,有 native 层 hook 经验; 6、对工作认真负责,有良好的沟通能力,能够融入团队. 满足以下条件之一的优先录用: 1、有一定的反混淆、脱壳经验优先; 2、有 Android 系统源码过研究经验优先; 3、有 支付相关项目经验优先;
Channel
技术/产品/运维/设计岗位JD
@ITTECH009
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,490subscribers
+2 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 | -1001912601809 |
|---|---|
| Type | Channel |
| Username | @ITTECH009 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ITTECH009 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 14:17 | 1,490 | -1 |
| 11 Aug 2026, 06:02 | 1,491 | +2 |
| 8 Aug 2026, 16:15 | 1,489 | +1 |
| 7 Aug 2026, 21:47 | 1,488 | no change |
| 7 Aug 2026, 17:33 | 1,488 | first reading |
Engagement
20 posts held, back to 7 May 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 26.4%
- avg views ÷ 1,490 subscribers
- Avg views / post
- 393
- 7 posts measured
- Reaction rate
- 0.275%
- reactions ÷ views · ER floor
- Posts in window
- 7
- 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 1 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 20 (7 May 2026 – 21 July 2026) |
| Views total | 2,752 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 21:47 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
6 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 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 7 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 6reactions 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 7 May 2026 to 21 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
职位名称:#AIGC 薪资待遇:面议 工作时间:9小时 / 月休4天 工作地点:远程(不限地区) 办公模式:#远程办公 #AIGC 工作职责 1. 负责基于 Lark(飞书)生态的 AI Agent、机器人、智能工作流等系统设计与开 发,推动业务智能化升级。 2.负责企业级 RAG(Retrieval-Augmented Generation)知识库体系建设,包括知 识接入、向量化、检索优化、权限体系及 AI 应用集成。 3. 深度参与 AI 应用全生命周期建设,包括需求分析、技术方案设计、开发实现、 部署上线、性能优化及稳定性保障。 4. 基于大模型能力(OpenAI / Anthropic / 国内大模型等),构建业务 Copilot、 智能助手、自动化运营工具等 AI 应用。 5. 负责 Prompt Engineering、Tool Calling、Workflow 编排、多 Agent 协同等能 力建…
职位名称:#高级前端工程师(Web / Hybrid / Vue3 / AI 工程化) 薪资待遇:面议 工作时间:9小时 #月休8+法定假 工作地点: #Serbia #塞尔维亚 办公模式: #现场办公(宿舍办公/工签办理好在办公室上班) #前端工程师 #高级前端工程师 岗位职责 负责核心业务前端架构设计与落地,覆盖 Web / H5 / Hybrid(App 内嵌)多端场景 主导复杂交互与状态管理设计(高频更新、实时数据、复杂表单、长列表等) 基于 Vue3 构建可维护的业务体系,而不是简单组件堆叠 推动前端工程体系建设(构建、发布、监控、性能优化) 参与 Hybrid 技术方案(WebView / JSBridge / 端能力调用) 熟练使用cursor/claude/trae 在团队内推动 AI 辅助开发流程落地(代码生成、Review、测试等) 任职要求(核心能力) 5 年以上前端经验,有中大型复杂系统…
职位名称:#高级工程师 (大模型方向) 薪资待遇:面议 工作时间:9小时 #月休8+法定假 工作地点: #Serbia #塞尔维亚 办公模式: #现场办公(宿舍办公/工签办理好在办公室上班) #高级工程师 职位描述 负责大模型相关能力在业务侧的落地,同时跟进主流技术演进,做必要验证并推动可用方案进入生产环境。 工作内容 参与大模型在实际业务中的应用建设(如客服、运营工具、内容处理,研发全流程等),从方案到上线持续迭代 设计并实现相关工程能力,包括检索增强(RAG)、工具调用、上下文管理、多模型接入等 抽象通用能力,减少重复开发,支持多业务复用 跟进主流模型与框架变化,做小规模验证,判断是否值得引入 在团队内推进AI辅助开发实践,研发全流程的全栈开发(设计生成、架构生成、prd生成、代码生成、测试辅助、简单自动化),提升研发效率 关注稳定性、延迟和成本,持续做优化 任职要求 工程基础扎实,熟悉Java / Go / Py…
职位名称:#测试工程师 薪资待遇:面议 工作时间:9小时 #月休8+法定假 工作地点: #Serbia #塞尔维亚 办公模式: #现场办公(宿舍办公/工签办理好在办公室上班) #测试 #自动化测试 岗位职责: ① 能帮助搭建整套自动化测试体系; ② 参与软件产品的需求分析,负责测试计划和测试方案的制定; ③ 负责测试环境设计及构建,软件的接口测试、功能测试和界面测试,进行问题跟踪和管理,保证软件质量; ④ 编写并完成测试相关的测试计划、设计测试数据、测试用例的执行工作。 ⑤ 提交、分析、跟踪软件缺陷,推动问题解决,保障产品质量。 任职要求: ① 计算机、通信等相关专业本科以上学历,2年以上测试工程工作经验; ② 掌握Python、JAVA、C/C++中至少一种语言,熟悉MySQL、Oracle、SQL Server中至少一种数据库的使用; ③ 熟悉软件开发过程,软件测试流程,软件测试理论和方法,熟练制定系统的测试计…
职位名称:#Java 开发工程师 薪资待遇:面议 工作时间:9小时 #月休8+法定假 工作地点: #Serbia #塞尔维亚 办公模式: #现场办公(宿舍办公/工签办理好在办公室上班) #Java #Java开发 岗位职责: ① 负责公司JAVA类项目后端开发工作。 ② 参与或直接负责需求调研和系统设计。 ③ 完成系统的核心架构实现; ④ 完成上级安排的其它工作及其他部门配合工作。 任职要求: ① 本科以上学历,计算机等相关专业,5年以上相关工作经验。 ② 熟悉SpringBoot、SpringCloud、MyBatis等开发框架。 ③ 熟悉JAVA设计模式,有模块化框架设计经验,有注解开发经验。 ④ 熟练掌握使用mysql、redis、ElasticSearch等常用存储,linux操作系统。 ⑤ 掌握MySQL等数据库开发,精通sql语句的编写,熟悉各种SQL性能优化方法。 ⑥ 有SAAS平台开发经验者优先。 …
职位名称:#Java 架构师 薪资待遇:面议 工作时间:9小时 #月休8+法定假 工作地点: #Serbia #塞尔维亚 办公模式: #现场办公(宿舍办公/工签办理好在办公室上班) #Java #Java架构师 岗位职责: ① 指导项目组软件基础架构搭建、调优,开源框架组件代码修改; ② 跟踪并督促技术架构落地,验证技术架构实现; ③ 指导开发人员按架构设计进行开发,负责解决技术架构相关疑难问题; ④ 负责异常定位和分析,并给出架构上的改进方案,通过架构优化,促进产品质量提升,提升研发效率; ⑤ 负责推进公司的技术标准与规范在产品的执行落地。 任职要求: ① 计本科以上学历,计算机等相关专业,5年以上Java平台架构设计经验; ② 扎实的Java基础,理解IO、多线程、集合等基础框架,对JVM原理有一定了解; ③ 熟悉微服务和领域设计;熟悉前后端分离的系统结构;熟悉分布式系统的设计和应用;具备高并发、海量数据系统的…
❤1
技术/产品/运维/设计岗位JD pinned «职位名称:#Java后端/前端/cocos creator/Java转devops 薪资待遇:面议 工作时间:8小时 #月休4 工作地点: #东京 #日本 办公模式: #现场办公 #A #产品经理 #产品 #Java #前端 #cocos creator/ #devops 一、全栈/运维开发工程师 负责以下一个或多个方向的工作: - 参与产品研发,围绕真实场景持续迭代。 - 打造可复用的Tools&Skills体系,提升扩展效率与规模化交付能力。 - 完善工程基建与效能体系(Telemetry、微服务质量、CI/CD…»
职位名称:#资深UI设计师(此岗位优先考虑到岗) 薪资待遇:远程美术 15-25k,日本美术 25-35k 工作时间:8小时 #月休4 工作地点: #东京 #日本 办公模式: #现场办公 #远程办公(混合) #A #UI #设计 #UI设计 远程美术要求: 需有能力办理3/5年多次往返签证 第一个月需要来日本办公,接受每年来半年左右,每次1个月-3个月出差。 资深UI设计师岗位jd 负责以下工作: - 参与产品研发,围绕真实场景持续迭代。 - 学习竞品,取长补短,不断优化产品。 - 持续塑造品牌感 需要具备的能力: - 精通Photoshop/Figma等常用软件 - 有精心设计的作品,并可以在面试时直接show off 你的作品 - 对当前主流的AI绘画、AI视频生成工具有深入的了解和丰富的实践经验 我们希望你: - 不墨守陈规:敢于质疑权威,敢于引领而非跟随; - 有品味:对产品的美感有追求 - 有强烈…
❤2
职位名称:#Java后端/前端/cocos creator/Java转devops 薪资待遇:面议 工作时间:8小时 #月休4 工作地点: #东京 #日本 办公模式: #现场办公 #A #产品经理 #产品 #Java #前端 #cocos creator/ #devops 一、全栈/运维开发工程师 负责以下一个或多个方向的工作: - 参与产品研发,围绕真实场景持续迭代。 - 打造可复用的Tools&Skills体系,提升扩展效率与规模化交付能力。 - 完善工程基建与效能体系(Telemetry、微服务质量、CI/CD DevOps、AI+研发流程)。 需要具备的能力: - 精通前端/服务端/COCOS Creator/K8S中任一技术栈 - Al-native,vibe coding重度使用者,能判断代码质量,有能力用大模型出色地完成任何项目 - 有精心维护的、你不断觉得它变成屎山然后重构/重写了的项目 - 精通Ja…
职位名称:#产品经理 #产品 薪资待遇:$6000 - $12000 / month 工作时间:9小时 #月休8 工作地点: #马来西亚 #吉隆波 办公模式: #现场办公 #远程办公(远程薪资面议) #88 #产品 我们正在打造一个全球领先的数字财富管理平台,为用户提供安全、合规、多元化的资产管理与增值服务。 🌱 岗位职责: 1️⃣ 一、需求分析与 PRD 撰写 - 负责 钱包支付(理财,支付,数字货币)产品需求文档撰写,包含功能描述、业务逻辑、异常流程、状态机定义; - 按端独立输出产品文档(APP 产品文档 / CMS 后台产品文档),结构清晰,可直接交付开发 2️⃣ 业务流程图 - 绘制完整业务流程图,覆盖正常流、异常流、边界条件,输出状态及文档 3️⃣ 原型设计 - 使用 Figma / Axure / Sketch 等工具输出中高保真交互原型,需覆盖核心交互流程和页面跳转逻辑; - 协调 UI 设计…
职位名称: #AI技术负责人(Go/Vue3)(1-2名) 薪资待遇: 面议(提供有竞争力的薪资福利) 工作时间:#月休6 工作地点:#迪拜 办公模式: #现场办公 #GC #技术管理 #AI #AI架构师 #技术负责人 我们正在建设AI Native研发团队。 开发工作已全面引入Cursor、Claude Code等AI工具,未来研发模式将以AI驱动开发为主,工程师核心职责是设计架构、管理AI开发流程、审核代码质量及推动项目交付。 岗位职责 负责核心业务系统架构设计与技术方案制定 利用AI工具完成复杂项目开发与交付 管理AI开发流程及Agent协作流程 审核AI生成代码并解决AI幻觉问题 负责关键模块技术攻关和代码质量治理 指导团队建立高效AI研发体系 任职要求 技术能力 8年以上研发经验 精通Go语言 熟悉Vue3及前后端分离架构 熟悉微服务、高并发、高可用系统设计 熟悉MySQL、Redis、Kafk…
Showing the 12 most recent of 20 posts we hold for @ITTECH009. 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 — 289,384 of 1,481,217entries 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 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.
@bnzhaopingmnl · 112,990
Telegram ranks this channel #70 of 84 here — alongside 83 others — read 15 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“技术/产品/运维/设计岗位JD” (@ITTECH009), 1,490 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ITTECH009.
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.