Channel
@behireit
On this record: Growth · Engagement · Posts · Citations · Cite this entry
21subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001960772738 |
|---|---|
| Type | Channel |
| Username | @behireit |
| Description | 咨询请私聊 @behiree |
| Created | 14 March 2024 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/behireit |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 14:46 | 21 | no change |
| 8 Aug 2026, 05:01 | 21 | first reading |
8 posts held, back to 14 March 2024 — 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 8 posts for this entry, the most recent from 8 January 2026. An engagement rate over an empty window would be a number about nothing.
🧂⚽🏀🏈 后端工程师 ⚾🥎🎾🏐 ✔上班地点：#斯里兰卡 ✔语言：中文 ✔工作时间： 9休4 ✔国籍： 不限 ✔薪资： 面议 20-45k ➡岗位要求 1、具有良好的协作沟通能力，高度的责任心与职业道德； 2、至少三年以上golang,java及php中的一种语言开发经验； 3、至少熟悉java(sping-cloud套件)、golang(gin,fasthttp)、php(laravel)中的一种； 4、了解mysql，redis的底层实现机制，并能在实际应用中利用其原理来很好的来解决问题，有过真实解决案例为加分项； 5、对高并发高可用有一定的了解； 6、熟悉tcp、http、websocket协议； 7、对ES、kafka、rabbitmq有一定的使用经验 ➡岗位职责： 1、负责各个模块业务前后台开发； 2、负责mysql表设计，redis缓存设计等； 3、从技术层面给开发，产品，需求方提出合理的建议； 🤢🤮😐😬 …
🧂⚽🏀🏈UI/UX高级设计师（外包）⚾🥎🎾🏐 ✔上班地点：#马来西亚 或 #泰国 ✔语言：中或英文（fluently in english or chinese ） ✔工作时间： 9休4 ✔国籍： 不限 ✔薪资： 面议 20-40k ➡岗位要求 • 美术、设计类相关专业，5年以上互联网产品设计经验，专业本科及以上学历（优先考虑）； • 参与产品的视觉研究、设计流行趋势分析和体验规划，主导设定整体视觉风格和UI设计； • 有足够的敏感度，找到并抓住业务、用户痛点，需求对接过程中快速理解、有思考，能够独立完成设计落地方案并验证复盘； • 重视细节，具备良好的产品思维和用户同理心，能够参与用户研究、交互设计、设计原型开发等工作中去； • 良好的适应能力和承压能力，能够快速融入团队，能够做好专项或业务需求的组织、沟通、协作、产出、推动等相关工作内容； • 应聘者请务必提交作品集。" ➡岗位职责： • 能够独立负责多种类产品的UI风…
🔥🔥🔥 🔥🔥🔥🔥🔥🔥🔥 🤢🤮😐😬 🚨🚨🚨测试工程师🚨🚨🚨 📍 #斯里兰卡 🇱🇰 🇱🇰 9休4，20-30k ➡岗位要求 1、统招大专以上学历；3年及以上功能测试经验 2、掌握软件测试基本理论和方法、测试需求分析及测试用例设计方法。 3、熟悉软件测试流程及行业规范、能够熟练使用JIRA，禅道等缺陷管理工具优先； 4，熟悉软件抓包工具 如 fiddler、Charles、proxyman等 5，熟练掌握至少一种大型数据库，熟练运用基本sql语句 6，熟练使用接口测试工具 如：postman jmeter 等 7、具有良好的沟通能力，强烈的责任心与团队合作精神，具有较强自驱性和拿结果能力优先；" ➡岗位负责 1、负责产品的全流程测试，包括参与需求分析和评审、制定测试计划、编写测试方案和测试用例设计； 2、负责产品的功能、性能方面的测试工作，执行测试用例，提交BUG，并进行BUG跟踪和回归测试，直到BUG解决； 3、分析并推动…
亲爱的友友们 技术更新岗位 具体私聊我，整年招聘 111111111111111111111111111111111111111111 #菲律宾 🇵🇭🇵🇭 卡加延 支付平台 telegram : @behiree 1 架构师 20k-40k + 绩效 2 架构-高级Java开发 20k-50k + 绩效 3 测试 高级测试 20k-50k + 绩效 4 测试 中级测试 20k-25k + 绩效 5 自动化高级测试 20k-50k + 绩效 6 高级产品 20k-50k + 绩效 7 大数据高级开发 20k-50k + 绩效 8 服务端开发 20k-50k + 绩效 9 算法工程师（风控方向） 20k-50k + 绩效 10 策略分析师（风控方向） 20k-35k + 绩效 11 风控产品经理 20k-50k + 绩效 12 风控数据分析 20k-50k + 绩效 13 高级设计师 20k-50k + 绩效 14 ZF-高级…
菲律宾🇵🇭🇵🇭 卡加延 支付平台 telegram : @behiree 1 技术总监 面议 2 架构师 30-50K+绩效 A 1.5，B1.2, C 1.0 3 高级Java开发 30-50K+绩效 A 50%，B20%, C 0% 4 高级测试 25K-35K+绩效 A 1.5，B1.2, C 1.0 5 中级测试 20K-30K+绩效 A 50%，B20%, C 0% 6 自动化/功能测试工程师（测试开发）30k-50k + 绩效 A 50%，B20%, C 0% 7 大数据高级开发 40K-50k+绩效 A1.5 B1.2 C1.0 8 服务端开发 40K-50k+绩效 A 50%，B20%, C 0% 9 高级Java开发 24K-45K+绩效 A 50%，B20%, C 0% 10 高级WEB前端开发工程 30K-50K+绩效 A1.5 B1.2 C1.0 11 高级flutter开发工程 30K…
斯里兰卡 Srilanka 🇱🇰9休4 1 外籍外包业务开发 2 安卓工程师 3500-8000u 3 IOS工程师 3500-8000u 4 前端 3500-8000u 5 总经办专员 1400-2200u 6 外籍中高级产品经理 3500-8000u 迪拜 Dubai 🇦🇪 9休4 1 桌面运维 3500-8000u 2 网络中高级工程师 3500-8000u 3 安全专家 3500-8000u 4 运维开发工程师 3500-8000u 5 CDN基础架构研发工程师研发 3500-8000u 6 运维工程师（中高级） 3500-8000u 7 高级红队渗透工程师 3500-8000u 8 行政专员 1400-2000u telegram : @behiree
telegram :@behiree 9 休 4 后端（架构师/专家） 45K-90K 后端（架构师/专家） 45K-90K 网络工程师 45K-75K 网络安全工程师 面议 DBA 中高级 面议 DBA架构师-专家 45K-90K TRANSLATOR 12K-15K 安全专家 60K-150K 安全工程师 20K-40K 安全工程师-攻防方向 20K-150K 大数据-初中高级 面议 大数据-架构师-专家级 45K-90K 运维专家 60K-100K CDN基础架构师专家研发 面议 UI/UX Designer 面议 运维开发工程师 面议 资深测试工程师 面议 设计专家 45K-75K 产品专家 45K-90K 前端技术专家/前端架构师 45K-90K 前端工程师 面议 运维安全工程师 面议 运维工程师（中高级） 面议 产品经理 面议 安卓技术专家/安卓架构师 45K-90…
Channel created
Showing the 8 most recent of 8 posts we hold for @behireit. 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 — 759,896 of 1,481,243entries 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.
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.
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.
“BEHIRE 技术 IT position” (@behireit), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/behireit.
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.