Channel
@elixir_jobs
On this record: Growth · Engagement · Posts · Cite this entry
2,769subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001353953380 |
|---|---|
| Type | Channel |
| Username | @elixir_jobs |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/elixir_jobs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 22:07 | 2,769 | +3 |
| 24 Aug 2026, 15:57 | 2,766 | -2 |
| 20 Aug 2026, 18:44 | 2,768 | -3 |
| 18 Aug 2026, 02:33 | 2,771 | -4 |
| 15 Aug 2026, 02:08 | 2,775 | -1 |
| 11 Aug 2026, 14:51 | 2,776 | +1 |
| 8 Aug 2026, 13:17 | 2,775 | no change |
| 7 Aug 2026, 21:02 | 2,775 | first reading |
20 posts held, back to 23 February 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.
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 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Full Stack Elixir Developer (Phoenix/LiveView) Patient Reach 360 (Remote (US Preferred, Open to International)) Full time - Remote https://elixirjobs.net/offers/patient-reach-360-full-stack-elixir-developer-phoenix-liveview-33c8825e
Software Engineer II (Backend) Comoto Family of Brands (Philadelphia, PA) Full time - Remote https://elixirjobs.net/offers/comoto-family-of-brands-software-engineer-ii-backend-909af6a7
Senior Software Engineer at US fintech Canary Data (California) Full time - Remote https://elixirjobs.net/offers/canary-data-senior-software-engineer-at-us-fintech-ce319f56
Senior Full Stack Engineer (Elixir / React) Rabbet (Remote (TX, CO, NC preferred)) Full time - Remote https://elixirjobs.net/offers/rabbet-senior-full-stack-engineer-elixir-react-4476be3e
Software Developer (m/w/d) Elixir Reifenhäuser NEXT (Köln (Cologne)) Full time - On-site / Remote https://elixirjobs.net/offers/reifenhauser-next-software-developer-m-w-d-elixir-2dffad2b
Elixir Senior Software Engineer - BBC - UK BBC (London/Glasgow/Salford/Cardiff/Newcastle - UK) Full time - On-site / Remote https://elixirjobs.net/offers/bbc-elixir-senior-software-engineer-bbc-uk-e2b9ff34
Software Engineer, Elixir (Junior/Middle) Telnyx (Ireland, Netherlands) Full time - On-site / Remote https://elixirjobs.net/offers/telnyx-software-engineer-elixir-junior-middle-a88637d3
Senior / Staff Software Engineer Govra (San Francisco) Full time - On-site / Remote https://elixirjobs.net/offers/govra-senior-staff-software-engineer-bf1660b0
Senior Software Engineer Dyad AI (London) Full time - On-site / Remote https://elixirjobs.net/offers/dyad-ai-senior-software-engineer-84d760b4
Senior Elixir Developer Hunit (Prague + remote) Full time - On-site / Remote https://elixirjobs.net/offers/hunit-senior-elixir-developer-e40f86a8
Full-Stack Elixir Engineer GOAL 3 (Netherlands) Full time - On-site / Remote https://elixirjobs.net/offers/goal-3-full-stack-elixir-engineer-5cde74e3
Elixir engineer SuperAPI (Melbourne) Full time - On-site https://elixirjobs.net/offers/superapi-elixir-engineer-d15e7a6c
Showing the 12 most recent of 20 posts we hold for @elixir_jobs. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Elixir Jobs” (@elixir_jobs), 2,769 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/elixir_jobs.
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.