Puneet Patwari

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):

@TTrimoreau Did from GoDaddy but so many ADs and quite slow UI.

Founders where do you usually buy your domains -GoDaddy -Dynadot -Hostinger -OVHCloud -Ionos And why ? 👇 because need a new one

@lunarfq Hello 👋

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.

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

@TTrimoreau Being relentless..

As a founder What is the one thing that separates winners from the rest?

@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.. 😁 😀

once AI will be able to cure cancer, all AI haters will go silent

@bindureddy Can you elaborate on "don't handle auth well"?

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

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.

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 ?

@OpenAIDevs Building my personal website as Notion is expensive and other platforms like gumroad and Topmate take big commission. My website - puneetpatwari.in

What are you building this weekend?

@mscode07 Puneetpatwari.in

Drop your project URL Let’s drive some traffic Curious to know what you all are building 👇🏼

@bymichael Working on my personal website puneetpatwari.in

Sunday check-in. What are you building right now? Websites, SaaS, tools, side projects, drop them below.👇

@samsonA535 Hello 👋

Need 500 followers Say hello We follow you

@suni_code Built my personal website puneetpatwari.in to mentor aspiring engineers in their job switch and provide high quality mock interviews.

Drop your project 👇🏻 let's drive some traffic!

@SumitM_X Sorry for using this as a promotion opportunity 😅. My product on system design fundamentals (check puneetpatwari.in) covers all of these topics systematically. Will be helpful for anyone preparing for interviews at all levels.

As a senior Java backend developer, It will be good if you have an understanding of the below 40 topics👇 1. CAP Theorem 2. Consistency Models 3. Distributed System Architectures 4. Socket Programming (TCP/IP and UDP) 5. HTTP and RESTful APIs 6. Remote Procedure Call (RPC) - gRPC, Thrift, RMI 7. Message Queues (Kafka, RabbitMQ, JMS) 8. Java Concurrency (ExecutorService, Future, ForkJoinPool) 9. Thread Safety and Synchronization 10. Java Memory Model 11. Distributed Databases (Cassandra, MongoDB, HBase) 12. Data Sharding and Partitioning 13. Caching Mechanisms (Redis, Memcached, Ehcache) 14. Zookeeper for Distributed Coordination 15. Consensus Algorithms (Paxos, Raft) 16. Distributed Locks (Zookeeper, Redis) 17. Spring Boot and Spring Cloud for Microservices 18. Service Discovery (Consul, Eureka, Kubernetes) 19. API Gateways (Zuul, NGINX, Spring Cloud Gateway) 20. Inter-service Communication (REST, gRPC, Kafka) 21. Circuit Breakers and Retry Patterns (Hystrix, Resilience4j) 22. Load Balancing (NGINX, Kubernetes, Ribbon) 23. Failover Mechanisms 24. Distributed Transactions (2PC, Saga Pattern) 25. Logging and Distributed Tracing (ELK Stack, Jaeger, Zipkin) 26. Monitoring and Metrics (Prometheus, Grafana, Micrometer) 27. Alerting Systems 28. Authentication and Authorization (OAuth, JWT) 29. Encryption (SSL/TLS) 30. Rate Limiting and Throttling 31. Apache Kafka for Distributed Streaming 32. Apache Zookeeper for Coordination 33. In-memory Data Grids (Hazelcast, Infinispan) 34. Akka for Actor-based Concurrency 35. Event-Driven Architecture: Event sourcing and CQRS (Command Query Responsibility Segregation). 36. Cluster Management: Kubernetes for container orchestration. 37. Cloud-Native Development: Using cloud platforms (AWS, GCP, Azure), and serverless computing (e.g., AWS Lambda). 38. Distributed Data Processing: Frameworks like Apache Spark or Apache Flink for large-scale data processing. 39. GraphQL: Alternative to REST for inter-service communication. 40. JVM Tuning for Distributed Systems: Memory management and performance tuning in distributed environments.

@maheshnani122 Depends on which phase of life I am in. In current situation will go for job at Google. Will help in further identity branding, can be leveraged later.

Which one would you pick? - Job at Google - 100 paying users for your SaaS

1. Built my own website - puneetpatwari.in 2. Created a product for system design fundamentals with 90+ questions 3. Ranked 8th in Topmate 2025 education category, even though I started in October 2025. 4. Delivered high visibility project on time. 5. Crossed 50K followers on LinkedIn.

What did you achieve in the first 3 months of 2026? Everything counts, big or small.

@sickdotdev Social Media.

Which industry has most liars?

@abhitwt Haha.

@system_monarch No way 😭

i am a Vibe Coder, scare me with one word

@KaiXCreator By working for the AI 🦾

If AI takes everything How will people make money?