Channel
@codeforinterview
On this record: Growth · Engagement · Reactions · Posts · Polls · Telegram's recommendations · Cite this entry
2,620subscribers
-4 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001249095448 |
|---|---|
| Type | Channel |
| Username | @codeforinterview |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/codeforinterview |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 11:35 | 2,620 | -4 |
| 30 Aug 2026, 09:13 | 2,624 | no change |
| 30 Aug 2026, 06:15 | 2,624 | first reading |
20 posts held, back to 9 June 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 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 20 (9 June 2024 – 22 August 2026) |
| Views total | 162 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 06:15 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.
19 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 94.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18 | 94.7% | |
| ❤ | 1 | 5.26% |
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 8 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 19 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 9 June 2024 to 22 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.
🔥 The DSA journey starts NOW! I’ve started a brand-new Data Structures & Algorithms series! 🚀 And we’re starting with the most important foundation — BIG O NOTATION. If you’ve ever wondered: ❓ Why is one solution better than another? ❓ How do we measure code efficiency? ❓ What does O(n), O(log n) or O(n²) actually mean? This first video will make it simple. 💯 🎬 DSA Series — Episode 1: Big O Notation 👉 Watch her…
I have completed my Node.js series where I have covered all the essential Node.js topics, including: * Node.js Fundamentals * Modules * File System (FS) * HTTP Module * Event Loop * Streams & Buffers * Express.js * Routing * Middleware * REST APIs * MongoDB & Mongoose * Authentication & JWT * File Uploads * Error Handling * Environment Variables * MVC Architecture * Deployment * And much more. Join me and learn ste…
👍3
Back with the Node.js series 💻 Join me and learn step by step https://www.youtube.com/playlist?list=PL_6klLfS1WqHJ9c4KBJNw3qKV0zYilwIk
https://youtu.be/0LvqcrTzxVA?si=AN3U7Dy9dHNI698G
Would you like me to create videos covering all the JavaScript interview questions?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍8
Which do you prefer: Promises or async/await?
Why do we need middleware in Node.js when we can write the same code in controller functions?
Which is more optimized for finding a value in JavaScript: using an object or a map?
👍1
What is memoization and how can you memoize a function in JavaScript
What are generators in JavaScript
What is the output? console.log(test3); console.log(test3()); var test3 = function(){return 3;}
What is the output? (function(){ var a = b = 1; })(); console.log('b', b); console.log('a', a);
Showing the 12 most recent of 20 posts we hold for @codeforinterview. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Would you like me to create videos covering all the JavaScript interview questions?
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 9 June 2024 to 22 August 2026. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“Code for Interview” (@codeforinterview), 2,620 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/codeforinterview.
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.