Rejected at EY Rejected at KPMG Rejected at Paytm https://www.linkedin.com/posts/shubhamwadekar_rejected-at-ey-rejected-at-kpmg-rejected-activity-7528659196670783489-F3WR do checkout ❤️
👍2
Signed Shubham

Channel
@shubham_wadekar_jobs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
24,292subscribers
-918 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002006104845 |
|---|---|
| Type | Channel |
| Username | @shubham_wadekar_jobs |
| Description | 𝗜 𝗵𝗮𝘃𝗲 𝗽𝗿𝗲𝗽𝗮𝗿𝗲𝗱 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗣𝗿𝗲𝗽𝗮𝗿𝗮𝘁𝗶𝗼𝗻 𝗚𝘂𝗶𝗱𝗲 𝗳𝗼𝗿 𝗗𝗮𝘁𝗮 𝗘𝗻𝗴𝗶𝗻𝗻𝗲𝗿𝘀. 𝗔𝘇𝘂𝗿𝗲: https://topmate.io/shubham_wadekar/1667764 𝗔𝗪𝗦: https://topmate.io/shubham_wadekar/1715556 𝗚𝗖𝗣: https://topmate.io/shubham_wadekar/1739621 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/shubham_wadekar_jobs |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 16:49 | 24,292 | -43 |
| 14 Nov 2026, 08:00 | 24,335 | -37 |
| 11 Nov 2026, 09:18 | 24,372 | -11 |
| 9 Nov 2026, 16:18 | 24,383 | -23 |
| 8 Nov 2026, 06:48 | 24,406 | -19 |
| 6 Nov 2026, 22:51 | 24,425 | -9 |
| 5 Nov 2026, 19:17 | 24,434 | -13 |
| 4 Nov 2026, 21:57 | 24,447 | +2 |
| 3 Nov 2026, 21:38 | 24,445 | -9 |
| 2 Nov 2026, 22:58 | 24,454 | -4 |
| 1 Nov 2026, 23:16 | 24,458 | -6 |
| 31 Oct 2026, 23:06 | 24,464 | -6 |
| 31 Oct 2026, 02:21 | 24,470 | -4 |
| 30 Oct 2026, 00:44 | 24,474 | -7 |
| 28 Oct 2026, 22:08 | 24,481 | -10 |
| 27 Oct 2026, 21:21 | 24,491 | -4 |
| 26 Oct 2026, 22:36 | 24,495 | -10 |
| 26 Oct 2026, 01:50 | 24,505 | -9 |
| 25 Oct 2026, 01:39 | 24,514 | -1 |
| 23 Oct 2026, 23:30 | 24,515 | first reading |
184 posts held, back to 31 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 147 pages 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. It is computed over the 41 of 48 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 184 (31 July 2026 – 18 November 2026) |
| Views total | 54,719 |
| Reactions total | 50 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 05:55 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 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
238 reactions across 166 posts, in 3 distinct kinds. The most used accounts for 73.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 174 | 73.1% | |
| ❤ | 57 | 23.9% | |
| 🔥 | 7 | 2.94% |
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 167 of the 184 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 238 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 184 most recent posts we hold, published 31 July 2026 to 18 November 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.
Telegram’s own ‘edited’ marker: 3 of 48 posts held from the last 30 days (6.25%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Rejected at EY Rejected at KPMG Rejected at Paytm https://www.linkedin.com/posts/shubhamwadekar_rejected-at-ey-rejected-at-kpmg-rejected-activity-7528659196670783489-F3WR do checkout ❤️
👍2
Signed Shubham
PayPal offers ₹30-40 LPA for Data Engineer I and ₹50-60 LPA for Data Engineer II. https://www.linkedin.com/posts/shubhamwadekar_paypal-offers-30-40-lpa-for-data-engineer-activity-7528442999769354240-KIfd do checkout guys❤️
❤1
Signed Shubham
🚀 𝗗𝗔𝗧𝗔 𝗘𝗡𝗚𝗜𝗡𝗘𝗘𝗥𝗦, 𝗜𝗧'𝗦 𝗧𝗜𝗠𝗘 𝗧𝗢 𝗟𝗘𝗩𝗘𝗟 𝗨𝗣! The tech industry is evolving fast. Are your skills keeping up? This is the right time to upgrade your skills, explore new technologies and unlock better career opportunities! 🔥 🎯 𝗝𝗼𝗶𝗻 𝗙𝗥𝗘𝗘 𝗟𝗜𝗩𝗘 𝗠𝗔𝗦𝗧𝗘𝗥𝗖𝗟𝗔𝗦𝗦𝗘𝗦 𝘁𝗼 𝗲𝘅𝗽𝗹𝗼𝗿𝗲: • ⚡ In-demand tools & technologies • 📈 Career growth & salary opportunities • 🛣️ Career roadmap & certification guidance • 💬 Live Q&A with indus…
Signed Shubham
Photo, posted without a caption
Signed Shubham
If i had to crack a Google Data Engineer interview from scratch, I'd ignore 80% of the advice you see online. https://www.linkedin.com/posts/shubhamwadekar_if-i-had-to-crack-a-google-data-engineer-activity-7527714814782140416-ePr8 do checkout guys❤️
❤1
Signed Shubham
clear all Data Engineering rounds, By Solving these 18 questions. https://www.linkedin.com/posts/shubhamwadekar_clear-all-data-engineering-rounds-by-solving-activity-7527216553491218432-XkIw do checkout ❤️
👍1
Signed Shubham
My friend Lost a 60 LPA job offer from PayPal Here is her interview experience How she applied: Through referral for the Data Enginner position https://www.linkedin.com/posts/shubhamwadekar_my-friend-lost-a-60-lpa-job-offer-from-paypal-activity-7526867530674589696-rfcA do read❤️
👍1
Signed Shubham
I got rejected by EY → Lost 27 LPA offer I got rejected by PwC → Lost 28 LPA offer I got rejected by Paytm → Lost 29 LPA offer https://www.linkedin.com/posts/shubhamwadekar_i-got-rejected-by-ey-lost-27-lpa-offer-activity-7526483846939402240-xKlH do checkout ❤️
👍1
Signed Shubham
You avoid SQL → Microsoft rejects you You avoid Python → Google rejects you You avoid Pyspark → Amazon rejects you https://www.linkedin.com/posts/shubhamwadekar_you-avoid-sql-microsoft-rejects-you-you-activity-7526116801806643200-HoIc do repost for others guys❤️👍
👍1
Signed Shubham
Two paths to becoming a highly paid Data Engineer: Path 1: https://www.linkedin.com/posts/shubhamwadekar_two-paths-to-becoming-a-highly-paid-data-activity-7525906082964295680-6hZj guys do checkout 💝
👍1
Signed Shubham
My journey as a Data Engineer: 3.6 LPA at TCS → 33+ LPA today. Here is the step-by-step process I followed: https://www.linkedin.com/posts/shubhamwadekar_my-journey-as-a-data-engineer-36-lpa-at-activity-7525756626159513600-zSd- do save the resources guys❤️
👍1
Signed Shubham
❌ Don’t join Wipro ❌ Don’t join Infosys ❌ Don’t join TCS https://www.linkedin.com/posts/shubhamwadekar_dont-join-wipro-dont-join-infosys-activity-7525549156711546880-Ivvv Do read guys❤️👍
👍1
Signed Shubham
Showing the 12 most recent of 184 posts we hold for @shubham_wadekar_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.
We recorded 2 posts on @shubham_wadekar_jobs as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 7 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Data Engineers❤️” (@shubham_wadekar_jobs), 24,292 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/shubham_wadekar_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.