Puneet Patwari

125 posts

Puneet Patwari banner
Puneet Patwari

Puneet Patwari

@system_monarch

Principal @Atlassian | Helping 100s of engineers reach Staff/Principal | 1:1 Mentorship & Mock Interviews | 90+ System design fundamentals - https://t.co/Ots2nRhO5f

Hyderabad انضم Aralık 2025
29 يتبع594 المتابعون
تغريدة مثبتة
Puneet Patwari
Puneet Patwari@system_monarch·
I interviewed at Google, Uber, Walmart, Amazon and several top startups (a total of 60+ interviews) during my job search from March to June 2025 before joining Atlassian as a Principal Engineer. Here’s what each experience taught me. If you’re prepping for a switch, I hope this gives you clarity on what to expect (and how to survive the roller coaster):
Puneet Patwari tweet media
English
2
2
8
1.9K
SumitM
SumitM@SumitM_X·
There are 4 types of software engineers: - Those who start with Service based MNCs like TCS, TechM, CTS, Accenture, and Wipro. - Those who start with Product based MNCs. - Those who start with captives - Those who start with start-up Which one are you ?
English
17
1
31
3.1K
Puneet Patwari
Puneet Patwari@system_monarch·
@knowRowan World was about to end in COVID but out came AI revolution out of nowhere. So we should have hope 😅
English
0
0
0
3
Rowan
Rowan@knowRowan·
Hot take: Ai will lower the IQ of the human race
English
314
35
498
17.6K
Dumisani Mananga
Dumisani Mananga@DMSCoding11·
Which one would you choose: 1. Job at Google 2. Job at Meta 3. Job at Apple
Dumisani Mananga tweet media
English
19
0
15
499
0xMarioNawfal
0xMarioNawfal@RoundtableSpace·
What are you building today?
English
442
4
287
64K
Yash
Yash@yashhq_22·
Posting 3x a day on X won't grow your account. Replying 100x a day will. Nobody wants to hear it though.
English
177
1
199
5.8K
Puneet Patwari
Puneet Patwari@system_monarch·
@TTrimoreau Improve onboarding & talking to churned users will reveal surprising stuff about the gaps.
English
1
0
1
4
Thomas Trimoreau
Thomas Trimoreau@TTrimoreau·
You just launched your SaaS. Users sign up… but no one comes back. You can only choose one move: -Improve onboarding -Add features -Send emails -Talk to churned users What are you doing? 👇
English
46
3
46
2.1K
Dharmvir
Dharmvir@dharmvir_·
Which is the Best platform to actually learn and build?
Dharmvir tweet mediaDharmvir tweet mediaDharmvir tweet mediaDharmvir tweet media
English
36
0
42
1.2K
Sick
Sick@sickdotdev·
Name a skill that actually makes you money
English
40
0
19
1.6K
Thomas Trimoreau
Thomas Trimoreau@TTrimoreau·
Founders where do you usually buy your domains -GoDaddy -Dynadot -Hostinger -OVHCloud -Ionos And why ? 👇 because need a new one
English
69
4
51
2.6K
luna
luna@lunarfq·
A lot of people are struggling to get 500 verified followers for monetization while I have about 6.4k verified mutuals out of 31.5k Do yourself a favour and say Hello, let them follow NOW.
luna tweet media
English
2.3K
162
1.5K
73.7K
Puneet Patwari
Puneet Patwari@system_monarch·
Backpressure stops your service from drowning. But how do you prevent clients from flooding you in the first place? That’s where "distributed rate limiting" comes in and most candidates treat it like a simple local counter. Here’s the Principal-level way I think about it: 1. Choose the right algorithm → Token Bucket (flexible bursts) vs Leaky Bucket (smooth flow) vs Fixed Window (simple but bursty) 2. Make it distributed → Never use in-memory counters alone. Use Redis (or similar) as a shared counter with Lua scripts for atomicity. 3. Handle hot spots & consistency → Shard by userID/clientID. Accept eventual consistency for most cases, but strong consistency for critical paths (e.g., login abuse). 4. Layer it properly → Edge (CDN/API Gateway) for coarse limits + Service layer for fine-grained per-tenant or per-feature limits. 5. Add observability & graceful handling → Track rejection rate, latency impact, and allowed vs throttled requests. Return 429 with Retry-After header + exponential backoff guidance. At Atlassian we combine rate limiting + backpressure + circuit breakers to keep Jira/Confluence stable even during massive spikes. The full deep dive on rate limiting algorithms, sharding trade-offs, and failure modes is inside my System Design Fundamentals Guide. → Free sample + 90+ fundamentals here: puneetpatwari.in What’s the trickiest part of rate limiting you’ve faced in production or interviews? Reply below 👇 #SystemDesign #DistributedSystems #StaffEngineer #RateLimiting
English
0
0
1
31
Thomas Trimoreau
Thomas Trimoreau@TTrimoreau·
As a founder What is the one thing that separates winners from the rest?
English
93
4
86
3.9K
Puneet Patwari
Puneet Patwari@system_monarch·
@Star_Knight12 In a dark sci-fi movie the story plays like this: - AI controls cancer cure process - AI injects cancer to it's haters - Force them to convert or die Happy Ending.. 😁 😀
English
1
0
0
81
Prasenjit
Prasenjit@Star_Knight12·
once AI will be able to cure cancer, all AI haters will go silent
English
175
17
286
13.3K
Bindu Reddy
Bindu Reddy@bindureddy·
RIP MCP! MCP is dying and we are back to using OAuth and APIs MCP servers are unreliable, very limited and don’t handle auth well Overall LLMs still struggle with connectors and operations on 3rd party systems
English
113
29
465
52K
Puneet Patwari
Puneet Patwari@system_monarch·
Spot on example! This Report class violates SRP by handling generation, persistence, and emailing. Suggestion for refactoring to create separate classes for these functions and have a orchestrator service like "ReportService" call them as required. Makes it readable, testable & maintainable.
English
0
0
2
5.4K
SumitM
SumitM@SumitM_X·
You see this class in the PR : class Report { void generate() {} void saveToDb() {} void sendEmail() {} } What's your suggestion to the Junior who wrote it ?
English
26
7
123
47.3K
Puneet Patwari
Puneet Patwari@system_monarch·
@OpenAIDevs Building my personal website as Notion is expensive and other platforms like gumroad and Topmate take big commission. My website - puneetpatwari.in
English
0
0
0
19
OpenAI Developers
OpenAI Developers@OpenAIDevs·
What are you building this weekend?
English
899
32
1.1K
118K