Telegram RegisterThe public register of Telegram
Telegram profile photo for Web3 jobs

Channel

Web3 jobs

@jobsweb3

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

1,079subscribers

+345 since we began measuring on 4 October 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001547756594
TypeChannel
Username@jobsweb3
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live24 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/jobsweb3

Topic

Job listings — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 21 October 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.

Growth

7341,079906.54 October 2026 — 734 subscribers4 October 2026 — 734 subscribers8 October 2026 — 760 subscribers14 October 2026 — 823 subscribers21 October 2026 — 1,064 subscribers24 October 2026 — 1,079 subscribers4 October 202624 October 2026
6 measurements spanning 19 days, net +345. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 682–1,131 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 02:291,079+15
21 Oct 2026, 12:591,064+241
14 Oct 2026, 22:36823+63
8 Oct 2026, 11:17760+26
4 Oct 2026, 18:22734no change
4 Oct 2026, 17:47734first reading

Engagement

20 posts held, back to 26 September 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.

ERR · 30 days
3.16%
avg views ÷ 1,079 subscribers
Avg views / post
34.0
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 October 2026
Posts held20 (26 September 2026 – 4 October 2026)
Views total681
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Oct 2026, 18:22 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.

Recent posts

4 Oct 2026, 11:32 UTC14 viewsread 4 October 2026

• Rain is hiring Account Manager • Stripe is hiring Strategy and Operations Analyst • Superstate is hiring Staff Full-Stack Engineer • Apple is hiring Apple Pay Financial Product Strategy Lead • Spruce is hiring Sr. GTM Marketing

4 Oct 2026, 03:52 UTC46 viewsread 4 October 2026

• Ramp is hiring Software Engineer • Coinme is hiring Live Phone Support Contractor • CertiK is hiring Strategic Account Executive • Zero Hash is hiring Director of Strategic Finance • CoinDCX is hiring Associate Director

3 Oct 2026, 19:32 UTC45 viewsread 4 October 2026

• Rain is hiring Software Engineer • WhiteBIT is hiring Middle Financial BI Analyst • Tether is hiring Engagement Manager • Robinhood is hiring Brokerage Communications Specialist • Binance is hiring Binance Accelerator Program

3 Oct 2026, 11:32 UTC43 viewsread 4 October 2026

• Bybit is hiring Product Design Lead • Stripe is hiring Operations Associate • Bitdeer is hiring Sr GPU Cloud K8S Expert • Jane Street is hiring HR Partner • Tangem is hiring Senior Devsecops Specialist

3 Oct 2026, 03:54 UTC34 viewsread 4 October 2026

• Stripe is hiring Security GRC Analyst/Program Manager • Tangem is hiring Senior Software Engineer Payment Solutions • Jane Street is hiring IT Operations Engineer • Turnkey is hiring Product Manager • Gate.io is hiring 核心开发(Trading Engine Core Dev)

2 Oct 2026, 19:32 UTC29 viewsread 4 October 2026

• Bybit is hiring Senior Regulatory Compliance Manager • River Financial is hiring Client Operations Associate • Crossmint is hiring Engineering Manager • BitGo is hiring Backend Engineer E2 • Toku is hiring Senior Software Engineer

2 Oct 2026, 11:32 UTC26 viewsread 4 October 2026

• Solflare is hiring Senior Data Engineer • Hyperliquid Labs is hiring Senior Frontend Engineer • DRW is hiring Data Analyst • Coinbase is hiring CRM and Lifecycle Manager II • Notabene is hiring Senior Customer Success Manager

2 Oct 2026, 04:06 UTC21 viewsread 4 October 2026

• Stripe is hiring Infrastructure Engineer • Arbitrum is hiring Head of Foundation • Cournot is hiring Business Development Manager • Circle is hiring Principal Product Manager • Coinbase is hiring Software Engineer

1 Oct 2026, 19:43 UTC17 viewsread 4 October 2026

• Jane Street is hiring IT Operations Engineer • Bitdeer is hiring Senior AI Scheduling & Orchestration Engineer • Parallel is hiring Cloud Partnerships • MoonPay is hiring Product Security Manager • Chainalysis is hiring Senior Software Engineer

1 Oct 2026, 11:32 UTC17 viewsread 4 October 2026

• Vana is hiring Fraud Data Science • Bybit is hiring Product Manager Expert • Cantina is hiring Machine Learning Engineer • Prime Intellect is hiring Research Engineer • Keyrock is hiring Head of Marketing

1 Oct 2026, 03:59 UTC15 viewsread 4 October 2026

• Binance is hiring Binance Accelerator Program- Monitorship • Tangem is hiring International Logistics Specialist B2c • Ripple is hiring Treasury Manager • Rain is hiring Financial Crimes Risk Senior Data Analyst/Data Scientist • Stripe is hiring Software Engineer

30 Sept 2026, 19:33 UTC16 viewsread 4 October 2026

• Tether is hiring Expansion Manager • Mesh is hiring Senior Product Manager • Wintermute is hiring Product Manager • Jane Street is hiring Linux Engineer • Block is hiring Senior Analytics Engineer

Showing the 12 most recent of 20 posts we hold for @jobsweb3. 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.

Mentions

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.

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 24 October 2026 — this entry's latest reading, not the date you are reading this.

“Web3 jobs” (@jobsweb3), 1,079 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/jobsweb3.

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.