𝗧𝗵𝗲𝘀𝗲 𝟱 𝗗𝗮𝘁𝗮 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗹𝗼𝗼𝗸 𝘀𝗶𝗺𝗽𝗹𝗲. But the follow-up questions are where most candidates get stuck. Here are 5 tricky ones I'd prepare before your next interview: https://www.linkedin.com/posts/akashsinnghh_%F0%9D%97%A7%F0%9D%97%B5%F0%9D%97%B2%F0%9D%98%80%F0%9D%97%B2-%F0%9D%9F%B1-%F0%9D%97%97%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%AE-%F0%9D%97%98%F0%9D%97%BB%F0%9D%97%B4%F0%9D%97%B6%F0%9D%97%BB%F0%9…

Channel
GharKaCoder_
@akashwithtechies
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
6,699subscribers
-32 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002493162005 |
|---|---|
| Type | Channel |
| Username | @akashwithtechies |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/akashwithtechies |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 23:24 | 6,699 | -8 |
| 19 Aug 2026, 22:43 | 6,707 | -11 |
| 16 Aug 2026, 21:58 | 6,718 | -2 |
| 13 Aug 2026, 05:56 | 6,720 | +2 |
| 10 Aug 2026, 07:22 | 6,718 | -13 |
| 7 Aug 2026, 17:01 | 6,731 | no change |
| 7 Aug 2026, 16:56 | 6,731 | first reading |
Engagement
35 posts held, back to 10 May 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 10 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.47%
- avg views ÷ 6,699 subscribers
- Avg views / post
- 567
- 23 posts measured
- Reaction rate
- 0.162%
- reactions ÷ views · ER floor
- Posts in window
- 23
- of 35 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. It is computed over the 5 of 23 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 35 (10 May 2026 – 20 August 2026) |
| Views total | 13,051 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 05:17 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.
Reaction mix
14 reactions across 8 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 100.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 9 of the 35 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 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 10 May 2026 to 20 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.
Recent posts
50 company career pages you should keep checking for Data Engineering opportunities: https://www.linkedin.com/posts/akashsinnghh_50-company-career-pages-you-should-keep-checking-share-7495688808944812033--aGc Give it a LIKE for reach👍🏻
My friend: Bro, I'm afraid of PySpark, it's too hard. Me: Don't worry, PySpark is only this much 👇 https://www.linkedin.com/posts/akashsinnghh_my-friend-bro-im-afraid-of-pyspark-its-share-7495311434105655296-FpCP Give it a LIKE for reach👍🏻
𝗜 𝘄𝗶𝘀𝗵 𝗜 𝗸𝗻𝗲𝘄 𝘁𝗵𝗲𝘀𝗲 𝗗𝗮𝘁𝗮 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝘁𝗲𝗮𝗰𝗵𝗲𝗿𝘀 𝘄𝗵𝗲𝗻 𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗱. Learning Data Engineering becomes much easier when you learn from the right people. Here are 14 creators I'd recommend adding to your learning list: https://www.linkedin.com/posts/akashsinnghh_%F0%9D%97%9C-%F0%9D%98%84%F0%9D%97%B6%F0%9D%98%80%F0%9D%97%B5-%F0%9D%97%9C-%F0%9D%97%B8%F0%9D%97%BB%F0%9D%97%B2%F0%9D%98%84-%F0%9D%98%81%F0%9D%97%B5%F0%9D%97%B2%F…
❤1
Want to learn Data Engineering without spending a penny? Here are some useful free resources to get started: https://www.linkedin.com/posts/akashsinnghh_want-to-learn-data-engineering-without-spending-share-7494595104905625600-AR8w Give it a LIKE for reach👍🏻
Azure Data Engineering looks complicated. Until you break it into the right concepts 👇 https://www.linkedin.com/posts/akashsinnghh_azure-data-engineering-looks-complicated-share-7493831615748571136-GghS Do read❤️
𝗜𝗳 𝗜 𝗵𝗮𝗱 𝟵𝟬 𝗱𝗮𝘆𝘀 𝘁𝗼 𝗽𝗿𝗲𝗽𝗮𝗿𝗲 𝗳𝗼𝗿 𝗮 𝗗𝗮𝘁𝗮 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗷𝗼𝗯, 𝗵𝗲𝗿𝗲'𝘀 𝗵𝗼𝘄 𝗜'𝗱 𝘀𝗽𝗲𝗻𝗱 𝗺𝘆 𝗱𝗮𝘆𝘀. https://www.linkedin.com/posts/akashsinnghh_%F0%9D%97%9C%F0%9D%97%B3-%F0%9D%97%9C-%F0%9D%97%B5%F0%9D%97%AE%F0%9D%97%B1-%F0%9D%9F%B5%F0%9D%9F%AC-%F0%9D%97%B1%F0%9D%97%AE%F0%9D%98%86%F0%9D%98%80-%F0%9D%98%81%F0%9D%97%BC-%F0%9D%97%BD%F0%9D%97%BF%F0%9D%97%B2%F0%9D%97%BD%F0%9D%97%AE%F0%9D%97%BF%F0%9D%97%B2-share-7493828039823433728-dpYo D
You skip SQL → You lose the SQL round. You skip PySpark → You lose the Spark round. You skip Cloud → You struggle with real projects. One weak skill can cost you the offer. Here's what I'd focus on: https://www.linkedin.com/posts/akashsinnghh_you-skip-sql-you-lose-the-sql-round-you-share-7493496338383437824-lO_f Give it a LIKE for reach👍🏻
❤1
I felt PySpark hard until I solved these 14 questions. https://www.linkedin.com/posts/akashsinnghh_i-felt-pyspark-hard-until-i-solved-these-share-7493134450327711745-B8p1 Give it a LIKE for reach👍🏻
𝗗𝗮𝘁𝗮 𝗪𝗮𝗿𝗲𝗵𝗼𝘂𝘀𝗶𝗻𝗴 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 ? Before you memorize definitions, make sure you can answer these 20 practical questions. https://www.linkedin.com/posts/akashsinnghh_%F0%9D%97%97%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%AE-%F0%9D%97%AA%F0%9D%97%AE%F0%9D%97%BF%F0%9D%97%B2%F0%9D%97%B5%F0%9D%97%BC%F0%9D%98%82%F0%9D%98%80%F0%9D%97%B6%F0%9D%97%BB%F0%9D%97%B4-%F0%9D%97%B6%F0%9D%97%BB%F0%9D%98%81%F0%9D%97%B2%F0%9D%97%BF%F0%9D%98%83%F…
My Friend: DSA is tough. Me: Not for me. I follow the 3-7-15 Rule. But let me be honest — It wasn’t always this way. I used to forget what I solved just a week ago. The problem wasn’t practice. It was retention. That’s when I created the 3-7-15 Rule 👇 https://www.linkedin.com/posts/akashsinnghh_my-friend-dsa-is-tough-me-not-for-me-share-7492831115380932609-y9rb Give it a LIKE for reach👍🏻
Forget you're a Data Engineer. If you can't answer these 10 SQL questions, there's probably a gap in your fundamentals. These are situations you'll actually face while working with data. https://www.linkedin.com/posts/akashsinnghh_forget-youre-a-data-engineer-if-you-cant-share-7492489272634155010-tyec Do read❤️
Showing the 12 most recent of 35 posts we hold for @akashwithtechies. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“GharKaCoder_” (@akashwithtechies), 6,699 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/akashwithtechies.
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.