How many years have you been programming professionally?
- Still learning / studying34%
- 0-1 years26%
- 2-4 years21%
- 5-10 years10%
- 10 years +8%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Channel
@prograjobs
On this record: Growth · Engagement · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
357subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001360984905 |
|---|---|
| Type | Channel |
| Username | @prograjobs |
| Created | Between 1 April 2018 and 15 April 2021— 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 | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/prograjobs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 09:24 | 357 | +1 |
| 7 Aug 2026, 00:16 | 356 | no change |
| 7 Aug 2026, 00:00 | 356 | first reading |
20 posts held, back to 15 April 2021 — 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 31 October 2021. An engagement rate over an empty window would be a number about nothing.
How many years have you been programming professionally?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Most common mistakes remote developer teams make 📵 : 1. Too many meetings: Try to keep meetings to a minimum. They are tiring and take away focus from what developers do best, write code. Instead, formulate your thoughts in writing and reserve meetings for the most important matters only. 2. Not having regular meetings: In contrast to the first point, you need to have regular meetings. Everyone needs a time during …
How many linkedin connections do you have?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Networking as a remote developer == important 👩💻 👨💻 When being 100% remote, it is crucial that you keep expanding your network online. Unfortunately, there are no shortcuts. Leaving a like or a reaction on a post and hoping the person will notice you is often not enough. Instead, try to genuinely reach out to the person with a personal comment/suggestion that really brings value to them. This could be as simple …
LEARNING +========+ As a developer, it's important that you keep learning, even if you are working full time. Here are some of our favourite resources 📚 : 1. Books / audiobooks: Go deep in the technologies you are using / currently learning. Another option is to read non-technical books that help you in your career. For example: "The Obstacle is the Way" might give you the right mentality for solving problems and *…
We will share resources, open positions and offer personal guidance
This channel is going to become the number one resource for getting a job as an international developer
Channel name was changed to «Programming jobs»
Channel name was changed to «Programming jobs. Super useful tips about switching jobs as a programmer»
Great News 🤩🤩🤩 +=====≈===+ We are currently looking for talented (fullstack, frontend, backend) developers to join our partner companies. We will guarantee full time, 100% remote & higher salary than what you currently earn If you are interested, please contact @BinaryByter or @Calle978 asap, demand is crazy right now 😅
How are jobs going to look like in the future?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Which language should a programmer learn first?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 20 posts we hold for @prograjobs. 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.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
How many years have you been programming professionally?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
How many linkedin connections do you have?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
How are jobs going to look like in the future?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Which language should a programmer learn first?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 15 April 2021 to 31 October 2021. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@prograjobs named 5 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Programming jobs” (@prograjobs), 357 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/prograjobs.
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.