Channel
@holder_job_devs
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
2,458subscribers
+75 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002118394321 |
|---|---|
| Type | Channel |
| Username | @holder_job_devs |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/holder_job_devs |
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 15 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 |
|---|---|---|
| 12 Oct 2026, 15:50 | 2,458 | -3 |
| 6 Oct 2026, 00:18 | 2,461 | -4 |
| 28 Sept 2026, 19:39 | 2,465 | +18 |
| 18 Sept 2026, 16:20 | 2,447 | +4 |
| 14 Sept 2026, 05:57 | 2,443 | +15 |
| 10 Sept 2026, 13:21 | 2,428 | +5 |
| 5 Sept 2026, 03:17 | 2,423 | +9 |
| 1 Sept 2026, 10:59 | 2,414 | +5 |
| 29 Aug 2026, 19:26 | 2,409 | +3 |
| 26 Aug 2026, 10:37 | 2,406 | +2 |
| 23 Aug 2026, 15:13 | 2,404 | -3 |
| 19 Aug 2026, 23:18 | 2,407 | +18 |
| 16 Aug 2026, 21:07 | 2,389 | +3 |
| 13 Aug 2026, 09:45 | 2,386 | +1 |
| 10 Aug 2026, 06:57 | 2,385 | +1 |
| 7 Aug 2026, 16:31 | 2,384 | +1 |
| 6 Aug 2026, 22:02 | 2,383 | first reading |
20 posts held, back to 18 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.
160 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 23.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💯 | 38 | 23.8% | |
| 🔥 | 29 | 18.1% | |
| 🥱 | 24 | 15.0% | |
| 😈 | 21 | 13.1% | |
| 👏 | 17 | 10.6% | |
| 🤷♂ | 12 | 7.50% | |
| 🐳 | 10 | 6.25% | |
| 👨💻 | 9 | 5.63% |
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 20 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 160 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 18 December 2025 to 3 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.
HIRING NOW ⚫️ QA Engineer (Desktop & Mobile) $2,600+ / month (≈ 1M AMD) | Remote | Armenia #QA #ManualQA #Desktop #Mobile #Windows #macOS #Unity #Remote Cross-platform product team is looking for an experienced QA Engineer with a strong background in native desktop applications. ✦ Key Responsibilities: — Test native Windows & macOS applications. — Perform functional & exploratory testing. — Validate installs, upd…
🐳3🔥2
Yo everyone 🤣 Hola! Bonjour! こんにちは! Merhaba! Aloha! The jobs I find for this channel usually don’t make it to job boards. So there aren’t many of them. But… I think I found something 😆
💯5👏3
👻👻👻 ⚫️ Middle Full-Stack TypeScript Developer (Web2/Web3 | React + Node.js) $2,500+ Remote | Full-time #FullStack #TypeScript #React #NodeJS #Web3 #gRPC #PostgreSQL #Redis #Remote 🔴IMPORTANT: Forward the job posting when applying. Product team building at the intersection of Web2 & Web3 is looking for a developer who can deliver features end-to-end — from backend architecture to frontend UI. ✦ Key Responsibil…
🥱5💯3👨💻2😈2
👻👻👻 Middle Android Developer (Kotlin | Web3 | Compose) 🔴IMPORTANT: Forward the job posting when applying. $4,200 – $6,000 | Remote | Full-time #Android #Kotlin #Mobile #Web3 #JetpackCompose #Remote Lagrange Labs is looking for an Android Developer to build and scale a mobile app connecting users to the Lagrange Web3 ecosystem. ✦ Key Responsibilities: — Develop & maintain Android app for Web3 ecosystem access.…
🔥5
😅 Web3 Software Developer (Fullstack | TypeScript | dApps) $5,000 – $7,000 | Remote | Full-time #Web3 #Fullstack #TypeScript #React #NextJS #Solidity #dApps #Remote Lagrange Labs is looking for a Web3 Developer to build decentralized applications integrated with ZK co-processors and developer tooling for next-gen blockchain infrastructure. ✦ Key Responsibilities: — Build full-stack dApps integrated with ZK infras…
💯7🐳4😈3
My friends HIRING NOW 😹Backend Engineer (Go | Highload | Mining Infra) $3,500 – $7,000 / month | Remote (US) | Full-time #Backend #Golang #Highload #Kubernetes #Mining #Infrastructure #DistributedSystems #Remote Luxor Technology — global Bitcoin mining infrastructure platform (pool, firmware, hardware, energy & financial tools in one ecosystem) is hiring a Backend Engineer. ✦ Role Mission: Build and scale next-ge…
HIRING NOW ✅ Blockchain & AI Infrastructure Engineer (DevOps | GPU | K8s) Apply only if you have relevant experience. Don’t damage your reputation or others. $4,000 – $6,000 | Remote | Full-time #DevOps #Blockchain #AI #Kubernetes #GPU #ComputerVision #Infrastructure #Remote NeuroVision — product company building AI + blockchain infrastructure solutions, is looking for a hands-on Senior engineer (not a manager) t…
💯3🤷♂2🐳1😈1
HIRING NOW ✅ Chief Technical Officer (CTO | DeFi Perp-DEX | AI) UPDATE: $3,000+ | Remote #CTO #Web3 #DeFi #Solana #Ethereum #AI #Architecture #Crypto #Remote Ambitious startup building a next-gen decentralized perp-DEX on Solana + Ethereum with AI as a product layer. Fast execution, zero bureaucracy, direct access to founders & investors. ✦ Role Mission: Define architecture vision, design system backbone, and s…
🥱5💯4😈2🐳1
HIRING NOW ✅ Senior .NET Backend Developer (Crypto / Trading Platform) $6,000 – $8,000 net | Remote | Full-time #DotNet #Backend #CSharp #Highload #Crypto #Fintech #Trading #Remote A high-load crypto exchange / trading platform (20k+ RPS) is looking for a strong .NET Backend Developer to build low-latency, mission-critical services. ✦ Key Responsibilities: — Build high-performance microservices on C# / .NET. — …
😈2
My HRiends are complaining that many candidates apply without actually reading the job details. Quick ask to everyone here: ———- Please read the job descriptions carefully. ———- Apply only to roles that are truly relevant to your experience. Let’s respect each other’s time 🫡
💯8👏4🥱3
HIRING NOW 🔴 Senior Data Analyst (Snowflake ) #DataAnalyst #Snowflake #SQL #AWS #ETL #DataModeling #Healthcare #Remote $3,000 – $4,000 / month | Remote A global pharma-focused company is looking for a Senior Data Analyst to drive data-powered strategic and operational decisions in a high-impact environment. ✦ Job Description: You’ll work with large-scale data in Snowflake, collaborate closely with business sta…
🥱4👨💻3😈2👏1
💙 Senior+ / Lead Python Developer $5,000+ net #Python #Lead #FastAPI #Crypto #iGaming #Remote #Highload JT Marketing — a global Crypto iGaming product. Building high-load B2C platforms with a focus on scaling and top-tier architecture. ✦ Job Description: You will lead the backend team and take ownership of technical excellence. The role combines hands-on architecture design with team management and process optimi…
🔥3👨💻1💯1🥱1
Showing the 12 most recent of 20 posts we hold for @holder_job_devs. 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.
@holder_job_devs named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Builders x Devs” (@holder_job_devs), 2,458 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/holder_job_devs.
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.