5 rounds. 80LPA. The Google Interview Breakdown Role: SDE-3 (L4), around 4 years of experience https://www.linkedin.com/posts/rajatgajbhiye_5-rounds-80lpa-the-google-interview-breakdown-share-7510918340798730240-EJ7d Must Read โค๏ธ๐๐ฝ
โค2

Channel
@softwaredevelopers007
On this record: Topic ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Posts edited after publishing ยท Citations ยท Telegram's recommendations ยท Cite this entry
21,394subscribers
-428 since we began measuring on 14 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1002154822888 |
|---|---|
| Type | Channel |
| Username | @softwaredevelopers007 |
| Description | A community for software developers, engineers, and tech enthusiasts. ๐โ๐๐ฒ ๐ฝ๐ฟ๐ฒ๐ฝ๐ฎ๐ฟ๐ฒ๐ฑ ๐ถ๐ป-๐ฑ๐ฒ๐ฝ๐๐ต ๐ฆ๐๐๐๐ฒ๐บ ๐๐ฒ๐๐ถ๐ด๐ป ๐๐๐ถ๐ฑ๐ฒ ๐๐ฒ๐ ๐๐ต๐ฒ ๐ด๐๐ถ๐ฑ๐ฒ: https://topmate.io/rajat_gajbhiye/1446625 Stay Hungry, Stay FoolisH! |
| Created | Between 1 June 2024 and 30 September 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/softwaredevelopers007 |
Technology โ 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 54% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 12:16 | 21,394 | -78 |
| 19 Sept 2026, 11:36 | 21,472 | -24 |
| 16 Sept 2026, 23:36 | 21,496 | -22 |
| 14 Sept 2026, 22:59 | 21,518 | -4 |
| 13 Sept 2026, 10:38 | 21,522 | -25 |
| 11 Sept 2026, 12:01 | 21,547 | -34 |
| 8 Sept 2026, 19:59 | 21,581 | -31 |
| 5 Sept 2026, 13:01 | 21,612 | -22 |
| 3 Sept 2026, 14:58 | 21,634 | -9 |
| 2 Sept 2026, 09:05 | 21,643 | -11 |
| 1 Sept 2026, 06:56 | 21,654 | -10 |
| 31 Aug 2026, 06:38 | 21,664 | -12 |
| 30 Aug 2026, 07:26 | 21,676 | -13 |
| 29 Aug 2026, 10:37 | 21,689 | -4 |
| 28 Aug 2026, 11:44 | 21,693 | -9 |
| 27 Aug 2026, 11:15 | 21,702 | -9 |
| 26 Aug 2026, 08:28 | 21,711 | -15 |
| 25 Aug 2026, 04:57 | 21,726 | -11 |
| 24 Aug 2026, 02:01 | 21,737 | -18 |
| 22 Aug 2026, 11:48 | 21,755 | first reading |
96 posts held, back to 5 August 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 42 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.
| Window | Rolling 30 days ยท latest post in window 30 September 2026 |
|---|---|
| Posts held | 96 (5 August 2026 โ 30 September 2026) |
| Views total | 19,074 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 30 Sept 2026, 16:04 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 30 September 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.
178 reactions across 91 posts, in 3 distinct kinds. The most used accounts for 90.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 161 | 90.4% | |
| ๐ | 15 | 8.43% | |
| ๐ฅ | 2 | 1.12% |
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 91 of the 96 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 178 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 96 most recent posts we hold, published 5 August 2026 to 30 September 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.
5 rounds. 80LPA. The Google Interview Breakdown Role: SDE-3 (L4), around 4 years of experience https://www.linkedin.com/posts/rajatgajbhiye_5-rounds-80lpa-the-google-interview-breakdown-share-7510918340798730240-EJ7d Must Read โค๏ธ๐๐ฝ
โค2
One year ago, I launched my System Design Interview Preparation Guide. Today, 7200+ engineers have used it, and hundreds have cracked top software roles using it. The response has been insane. This is one of the best review I gotโฆ To celebrate 1 year, Iโm offering 50% off to the community. https://www.linkedin.com/posts/rajatgajbhiye_one-year-ago-i-launched-my-system-design-ugcPost-7510698880788004864-RPT9 โค๏ธ๐๐ฝ
โค1
Navi Interview Experience Compensation: 44 LPA Position: SDE-2, Backend https://www.linkedin.com/posts/rajatgajbhiye_navi-interview-experience-compensation-44-share-7510571177581568000-pIlK Must Read โค๏ธ๐๐ฝ
๐1
I rejected a 32 LPA offer. My parents thought I was being arrogant. My friends thought I was crazy. Even I had a moment of doubt. But I had a reason. https://www.linkedin.com/posts/rajatgajbhiye_i-rejected-a-32-lpa-offer-my-parents-thought-share-7510338713319702529-Cfbt Must Read โค๏ธ๐๐ฝ
๐1
I recently attended interviews for Backend Developer roles at Barclays, Capgemini, City Bank, Infosys, JPMorganChase and Tata Consultancy Services. I wanted to share my experience along with the questions that were asked. https://www.linkedin.com/posts/rajatgajbhiye_i-recently-attended-interviews-for-backend-share-7510211155873705984-IvXR Must Read โค๏ธ๐๐ฝ
โค1
https://www.linkedin.com/posts/rajatgajbhiye_these-22-system-design-patterns-cover-90-share-7509815281427533824-gi_F
โค2
Clear all DSA rounds By mastering these 22 DSA patterns https://www.linkedin.com/posts/rajatgajbhiye_clear-all-dsa-rounds-by-mastering-these-activity-7509621609880563712-L7M2 Must Read โค๏ธ๐
โค2
Put up a new post on how caching quietly takes down databases at scale. The 3 cache killers every backend engineer should know cold, penetration, breakdown, avalanche, and how to actually fix each one. If you are prepping for system design rounds, this is worth a read: https://www.linkedin.com/posts/rajatgajbhiye_walmart-interviewer-tell-me-how-you-stop-share-7509452298125819904-_d-V Stay Hungry, Stay FoolisH!
โค1
Software Engineers โค๏ธ๐ pinned ยซ๐๐ฒ๐ฒ๐ฝ๐ถ๐ป๐ด ๐๐ต๐ถ๐ ๐ถ๐ป ๐บ๐ถ๐ป๐ฑ, ๐ ๐๐ฒ๐ป๐ ๐ฑ๐ฒ๐ฒ๐ฝ ๐ฎ๐ป๐ฑ ๐ฑ๐ผ๐ฐ๐๐บ๐ฒ๐ป๐๐ฒ๐ฑ ๐ฒ๐๐ฒ๐ฟ๐๐๐ต๐ถ๐ป๐ด ๐ถ๐ป๐๐ผ ๐ฎ ๐๐ฎ๐๐ฎ ๐๐ฎ๐ฐ๐ธ๐ฒ๐ป๐ฑ ๐๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐ฒ๐ฟ ๐๐๐ถ๐ฑ๐ฒ. ๐๐ฒ๐ ๐๐ต๐ฒ ๐๐๐ถ๐ฑ๐ฒ ๐ต๐ฒ๐ฟ๐ฒ: https://topmate.io/rajat_gajbhiye/1970579 Use SENIOR30 to get special 30% off for the communityยป
Recently, I appeared for a Java Developer (Core Java + Spring Boot + Microservices) interview - and hereโs what I learned. Before walking in, I made sure I had a strong grip on every layer that matters for backend development. https://www.linkedin.com/posts/rajatgajbhiye_recently-i-appeared-for-a-java-developer-share-7508887116173578241-h0Nf Must Read โค๏ธ๐๐ฝ
โค2
Cleared all three rounds at Kotak for SDE-2, 25 to 30 LPA. Then HR asked one question and the offer became SDE-1. Offer DECLINED. The whole loop is up, round by round, with the Kafka discussion, the LLD they wanted State for, and every question this band gets asked. https://www.linkedin.com/posts/rajatgajbhiye_kotak-mahindra-bank-interview-experience-share-7508734103131922432-2CHI Stay Hungry, Stay FoolisH!
โค1
๐๐ฒ๐ฒ๐ฝ๐ถ๐ป๐ด ๐๐ต๐ถ๐ ๐ถ๐ป ๐บ๐ถ๐ป๐ฑ, ๐ ๐๐ฒ๐ป๐ ๐ฑ๐ฒ๐ฒ๐ฝ ๐ฎ๐ป๐ฑ ๐ฑ๐ผ๐ฐ๐๐บ๐ฒ๐ป๐๐ฒ๐ฑ ๐ฒ๐๐ฒ๐ฟ๐๐๐ต๐ถ๐ป๐ด ๐ถ๐ป๐๐ผ ๐ฎ ๐๐ฎ๐๐ฎ ๐๐ฎ๐ฐ๐ธ๐ฒ๐ป๐ฑ ๐๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐ฒ๐ฟ ๐๐๐ถ๐ฑ๐ฒ. ๐๐ฒ๐ ๐๐ต๐ฒ ๐๐๐ถ๐ฑ๐ฒ ๐ต๐ฒ๐ฟ๐ฒ: https://topmate.io/rajat_gajbhiye/1970579 Use SENIOR30 to get special 30% off for the community
๐1
Showing the 12 most recent of 96 posts we hold for @softwaredevelopers007. 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.
@softwaredevelopers007 edited 1 post after it first published โ the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too โ this register can tell you the wording changed and when, not why. 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 23 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 13 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 26 September 2026 โ this entry's latest reading, not the date you are reading this.
โSoftware Engineers โค๏ธ๐โ (@softwaredevelopers007), 21,394 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/softwaredevelopers007.
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.