Channel
@coding_interview_preparation
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
5,906subscribers
+11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001308712623 |
|---|---|
| Type | Channel |
| Username | @coding_interview_preparation |
| Description | Coding interview preparation for software engineers Interview questions, DSA, clean solutions. Join 👉 https://rebrand.ly/bigdatachannels Buy ads: https://telega.io/c/coding_interview_preparation DMCA: @disclosure_bds Contact: @mldatascientist |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/coding_interview_preparation |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:31 | 5,906 | +12 |
| 7 Aug 2026, 06:45 | 5,894 | -1 |
| 7 Aug 2026, 04:15 | 5,895 | no change |
| 7 Aug 2026, 04:07 | 5,895 | first reading |
30 posts held, back to 25 July 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 9 pagesof 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. It is computed over the 6 of 30 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 30 (25 July 2026 – 11 August 2026) |
| Views total | 6,398 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:44 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 75.0% | |
| 👍 | 2 | 25.0% |
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 6 of the 30 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 30 most recent posts we hold, published 25 July 2026 to 11 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.
⚠️ COMMON INTERVIEW MISTAKE #4 - Bad-Mouthing a Previous Employer This comes up constantly in "why are you leaving your current role" - and it's one of the fastest ways to quietly lose an interviewer's trust, even if every word you say is true. Here's why: the interviewer isn't just evaluating your former company. They're predicting how you'll talk about THEIR company someday, if things go wrong. ❌ "My manager was…
💰 SALARY NEGOTIATION #4 - Negotiating Equity, Not Just Salary Especially at startups, equity can be worth more than the base salary difference - but most candidates don't know what questions to ask. ✅ Questions to ask before accepting any equity offer: 1. "How many total shares are outstanding, fully diluted?" (Your number of shares means nothing without this - 10,000 shares out of 10 million is very different fro…
🧠 EDUCATIONAL CS #4 - Trees, Graphs, and the Difference That Matters A tree is just a graph with two extra rules: no cycles, and exactly one path between any two nodes. Tree: Graph (with cycle): 1 1 --- 2 / \ | | 2 3 4 --- 3 Why does this distinction matter in interviews? 🔹 In a tree, you never need to track visited nodes during…
🏗️ SYSTEM DESIGN MONDAY #5 - Let's Design TinyURL Time for our first full end-to-end design. Requirements: ✅ Given a long URL, generate a short one ✅ Given a short URL, redirect to the original ✅ High read traffic (redirects happen constantly), lower write traffic (new URLs created less often) Step 1 - the core challenge: how do we generate a short, unique code for each URL? Option A: Hash the URL (like MD5) and …
🔍 GUESS THE OUTPUT #5 - full breakdown python print(bool("False")) print(bool("")) print(bool([False])) print(bool(0.0)) Answers: True False True False Breakdown: 1️⃣ "False" is a non-empty string - any non-empty string is truthy, REGARDLESS of its content. The string literally saying "False" doesn't matter. 2️⃣ "" is an empty string - falsy. 3️⃣ [False] is a list containing one element - and non-empty lists ar…
What does bool("False") return in Python?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🔍 GUESS THE OUTPUT #5 Language: Python python print(bool("False")) print(bool("")) print(bool([False])) print(bool(0.0)) Lock in your answer, then vote on the quiz below 👇
📊 SQL SATURDAY #5 - Window Functions (The Interview Differentiator) If GROUP BY collapses rows, window functions let you calculate aggregates WITHOUT collapsing them - you keep every row, plus a calculated value alongside it. This is one of the clearest signals of SQL seniority in interviews. sales +----+------------+--------+ | id | department | amount | +----+------------+--------+ | 1 | Eng | 100 | |…
📄 RESUME ROAST #4 > "2020-2023: Software Engineer > 2023-2024: Senior Software Engineer > 2024-Present: Software Engineer II" Spot the issue before I explain 👇 . . . The roast: This looks like a demotion, and recruiters WILL notice and wonder about it - even if "Software Engineer II" is actually a level ABOVE "Senior Software Engineer" at your specific company (title inflation and naming varies wildly between com…
🎯 CODING CHALLENGE #7 - Kth Largest Element in an Array Difficulty: Medium | Asked at: Facebook, Amazon, Google Input: nums = [3,2,1,5,6,4], k = 2 Output: 5 💡 Hint: Sorting works but is O(n log n). Can you do better with a heap that only ever holds k elements? Solution (min-heap approach): python import heapq def find_kth_largest(nums, k): heap = nums[:k] heapq.heapify(heap) for num in nums[k:]: …
🕵️ RECRUITER SECRETS #4 - What Actually Happens After Your Interview Ever wondered what happens the moment you leave that Zoom call? Here's the real process at most mid-to-large companies: 1️⃣ Each interviewer independently writes feedback and a rating (usually a scale like "Strong Hire / Hire / No Hire / Strong No Hire") before discussing with anyone else - this is intentional, to avoid groupthink. 2️⃣ These are …
❤2
🐛 SPOT THE BUG #4 Language: JavaScript (React) javascript function UserProfile({ userId }) { const [user, setUser] = useState(null); useEffect(() => { fetchUser(userId).then(data => setUser(data)); }); return <div>{user?.name}</div>; } What's the bug? 👇 . . . The bug: Missing dependency array in useEffect. Without [userId] (or even []), this effect runs after EVERY render - and since setUser trigge…
Showing the 12 most recent of 30 posts we hold for @coding_interview_preparation. 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.
What does bool("False") return in Python?
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 30 most recent posts we hold, published 25 July 2026 to 11 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.
Citation-graph rank — 980,416 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Coding Interview Preparation” (@coding_interview_preparation), 5,906 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/coding_interview_preparation.
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.